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

[Q] HELPPPPP please soft brick

Hey peeps iv got a big problem it happened yesterday with my Galaxy note GTn7000. I was on stock ICS LPT and was flashing new kernels through CWM when suddenly my phone just kept freezing on the Samsung screen when I start it up and it has been happening since yesterday. I think it was the speedmod ICS kernel that I flashed that made this happen. I flashed Abys kernel through odin and could get in to CWM. I did factory reset/wipe cache/dalvik/cache and then flashed checkrom which was on my SD card. Installation was fine but then it got stuck on the Galaxy note startup screen. I was searching for answers on the XDA forums and someone suggested that you flash a stock full wipe GB rom. So I tried to flash LC1 open Europe rom and was waiting for an hour the the rom to flash through ODIN which had only a bit left on the bar to flash and it didn’t flash it just froze. I tried 3 times and the same thing happened . I have used the USB jig to erase previous downloads and reset binary count. I flashed ICS LPT rom through odin and it flashed normally but when it starts up it gets stuck on the Samsung screen. Any suggestions? I can get into download mode and CWM so it means Im in a softbrick. Do you think I should download an ICS rom and put it on to my SD card and then try flashing it ? Help would be appreciated thanks.
Here is the video of what happens. Basically i have waited for 4 hours yesterday and it just stays on the samsung screen

Hey, Id recommend you flashing back to GB via ODIN before we continue.
ICS still has a few bugs and that could interfere with getting you back up and running.

Hey thanks i will download a new GB stock rom, i cant post the video link because im a new member dang...

azzledazzle said:
Hey, Id recommend you flashing back to GB via ODIN before we continue.
ICS still has a few bugs and that could interfere with getting you back up and running.
Click to expand...
Click to collapse
Flashed N7000XXLQ2_N7000XXLPT_N7000CPWLP4_HOME.tar GB rom, it restarted and still the same. Freezes on the Galaxy note startup screen

1st can i ask how are u flashing roms?
2nd i assume u are able to go into recovery?
steps to install customs roms
1-go recovery
2-flash abyss4.2
3-go advance -> reboot recovery
4-wipe cache n dalivk
5-flash custom roms
6-reboot
did u do this?

Thai Damen said:
1st can i ask how are u flashing roms?
2nd i assume u are able to go into recovery?
steps to install customs roms
1-go recovery
2-flash abyss4.2
3-go advance -> reboot recovery
4-wipe cache n dalivk
5-flash custom roms
6-reboot
did u do this?
Click to expand...
Click to collapse
Im flashing through ODIN. I did the abys kernel flash before and installed a custom rom but it still kept freezing. Now i am downloading the XLA3 GB rom and hope to flash it through ODIN

CODE_N7000XXLA3_CL880036_REV02_user_low_ship.tar.md5
EFS_N7000XXLA3_CL880036_REV02_user_low_ship.tar.md5
KERNEL_N7000XXLA3_CL880036_REV02_eng_mid_noship.tar.md5
Q1_20110914_16GB.pit
UMS_N7000XXLA3_CL880036_REV02_user_low_ship_16GB.tar.md5
MODEM_N7000XXLA3_REV_05_CL1095424.tar.md5
GT-N7000-MULTI-CSC-OXALA3.tar.md5
im gonna flash the XLA3 GB rom through ODIN. I dont know where all these files go in ODIN. Anyone ?...

IsmailZU said:
CODE_N7000XXLA3_CL880036_REV02_user_low_ship.tar.md5
EFS_N7000XXLA3_CL880036_REV02_user_low_ship.tar.md5
KERNEL_N7000XXLA3_CL880036_REV02_eng_mid_noship.tar.md5
Q1_20110914_16GB.pit
UMS_N7000XXLA3_CL880036_REV02_user_low_ship_16GB.tar.md5
MODEM_N7000XXLA3_REV_05_CL1095424.tar.md5
GT-N7000-MULTI-CSC-OXALA3.tar.md5
im gonna flash the XLA3 GB rom through ODIN. I dont know where all these files go in ODIN. Anyone ?...
Click to expand...
Click to collapse
So you've extracted the original tar file, you don't need to, just point the original tar file to the pda section of pc odin, it will sort out each partition for you.
Sent from my GT-N7000 using xda premium

