Hi guys, i 've got a problem, maybe serious. My S2 freezed. I have a custom jelly bean rom. I took off the battery, tried to turn on, but it stucked on bootloop. Now it only goes on download mode. I used Odin, trying to upload a stock Rom. But each time it failed, stucked as showed:
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It happens with each version of Odin.
It stucks even when i try to upload the .PIT file or a Kernel one, changing all the USB port I have.
I even tried with ADB, but Adb does'nt recognize galaxy s2. I know ADB requires usb debugging enabled to detect your device, but in jellybean, Developer options are DISABLED by default, therefore, usb debugging is disabled too.
Is there anyone who can help me?
Thanks a lot
You cant enter recovery mode? If you have download mode try to reinstall drivers for Phone and try another cable or another pc.
Odin recognized your phone?
mosespl said:
You cant enter recovery mode? If you have download mode try to reinstall drivers for Phone and try another cable or another pc.
Odin recognized your phone?
Click to expand...
Click to collapse
Yes, Odin recognizes my phone, but stucks as i said before. I' ve tried all port usb I have got, and cables too. But, nothing. Maybe another pc...
Related
Yesterday, I installed FFC, and wanted a fresh install so I formatted sd and tried to flash JI6 with it, but flashing failed and whenever I boot, I get the phone icon with dotted line to a computer icon which has an orange exclamation icon in the middle.
The button-based boot into download mode failed. So I made a jig using a microusb plus 120k, 180k, and 1k resistor. But the method still only boots into the same orange exclamation icon from phone to computer icon. It sounds like it's completely bricked. Is there a snowball chance that samsung would still fix this?
Help would be appreciated.
Thanks, Paul
Okay, there are two methods to fix this: first method is more reliable.
First download Samsung Kies, this gives you correct drivers and makes sure you never have a flash that gets interrupted because of bad drivers. Here is the link to samsung kies:http://downloadcenter.samsung.com/content/SW/201101/20110124222256530/Kies_Mini_For_Vibrant_11011_4.exe
1. Now, take out your battery
2. Put the USB cable that is connected to the computer in.
3. Hold down the two volume buttons while keeping the USB cable in
4. Put the battery in while USB cable is in and volume buttons are still held
5. You should find yourself in download mode.
6. Now, put the pit file I have at the end into PIT and the Tar file I have at the end into PDA, happy flashing.
Second method (unreliable but easier)
1. Install Samsung Kies.
2.Having Odin open, plug in your phone into the cpu using USB cable.
3. Hope that Odin recognizes the device, if it does be happy and flash.
4. Now, put the pit file I have at the end into PIT and the Tar file I have at the end into PDA, happy flashing.
FLASH JFD INSTEAD OF JI6 TO GO TO STOCK, JI6 HAS ALWAYS GIVEN ME PROBLEMS, JUST USE JFD. HERE IS THE LINK: http://sourceforge.net/projects/stockodinjfd/files/T959UVJFD.tar/download HERE IS THE PIT FILE: http://sourceforge.net/projects/stockodinjfd/files/s1_odin_20100512.pit/download
Thanks Ali, second method is the only one that worked, however, after flashing (according to odin, it was successful)
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.rfs
<ID:0/005> modem.bin
<ID:0/005> factoryfs.rfs
<ID:0/005> dbdata.rfs
<ID:0/005> param.lfs
<ID:0/005> zImage
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
it reboots and shows the Vibrant text logo and is stuck there for 10 minutes.
Is this normal?
flashed JI6 and now it's working, i think there might be something faulty with the JFD you posted, that or the fact that sourceforge kills my download every 20 second, i had to use a download manager.
anyway, thanks
Tmobile t959 samsung galaxy s vibrant
Hey guys, I had version 2.2 on my phone. I had this phone for about 1.5 years so I figured, why not update a custom flash?
Anyways, so I googled a friendly newbie guide, as I have no experience with phones. I used odin with a custom flash and it failed giving this message:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.rfs
<ID:0/003> modem.bin
<ID:0/003> factoryfs.rfs
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now I cant use my phone at all. I can get back into downloading mode, with the yellow android shoveling, but no matter what i load for a rom file, it always gives me an error. I tried searching endlessly, and I cant figure anything out.
Please, someone, I would really appreciate it if i could get some help. Is there anything I can try? This didnt work from the start...I first thought it was my usb drivers i even updated them but I dont know why I keep getting this fail error message:
Can a mod please delete this? I was doing the stupidest mistake...I was selecting file under PHONE instead of PDA....and I just saw in a youtube video someone selected PDA....as soon as I did that it worked!!!
really bricked phone is solved only by service tools
is not bricked because a really bricked phone will not boot in download mode it's like dead better is to say "is not booting" and the way to solve a "bricked" phone is to flash a stock rom that surely works you have to try many times because you don not know what rom was previously on the phone
1.get a stock rom on sammobile
2.also get corresponding Odin an pit file from there
3.flash by Odin in download mode
if not working try another rom also check if you have Android SDK an Kies make sure you have these tools- you need adb interface working and samsung drivers installed
when in download mode open Device Manager start/run/devmgmt.msc and check if you have adb interface active if not install Odin and SDK then restart PC and try again in download mode...
(don't do anything until you see something like this is Dev Manager -you see this only when phone is connected to PC yes in download mode)
tips
-pit file tells Odin how to flash files on phone in what order and how to so unpack rom and check if you see at least 3 md5 files : CSC/Modem/PDA not all roms are complete don't use a pit file until you have these 3 files in archive
-if Odin says "done" but phone is not booting try to enter recovery and (should work if you downloaded a complete rom ) ...and wipe data/cache/Dalvik-cache then reboot
-if you see ADB Interface connected in Dev Manager it means your phone is in download mode and is not bricked so can be solved ! do not believe me just try !
-if you do not see this install (again) everything/ use another computer and try again! if you don't get a sign this is bricked and send it in service don't lose time
Info:
Samsung Galaxy S 3 GT-I9300 (Europe, Denmark)
everything is stock
I used mskip's unified toolkit for my phone's model and tried to root. I tried searching for this problem but haven't come across one yet.
1. I installed necessary drivers for toolkit to work.
2. Chose Root/Unroot Options > ALLINONE (insecure boot, recovery, root, busybox, restore files)
3. Odin opens and I follow instructions to load the corresponding tar file.
4. I press Start. Odin's message field says:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
5. Odin is stuck here and the phone's screen says "Downloading..." I have left it for 1.5 hours and it hasn't rebooted. I think the file also has not been pushed onto the device.
6. I exit out of Odin, then hold the phone's power button to turn off.
7. I reboot and the phone loads fine. Here, the toolkit tries to push superuser but it gets "device not found" error messages. The toolkit then goes back to the main menu.
8. I retry steps 2-4 but only for an insecure boot image. Again, I get the same results. I also used Root Checker to see if it was rooted. It is not.
Is there something I'm missing? Kies is not running on my PC. Should I use another program to root/install a recovery?
Thanks for reading.
Make sure Kies isnt running in the background.
Try turning off any anti-virus / firewall you have.
mikep99 said:
Make sure Kies isnt running in the background.
Try turning off any anti-virus / firewall you have.
Click to expand...
Click to collapse
I turned off my anti-virus and firewall, and it didn't help. Afterwards, I also tried another USB port, to rule out any COM issues. Again, nothing. I doubt it has anything to do with the USB cable itself since I'm able to transfer files between the PC and the phone's internal storage.
Kies? I'd uninstall it if you have it and dont need it.
USB debugging on?
EDIT - Run ODIN as admin?
mikep99 said:
Kies? I'd uninstall it if you have it and dont need it.
USB debugging on?
EDIT - Run ODIN as admin?
Click to expand...
Click to collapse
I do not have Kies installed. USB debugging is on. This is verified by the toolkit, as it does not let me proceed without USB debugging on.
I am pretty sure ODIN is being run as admin. However, the toolkit opens ODIN for me from a batch file. I am trying one more time, this time using another USB cable.
More info:
Samsung Galaxy S3 toolkit v7.0
which contains Odin v3.07
EDIT:
I changed the USB cable from an older one to the one that came with the phone. This apparently made all the difference. Thank you, mikep99 for all your help.
No problem - glad you got it sorted
Hm. Mine gets stuck at Getting PIT for mapping (Brand new phone, old one broke).
Just trying out a different COM port as well :/ Hope it works some time soon. I HATE the cr*p the German Telekom puts on their devices -_-
Lg
I have a similar problem to yours, slight worse.
My phone was going really slow at one point and decided to un root it, with no success. I only factory reset it and still had the root.
I tried to flash it with the stock thingy and got this message in Odin:
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
I left it like this for an hour maybe, and I got inpatient and pulled the plug (I may think I should shoot myself for the stupidity)
And I got the error: "Firmware upgrade encountered an issue. Please selected recovery mode in Kies & try again."
At that point I tried to root it with the original root I used at first (CF-Root-SGs3-v6.3) and that worked slightly, but now I have the problem where the galaxy s3 logo "freezes" with an red exclamation mark in the top left corner, I am stuck as ****, ****ed up bigtime, halp.
So I was trying to unroot my phone, to be able to play that new mobile nintendo game of all things and in the process of that got myself stuck in a boot loop, with my wits I tried on my own to get my phone out of the loop. With the TWRP recovery thing in hand I had mangaed to complete wipe my device I think. So now, it will load up to the sprint screen and sit there. I can boot up into TWRP and into the download mode; I don't think I can boot into the stock recovery thing. I tried to use Odin to get a OS onto my device but it said this "<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925PVPU1AOCF_G925PSPT1AOCF_G925PVPU1AOCF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
And on my phone it had said
SW REV CHECK FAIL DEVICE 3 BINARY 1
Please help me on this, I would rather not just have a soft bricked phone out of my own stupidity.
also not really sure what fastboot is but I don't think I can access it, When i try to hold the power vol up, down. It just turns the phone off (?) and shows the battery charging.
If you can go into recovery mode you just adb push a rom from your pc.
http://highonandroid.com/android-ro...r-android-in-a-bootloop-with-no-os-using-adb/
StillLiam said:
So I was trying to unroot my phone, to be able to play that new mobile nintendo game of all things and in the process of that got myself stuck in a boot loop, with my wits I tried on my own to get my phone out of the loop. With the TWRP recovery thing in hand I had mangaed to complete wipe my device I think. So now, it will load up to the sprint screen and sit there. I can boot up into TWRP and into the download mode; I don't think I can boot into the stock recovery thing. I tried to use Odis to get a OS onto my device but it said this "<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925PVPU1AOCF_G925PSPT1AOCF_G925PVPU1AOCF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
And on my phone it had said
SW REV CHECK FAIL DEVICE 3 BINARY 1
Please help me on this, I would rather not just have a soft bricked phone out of my own stupidity.
Click to expand...
Click to collapse
When i did this go into twrp and clear delvik. Cache. System
Sd card. And usb check em all coach.
Do it then reboot system and quickly press (power - volume down - and menu key all at once. Download a completely stock rar and install it using odin .
The id005 thing is all good . Dont mess with settings jusy navigate to .tar and flash
ilqs said:
If you can go into recovery mode you just adb push a rom from your pc.
Click to expand...
Click to collapse
As I had said up there I cant boot into recovery mode, whenever I try to my phone just boots into TWRP.
bipolargroup said:
When i did this go into twrp and clear delvik. Cache. System
Sd card. And usb check em all coach.
Do it then reboot system and quickly press (power - volume down - and menu key all at once. Download a completely stock rar and install it using odin .
The id005 thing is all good . Dont mess with settings jusy navigate to .tar and flash
Click to expand...
Click to collapse
I'm not sure I can get a rom in there through Odin, As I had posted up there whenever I tried to do that it gave me that error.
I would really appreciate some help here, been over 12 hours of me trying to fix it on my own. To no avail.
try samsung smart switch. it will download the original firmware that came with the phone and flash it for you..
success123 said:
try samsung smart switch. it will download the original firmware that came with the phone and flash it for you..
Click to expand...
Click to collapse
How do I do that? Does it require my phone to boot?
as digital tumbleweed passes through
StillLiam said:
As I had said up there I cant boot into recovery mode, whenever I try to my phone just boots into TWRP.
Click to expand...
Click to collapse
Did you see the link? If you can access TWRP you are good. Just follow the guide.
StillLiam said:
How do I do that? Does it require my phone to boot?
Click to expand...
Click to collapse
http://samsungsmartswitch.org/ download it from here. put your phone into download mode and follow the steps
download it from here. put your phone into download mode and follow the steps[/QUOTE said:
I tried using Smart Switch and it didn't recognize my phone. I had tried putting my model number and serial number in on it too in the emergency software thing, didn't recognize it.
Click to expand...
Click to collapse
Shooot. Well id do this if you can still get into twrp you really are safe. Click on twrp and i think under Home advamced. Find the fix file permissions. Do it "JUST IN CASE" .i had this happen to me
Then folllow the post here at this link
Click Me Stock Firmware This worked for me when i was Bricked .No os . No nothing . What do you have to lose
ADB Sideload in worst case
Your last but 100% working hope once executed the right way will be the use of ADB Sideload within TWRP which is your obvious recovery. You will need either a SDcard (not for S6 and Edge), a USB with a direct usb cord, or a PC with USB cord to do this. For PC you will need the ADB SideLoad drivers for your phone model to be installed on your PC. Once installed you can connect your phone via USB to your PC and run the ADB SideLoad executable which will run in a CMD window. I don't know the exact commands anymore, but long story short, you want to push the OS install package (Self-installing OS NOT WITH CUSTOM INSTALL MENU) to your phones internal memory which after you'll need to execute by using TWRP. This i have done myself after i hard bricked my S6 edge the first day i got it. I used (by accident) Nand Erase including every other erase to get it back to work which just only put me to more trouble having me to use ADB SideLoad. I hope this bare information helps you out since i can feel the pain you are going through having to know you may have permanently lost your phone lol... Report back if it helped or if you need any more information regarding ADB SideLoad.
- GhostGurio
Try some other original cable. N try flashing via odin.
Also there sometimes u need to flash with pit file. Not sure though.
I had same problem with my s4. Failing at nand write.
In my case cable thing worked.
I have tried flashing the correct firmware (sm-g965f - The firmware I try installing is the one in the folders that say like AP and BL etc..) through Odin and whenever I try flashing that Odin either gets stuck on "Setup Connection", says "Complete(Write) operation failed.", or "Can't open the serial(COM) port." I have reinstalled the Samsung USB Drivers 3 different times, restarted my computer, tried different firmware updates from different websites, different computers, different cords, patched odin, old versions of odin, PC Smart Switch (my device did not show up in Software Emergency Recovery), reinstalled TWRP to no avail. Anyone have a fix? I don't care about saving data or anything, I just want to be in a position where I can attempt to install Magisk again. Also have attempted to reflash TWRP but it just says "
<ID:0/011> Initialzation..
<ID:0/011> FAIL! (DeviceInfo) "
Also when trying to flash firmware it says
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011>
<ID:0/011> FAIL! (DeviceInfo)