I succesfully flashed Fusion V2 in my GNote. I've being trying to flash thru Odin a Stock Rom since I just prefer Stock. I flashed a GB Kernel, I think its called Abyss (sorry If I Mispell). And then try to flash the Stock ICS Rom. The process stops at:
FactoryFS.img
Nand write Start.
It stops right there.
What should I do????
Sorry for my english.
kindly post your full error log here, whether it was stopped with msg successfull0/failed 1 Or it was stuck?
dr.ketan said:
kindly post your full error log here, whether it was stopped with msg successfull0/failed 1 Or it was stuck?
Click to expand...
Click to collapse
The thing is that Odin doesnt show any error, it just stops. I waited 30mins and nothing so I unplugged the phone. The phone didnt show a download bar. The phone was in download mode.
That is really bad sign
Any way download any Stock GB ROM
and flash again with pit file
If your device is 16GB model (not 32GB) then use this pit with re partition option enable on PC Odin
http://d-h.st/FVh
dr.ketan said:
That is really bad sign
Any way download any Stock GB ROM
and flash again with pit file
If your device is 16GB model (not 32GB) then use this pit with re partition option enable on PC Odin
http://d-h.st/FVh
Click to expand...
Click to collapse
Yes is a 16gb model. Where can I get the Pit file?
I have pasted link in my previous post, And you have quoted too.
darielsantana said:
Yes is a 16gb model. Where can I get the Pit file?
Click to expand...
Click to collapse
Perfect just saw the download link.
Ill try that once I get home.
Btw your posts are great. Thanks for them.
dr.ketan said:
I have pasted link in my previous post, And you have quoted too.
Click to expand...
Click to collapse
<ID:0/007> 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/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
Im trying to flash the GB Rom with the Pit file you gave me and thats the msg I get. Is this process really slow or am I having trouble?
I have around 10mins waiting and nothing else is happening
darielsantana said:
<ID:0/007> 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/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
Im trying to flash the GB Rom with the Pit file you gave me and thats the msg I get. Is this process really slow or am I having trouble?
I have around 10mins waiting and nothing else is happening
Click to expand...
Click to collapse
Got this error!!!
<ID:0/007> 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/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
It appears ODIN is struggling to find your device, Do you have the correct drivers installed ? Have you exited kies (including system tray?) Have you tried alternative USB ports ? Preferably direct into the MoBo (back of tower?) What shows up in ODIN when you connect your phone in download mode ?
azzledazzle said:
It appears ODIN is struggling to find your device, Do you have the correct drivers installed ? Have you exited kies (including system tray?) Have you tried alternative USB ports ? Preferably direct into the MoBo (back of tower?) What shows up in ODIN when you connect your phone in download mode ?
Click to expand...
Click to collapse
Now it connected but when trying to Flash Stock GB it shows this:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKKA_N7000OXXKK6_N7000XXKK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
<ID:0/007> factoryfs.img
whats happening? why cant i flash the rom??
How log has it been stuck like that for ??
Usually sticking at factoryfs.img is not a good sign, You can use the unbrick method to repartition the phone and get you up and running again, However you will lose some space (2-3gb)
Here's the link http://forum.xda-developers.com/showthread.php?t=1667886
I would wait for some confirmation from someone else firstly, Someone like the god himself - Dr.Ketan
Ive never bricked my note so luckily ive never had to try that method ^^
azzledazzle said:
How log has it been stuck like that for ??
Usually sticking at factoryfs.img is not a good sign, You can use the unbrick method to repartition the phone and get you up and running again, However you will lose some space (2-3gb)
Here's the link http://forum.xda-developers.com/showthread.php?t=1667886
I would wait for some confirmation from someone else firstly, Someone like the god himself - Dr.Ketan
Ive never bricked my note so luckily ive never had to try that method ^^
Click to expand...
Click to collapse
Yeah I followed that method but only can flash Custom Roms after the repartition. I dont know what to do :S. I've being waiting his reply.
Why can you only flash custom ROMs ? Cant you flash a stock one via ODIN but include the patched .pit file ?
Sorry im of no use
azzledazzle said:
Why can you only flash custom ROMs ? Cant you flash a stock one via ODIN but include the patched .pit file ?
Sorry im of no use
Click to expand...
Click to collapse
I cant flash stock rom with pit file given :s
Its ok at least someone is trying to help
Do you have warranty ?? You could flash a stock ROM without pit, which will put your phone back into the bricked state, Then send it off for warranty ?
azzledazzle said:
Do you have warranty ?? You could flash a stock ROM without pit, which will put your phone back into the bricked state, Then send it off for warranty ?
Click to expand...
Click to collapse
no warranty
Why dont you have warranty ? All Samsungs come with at least 12-24 months manufacturer warranty.
azzledazzle said:
Why dont you have warranty ? All Samsungs come with at least 12-24 months manufacturer warranty.
Click to expand...
Click to collapse
well i might have but I bought in Ebay. And live at Dominican Republic. There is no Samsung representative over here. And I dont have a Bill.
Well hold on for some other opinions, But if you dont get a solution then consider sending it to samsung, They should repair it, However you might have to pay postage charges, Give them a call first and blame it on a OTA / Kies update
Related
Hi everyone, sorry if this is the wrong place for this post, mods pls move it to the right forum.
I have a non-rooted, non-operator free Samsung Galaxy Note with Gingerbread and I want to root it, set it operator free and flash ICS.
I tried to flash a ROM via Odin (N7000XXLPY_N7000OXALPY_DBT), followed the steps (open Odin, select the md5 file @ PDA, startup the phone on download mode, connect the phone to pc, now Odin recognizes it and shows the yellow case, then I press start) but at a certain point it just stops working and I dunno what to do, its frustrating...
Here's the Odin's Console log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLPY_N7000OXALPY_N7000XXLPT_HOME.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.img
It just stops at this point and don't do nothing... What can I do?
kelomancer said:
Hi everyone, sorry if this is the wrong place for this post, mods pls move it to the right forum.
I have a non-rooted, non-operator free Samsung Galaxy Note with Gingerbread and I want to root it, set it operator free and flash ICS.
I tried to flash a ROM via Odin (N7000XXLPY_N7000OXALPY_DBT), followed the steps (open Odin, select the md5 file @ PDA, startup the phone on download mode, connect the phone to pc, now Odin recognizes it and shows the yellow case, then I press start) but at a certain point it just stops working and I dunno what to do, its frustrating...
Here's the Odin's Console log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLPY_N7000OXALPY_N7000XXLPT_HOME.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.img
It just stops at this point and don't do nothing... What can I do?
Click to expand...
Click to collapse
Usually ODIN takes a lil long to flash a rom.So give it a good 10mins time and see it comoletes the installation....
Or you may use the new ODIN by grgsiocl.It shows the remaining time left to finish flashing.Its there in themes and apps section.
Sent from my GT-N7000 using xda app-developers app
sometimes 30 or more minutes.
Usually it stops there either thought corrupt download of rom, redownload it try again.
Or because you have bricked it "op op" emmc "style" way.
If you did not root phone, or put different kernels on, then dont do anything and contact entropy, he is looking for a case where without this the phone was superbricked.
Sent from my GT-N7000 using Tapatalk 2
You may not have all the drivers from Samsung? Download Kies, run it. Then turn off Kies, antivirus and firewall. Commissioning Odin as administrator.
Wait for atleast 20 mins approx to get the stage completed or throw out to samsung service center to get it done.
Swyped From My Juicy Flavoured AOKP JB.
Hi
Can somebody help me with this problem
Firstly during an official update from 2.3.6 to 4.0.4 using KIES bombed out at 4% so soft bricked is what we call it!!!
Can only boot into download mode so using odin to wack on
"N7000XXLRG_N7000DBTLRG_DBT\N7000XXLRG_N7000DBTLRG_N7000XXLRB_HOME.tar.md5"
Following message appears in Odin
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRG_N7000DBTLRG_N7000XXLRB_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> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006>
<ID:0/006> Receive Response form LOKE
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there anyway I can force write to it?
Could it be the firmware that is the issue or would I get this on everything I try?
Please help
Thanks
EFCLEE said:
Hi
Can somebody help me with this problem
Firstly during an official update from 2.3.6 to 4.0.4 using KIES bombed out at 4% so soft bricked is what we call it!!!
Can only boot into download mode so using odin to wack on
"N7000XXLRG_N7000DBTLRG_DBT\N7000XXLRG_N7000DBTLRG_N7000XXLRB_HOME.tar.md5"
Following message appears in Odin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006>
<ID:0/006> Receive Response form LOKE
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there anyway I can force write to it?
Could it be the firmware that is the issue or would I get this on everything I try?
Please help
Thanks
Click to expand...
Click to collapse
Did you select the firmware .tar file in odin PDA tab only?
This sometimes happens due to bad download file, try flashing some other firmware, preferably GB so that you can wipe if required.
search google with 'Receive Response form LOKE" and you will find lot of people having same issue and most of them able to resolve by flashing different firmware.
jeetu1981 said:
Did you selected the firmware .tar file in odin PDA tab only?
This sometimes happens due to bad download file, try flashing some other firmware, preferably GB so that you can wipe if required.
search google with 'Receive Response form LOKE" and you will find lot of people having same issue and most of them able to resolve by flashing different firmware.
Click to expand...
Click to collapse
No I have been adding it to PHONE, is this wrong?
Anyways I just tried it again adding to PDA and this time it gets stuck on
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRI_N7000OXXLP8_N7000XXLRB_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..
Any ideas?
EFCLEE said:
No I have been adding it to PHONE, is this wrong?
Anyways I just tried it again adding to PDA and this time it gets stuck on
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRI_N7000OXXLP8_N7000XXLRB_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..
Any ideas?
Click to expand...
Click to collapse
Yes, its completely wrong, you should select single firmware .tar in PDA tab only. Try again by rebooting your phone and check if you have kies running, if so close it completely.
SUGGESTION- Do not flash ICS stock rom now, I am not sure what has been messed up by flashing this using phone tab (ICS phone files on GB base, not sure), best is flash stock GB firmware first, then wipe in stock recovery and flash ICS.
jeetu1981 said:
Yes, its completely wrong, you should select single firmware .tar in PDA tab only. Try again by rebooting your phone and check if you have kies running, if so close it completely.
SUGGESTION- Do not flash ICS stock rom now, I am not sure what has been messed up by flashing this using phone tab (ICS phone files on GB base, not sure), best is flash stock GB firmware first, then wipe in stock recovery and flash ICS.
Click to expand...
Click to collapse
WOW!!! Restarted phone wacked it into PDA and BAM!! started to copy over!!!
A million thank you's Jeetu1981 your a fkin diamond!!!!!
EFCLEE said:
WOW!!! Restarted phone wacked it into PDA and BAM!! started to copy over!!!
A million thank you's Jeetu1981 your a fkin diamond!!!!!
Click to expand...
Click to collapse
Cool... Consider urself lucky this time
And click on thanks is better than million thanks, lol
Sent from my GT-N7000
Hi, I tried to flash something in odin and my pc stopped usb connection, and now my phone can enter only in download mode.
When I try to flash something odin says write error. I searched on the internet and I saw that it might be an flash lock.
But I dont selected it in odin. I called samsung, and they recommended me a service. And it will be repaired for 28 USD . Can someone help me? As I helped others, now I need your help!
I will sent it to service in 3 days! Also, the repair is not free, because I dont reset binary counter....now is custom (5)
use 3 file rom file
Try wit Secure PIT file
Antox97 said:
Try wit Secure PIT file
Click to expand...
Click to collapse
amir_n71 said:
use 3 file rom file
Click to expand...
Click to collapse
Sorry but no one solution is working. I whink that I can't recover my photos from internal sdcard.
On phone appears: ,,odin transaction fail,, when I am connecting it....and on pc ,,write fail,,
What TO DO???!!!
All depends on what file the USB connection stopped.
If it was fat.bin, then it's pretty much dead.
MrMateczko said:
All depends on what file the USB connection stopped.
If it was fat.bin, then it's pretty much dead.
Click to expand...
Click to collapse
It says write error on any file. I don't know why, I never checked flash lock.
Also 1 click unbrick for samsung devices in not running on my pc.
(flash progress won't start)
-----2 days until service
Odin messages
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S6500DBGMK1_S6500DXXMK1_S6500DXECML1_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> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
MaDaLiNoSt said:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S6500DBGMK1_S6500DXXMK1_S6500DXECML1_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> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I've NEVER seen that before It stop almost imediately Before flashing anything .. My Mini 2 stops in "Fat.Bin" .. Thats all .. did it showed any message at your phone ?? like "Secure Check Fail Id:0x95" ??
I never seen it too! I think that you must send your device into assistance, I'm really sorry
PHOTOS
Ezzam_Itachi said:
I've NEVER seen that before ... Did it showed any message at your phone ?? like "Secure Check Fail Id:0x95" ??
Click to expand...
Click to collapse
Now you can see how my phone is looking:
I see firmware error on power and recovery mode.
When I connect the usb cable in phone, I get error!
What to do??!! Next morning, tomorrow I will send it into service :crying:
Happy again
Hi, and thank you for all your feedbacks (posts). Now I recovered my phone with some pc softwares and everything is ok :victory:
Odin Log:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S6500DBGMK1_S6500DXXMK1_S6500DXECML1_HOME.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> system.img.ext4
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> fat.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> appsbl
<ID:0/003> oemsbl
<ID:0/003> partition.bin
<ID:0/003> qcsbl.mbn
<ID:0/003> qcsblhd_cfgdata.mbn
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
PC Screenshot:
Note: Next time when someone will have connecting issues with phone, is easy to post here and I will give help !
Do not create a new thread, because there are too many threads based same error. (eg. recovery ramdump or not working)
Owh, now I remember that writings.. For that I have sent my device into service :/
When your device are coming back, don't flash any firmware! If you have a NFC model, you must flash a NFC model like XXLD2!
Waw !! You made it !! :victory: okay now I need your help ... How did you do that ?? I oftenly flash my phone with odin .. Unfortunately, It never .. NEVER pass the flash ..It always failed .. Maybe with your solution I can get this done .. Thanks for your help !!
Little Flashing TUT
Ezzam_Itachi said:
How did you do that?
Click to expand...
Click to collapse
Download mini 2 firmware from SamMobile
Click to expand...
Click to collapse
Simply enter the model number of your device in the search box and a list of latest firmwares will come up. To download a firmware, you will need to be logged in to your SamMobile account using your username and password.
Click to expand...
Click to collapse
Demo Firmware list:
Disclaimer
SamMobile & me are not responsible if you brick or damage your device by using the files available on SamMobile Firmware Portal. You are doing all at your own risk! Proceed only if you are 100% sure that you know what you are doing.
Click to expand...
Click to collapse
Download and install compatible Kies from Samsung
Select Kies 2.6 for devices launched before September 2013
Click to expand...
Click to collapse
Now lastest drivers should be installed via kies application.
Download and install Odin3 from internet.
Click to expand...
Click to collapse
Now boot phone in download mode via an key combination: Volume down + home + power
If your device is not recognized, or windows failed istalling drivers (CDC or other driver)
use Zadig to force reinstall drive. Zadig can be found in heimdall unbrick pack for windows.
Click to expand...
Click to collapse
An alternative of Zadig is Microsoft Device manager. Select uninstall device from app menu, and then move usb cable to another port.
This solution might not solve your problem.
Click to expand...
Click to collapse
Good luck with flashing!
About you fat.bin error:
-Download another compatible rom
-That's it! : )
Amazing! Congratulations
Antox97 said:
Amazing! Congratulations
Click to expand...
Click to collapse
Thanks :laugh:
Thanks !!
Ezzam_Itachi said:
Thanks !!
Click to expand...
Click to collapse
No problem
Sent from my GT-S6500D using Tapatalk 2
The phone shows " Firmware upgrade issue encountered an issue. Please select recovery mode in Kies & try again". I cant go to recovery mode ie. vol up+home+power. THings I have tried:
1. with Kies the device isnt recognised. I have updated the driver as well.
2. with odin every thing fails... flashing "all samsung recovery.tar", flashing stock jelly bean, flashing .pit file
I have googled for days and tried many things but isnt working. Need help
Where and why the stock firmware flashing is going wrong?
nokiamodeln91 said:
Where and why the stock firmware flashing is going wrong?
Click to expand...
Click to collapse
Hello,
Now the odin is not even recognising the device, Before it couldnt perforn the NAND write.
Start fresh... Remove battery and let the phone rest for couple of minutes.. Then try again.. Just go ahead and flash a stock rom. And check where it fails.
nokiamodeln91 said:
Start fresh... Remove battery and let the phone rest for couple of minutes.. Then try again.. Just go ahead and flash a stock rom. And check where it fails.
Click to expand...
Click to collapse
I had done what you've suggested. It dint work. The message in the odin3 v3.04 when trying to flash stock jellybean was
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N7000XXLSZ_N7000OXALSZ_906407_REV02_user_low_ship.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> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
loveandroider said:
I had done what you've suggested. It dint work. The message in the odin3 v3.04 when trying to flash stock jellybean was
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N7000XXLSZ_N7000OXALSZ_906407_REV02_user_low_ship.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> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Where did you download this file from? SAMmobile?
Try redownloading the file, it may be corrupted during download.
AutumQueen92 said:
Where did you download this file from? SAMmobile?
Try redownloading the file, it may be corrupted during download.
Click to expand...
Click to collapse
Hello. I can say that the file isnt corrupt because I have flash that ROM a numerous time before. But until the last time when I was flashing custom rom night owl lollypop version, it stuck in boot loop and then when I tried to flash that , it dint work. Now I cant even go to recovery mode.
loveandroider said:
Hello. I can say that the file isnt corrupt because I have flash that ROM a numerous time before. But until the last time when I was flashing custom rom night owl lollypop version, it stuck in boot loop and then when I tried to flash that , it dint work. Now I cant even go to recovery mode.
Click to expand...
Click to collapse
As the log say "<ID:0/003> SetupConnection.." and not move ahead.. there is some connection problem with Phone and PC... Could be a driver problem.. or Kies might be running in the background...
There is no writing of data what so ever.
I tried in another laptop and it worked. My mobile was dead for weeks and its back to life. But I had samsung driver. I dint have Kies installed. dont know was the problem in connection. Anyways thanks to nokiamodeln91 and AutumQueen92 :good:
i have once rooted my N7000 after using for few months, i returned to original Jellybean OS
"""N7000DDLSC_N7000ODDLSC_N7000DDLS6_HOME.tar"""
But now my phone is not working ""No Recovery mode, only download mode""
tried to flash a ""TWRP CWM---PhilZ-cwm6-DDLSC-ODD-5.06.1.tar,,
&,,CF-Root-SGN_XX_OXA_LPY-v5.3-CWM5"" but both failed via ""Odin_v3.04""
now i am middle of nowhere, only samsung logo & an yellow triangle.
Tried to flash original Jellybean OS several times,
""" Custom binary count is (6):crying:
Odin Dispaly this message
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DDLSC_N7000ODDLSC_N7000DDLS6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> factoryfs.img
<ID:0/007> NAND Write Start!!
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Read almost everything, tried everything one thing came across (emmc bug ????), dont want to hard brick my phone, kindly suggest me something to do with my phone,,
plz help me
Kill all kies procesess using task manager if running in the back ground. Use main usb ports, original USB cable.. Try again to flash the Philz kernel using odin 1.85.. If that fails try a different pc. Install the samsung USB driver using this
Thanks for reply Buddy, can you plzz guide me the exact or specific philZ kernel + recovery to flash via odin 1.85...:crying:
i have already tried most of it,,, which i used earlier for rooting my phone....
erosnyx said:
Thanks for reply Buddy, can you plzz guide me the exact or specific philZ kernel + recovery to flash via odin 1.85...:crying:
i have already tried most of it,,, which i used earlier for rooting my phone....
Click to expand...
Click to collapse
Go to Philz kernel thread for n7000 and read the 3rd post.. Links are there.. Try the xxlta version..