SpyderTracks said:
So you've extracted the original tar file, you don't need to, just point the original tar file to the pda section of pc odin, it will sort out each partition for you.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
its an .rar file. How do i change it into a tar file ?

Is it a rar. Or a zip? If it's a rar, re download from here http://forum.xda-developers.com/showthread.php?t=1424997 then extract one level with 7zip to get the tar file.
Sent from my GT-N7000 using xda premium

was in similar situation . flashed with ICS stock ROM after entering in to download mode as described here http://forum.xda-developers.com/showthread.php?t=1424997 using odin on laptop method. thanks

[Q][Solved] The system and data partitions are corrupt..should i goto service center?

So i found out about the ICS kernels issue a little bit too late :crying:
and now the /system and /data partitions can't be mounted nor formatted...so it's pretty much safe to say they are corrupt.
My question is: do service centers have the tools to completely restore the lost memory ? or should i proceed with searching for some workarounds via odin?
I am out of my warranty but willing to pay if the service center is caoable of completely fixing the issue WITHOUT replacing the motherboard?
Any help is much appreciated.
---
Now after seven days of this post..i have tried a zillion solutions and the one that actually worked is pit file and instructions by forest 1971 on the 15th comment
But sadly i lost 3 Gigabytes of my memory after this

What do you mean you are out of warranty
If your flash counter is increased,you can reset it
And i dont think it can be fixed without motherboard replacement

@OP
question to you: are you still able to work your way to download mode /recovery mode? you say "workarounds with ODIN" <--- just what exactly do you mean by that?

Should do some partition scan to make sure it is partition damage. Given your wipe using ics and the symptoms it is most likely the case of emmc brick. No way to fix it yet. Only two solutions, repartition workaround or change mobo.
Sent from my phone

I agree, go to the link (just saw it on Xda portal awhile back, congrats to hg42 for his tremendous effort for his contributions and forest as well) --- http://www.xda-developers.com/android/partition-scanner-helps-your-emmc-bricked-devices/

forest1971 said:
Should do some partition scan to make sure it is partition damage. Given your wipe using ics and the symptoms it is most likely the case of emmc brick. No way to fix it yet. Only two solutions, repartition workaround or change mobo.
Click to expand...
Click to collapse
Nope i don't think it's the emmc partition because it can be mounted so i don't think it's damaged. Are you sure the service center can't do more than changing the mobo?
letters_to_cleo said:
@OP
question to you: are you still able to work your way to download mode /recovery mode? you say "workarounds with ODIN" <--- just what exactly do you mean by that?
Click to expand...
Click to collapse
I could get to download mode and recovery mode then i tried to repartition using odin -a pit file-but it froze during the flashing process...so i lost access to recovery mode but not download.
workarounds with Odin means repartitioning my internal memory to have another /data & /system instead of the damaged ones
rajsekhar.300 said:
What do you mean you are out of warranty
If your flash counter is increased,you can reset it
And i dont think it can be fixed without motherboard replacement
Click to expand...
Click to collapse
Nope that's not what i mean -my flash counter is still 0- it's just that i bought my phone from another country and the warranty is only valid in that country bu not here...so i am without warranty right now...and it sucks ALOT

try to see first if you can flash one of the files from the link- http://www.xda-developers.com/android/partition-scanner-helps-your-emmc-bricked-devices/ to scan your partition. See to it if you have or don't have one of those damn brick blocks inside your phone.

Amr Shibiny said:
Nope i don't think it's the emmc partition because it can be mounted so i don't think it's damaged. Are you sure the service center can't do more than changing the mobo?
Click to expand...
Click to collapse
The term emmc brick just refer to brick cause by the buggy kernel which cause damage to some partition such as system or data or usb storage (that is part of the emmc).
if you can get to recovery then try to use the scanner from hg42 to identify area of damage, as suggested by Cleo. Maybe flash a custom kernel could help to get into recovery again.
Also, it seemed you have used a custom pit file could you give more detail which one you have used?

