Database Develop

[Q] Galaxy Note bricked? No. Problem solved.

This is the situation:
Windows XP 32bit
Galaxy Note with LA4
Odin V1.85
KIES latest version
Latest Android SDK
I tried today to downgrade to a directly rootable stock ROM. It failed?
My Note stucks on the bootscreen.
I can put the Note in the downloadmode. When I start Odin, I see a yellow box under ID:COM with 0:[COM7], so my computer sees the Note. I want to flash the rootable stock ROM as described in many threads, especially following Dr. Ketans Guide
But it fails, it stucks at Initialzation..
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK9_N7000OXAKK9_N7000XXKK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
I tried the LA4 stock ROM, same problem.
After this I have putted the Note in recovery mode and this is what I see:
"E:failed to mount /sdcard (Unknown error: 0)"
"E:install_application_for_customer:Can't mount /sdcard"
" your storage not prepared yet. please use UI menu for format and reboot actions."
"copy application failed"
In the recovery mode I tried Factory reset and Wipe cache...no effect.
Since 4pm I have tried many things, read threads and posts, but nothing has solved my problem. By the way I have not seen a problem as described above no where. Is there a genius who can solve this/my problem?
Or is my Note bricked?

The only thing i can see is that it can't mount the SD. Other than that, i don't know. And you know i had my own problems yesterday, so i'm not in the position to know what might be wrong. But one thing is sure, it's not bricked since you can enter download mode.
I know it's frustrating, but you'll have to wait for somebody that knows some things about Odin. I used it myself for the first time yesterday since the Note is my first Samsung device.
Sent from my iPad GT-N7000 using xda premium

see if you can turn off the note. press and hold volume + power and home to get to cwm.. do a data factory reset. then flash with odin in download mode. also make sure you put the correct files in odin when flashing. i had the same problem with my sg2 a few months back when i was fresh with android os. i spent 4 hours figuring it out when it only took 5 mins to fix lol.

dnyc said:
see if you can turn off the note. press and hold volume + power and home to get to cwm.. do a data factory reset. then flash with odin in download mode. also make sure you put the correct files in odin when flashing. i had the same problem with my sg2 a few months back when i was fresh with android os. i spent 4 hours figuring it out when it only took 5 mins to fix lol.
Click to expand...
Click to collapse
Connect to Kies and see if your phone is beeing recognized. If not reinstall the usb drivers. Reboot the phone and pc afterwards and try again. ENABLE USB DEBUGGING in settings also.
Hope it helps

I think this is related to SD card.(Internal)
Have you try using repartition?
I think it may work, NOTE THIS is just my thinking, I can't take any guarranty, you may use at your own risk, if other measures failed
Flash with repartition selected, n selecting pit file
here attached it (extract before use)for note 16GB (routine, not for 32GB)

Reflash stock rom with a different usb port and cable
Sent from my Transformer TF101 using xda premium

dnyc said:
see if you can turn off the note. press and hold volume + power and home to get to cwm.. do a data factory reset. then flash with odin in download mode. also make sure you put the correct files in odin when flashing. i had the same problem with my sg2 a few months back when i was fresh with android os. i spent 4 hours figuring it out when it only took 5 mins to fix lol.
Click to expand...
Click to collapse
As you can read I did trie data factory reset, after flash with Odin it didn't work. Thanks for your help.

gee2012 said:
Connect to Kies and see if your phone is beeing recognized. If not reinstall the usb drivers. Reboot the phone and pc afterwards and try again. ENABLE USB DEBUGGING in settings also.
Hope it helps
Click to expand...
Click to collapse
As you can read I can't ENABLE USB DEBUGGING, because I can't start my Note up normally. Thanks for your help.

Loftus said:
Reflash stock rom with a different usb port and cable
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Thanks, but no effect.

