Related
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?
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.....
Hi,
My Galaxy Note has failed when i tried to flash into 4.0.3, story was like this.
My Note has rooted long time ago and flashed with N7000DXLA1_N7000OLBKL2_XSP, and then I noticed a new 4.0.3 has officially came up on kies for upgrade, so I plug my phone into kies, however its said i can not upgrade with my current firmware. then I went to restore my phone back to my very 1st backup with my original firmware KK1. however still no luck, kies still said I can not upgrade with my current firmware. so at the end I decided to flash the rom with Moblie Odin Pro into N7000ZSLPF_N7000OZSLPF_TGY (Hong Kong). then It was finally upgraded into 4.0.3, however my data has all gone, so I then tried to restore my phone using CWM Manage back to my LA1. and then problem comes!!!
when I restore back to LA1, my Note went in to boot loop, and never wanted to boot up. so then I decided to flash it back to N7000ZSLPF_N7000OZSLPF_TGY (Hong Kong) with PC Odin, However it stays in the samsung logo and not going any further. then I tried to flash it with N7000ZSKK1, but even worst , it stucks at the <ID:0/006> data.img for a long time about 2 hours, and then finally said FAILED, I have copy the log below.
now I turn on my phone it said "firmware upgarde encountered an issue. please select recovery mode in kies & try again". I tried to connect my note with kies, but then kies connection file too.
Could anyone please help ??
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7000ZSKK1_CL706440_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_N7000XXKJ6_REV_05_CL1070146.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OZSKK1.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> 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> zImage
<ID:0/006> factoryfs.img
<ID:0/006> data.img
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
could you enter in CWM recovery?
Probably bricked. Send back to ssc to get it fixed if still have warranty else read this post and try fixing it yourself, http://forum.xda-developers.com/showthread.php?t=1667886
Sent from my GT-N7000 using Tapatalk 2
Your mistake was recovering through cwm. That recovers nearly the whole rom, and on ICS, can be dangerous. Not counting the fact you are rewriting a ics rom with gb.
Your device is bricked. Maybe not hardbricked.
Download pitfile for your phone from drketans thread, redo flash of your rom choice with pitfile selected. I recommend a GB rom as ICS factory reset or wipe from recovery is dangerous. This should enable safely repartition. Do not check this without pitfile selected. This should safely fix your brick. Do not select clear efs.
If it doesnt reboot, bootloop, at least you got gb. The rom you flashed is not wipe version and stuff is lingering that stops reboot. Go to recovery and perform factory reset. If no bootloop,
do a safe factory reset from dialer anyway. Code google it, it should have 3855 in it. Now root it and with mobile odin install cf kernel and in recovery, after safe reboot retore your cwm backup. Note, with ICS it is not recommended recovering data or apps. Should you want to backup and recover apps, non system ones you can with titanium backup. Data again not recommended.
All at own risk.
Sent from my GT-N7000 using Tapatalk 2
Hi Derekzxy,
Follow what Baz77 said.
I'm just curious what kernel were you using when you performed nandroid restore?
Hope you get your device working back soon.
DrKetans thread is the one in development section, then in stickies btw
Sent from my GT-N7000 using Tapatalk 2
riccardo_1958 said:
could you enter in CWM recovery?
Click to expand...
Click to collapse
Yes I can, however it only has these option and error message:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
test redbend fota[FS]
E: failed to mount / data (unknown error: 0)
-- copying media files..
-- updating application ..
E:filed to mount / data (unknown error: 0)
E: install_application_for_customer:Cant's mount /data
your storage not prepared yet. please use UI menu for format and reboot actions. copy application failed.
-- Appling Multi-CSC...
installing Multi-CSC
Copied the packages.
Copied the default_wallpaper file.
Coplied the power on / off animation files.
Can't access to '/system/csc/TGY/system/'.
Successfully applied multi-CSC.
Thats all i have got.
derekzxy said:
Yes I can, however it only has these option and error message:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
test redbend fota[FS]
E: failed to mount / data (unknown error: 0)
-- copying media files..
-- updating application ..
E:filed to mount / data (unknown error: 0)
E: install_application_for_customer:Cant's mount /data
your storage not prepared yet. please use UI menu for format and reboot actions. copy application failed.
-- Appling Multi-CSC...
installing Multi-CSC
Copied the packages.
Copied the default_wallpaper file.
Coplied the power on / off animation files.
Can't access to '/system/csc/TGY/system/'.
Successfully applied multi-CSC.
Thats all i have got.
Click to expand...
Click to collapse
Can you try what I posted?
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
Can you try what I posted?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks I will try that later and will let you know the result
Boy124 said:
Hi Derekzxy,
Follow what Baz77 said.
I'm just curious what kernel were you using when you performed nandroid restore?
Hope you get your device working back soon.
Click to expand...
Click to collapse
I have upgraded to N7000ZSLPF and then restored to N7000DXLA1.
Ya, i hope i can get it fix soon.
baz77 said:
Your mistake was recovering through cwm. That recovers nearly the whole rom, and on ICS, can be dangerous. Not counting the fact you are rewriting a ics rom with gb.
Your device is bricked. Maybe not hardbricked.
Download pitfile for your phone from drketans thread, redo flash of your rom choice with pitfile selected. I recommend a GB rom as ICS factory reset or wipe from recovery is dangerous. This should enable safely repartition. Do not check this without pitfile selected. This should safely fix your brick. Do not select clear efs.
If it doesnt reboot, bootloop, at least you got gb. The rom you flashed is not wipe version and stuff is lingering that stops reboot. Go to recovery and perform factory reset. If no bootloop,
do a safe factory reset from dialer anyway. Code google it, it should have 3855 in it. Now root it and with mobile odin install cf kernel and in recovery, after safe reboot retore your cwm backup. Note, with ICS it is not recommended recovering data or apps. Should you want to backup and recover apps, non system ones you can with titanium backup. Data again not recommended.
All at own risk.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Hi, I'm trying to find the pitfile you mentioned, but I couldn't find it, may you post the link to the pitfile, and do I use Odin to flash it, and what option I should check and which i shouldn't, sorry to bother you, but you may be my life saver
http://forum.xda-developers.com/showthread.php?t=1424997
Best read whole ghread, I provided shortcut route lol
If you have 16gb you can use this one I thinkhttp://forum.xda-developers.com/showthread.php?p=26162413
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
http://forum.xda-developers.com/showthread.php?t=1424997
Best read whole ghread, I provided shortcut route lol
If you have 16gb you can use this one I thinkhttp://forum.xda-developers.com/showthread.php?p=26162413
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Hi, I have found the pitfile, and I have looked through most of the post up there, but I still couldn't found the option which i need to check in PC Odin when flashing with the pitfile. please kindly help me out Thanks x 1000
Select tar md5 file in pda, select pit file in pit file and see that repartion is now checked.
Its that easy Odin is even supplied with the pit file,
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
Select tar md5 file in pda, select pit file in pit file and see that repartion is now checked.
Its that easy Odin is even supplied with the pit file,
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
No Luck. My 1st try, its stuck at factorygf.img
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DXLA1_N7000OLBKL2_N7000DXKL2_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..
<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> cache.img
<ID:0/006> NAND Write Start!!
<ID:0/006> factoryfs.img
see attachment
I have tried to flash with KK1 which has Code, Modem and CSC file and also Pit file.. it has passed the factorys.img, however stuck at DATA see result below:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7000ZSKK1_CL706440_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_N7000XXKJ6_REV_05_CL1070146.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OZSKK1.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> zImage
<ID:0/006> factoryfs.img
<ID:0/006> data.img
should I perform this action in the post http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
THanks
Hello,
I too have same problem now. Please help me.
If it getsvstuck on factory thrn you have hardbrick, best to return phone dude
Sent from my GT-N7000 using Tapatalk 2
derekzxy said:
Hi, I have found the pitfile, and I have looked through most of the post up there, but I still couldn't found the option which i need to check in PC Odin when flashing with the pitfile. please kindly help me out Thanks x 1000
Click to expand...
Click to collapse
Try this method my friend
http://forum.xda-developers.com/showthread.php?t=1667886
It works for me..
wipe helps
I have exactly the same problem after flashing the stock gingerbread and custom pit file with odin to solve a brick (http://forum.xda-developers.com/showthread.php?t=1667886
In the recovery mode with
E: failed to mount / data (unknown error: 0) ...
Click to expand...
Click to collapse
error message. Just do
wipe data/factory reset and then 'reboot system now
Click to expand...
Click to collapse
It works for me.
Do not 'wipe data' with CWM, that caused me the brick in the first place.
i know there's a lot of thread about this and some of it already fixed..BUT NOT ME! really sorry if this is a repeated question....
i did search,followed all thread, flash thousand times of ICS,then GB Rom..tried include PIT file,..then messed everything up again..still no go for me... :'(
followed all this thread instructions..
http://forum.xda-developers.com/showthread.php?p=23234683
http://forum.xda-developers.com/showthread.php?t=1724696
http://forum.xda-developers.com/showthread.php?t=1659768
here the ODIN message
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7000XXLC1_CL1003701_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_N7000XXLB2_REV_05_CL1106002.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OXALC1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> factoryfs.img
and just stuck there everytime i flashed... PLEASE..PLEASE...!! Im so depressed...
here's how it started....i successfully rooted ICS rom (LP9) then i wanna flash the PARANOIDANDROID ROM..
so in recovery mode,i did a data wipe (always did it with my SGS,SGS2)...AND IT STUCK THERE!
so i forced reboot the phoned and now IM TOTALLY ****ED!!
PLEASE..!!PLEASE..!! already 12 hours on this and still ****ED..im so tired..gotta go to bed now (3.21am)
You are super bricked if it is hanging on factoryfs.img. Why did you wipe in stock ICS? You NEED to read! I'm sorry. Go to Samsung service center or send your phone off to get the motherboard replaced.
kamaliqwan said:
i know there's a lot of thread about this and some of it already fixed..BUT NOT ME! really sorry if this is a repeated question....
here the ODIN message
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7000XXLC1_CL1003701_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_N7000XXLB2_REV_05_CL1106002.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OXALC1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> factoryfs.img
and just stuck there everytime i flashed... PLEASE..PLEASE...!! Im so depressed...
PLEASE..!!PLEASE..!! already 12 hours on this and still ****ED..im so tired..gotta go to bed now (3.21am)
Click to expand...
Click to collapse
Yours looks like a typical case of superbrick where some blocks in a certain partition in the internal memory were damaged by wiping under buggy ICS kernel.
If you have warranty covered then go to get help from SS service. If you are out of warranty the repartition solution described in the thread below can give you a way out.
http://forum.xda-developers.com/showthread.php?t=1661590
cheers,
andreww88 said:
You are super bricked if it is hanging on factoryfs.img. Why did you wipe in stock ICS? You NEED to read! I'm sorry. Go to Samsung service center or send your phone off to get the motherboard replaced.
Click to expand...
Click to collapse
Whooow really...? **** i thought it was just a soft bricked..
Anyway can i fixed this myself..?
I wipe because i wanna flash a fresh new rom.. It's a normal thing on SGS,SGS2 or even SGS3 right?
Oh.. Please... This is not my phone.. I just wanna help my friend to get a custom rom..
If you flash paranoid you must be in gb first not on ics.
All you can do is claim the waranty. Erase all the evidence, the yellow tringle and binary counter. Im sorry i know your situation your in.
Man u have bricked your SGN, Actually you have corrupted emmc area on your SGN,
You can easily Recover your Note by flashing it with different pit files, but you will loose some space on emmc, it depends on which pit file works for you, higher the pit file number less space you loose,
I have attached the pit files, use it carefully, as there are pits for both 16gb and 32gb so use it accordingly depending on your note ver.
One more thing....Your Warranty will be void
So if you have warrany left...its better to replace the mother board
USE IT AT YOUR OWN RISK
guys thanks for your answers..im done!!
i found this solution.
http://forum.xda-developers.com/showthread.php?t=1667886
man..after 2 days..i just thinkin to go to samsung service center tomorrow
im sooo happy..!!
hope this will help others too...!ALWAYS READ 1ST! i flashed the +pits-patched-standard.zip
Here are some cleaner instructions for unexperienced users:
If you do this for the first time, then you should use
Q1_*_16GB-patched.pit or Q1_*_32GB-patched.pit from the pits*patched-standard.zip.
according to your memory size (you bought a 16GB or a 32GB model, the number can be found on the back of the sales packaging, top left corner).
After flashing the PIT you have three empty partitions: system, data and internal SD.
So you have to put something senseful on it .
Otherwise it does in nearly no user noticeable way differ from a stock phone.
You just have a smaller internal SD.
Note, there are multiple ways to reinstall the phone.
The first is probably the most simplest (but note, this is from my memory, I use CyanogenMod-like ROMs all the time):
* Flash a known good ROM via Odin (especially not one of the faulty ICS ROMs)
* reboot into recovery (just hold Vol-Up + Home + Power until you arrive there)
* wipe cache
* wipe data
* format internal SD (first remove the external SD, to be sure you are handling the internal SD)
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