So i took my phone to service center and they told me the only thing they can di is changing the Mother board.
I took my phone home for further debugging and tried that memory scanner by hg42 only to find that i need the recovery mode to perform that scan
My recovery mode was lost due to an incomplete bootloader flashing
i falshed many kernels and flashed the same bootloader again but nothing seems to work
Any suggestions for good bootloaders? remember my phone is an ICS GT-N7000

Amr Shibiny said:
So i took my phone to service center and they told me the only thing they can di is changing the Mother board.
I took my phone home for further debugging and tried that memory scanner by hg42 only to find that i need the recovery mode to perform that scan
My recovery mode was lost due to an incomplete bootloader flashing
i falshed many kernels and flashed the same bootloader again but nothing seems to work
Any suggestions for good bootloaders? remember my phone is an ICS GT-N7000
Click to expand...
Click to collapse
If you really think there is a problem with wrong bootloader, then can try to flash the correct one from Dr.Ketan's toolbox below. There are both gb and ics version. I think using gb bootloader is ok.
http://forum.xda-developers.com/showthread.php?t=1801341
Then download and flash a kernel in .tar format using PC odin.
For ICS: flash hydracore standard kernel from link below:
http://forum.xda-developers.com/showthread.php?t=1749863
For GB: flash 4-pda kernel from this link:
http://www.mediafire.com/?smwswkxwa3u3p4s
after flash kernel try to get into recovery using the three button.
see how it goes.

forest1971 said:
If you really think there is a problem with wrong bootloader, then can try to flash the correct one from Dr.Ketan's toolbox below. There are both gb and ics version. I think using gb bootloader is ok.
http://forum.xda-developers.com/showthread.php?t=1801341
Then download and flash a kernel in .tar format using PC odin.
For ICS: flash hydracore standard kernel from link below:
http://forum.xda-developers.com/showthread.php?t=1749863
For GB: flash 4-pda kernel from this link:
http://www.mediafire.com/?smwswkxwa3u3p4s
after flash kernel try to get into recovery using the three button.
see how it goes.
Click to expand...
Click to collapse
After further reading in similar posts i am starting to think the bootloader isn't the problem....but the problem is i can't think of any other reason. It's definitely not the rom since there is not even a system partition right now and it isn't the kernel because i tried many (speedmod, franco...) and got no response. Any ideas?
Any way, I'll give it a shot using these links..hope it works

forest1971 said:
If you really think there is a problem with wrong bootloader, then can try to flash the correct one from Dr.Ketan's toolbox below. There are both gb and ics version. I think using gb bootloader is ok.
http://forum.xda-developers.com/showthread.php?t=1801341
Then download and flash a kernel in .tar format using PC odin.
For ICS: flash hydracore standard kernel from link below:
http://forum.xda-developers.com/showthread.php?t=1749863
For GB: flash 4-pda kernel from this link:
http://www.mediafire.com/?smwswkxwa3u3p4s
after flash kernel try to get into recovery using the three button.
see how it goes.
Click to expand...
Click to collapse
Well, the problem wasn't the boot loader after all
Tried all that and didn't work. I still can't access recovery mode on my device.
I tried usb debugging but there seems to be something wrong with the "adb shell" command. Whenever i write it it shoes a black screen on cmd..when i try to write something it's written without '#' or '$' in the beginning and when i press Enter the line i wrote is rewrote again and that's it. What does this mean?
Right now i need any help available to get either recovery mode or adb to work
thanks in advance

It seems you have tried to connect adb while the phone is in download mode, so it will not work. Adb requires the phone in recovery mode, which is still the problem so far.
I would try to flash the original pit file from dr.ketan toolbox, together with one of the above kernel again. see how it goes.
Sent from my phone

forest1971 said:
It seems you have tried to connect adb while the phone is in download mode, so it will not work. Adb requires the phone in recovery mode, which is still the problem so far.
I would try to flash the original pit file from dr.ketan toolbox, together with one of the above kernel again. see how it goes.
Sent from my phone
Click to expand...
Click to collapse
Nope..no effect
I tried it once with <repartition> ticked and another without it being ticked
I think you should know too that when i type "adb devices" the result is : "<big number> recovery". I don't know if this means i have recovery or it's just nonsense.