dr.ketan said:
I think this is related to SD card.(Internal)
Have you try using repartition?
I think it may work, NOTE THIS is just my thinking, I can't take any guarranty, you may use at your own risk, if other measures failed
Flash with repartition selected, n selecting pit file
here attached it (extract before use)for note 16GB (routine, not for 32GB)
Click to expand...
Click to collapse
With the pit-file it showed PASS!:
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
<ID:0/006> Added!!
At my screen the following:
Firmware upgrade encountered an isseu.
Please select recovery mode in Kies & try again
If I open Kies to select recevory mode it asks for a recovery code. I tried some codes like 0000,1234 and others, but no good...
Then, I entered the download mode of the Note and tried a flash with KK9 (one file) it shows PASS:
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> zImage
<ID:0/006> hidden.img
<ID:0/006> modem.bin
<ID:0/006> cache.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
....and it works now for me!!! I thought it was wipe, but I have now with KK9 the same apps and configuration as before on the LA4. Weird but good for me!
All of you thanks for your help, especially dr.Ketan

Note not bricked.
Problem solved.

And the problem was?
Sent from my GT-N7000 using xda premium

Read my first post...

got the same problem, did all you did, but get "fail" after is starts working.
any suggest?
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK9_N7000OXAKK9_N7000XXKK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> factoryfs.img
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
thanks

Caesarea038 said:
With the pit-file it showed PASS!:
....and it works now for me!!! I thought it was wipe, but I have now with KK9 the same apps and configuration as before on the LA4. Weird but good for me!
All of you thanks for your help, especially dr.Ketan
Click to expand...
Click to collapse
Really glad to hear.
It is really painful when some one say bricked lovely device.
its ok now, congratulation.
it is advisable once you format internal SD card. Not in hurry, but at least before next update.
Sent from my GT-N7000 using xda premium

shaharda said:
got the same problem, did all you did, but get "fail" after is starts working.
any suggest?
<ID:0/005> Added!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
...........................
<ID:0/005> factoryfs.img
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
thanks
Click to expand...
Click to collapse
Can you tell me exactly the problem and what you did step by step?

Loftus said:
Reflash stock rom with a different usb port and cable
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Today I figured something out:
If you encounter problems with rooting/flashing try another or original USB cable, maybe a different USB port....
My problem as described in my first post was a combination of a fail USB cable and a software problem.

thanks for the help.
i'll try to replace my cable and try a new port.
what i did is trues to flash xxla4 from criskelo with Odin.
while doing that yhe action was breaked an since than i get the massege "an issue encountered...".
i tried almost everything (all i knew and mange to find in the net): tried again with odin, tried to flash 5 different roms from the list in dr.ketan thread.
tries to boot into recovery (no success), tried to recover with kies (it is not being identified by it).

