Database Develop

Fix for Galaxy S i9000 frozen screen

My galaxy was flashed with the latest beta of Android 2.2 then I applied the root, since then my download mode stopped working and my galaxy get frozen after I turn it ON at the Galaxy S black and white screen... The only two mode that I was able to bring up is FORCED UPLOAD by KEY PRESSING and UNKNOWN MODE...
This is what I did to get the download mode and I double checked it twice that his method works before I posted here:
btw: my OS is Windows 7 and I installed the Windows 7 drivers the filename is "Windows 7&Vista x64 USB Driver.zip"
file required are the firmware that I don't have I used again Android 2.2 I don't know what firmware to put I would like to know what firmware was on the original Bell i9000M if someone can tell me it's appreciated.
The other required file is Odin3 v1.30
I did the following first I right clicked the Odin3 and UNBLOCK it and change the compatible mod to XP
Here are the STEPS:
1- disconnect the cable from the phone.
2- launch Odin3 v1.30
3- Put your phone into FORCED UPLOAD by KEY PRESSING
4- Connect the USB cable to your phone (Odin3 should display "Added!!"
5- Select your file PIT, PDA, PHONE and CSC then click on START
6- Your Odin will stop on "SetupConnection.." (if you use the older version of Odin it will stop at "File analysis.." and I don`t know if it works with the older version.
7. Now when you see the "SetupConnection.." Press Volume down + Home + Power and KEEP HOLDING IT UNTIL YOU SEE the DOWNLOAD MODE
This is the LOG of my Odin
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Removed!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> Sbl.bin
<ID:0/005> param.lfs
<ID:0/005> factoryfs.rfs
<ID:0/005> cache.rfs
<ID:0/005> dbdata.rfs
<ID:0/005> zImage
<ID:0/005> modem.bin
<ID:0/005> cache.rfs
<ID:0/005> dbdata.rfs
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Added!!
<ID:0/006> Removed!!
If you have noticed after you see "SetupConnection.." your phone will be disconnected from Odin3 then it will reconnect then BINGO you will get the download mode.
I hope this will help all ppl who are stuck at the boot screen without having access to the download mode.
Now I need a favor I dont know when to get the original firmware of bell I wanna bring back my phone to the original state.
Thanks
DeCoDish
Update: I've installed Kies the latest version I thought I can get the original firmware using Kies so I decided to bring the download mode using the above procedure then I was surprised the I could not get to the download mode again!!! Hmmm.... I uninstalled Kies then I tried again with no luck... I re-installed the driver "Windows 7&Vista x64 USB Driver.zip" then I repeated the above steps then the download mode is back.... Weird isn't??? It looks like the Kies override the driver with another driver... So in order to get my procedure working make sure you UNINSTALL completely KIES from your system and install the drivers that I mentioned... Also notice that adb.exe detects my device and it wasn't before... Now I have the Downloading mode but I don't know what to load Hope that anyone can point me where I can download the original firmware that comes with Bell i9000M model...
DeCoDish

OUTCH!!!! What is that file s1_odin_20100512.pit ???????
I loaded only this file using repartition option without selecting the PDA, MODEM and CSC the I flashed the pit file the phone rebooted then BLACK SCREEN OF DEATH the PHONE DOES NOT TURN ON!!!! Anyone knows why??
DeCoDish

I have the same problem flashed to jp3 my i9000m loosed its recovery and download mode. Work hard to get it now easily lost

Hi DeCoDish,
Thanks - you revived my device from bricked state.
You can find almost all official firmware version on www samfirmware com (sorry not allowed to post full url as I am a new user and still waits to be verified by moderator).
/Anders

How long should keep pressing that combo for download mode, cuz when I'm keep pressing it it just shows recharge screen and i realy need download mode.

DeCoDish said:
OUTCH!!!! What is that file s1_odin_20100512.pit ???????
I loaded only this file using repartition option without selecting the PDA, MODEM and CSC the I flashed the pit file the phone rebooted then BLACK SCREEN OF DEATH the PHONE DOES NOT TURN ON!!!! Anyone knows why??
DeCoDish
Click to expand...
Click to collapse
So you just randomly flashed a file to your phone, not even knowing what it is or does?
Just for the fun of it?
And you're wondering why your phone is now fked?
Do a full reflash with PIT, CSC, MODEM and PDA.
FFS...

DeCoDish said:
My galaxy was flashed with the latest beta of Android 2.2 then I applied the root, since then my download mode stopped working and my galaxy get frozen after I turn it ON at the Galaxy S black and white screen... The only two mode that I was able to bring up is FORCED UPLOAD by KEY PRESSING and UNKNOWN MODE...
This is what I did to get the download mode and I double checked it twice that his method works before I posted here:
btw: my OS is Windows 7 and I installed the Windows 7 drivers the filename is "Windows 7&Vista x64 USB Driver.zip"
file required are the firmware that I don't have I used again Android 2.2 I don't know what firmware to put I would like to know what firmware was on the original Bell i9000M if someone can tell me it's appreciated.
The other required file is Odin3 v1.30
I did the following first I right clicked the Odin3 and UNBLOCK it and change the compatible mod to XP
Here are the STEPS:
1- disconnect the cable from the phone.
2- launch Odin3 v1.30
3- Put your phone into FORCED UPLOAD by KEY PRESSING
4- Connect the USB cable to your phone (Odin3 should display "Added!!"
5- Select your file PIT, PDA, PHONE and CSC then click on START
6- Your Odin will stop on "SetupConnection.." (if you use the older version of Odin it will stop at "File analysis.." and I don`t know if it works with the older version.
7. Now when you see the "SetupConnection.." Press Volume down + Home + Power and KEEP HOLDING IT UNTIL YOU SEE the DOWNLOAD MODE
This is the LOG of my Odin
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Removed!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> Sbl.bin
<ID:0/005> param.lfs
<ID:0/005> factoryfs.rfs
<ID:0/005> cache.rfs
<ID:0/005> dbdata.rfs
<ID:0/005> zImage
<ID:0/005> modem.bin
<ID:0/005> cache.rfs
<ID:0/005> dbdata.rfs
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Added!!
<ID:0/006> Removed!!
If you have noticed after you see "SetupConnection.." your phone will be disconnected from Odin3 then it will reconnect then BINGO you will get the download mode.
I hope this will help all ppl who are stuck at the boot screen without having access to the download mode.
Now I need a favor I dont know when to get the original firmware of bell I wanna bring back my phone to the original state.
Thanks
DeCoDish
Update: I've installed Kies the latest version I thought I can get the original firmware using Kies so I decided to bring the download mode using the above procedure then I was surprised the I could not get to the download mode again!!! Hmmm.... I uninstalled Kies then I tried again with no luck... I re-installed the driver "Windows 7&Vista x64 USB Driver.zip" then I repeated the above steps then the download mode is back.... Weird isn't??? It looks like the Kies override the driver with another driver... So in order to get my procedure working make sure you UNINSTALL completely KIES from your system and install the drivers that I mentioned... Also notice that adb.exe detects my device and it wasn't before... Now I have the Downloading mode but I don't know what to load Hope that anyone can point me where I can download the original firmware that comes with Bell i9000M model...
DeCoDish
Click to expand...
Click to collapse
I did everything step by step...
but now my phone doesn't even starts, it's like it died litterally...
any ideas...???

ANYONE...?????

xero2002 said:
So you just randomly flashed a file to your phone, not even knowing what it is or does?
Just for the fun of it?
And you're wondering why your phone is now fked?
Do a full reflash with PIT, CSC, MODEM and PDA.
FFS...
Click to expand...
Click to collapse
how do we do this since the phone does not even starts...
not even with the key combination...

SOLVED
You need to hold the power, vol down and home key down and then put the battery in.

"5- Select your file PIT, PDA, PHONE and CSC then click on START"
Where can i get these files? I got my phone into this state through some ****ty app, i dont need to be told how dumb i am, if you can help this is greatly appreciated.

Can anyone please share the file Windows 7&Vista x64 USB Driver.zip ?
Thanks

[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?

[Q] Galaxy Note Flashing Failed need help

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.

[Q] Galaxy Note N7000 Noob questions (I have done my research)

This has a happy ending even though it is a whopping 3 posts long lmao!
I would like to give Antiochasylum some recognition. His rom solely pulled this Galaxy Note out of a HardBrick! Thank you for providing this rom
This is the rom that was used!
[ROM][KANG][ICS][AOSP/CM9]Asylum ICS 08[5-31-2012]
http://forum.xda-developers.com/showthread.php?t=1650413
Kernel: Abyss Note Kernel 42CWT Touch Custom Logo
Firmware: None (There is a folder in the root of the phone for firmware but nothing is in it, I am using the Recovery Aroma File Manager)
Model: GT-N7000 (Not the AT&T version)
CWM Version: 5.8.1.5 Touch (Thanks to the Abyss Kernel)
I guess this info would also be good, The Yellow triangle shows at boot logo, as well as in Download mode the custom binary count is at 5
(Since I can't get the phone to boot into anything other than download mode and CWM the only thing I have tried is to ODIN param.tar) which gets me to the android with the weird wireframe hexagon looking thing and a load bar, then fails and spits me into CWM.
I have also tried download mode using PC ODIN 1.3, 1.87, and 3.95
When I ODIN the boot loader + Pit file it reboots into the logo and that is it
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
When I ODIN the Pit + Bootloader + Rom (From what I have read you put the single file into PDA, which is what I did)It hangs on Factoryfs for ever.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLA4_N7000OXALA4_N7000XXLA4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> Sbl.bin
<ID:0/005> factoryfs.img
So I have a Bricked Galaxy Note GT-N7000.
Here is what happened,
My friend tried downgrading from KingDroid, to a older version for stability.
anyhow when he was in CWM he tried wiping the cache and it got stuck at the logo screen.
When I went into CWM and tried to mount or unmount /system, /data, /emmc, /cache, It would tell me failure to mount all of them.... So after tinkering with it, I was able to get everything to mount and unmount, I flashed the newest abyss kernel.
Now I am able to preform a full wipe/factory reset. Wipe the cache. and everything works in CWM now as far as wiping stuff and mounting it (I was basically having the problem of the phone not recognizing /system or any of the rest).
The only thing I get to now is,
Installing: /sdcard/update.zip (This is the stock rom from sammobile or whatever the website is called, I also tried without renaming it to update.zip)
finding update package...
opening update package...
installing update...
installation aborted.
I have searched MANY MANY ways to get this thing back to life, and through various little fix's I was able to get it to where I can preform everything but recovery and flashing the rom apparently....
He made no recovery so, that is not an option.
I have also been looking for the stock kernel which I was unable to find, probably from my own stupidity, but this is where I need help. From the 100+ threads I have read about this issue with the note, I have tried damn near all of them, and got somethings that weren't working in CWM to work, like the format thing, now I am on to flashing. If someone has a link to the stock kernel that would help greatly, as for the stock rom I am using,
N7000XXLA4_N7000OXALA4_DBT.zip
This is the one I have tried flashing, but I get installation aborted. I have tried doing it with the name above as well as renaming it update.zip
The Abyss Kernel I am using right now claims to be compatible with stock roms.
keep in mind that this thing wont boot into anything other than the splash screen for the kernel (This has only happened because I flashed the Abyss Kernel) when the screen comes up it will say Abyss bla bla bla, then at the bottom will say Loading.... I think it is safe to say there is no OS on this Note.
Now I know this phone is far from dead, I just need to know if anyone has had this same problem that has a fix that might work for this.... As I have said I have been through a hundred threads or so about bricked Notes, as well as I have tried threads that were not intended for bricked phones. I have been up for the past 3 days trying to figure this out. and have crashed my computer 2x from all of the threads I have had open in Google chrome.
I know this can be fixed, I just have to find the right one.... right Now I am at a loss.... I will keep updating this as I try new things until some one responds (Hopefully quickly). If you have any questions for me post them and I will do my best to provide good answers
sorry for the long post, I am also sorry if it is confusing I am VERY tired and just want this damned thing to freaking work!

http://forum.xda-developers.com/showthread.php?t=1667886Most stuck at factory thing are hardbricked and need mobo replacement :-(
There is thread on how fix that but its difficult. Try that
Sent from my GT-N7000 using Tapatalk 2

Hey so I checked out that thread, which I used the PIT files that he had, then I stumbled on to Asylum ICS, used the kernel that worked for the ROM installed the rom and now I am back in business.... For some reason I still cannot flash a stock rom onto the phone but I really don't care at this point.
My friend realizes that he is damned lucky that Antiochasylum's rom flashed in the first place. I will edit my first post and put his name and a link to his rom in there for recognition, not because he intentionally provided a fix but because his rom solely pulled this Galaxy Note out of the graveyard...
I also want to thank you Baz77, for replying, because honestly if you hadn't I would have just given up. Your post is what lead me to search just a LITTLE bit more for a fix...
I would change the title to say solved, but 1 I don't know how to and 2 it was a lucky fix in the first place Thank you again for your reply, I like happy endings

Glad I could help.
Sent from my GT-N7000 using Tapatalk 2

Same here. Always good to bring a note back.

Great going mate!! Happy rooting!!
KitsuKun said:
This has a happy ending even though it is a whopping 3 posts long lmao!
I would like to give Antiochasylum some recognition. His rom solely pulled this Galaxy Note out of a HardBrick! Thank you for providing this rom
This is the rom that was used!
[ROM][KANG][ICS][AOSP/CM9]Asylum ICS 08[5-31-2012]
http://forum.xda-developers.com/showthread.php?t=1650413
Kernel: Abyss Note Kernel 42CWT Touch Custom Logo
Firmware: None (There is a folder in the root of the phone for firmware but nothing is in it, I am using the Recovery Aroma File Manager)
Model: GT-N7000 (Not the AT&T version)
CWM Version: 5.8.1.5 Touch (Thanks to the Abyss Kernel)
I guess this info would also be good, The Yellow triangle shows at boot logo, as well as in Download mode the custom binary count is at 5
(Since I can't get the phone to boot into anything other than download mode and CWM the only thing I have tried is to ODIN param.tar) which gets me to the android with the weird wireframe hexagon looking thing and a load bar, then fails and spits me into CWM.
I have also tried download mode using PC ODIN 1.3, 1.87, and 3.95
When I ODIN the boot loader + Pit file it reboots into the logo and that is it
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
When I ODIN the Pit + Bootloader + Rom (From what I have read you put the single file into PDA, which is what I did)It hangs on Factoryfs for ever.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLA4_N7000OXALA4_N7000XXLA4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> Sbl.bin
<ID:0/005> factoryfs.img
So I have a Bricked Galaxy Note GT-N7000.
Here is what happened,
My friend tried downgrading from KingDroid, to a older version for stability.
anyhow when he was in CWM he tried wiping the cache and it got stuck at the logo screen.
When I went into CWM and tried to mount or unmount /system, /data, /emmc, /cache, It would tell me failure to mount all of them.... So after tinkering with it, I was able to get everything to mount and unmount, I flashed the newest abyss kernel.
Now I am able to preform a full wipe/factory reset. Wipe the cache. and everything works in CWM now as far as wiping stuff and mounting it (I was basically having the problem of the phone not recognizing /system or any of the rest).
The only thing I get to now is,
Installing: /sdcard/update.zip (This is the stock rom from sammobile or whatever the website is called, I also tried without renaming it to update.zip)
finding update package...
opening update package...
installing update...
installation aborted.
I have searched MANY MANY ways to get this thing back to life, and through various little fix's I was able to get it to where I can preform everything but recovery and flashing the rom apparently....
He made no recovery so, that is not an option.
I have also been looking for the stock kernel which I was unable to find, probably from my own stupidity, but this is where I need help. From the 100+ threads I have read about this issue with the note, I have tried damn near all of them, and got somethings that weren't working in CWM to work, like the format thing, now I am on to flashing. If someone has a link to the stock kernel that would help greatly, as for the stock rom I am using,
N7000XXLA4_N7000OXALA4_DBT.zip
This is the one I have tried flashing, but I get installation aborted. I have tried doing it with the name above as well as renaming it update.zip
The Abyss Kernel I am using right now claims to be compatible with stock roms.
keep in mind that this thing wont boot into anything other than the splash screen for the kernel (This has only happened because I flashed the Abyss Kernel) when the screen comes up it will say Abyss bla bla bla, then at the bottom will say Loading.... I think it is safe to say there is no OS on this Note.
Now I know this phone is far from dead, I just need to know if anyone has had this same problem that has a fix that might work for this.... As I have said I have been through a hundred threads or so about bricked Notes, as well as I have tried threads that were not intended for bricked phones. I have been up for the past 3 days trying to figure this out. and have crashed my computer 2x from all of the threads I have had open in Google chrome.
I know this can be fixed, I just have to find the right one.... right Now I am at a loss.... I will keep updating this as I try new things until some one responds (Hopefully quickly). If you have any questions for me post them and I will do my best to provide good answers
sorry for the long post, I am also sorry if it is confusing I am VERY tired and just want this damned thing to freaking work!
Click to expand...
Click to collapse

[Q] I9305 doesn't boot, Odin fails at flashing boot.img

Galaxy SIII I9305 shows up with not booting, getting stuck at the SIII logo.
Does the same when trying to get into recovery, so I tried to flash it with Odin.
Flash screen says:
Odin Mode
Product Name: GT-I9305
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Knox Warranty Void: 0
RP SWREV: A2
Click to expand...
Click to collapse
I tried to flash it with the latest packages from Sammobile, but no matter what I try, Odin always fails right away when flashing boot.img... any idea what the problem might be, or what I'm doing wrong?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXUENE4_I9305H3GENE1_I9305NEUEML2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse

Centrumgsm said:
Galaxy SIII I9305 shows up with not booting, getting stuck at the SIII logo.
Does the same when trying to get into recovery, so I tried to flash it with Odin.
Flash screen says:
I tried to flash it with the latest packages from Sammobile, but no matter what I try, Odin always fails right away when flashing boot.img... any idea what the problem might be, or what I'm doing wrong?
Click to expand...
Click to collapse
stupid question, but did you go in to download mode when flashing? thats by pressing menu button + volume down button + power button. then press volume up to agree with download mode and then flash with odin. And make sure you have all drivers installed

klemen241 said:
stupid question, but did you go in to download mode when flashing? thats by pressing menu button + volume down button + power button. then press volume up to agree with download mode and then flash with odin. And make sure you have all drivers installed
Click to expand...
Click to collapse
I did. As far as I can tell, I did everything according to the guides.
[edit] I also managed to flash a different I9305 without problem, so I'm sure it's not driver or flash file related. There is something with this specific phone that prevents flashing.
I've seen a "rescue firmware" for the I9300 with separate PDA, MODEM and CSC (+.pit) files for when the regular stock firmware wouldn't flash, and I was wondering if such a thing exists for the I9305 or if there is a guide on how I could make one.

Try to get a PIT file for the i9305 and add it to ODIN. If you don't do this, ODIN extracts the PIT from the device, and that might be corrupted.

daedric said:
Try to get a PIT file for the i9305 and add it to ODIN. If you don't do this, ODIN extracts the PIT from the device, and that might be corrupted.
Click to expand...
Click to collapse
Can't brick the device much more than it already is, right? I tried it, but it just gets stuck here:
<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..
Click to expand...
Click to collapse
I got bored after 15 minutes, turned off the target, turned on the target, no change, still the same error when flashing.
Thought about the Knox bootloader preventing me from updating it, but that usually gives me some kind of error message right on the flash screen. Plus I'm using the latest images, and the other I9305 also says "SWREV A2", so that shouldn't be a problem.
This looks more and more like a motherboard replacement...

All i have to say is, good luck. Things don't look good.
Try to flash just a recovery via ODIN. You'll kiss knox goodbye, but we're out of options.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9305/

daedric said:
Try to flash just a recovery via ODIN. You'll kiss knox goodbye, but we're out of options.
Click to expand...
Click to collapse
Tried it, no go. Same error, still won't boot into recovery. On the upside, it didn't trip Knox either

Ok, just for good measure, let's get down to the basics.
Questions:
1. What type of USB cable are you using? Can you try another?
2. Is the USB cable connected directly to the computer , or via HUB / Front ports ?
3. Have you tried cleaning the usb port on the device ?

I've covered all the basics, even tried another computer. Same results.
I couldn't find a solution, ended up sending the phone for a motherboard replacement. Thanks for the suggestions, everyone!