Amr Shibiny said:
Nope..no effect
I tried it once with <repartition> ticked and another without it being ticked
I think you should know too that when i type "adb devices" the result is : "<big number> recovery". I don't know if this means i have recovery or it's just nonsense.
Click to expand...
Click to collapse
in that case try to type in CMD:
Code:
adb reboot recovery
see if it has any effect (to reboot phone in recovery).
---------- Post added at 10:56 AM ---------- Previous post was at 10:45 AM ----------
If it does nothing, then I would now try to flash the custom pit from hg42 in the file attached (unzip it first to get .pit file), together with a suitable stock rom from dr.ketan thread (http://forum.xda-developers.com/showthread.php?t=1424997) and repartition box checked.
This PIT will leave the former system and data partition unused. after flash, try to get into recovery and wipe and try to boot normally. see how it goes.
Note: to make sure to avoid unsafe ICS kernel, should always use gb rom for reviving the phone and only upgrade to ics when it is working.

forest1971 said:
in that case try to type in CMD:
Code:
adb reboot recovery
see if it has any effect (to reboot phone in recovery).
---------- Post added at 10:56 AM ---------- Previous post was at 10:45 AM ----------
If it does nothing, then I would now try to flash the custom pit from hg42 in the file attached (unzip it first to get .pit file), together with a suitable stock rom from dr.ketan thread (http://forum.xda-developers.com/showthread.php?t=1424997) and repartition box checked.
This PIT will leave the former system and data partition unused. after flash, try to get into recovery and wipe and try to boot normally. see how it goes.
Note: to make sure to avoid unsafe ICS kernel, should always use gb rom for reviving the phone and only upgrade to ics when it is working.
Click to expand...
Click to collapse
It Worked!!! It f***ing Worked !!
Now my phone is back to business...but it lost 3 Gigabytes of memory right now
Thanks a billion for your patience forest1971
So is there anything not allowed after this solution? like rerooting, flashing via odin, flashing via cwm or downgrading to Android 2.3?
and btw just to understand more...why did you specifically give me this pit file? this is from hg42's collection, right? there are a lot of files in this collection and one should be chosen based on the result of the memory scanners, right? How did you know that's the one for me?

Amr Shibiny said:
It Worked!!! It f***ing Worked !!
Now my phone is back to business...but it lost 3 Gigabytes of memory right now
Thanks a billion for your patience forest1971
So is there anything not allowed after this solution? like rerooting, flashing via odin, flashing via cwm or downgrading to Android 2.3?
and btw just to understand more...why did you specifically give me this pit file? this is from hg42's collection, right? there are a lot of files in this collection and one should be chosen based on the result of the memory scanners, right? How did you know that's the one for me?
Click to expand...
Click to collapse
Good to know you made it !
You can do all things as before. Hope it will be running well.
I helped cases before, so can pick a suitable pit file !
Sent from my phone

forest1971 said:
Good to know you made it !
You can do all things as before. Hope it will be running well.
I helped cases before, so can pick a suitable pit file !
Sent from my phone
Click to expand...
Click to collapse
I see
Do you know too the best way to downgrade?
Don't want to mess it up again

Amr Shibiny said:
I see
Do you know too the best way to downgrade?
Don't want to mess it up again
Click to expand...
Click to collapse
The best way is using PC odin to flash pre-rooted gb rom from dr.ketan:
http://d-h.st/HJM
Or you can flash other stock gb rom which is suitable for your country from Dr ketan' thread as well (post 2)
http://forum.xda-developers.com/showthread.php?t=1424997
Using gb rom with a custom kernel such as FM or Abyssnote seem to work well, smooth and no problem. Or you can use some custom gb rom such as rocket v22 or other gb custom rom from link below:
http://rootgalaxynote.com/category/galaxy-note-roms/page/4/
cheers.

forest1971 said:
The best way is using PC odin to flash pre-rooted gb rom from dr.ketan:
http://d-h.st/HJM
Click to expand...
Click to collapse
But this is a .img file...i searched for the way of flashing it and i found i should use fastboot. For some reason fastboot isn't working. Is there a way of flashing it via Odin?

[Q] HELP! bircked note

hello everyone
my friend bricked his note and i don't know what to do for him, my friend has no exper experience, he did a restore on a nonsafe kernel
his phone is semi bricked (if not fully bricked), i tried using odin to flash a stock rom (gb then ics) but had no luck and proccess stops at "NAND write start", i tried only to flash a kernel which was abyssnote but also got stuck on "NAND write start" and i tried to use the pit file from this post (http://forum.xda-developers.com/showthread.php?t=1667886) with a stock rom and with re-partition checked on odin and now it is stuck on:
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
please help me as the phone has been stuck on this state (pit file way) for over 80 minutes
waiting for your answer...

i unpluged my phone now and i am trying a custom pit file (N7000_16GB_Q1_20110914--patched--brick-between-281-and-3770-MB--FACTORYFS-moved-by-3328-MiB.pit) after leaving my phone for up to 2 hours and with no progress using N7000_16GB_Q1_20110914-stock.pit
file, hope i can revive my friend phone and please try to point me for any solution i can try.

Check your connection. Usually if bricked the process will start ok but halt at factory.fs. Try with a different usb cable, make sure it's in a mobo usb port not front one.
Pit files should be a last resort. I don't think it's bricked personally. Does it power on at all?
Sent from my GT-N7000 using xda app-developers app

SpyderTracks said:
Check your connection. Usually if bricked the process will start ok but halt at factory.fs. Try with a different usb cable, make sure it's in a mobo usb port not front one.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
how can i use mobie odin if i can't even access phone nor recovery?
hope there is a way

darkelfa2 said:
how can i use mobie odin if i can't even access phone nor recovery?
hope there is a way
Click to expand...
Click to collapse
Yeah, edited afterward.
Sent from my GT-N7000 using xda app-developers app

come on people... there most be someone who knows what i should do, please help

SpyderTracks said:
Check your connection. Usually if bricked the process will start ok but halt at factory.fs. Try with a different usb cable, make sure it's in a mobo usb port not front one.
Pit files should be a last resort. I don't think it's bricked personally. Does it power on at all?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
when odin get stuck on nand write start, the box above the port number with yellow mark says factoryfs, and yes the phone can olny boot to download mode

darkelfa2 said:
when odin get stuck on nand write start, the box above the port number with yellow mark says factoryfs, and yes the phone can olny boot to download mode
Click to expand...
Click to collapse
What is the outcome of flashing the "N7000_16GB_Q1_20110914--patched--brick-between-281-and-3770-MB--FACTORYFS-moved-by-3328-MiB.pit" as you mentioned above?
If you can also get into recovery, then better try to use hg42 partition scanner first, to see if and where the damage is in the emmc.
http://forum.xda-developers.com/showthread.php?t=1823918

forest1971 said:
What is the outcome of flashing the "N7000_16GB_Q1_20110914--patched--brick-between-281-and-3770-MB--FACTORYFS-moved-by-3328-MiB.pit" as you mentioned above?
If you can also get into recovery, then better try to use hg42 partition scanner first, to see if and where the damage is in the emmc.
http://forum.xda-developers.com/showthread.php?t=1823918
Click to expand...
Click to collapse
phone been on odin for about 40 minutes or so (is that normal?) but stuck on set partition and as i mentioned above, i cant access my phone nor recovery but i can access download mode.

darkelfa2 said:
phone been on odin for about 40 minutes or so (is that norma?l) but stuck on set partition and as i mentioned above, i cant access my phone nor recovery but i can access download mode.
Click to expand...
Click to collapse
If that long, then that pit doesn't seem to work.
I would try to flash a custom kernel such as hydracore or some other kernel that are available in .tar format. Then see if it help the phone get into recovery.
If that does not work, then just need to try other pit file from hg42 thread which move factoryfs by bigger number until it work. This is not a good strategy but it seems to be the only way.
---------- Post added at 11:29 PM ---------- Previous post was at 11:19 PM ----------
This is a gb kernel that can be flashed via odin to see if recovery works.
http://www.mediafire.com/?smwswkxwa3u3p4s

forest1971 said:
If that long, then that pit doesn't seem to work.
I would try to flash a custom kernel such as hydracore or some other kernel that are available in .tar format. Then see if it help the phone get into recovery.
If that does not work, then just need to try other pit file from hg42 thread which move factoryfs by bigger number until it work. This is not a good strategy but it seems to be the only way.
---------- Post added at 11:29 PM ---------- Previous post was at 11:19 PM ----------
This is a gb kernel that can be flashed via odin to see if recovery works.
http://www.mediafire.com/?smwswkxwa3u3p4s
Click to expand...
Click to collapse
i got stuck on NAND write start agine, i think its time to try your other strategy, should i go with pit file that has factoryfs moved by the largest number first or the one with the less number?

darkelfa2 said:
i got stuck on NAND write start agine, i think its time to try your other strategy, should i go with pit file that has factoryfs moved by the largest number first or the one with the less number?
Click to expand...
Click to collapse
I would try the first way of flash a kernel since it does not take much time.
Anyway, if want to try second strategy should move up by 500 mb or 1 gb each time.
I saw some people reported problem after flashing a pit with big number them move back to flash a pit with small number so should try to avoid that situattion.
The next pit I would choose it the one move fatoryfs by 4608mib for example.

forest1971 said:
I would try the first way of flash a kernel since it does not take much time.
Anyway, if want to try second strategy should move up by 500 mb or 1 gb each time.
I saw some people reported problem after flashing a pit with big number them move back to flash a pit with small number so should try to avoid that situattion.
The next pit I would choose it the one move fatoryfs by 4608mib for example.
Click to expand...
Click to collapse
thank you for your replies, i will try to try them as you mentioned above and by the way and will wait 15-20 minutes in each operation, i already tried the last version of hydracore but had no success, one last thing, if none of them worked (hope not), is there any other possible way to revive from the brick(other than replacing the motherboard or replacing the phone from samsung)?

bricked or not
same problem here, was on stock ics rooted for quite sometime, today decided to flash alliance rom v2.1, booted to cwm recovery, did a full wipe and after that i just hated myself. phone didnt boot into recovery and odin gets stucked at factoryfs, tried to flash with pit file too but no result same stuck in problem. then i flashed different kernel fm note kernel through odin which was a success, got my recovery back but unfortunately the only rom i have on internal sd was alliance rom which doesnt install, either says emmc error alliance rom or stucks at extracting system. so again flashed abyss kernel and did a full wipe again but odin still does not go beyond factory fs and i am trying to flash ics rom again. any idea what i should do now as i can flash a kernel and go into recovery. help will be appreciated. meanwhile downloading gb rom to check as i read in other posts it works tough not sure.

sahil4u said:
same problem here, was on stock ics rooted for quite sometime, today decided to flash alliance rom v2.1, booted to cwm recovery, did a full wipe and after that i just hated myself. phone didnt boot into recovery and odin gets stucked at factoryfs, tried to flash with pit file too but no result same stuck in problem. then i flashed different kernel fm note kernel through odin which was a success, got my recovery back but unfortunately the only rom i have on internal sd was alliance rom which doesnt install, either says emmc error alliance rom or stucks at extracting system. so again flashed abyss kernel and did a full wipe again but odin still does not go beyond factory fs and i am trying to flash ics rom again. any idea what i should do now as i can flash a kernel and go into recovery. help will be appreciated. meanwhile downloading gb rom to check as i read in other posts it works tough not sure.
Click to expand...
Click to collapse
it is good as far as you can access cwm recovery, try to get any external sd, download a rom and put it on the external sd using other phone
and flash it using cwm and dont forget your safe kernel , and can you tell me please what kernel you've used?

sahil4u said:
same problem here, was on stock ics rooted for quite sometime, today decided to flash alliance rom v2.1, booted to cwm recovery, did a full wipe and after that i just hated myself. phone didnt boot into recovery and odin gets stucked at factoryfs, tried to flash with pit file too but no result same stuck in problem. then i flashed different kernel fm note kernel through odin which was a success, got my recovery back but unfortunately the only rom i have on internal sd was alliance rom which doesnt install, either says emmc error alliance rom or stucks at extracting system. so again flashed abyss kernel and did a full wipe again but odin still does not go beyond factory fs and i am trying to flash ics rom again. any idea what i should do now as i can flash a kernel and go into recovery. help will be appreciated. meanwhile downloading gb rom to check as i read in other posts it works tough not sure.
Click to expand...
Click to collapse
Once get recovery it is best to try to scan partition to identify where the damage is. You can you adb method in my manual repartition guide or the scanner from hg42 which is even better.
Sent from my phone
---------- Post added at 06:30 AM ---------- Previous post was at 06:25 AM ----------
darkelfa2 said:
thank you for your replies, i will try to try them as you mentioned above and by the way and will wait 15-20 minutes in each operation, i already tried the last version of hydracore but had no success, one last thing, if none of them worked (hope not), is there any other possible way to revive from the brick(other than replacing the motherboard or replacing the phone from samsung)?
Click to expand...
Click to collapse
Should try the kernel I sent and also the fm kernel suggested in the post above. Once having recovery it is much easier and there are more options. Otherwise, custom pit is the last resort before mobo replacement.
Sent from my phone

sahil4u said:
same problem here, was on stock ics rooted for quite sometime, today decided to flash alliance rom v2.1, booted to cwm recovery, did a full wipe and after that i just hated myself. phone didnt boot into recovery and odin gets stucked at factoryfs, tried to flash with pit file too but no result same stuck in problem. then i flashed different kernel fm note kernel through odin which was a success, got my recovery back but unfortunately the only rom i have on internal sd was alliance rom which doesnt install, either says emmc error alliance rom or stucks at extracting system. so again flashed abyss kernel and did a full wipe again but odin still does not go beyond factory fs and i am trying to flash ics rom again. any idea what i should do now as i can flash a kernel and go into recovery. help will be appreciated. meanwhile downloading gb rom to check as i read in other posts it works tough not sure.
Click to expand...
Click to collapse
Hi there, sounds like a bad flash or bad download. Firstly remove your external micro SD card and connect it to a PC / Laptop (standard SD adaptor or Card Reader). Download a "default" ROM and kernel and KEEP them on the card (you never know when you need to go back to them). I use Abyss 4.2 kernel and Chrack ROM personally. I always have the jBroid Kernel Cleaner saved also). Replace the micro SD card.
If you can get into Recovery, flash the jBroid script cleaner. Now flash Abyss 4.2 kernel (GB safe kernel) and reboot into Recovery again. Now flash Chrack Rom. I've had a number of bad flashes and these 3 zips have always pulled me out a hole.
Hope this helps. Hit Thanks if it did.

Alba Donzo said:
Hi there, sounds like a bad flash or bad download. Firstly remove your external micro SD card and connect it to a PC / Laptop (standard SD adaptor or Card Reader). Download a "default" ROM and kernel and KEEP them on the card (you never know when you need to go back to them). I use Abyss 4.2 kernel and Chrack ROM personally. I always have the jBroid Kernel Cleaner saved also). Replace the micro SD card.
If you can get into Recovery, flash the jBroid script cleaner. Now flash Abyss 4.2 kernel (GB safe kernel) and reboot into Recovery again. Now flash Chrack Rom. I've had a number of bad flashes and these 3 zips have always pulled me out a hole.
Hope this helps. Hit Thanks if it did.
Click to expand...
Click to collapse
i've already mentioned that it has no recovery mode, and yes, i always have abyssnote kernel in my ex-sd also in my friend's phone, the thing is that he don't know about the emmc bug and he did a restore on a none safe kernel and thats how he bricked his phone
what i've done so far is trying the pit file way but had no luck, now the thing is that the binary counter is 5 and i can't go to have a m/b replacement for free as the warranty is voided, is there any way to reset the counter or to hardbrick the phone except for the jig method?