now the battary won't charge. need to send it to the Lab.
thanks anyway. (i'll as them what they did)

shaharda said:
thanks for the help.
i'll try to replace my cable and try a new port.
what i did is trues to flash xxla4 from criskelo with Odin.
while doing that yhe action was breaked an since than i get the massege "an issue encountered...".
i tried almost everything (all i knew and mange to find in the net): tried again with odin, tried to flash 5 different roms from the list in dr.ketan thread.
tries to boot into recovery (no success), tried to recover with kies (it is not being identified by it).
Click to expand...
Click to collapse
Can you enter DOWNLOAD MODE?

[HELP] - upgrade gone wrong?

hi all,
i was on KL3, rooted, then KIES kept bothering me so i thought i'd upgrade to the new LA3 i think....
then the thing crashed and now all i get is the Firmware upgrade encounted an issue. PLease recovery mode in Kies and try again.
problem is, i cant get it to go into recovery mode?!??!?! (volume up, power?)
nothng works, KIes cant detect it, and cant upgrade anything, i am a total noob, and can only get into ODin mode..
HELP please?!?!?
what do i need to do, please step by step, what to download, what to press and whether i need to get a micro sd to install some firmware?
thankyou - urgent help needed!

First of all, relax
You said you can get into "Odin Mode"? I suppose that's download mode. Just go to this thread and everything is explained here. No need to worry
http://forum.xda-developers.com/showthread.php?t=1424997
Just flash another firmware (why not the latest) and everything will be just fine.
P.S. Once rooted, you should probably stay away from stock upgrades...
Press thanks if it helped

Recovery : vol up + home + power
If you get into recovery just wipe cache n wipe data
If error still there
Go to download :
vol dwn + home + power
Reflash new rom
Sent from my GT-N7000 using xda premium

this is all i get and gets stuck???
i chose this one: N7000XXLC1---------2.3.6-------2012 March----------N7000OXXLB3-----------France------------------------------------Download
went to bed for 2 hours and it didnt move...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLC1_N7000OXXLB3_N7000XXLB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.img

confirm you have close antivirus if running
Dont put ROM file too deep, better keep on Root folder e.g. C:/Folder/***.tar.md5
Dont use USB extension, attach USB cable direct to slot on PC, try using different slot (preferably back side PC)
N dont forget to put device in download mode.

Thankyou Dr.Ketan and eug3n91
worked after i switched to the onboard USB.
i guess thats probably why Kies failed too....
this site is fantastic, been a lurker for a while, but never needed to post until today and its proven to be very succesful with both of you helping out so quick.
cant thankyou enough!

Dr.Ketan I am facing the same problem and did exactly the same but this is all i get
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK3_N7000ODDKK1_N7000DDKJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Set PIT file..
<ID:0/015> DO NOT TURN OFF TARGET!!
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> boot.bin
<ID:0/015> cache.img
<ID:0/015> factoryfs.img

same problem here. flashed ROCKET ROM but now i can just go into download mode and CWM. ICS roms stuck on NAND WRITE START and GB roms on FACTORYFS.IMG
I tried everything ever mentioned i guess:
-Tried fix it with KIES but it doesn't even find my device
-use different USB port
-install USB drivers new
-flash Q1_20110914_16GB.pit
-flash other kernel "CF-Root-SGN_XX_OXA_LPY-v5.3-CWM5"
-flash "N7000_XXKL8" where i have to flash three files with odin v1.85
-took the battery out for a longer time
-Flashed different Stock Roms (wipa and without wipe)
-flashed the Abyss Kernel 4.2 again
-flashed "Criskelo's Rom" with CMW
-Tried on different PC with Windows XP
Please there must be a way to help me and khok3893

ow1166 said:
same problem here. flashed ROCKET ROM but now i can just go into download mode and CWM. ICS roms stuck on NAND WRITE START and GB roms on FACTORYFS.IMG
I tried everything ever mentioned i guess:
-Tried fix it with KIES but it doesn't even find my device
-use different USB port
-install USB drivers new
-flash Q1_20110914_16GB.pit
-flash other kernel "CF-Root-SGN_XX_OXA_LPY-v5.3-CWM5"
-flash "N7000_XXKL8" where i have to flash three files with odin v1.85
-took the battery out for a longer time
-Flashed different Stock Roms (wipa and without wipe)
-flashed the Abyss Kernel 4.2 again
-flashed "Criskelo's Rom" with CMW
-Tried on different PC with Windows XP
Please there must be a way to help me and khok3893
Click to expand...
Click to collapse
I'm afraid this has to do with corrupted memory partitions. It's what devs called 'superbricks' if I'm not mistaking...
You could try a ROM with a PIT file, hoping that would repartition any bad sectors.
Again, I could be mistaken. Try to read some other threads around here. A lot of.others have also encountered this problem

khok3893 said:
<ID:0/015> factoryfs.img
Click to expand...
Click to collapse
When you stuck at factoryfs.img = system partition corrupted

I tried with PIT file (Q1_20110914_16GB.pit) and ICS LYP Rom and it stucks on "NAND WRITE START" that comes after "factoryfs.img" I even uses "re-partition" in Odin. Nothing works.....

[Q] Stuck at samsung logo - want to go back to GB

Hello,
I had ICS through KIES (never rooted/never flashed). But now the phone is stuck at samsung logo and doesn't start up. I want to flash GB rom through ODIN.
Just wanted to know whether i can use a wipe rom. This is the rom im planning to use from dr.ketan's post -
N7000XXLC1_N7000OXALC1
Thanks for your time!

have you tried pulling the battery out and restarting after 10 minutes?
if that does not work, then yes, you can use that GB rom via odin.

This is common issue, Just put your device in download mode and flash GB ROM.
Dont worry even after that you may get same symptoms. then
Go to recovery and wipe cache and wipe data. Then it shud boot normally.
remember wipe cache and data only after flashing GB ROM.

wipe - nonwipe difference
praetorius - thanks, but it didnt work in my case
doctor ji, thanks, sorry i have one last question - whats the difference between wipe and non-wipe roms... what I have is a wipe rom so is it still safe to flash it, as my current rom i think is the dreaded lpy rom.
Apologies again for being such a n00b
--
I guess my question is with wipe roms does the wiping happen in ics or in gb :-s

ignore me
Hi,
Just did it after seeing that manloonw had the same problem.
My galaxy note is alive... :crying: (of joy)
Thanks to all the XDA posts and especially dr.Ketan's posts!
--had a md5 invalid message intially, but i unzipped the file again and it worked!
Logs-
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> factoryfs.img
<ID:0/008> NAND Write Start!!
<ID:0/008> zImage
<ID:0/008> hidden.img
<ID:0/008> modem.bin
<ID:0/008> cache.img
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/008> Removed!!
<ID:0/018> Added!!
<ID:0/018> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!

dr.ketan said:
This is common issue, Just put your device in download mode and flash GB ROM.
Dont worry even after that you may get same symptoms. then
Go to recovery and wipe cache and wipe data. Then it shud boot normally.
remember wipe cache and data only after flashing GB ROM.
Click to expand...
Click to collapse
Why not dalvik cache too?

dr.ketan said:
This is common issue, Just put your device in download mode and flash GB ROM.
Dont worry even after that you may get same symptoms. then
Go to recovery and wipe cache and wipe data. Then it shud boot normally.
remember wipe cache and data only after flashing GB ROM.
Click to expand...
Click to collapse
Hi Dr. Ketan,
My Note is on stock ICS rooted LRG ROM. I have the CWM recovery installed. But for some reason when i press Vol up + Home + Power, it doesnt boot into recovery. The only way i can get into recovery is by opening CWM application and selecting "Boot into recovery". I'm not sure if my recovery is broken or if its a standard feature.
I would like to downgrade to KK2 or KK5 firmware using PC Odin. I know after installing GB ROM the next step involves "Wiping" for GB to boot properly (otherwise gets stuck on samsung animation). But until I boot theres no way to get into recovery. How do I go about it?
Many Thanks

[Q] How can i fix my phone

i get this log from odin. i tried4.0.3 stock rom i will get error while copy data.img. after i tried 2.3.6 stcok rom (3 files and one file rom) odin process compleated but my device stuck on boot screen. i did all wipe but still stuck on boot screen.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000_APBOOT_N7000ZSLPF_CL558430_REV02_user_low_sh ip.tar.md5 is valid.
<OSM> N7000_CODE_N7000ZSLPF_CL558430_REV02_user_low_ship .tar.md5 is valid.
<OSM> MODEM_N7000XXLR1_REV_05_CL1144476.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OZSLPF.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> boot.bin
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> zImage
<ID:0/006> factoryfs.img
<ID:0/006> data.img

ca you tell me
what was the last msg?
does it was stuck during data img or it said successfull1/failed0 ?
and wat was your file selection for each tab?

if i select a file rom only 1 file. i open odin and uncheck re partition after i click to pda and select a rom file and flash this file to phone. and odin stop to datafs
if i select 3 files rom i open odin and check repartition after i selcet pit file bootloader file (N7000_APBOOT_N7000ZSLPF_CL558430_REV02_user_low_ship.tar)
pda file (N7000_CODE_N7000ZSLPF_CL558430_REV02_user_low_ship.tar) modem file(MODEM_N7000XXLR1_REV_05_CL1144476.tar) and csc file (GT-N7000-MULTI-CSC-OZSLPF.tar) respectively. and flash these files to phone . if i do that odin stop to datafs.
if i want to flash 2.3.6 rom (3 files) i use same way but odin, flash every file to phone (i think 2.3.6 rom havent data.img file) because odin didnt stop datafs. but if i flash 2.3.6 rom.phone stuck to the boot screen (samsung galaxy note n7000).
after i flash cf root file for enter the cwm. in cwm i do all wipe process. but still stuck on the boot screen.
in my opinion when the phone is formating the /data disk something is wrong. i think /data disk is corrupt. how can i fix this problem i dont find any other methods. please suggest me any solution method. thank u

What should I do ?
for some reason my Data gets shut off
how do i make sure its always on
I want my WhatsApp on all the time
I have to restart phone & then my Data gets on
Please

@tito1905
You have corrupt data.img location
Have you tried flashing gb rom and then wipe data?
May be this can b emmc brick bug
Sent from my GT-N7000 using xda premium

dr.ketan said:
@tito1905
You have corrupt data.img location
Have you tried flashing gb rom and then wipe data?
May be this can b emmc brick bug
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
how can i format /data location from pc (windows or linux ) data wipe isnt work ics or gb i tried both of them restart phone before data formating complete.

You can solve with repartitioning method
There is thread in general section
Title is
Relatively easy way to comeout from bricked note like somthing
It is hot topic n may find in first two page.
Sent from my GT-N7000 using xda premium

thank u so much dr.ketan i solved my bricl problem

How much spare u have.to sacrificed?
Sent from my GT-N7000 using xda premium

brick n7000

Hi
Need some help.
I had sweet rom 11 on my samsung galaxy note n7000. wanted to try cyanogenmod. wasent happy with it. wanted to go back to sweetrom.
So I used odin 3 1.85. (have installed usb drivers). to unroot my n7000 and come back to stock jelly bean by putting the .tar stock file in PDA. And wanted from there to root + cmw and then flash sweetrom again.
But when I used odin and flashed stock jelly bean it went into bootloop. tried to wipe cache(could not find wipe dalvik i stock menu) and reboot but not sucsess. Now it only show " Samsung Galaxy Note gt-n7000" logo. Tried to flash another time but stil bootloop again
On odin it says pass and this is what the odlin log said: se below
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLT5_N7000XXLT3_N7000NEELT2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.img
<ID:0/005> NAND Write Start!!
<ID:0/005> factoryfs.img
<ID:0/005> hidden.img
<ID:0/005> modem.bin
<ID:0/005> zImage
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!
What do I do now. Hope somebody can help me. I have only flashed sweetrom and cyonogenmod based on android 4.2.2
saw just a youtube video which used 3 files pda phone and csc when repairing soft brick. But dont know where to find them. the downloadlink in the Youtube video does not work
https://www.youtube.com/watch?v=FKrNb2q5HFM
Help much appreaceted !

Boot into recovery and do wipe data/ factory reset
Sent from my GT-N7000 using Tapatalk 2

Resolved
forest1971 said:
Boot into recovery and do wipe data/ factory reset
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks mate for quick response
Just saw a video with zedomax. he said to wipe cache and dalvik. that did not work. Just read that i could wipe data reset and woala!
But Youre response was much appreaceted
Thanks alot
Everything works now

Btw, your way of changing rom is too complicated. The best way is to use custom recovery to wipe cache and data and then just flash the custom rom.zip. no need to use odin.
Sent from my GT-N7000 using Tapatalk 2