Hello,
My friend gave me a phone to wipe.
The problem is:
The Pattern is locked due to many attempts. (To many attempts for pattern)
He did try to flash CWM to it but now recovery is not working at all.
At this point he gave the phone to me.
I flashed fresh XEN firmware to the I9001 and the stock recovery is showing up again. But it still isn't working. It says in the bottom of the screen >>> status = 0 <<<
I can scroll through the recovery but even the reboot phone option doesnt work.
How can I perform an full wipe so that the phone doesn't ask for email/password?
I tried SPH-D710.ODIN_WIPE_CACHE_DATA.exe but that does nothing.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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..
And then nothing, After 60 minutes it still hangs here.
Does anybody have some idead how i can wipe it via Odin or ADB?
Please, tell me what XEN firmware is, I've never read it somewhere (in connection to android)?!
Did you find out your I9001 is a special hardware release?
Did you try to flash a custom recovery like ClockWorkMode (CWM) Recovery or TWRP?
Do you want to keep this phone stock?
Greetings
Related
Hi so about a week ago I flashed the 2.3.3 gingerbread bootloaders and stock gingerbread rom using this method: http://forum.xda-developers.com/showthread.php?t=1045734
Then I flashed GR-11, then Continuum v5.3, and then Perception II Beta 3. Then I decided to flash back to stock 2.1 using Odin one click. But now I want to flash the 2.3.3 bootloaders and gingerbread stock rom again by using the same method (http://forum.xda-developers.com/showthread.php?t=1045734), but now everytime i try to reflash them, it fails.
this is what odin says specifically: <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_XWJVB_Sbl.tar.md5 is valid.
<OSM> PHONE_XXJVK.tar.md5 is valid.
<OSM> CSC_NEE_JV3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help? I tried searching for this but could not find it so sorry if there is another thread about this :\
make sure "repartition" is selected" ?
Yes I did that I followed the directions from the link exactly. Am i supposed to pull out the sim card or something?
Just wondering - did you have the phone in download mode?
When i had it plugged into odin, yeah. My phone doesnt have the 3 button fix so i had to use adb reboot download and then i disconnected it and opened odin and plugged it back in. Should i just use my jig to put it into download mode instead of using adb because that could interrupt it or something?
Switch usb ports on your pc, make sure it's on the back connected to the motherboard, not a front port our a hub.
I tried that too with no luck :'(
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)
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:
hi i think my phone was bricked
the phone can not started anymore logo samsung then logo orange (france) again and again
i have no access to the recovery only the download mode the phone is recognized by the pc
i try to flash a stock rom via odin but it stuck at the step initialization
i try two different cable different odin different stock rom
i try t flash a recovery
but always them result can you help me please
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G800FXXU1ANL1_G800FFTM1ANL2_G800FXXU1AOC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
I have the same issue with my wife's phone. Yesterday all of a sudden the phone rebooted and now we can't pass the Samsung logo.
I can't boot into recovery, but i can boot into Download mode. The problem is I can't use ODIN to re flash the phone or do something since it gets stuck in "Initialzation".
Hi iam still at the same issue
I have test many solution but nothing work for my phone
Maybe you will have more chance
Same to problem G800H dualism. How to fix it . when I cunnect my pc with USB then show zelus driver.