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:
Related
I was trying to root my galaxy note, I download the rooted stock rom (N7000DXLC2) from here http://forum.xda-developers.com/showthread.php?t=1535025
but the odin failed and showing this
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Rooted_Stock_Odex_N7000DXLC2.tar.md5 is valid.
<OSM> MODEM.tar.md5 is valid.
<OSM> CSC_N7000OLBLC2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> factoryfs.img
<ID:0/013> NAND Write Start!!
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
then my phone can't boot anymore, it jus stuck at the samsung n7000 screen,
i tried to download stock rom and flash again, but it failed like above,
and when i go try to flash the kernel, it success to go to the recovery mode,
but it showing error like
E:Error in /cache/recovery/sec_csc.zip (status 7)
And i maybe forgot to enable usb debugging before i root, is this the cause? how i enable it now?
what can i do now? I tried to change port, change pc, uninstall kies, reinstall driver, close antivirus, and all doesn't work, please help...
To be sure, take out all unnecessary USB devices and use a USB port that's directly attached to your motherboard. Without your phone attached load Odin and load all files. Put the phone in Download mode and hook it up to your pc. When Odin recognizes it then try and flash again.
Make sure there's not a trace of Kies on the pc, just have the drivers installed.
USB debugging should not have to be enabled. There's no way of enabling it without booting up the phone and setting it in the options anyway.
bioweb said:
To be sure, take out all unnecessary USB devices and use a USB port that's directly attached to your motherboard. Without your phone attached load Odin and load all files. Put the phone in Download mode and hook it up to your pc. When Odin recognizes it then try and flash again.
Make sure there's not a trace of Kies on the pc, just have the drivers installed.
USB debugging should not have to be enabled. There's no way of enabling it without booting up the phone and set it in the options anyway.
Click to expand...
Click to collapse
I tried that, and I uninstalled the kies,
but the odin still showing the same error.
PROBLEM SOLVED
for who facing the same problem, just include a pit file in PIT,u can find it here
http://forum.xda-developers.com/showpost.php?p=23234683&postcount=10
solving this for whole day,thanks god it worked......
17n337 said:
PROBLEM SOLVED
for who facing the same problem, just include a pit file in PIT,u can find it here
http://forum.xda-developers.com/showpost.php?p=23234683&postcount=10
solving this for whole day,thanks god it worked......
Click to expand...
Click to collapse
CAUTION : Just dont go on blindly flashing the PIT file. Its a repartitioning file. To be used only when your partition is corrupted.
Galaxy Note stuck
hello,
I was running stock ICS 4.0.4 on my GT-N7000. I rooted my device. Took the titanium backup.
After this, i opened odin. Under phone i provided the path to my downloaded ICS 4.0.4 file. Odin started flashing the device but operation failed showing:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> factoryfs.img
<ID:0/010> NAND Write Start!!
<ID:0/010> Transmission Complete..
<ID:0/010> Now Writing.. Please wait about 2 minutes
<ID:0/010>
<ID:0/010> Receive Response form LOKE
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried many times but showing the same error everytime.
I am not able to go into the recovery mode......although i can go into the download mode.
When i reboot it says "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." There is no samsung logo or GT-N7000 logo when you reboot your phone. You only see this warning.
I have some imp data on my internal memory(Phone storage). I have to save that data. Please please please help me out. Is there any way to recover phone storage data???
Can anyone explain my current situation...???
vinay28761 said:
I was running stock ICS 4.0.4 on my GT-N7000. I rooted my device. Took the titanium backup.
...
After this, i opened odin. Under phone i provided the path to my downloaded ICS 4.0.4 file. Odin started flashing the device but
...
<OSM> N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 is valid.
...
Can anyone explain my current situation...???
Click to expand...
Click to collapse
First: this thread is marked as solved since april. Chances are very low for a reaction (but at least I did)
Second: Make a new one in Q&A
Third: What do you mean with "Took the TB"? Especially when you flash a new Stock Rom after
Fourth: Did you put the tar-file under "Phone"? Should be "PDA".
Fifth: Read a lot in the stickies here - good start for handling Odin is Dr. Ketan's thread
Sixth: your current situation might result from not reading enough. I hope you didn't brick your device and can restore a running Rom with the instructions from the stickies. Good Luck
how exactly did you reach this situation?
Did you resolve this ?
vinay28761 said:
hello,
I was running stock ICS 4.0.4 on my GT-N7000. I rooted my device. Took the titanium backup.
After this, i opened odin. Under phone i provided the path to my downloaded ICS 4.0.4 file. Odin started flashing the device but operation failed showing:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> factoryfs.img
<ID:0/010> NAND Write Start!!
<ID:0/010> Transmission Complete..
<ID:0/010> Now Writing.. Please wait about 2 minutes
<ID:0/010>
<ID:0/010> Receive Response form LOKE
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried many times but showing the same error everytime.
I am not able to go into the recovery mode......although i can go into the download mode.
When i reboot it says "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." There is no samsung logo or GT-N7000 logo when you reboot your phone. You only see this warning.
I have some imp data on my internal memory(Phone storage). I have to save that data. Please please please help me out. Is there any way to recover phone storage data???
Can anyone explain my current situation...???
Click to expand...
Click to collapse
@vinay28761
I have your exact problem. Phone came to me with problem of hanging on Samsung N7000 Logo.
After flash everything, it shows error, exactly like yours.
Were you able to fix it? How ?
dannyogolo said:
@vinay28761
I have your exact problem. Phone came to me with problem of hanging on Samsung N7000 Logo.
After flash everything, it shows error, exactly like yours.
Were you able to fix it? How ?
Click to expand...
Click to collapse
Yes, i resolved it. I just followed dr. ketan's guide to flash through ODIN properly and exactly as described. I would request you to do the same.
Hope it solves your error too. If not, please post your screenshots.
could you jst give me details about dis nand write fail problem?i m having same problem in my gt n7000
Does anyone know where i can download PIT file for samsung gts6802 and a bootloader?
It woulb be very helpful. Thank You
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
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
Hello,
I have I rare problem. I tried to flash a new ROM and it failed, so now the phone is stuck on the boot image. Ok, usualy I would have solved this with CMW 3 button recovery combination, but my phones Home button is broken so I cannot acces it, but I made the USB Jig and can acces download mode.
My question is how do I unbrick my phone?
What I tried: Using SDK tools to reboot the phone in recovery with ADB, no succes. Sdk doesnt see my device.
Something called Fastboot, but from what I read Samsung doesn't have such a feature for the phone to enable.
Thank you.
I had the same problem a couple of time ago, but all 3 buttons were defect (see my signature ).
What I always did:
when you can get in download mode then restock via odin and phone will boot again.
Here is slappys rescue kit what i always use when i have to restock.
Unzip it and flash the Rom via Odin. There is also a txt file with a guide included.
http://forum.xda-developers.com/showpost.php?p=29114573&postcount=2
With this flashed rom you will have in the power down menue the funktion: back to recovery or back to download. So first time go back to download mode or use usb jig again and then flash the included root kernel.
Then flash the rom of your choice.
If you would go to jelly bean i would recommend to use Mackays 1.3.0. first. Because you have to flash JB twice or even 3 times and after the first flash of this Mackay it goes automatically back in recovery mode.
Link to older Mackay Roms:
http://www.xdafileserver.nl/index.php?dir=Samsung/Galaxy+S/MackayROM/JB41/old
After flashing this you could go to google play and download an app for softkeys for example softkeys for root users.
After that and if you want or like you could flash also a JB rom with included virtual softkeys, like for example SLIM. You have to enable the navigation bar in settings but after that you can use your phone quite normal.
Hope this helps and wish you a good success!
How long should it last to restock with odin?I'm waiting for about 30m and nothing. Still says Do not turn of target! No Loading bar n phone or Odin showing any progress. What is wrong?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> EZbase-PHONE-XXJVO.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!!
Solved it. I was using the USB port in front of the Desktop unit and i guess it doesn't have enough voltage. Worked when i switched to the back USB port. Thanks a lot man!! You saved my phone !
rahbert said:
How long should it last to restock with odin?I'm waiting for about 30m and nothing. Still says Do not turn of target! No Loading bar n phone or Odin showing any progress. What is wrong?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> EZbase-PHONE-XXJVO.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!!
Click to expand...
Click to collapse
rahbert said:
Solved it. I was using the USB port in front of the Desktop unit and i guess it doesn't have enough voltage. Worked when i switched to the back USB port. Thanks a lot man!! You saved my phone !
Click to expand...
Click to collapse
Great and Strike . Glad i could help and you can use your phone again!
Have fun with it and enjoy...perhaps JB?!
Hello everyone,
im having some issues with my GT 9001.
Im running a custim rom With 2.3.4
Kernel 2.6.35.7-perf [email protected] '1
Buildnumber Gingerbread.XXKP4
I want to go back to my stock Rom. I'Ve Downloaded the newest Firmware from Sammobile together With odin.
When i now Start to flash it always end up with
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9001BOKQ4_I9001BOKQ3_I9001DTMKQ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Complete(Write) operation failed.
<ID:0/010> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
I've already tried that with different Cables and Computers always the same Message.
After this doesn'T worked i'Ve tried to install any custom Through CWM.
On this example i tried to Install the new Cyangemod via CWM.
Im getting the following Errors that way.
s1.directupload.net/images/130421/fzakpov4.jpg
I hope anyone can help me to install any other rom
Thx
Gh0stwind said:
Hello everyone,
im having some issues with my GT 9001.
Im running a custim rom With 2.3.4
Kernel 2.6.35.7-perf [email protected] '1
Buildnumber Gingerbread.XXKP4
I want to go back to my stock Rom. I'Ve Downloaded the newest Firmware from Sammobile together With odin.
When i now Start to flash it always end up with
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9001BOKQ4_I9001BOKQ3_I9001DTMKQ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Complete(Write) operation failed.
<ID:0/010> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
I've already tried that with different Cables and Computers always the same Message.
After this doesn'T worked i'Ve tried to install any custom Through CWM.
On this example i tried to Install the new Cyangemod via CWM.
Im getting the following Errors that way.
s1.directupload.net/images/130421/fzakpov4.jpg
I hope anyone can help me to install any other rom
Thx
Click to expand...
Click to collapse
First of all, it is I9001. Second, you need a custom recovery, check out the one in my signature (yes it is a link, you can click on it). You definitely didn't install it from CWM!!!
I don't know much about Odin.... Try the one's on our wiki (the phone name in my sig -- ALso a link.)
ps. Please be a bit more specific next time you post, like what custom rom you installed and what version of CWM, etc. It makes it that much easier to help:silly:
Thank you for the Help.
I've installed the New Arisve and it seems to work.
The update CyangenMod seem to work now. Its starting with the CyangenMod right now. Hope everything will work now.
Edit: The Cyangenmod is now stucked at the loadingscreen from cyangenmod. I already flashed it again Via CWM and still the same stuck on loading screen.
I tried to flash the Rom from the Signatur of stepie22.
Flashing a Stock rom via Odin still doesn't work. Got the Same error mentioned in the starting post.
@Gh0stwind There is a bit of a language gap here, so correct me if I'm wrong here. What you're saying is:
I've installed the New Arisve and it seems to work.
Click to expand...
Click to collapse
Flashing a Stock rom via Odin still doesn't work. Got the Same error mentioned in the starting post.
Click to expand...
Click to collapse
You've tried to flash stock rom via ODIN, but you got the same error
The update CyangenMod seem to work now. Its starting with the CyangenMod right now. Hope everything will work now.
Edit: The Cyangenmod is now stucked at the loadingscreen from cyangenmod. I already flashed it again Via CWM and still the same stuck on loading screen.
I tried to flash the Rom from the Signatur of stepie22.
Click to expand...
Click to collapse
You've got it working somehow, not it hangs at the boot animation.
------------------------------------------------------------------------------------------------------
Could you try to take some pictures of your phone??? Like in recovery, where you said it's stuck, etc., just sothat I can see what's going on, that I don't have to guess. Doesn't have to be great resolution, just more or less see what's going on.
EDIT: Try the odin and stuffs from the wiki page (also in my sig)