Hey,
I got my Nexus S stuck in a boot loop and my power button is broken too.. I also failed to check usb debugging while I was still able to boot, so I guess adb isn't going to find my device.. (already tried that, but even Windows/Ubuntu doesn't seem to recognize my device). Will I ever be able to get out of this boot loop?
You should try the usb jig.. Is a little device that brings the the phone to download mode.. You can then flash any rom with odin..
You can find the jig here..
The download mode. Just to know what to expect..
Okay, I bought the jig. It was delivered pretty fast
But I tried Odin, the way it should work (official firmware for I9023 which is my model), it worked (or at least I thought it did) because it gave me this:
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Bootloader_I9023XXKA3.tar.md5 is valid.
<OSM> PDA_SOJU_GRJ22_TMO_EUR_MR2_SIGNED.tar.md5 is valid.
<OSM> MODEM_I9023XXKD1_REV_00_CL990283_SIGNED.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> bootloader.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> userdata.img
<ID:0/003> radio.xx.img
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response form LOKE
<ID:0/003> dgs.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
My phone rebooted and the home and search button lighted up, then only the menu key and the back key joined not that long after that. But nothing on my screen or anything. So I guess I really killed it. I've let it sit there for about 10 minutes, then pulled the battery out and tried rebooting, but the same procedure started and nothing else really happened..
I had this problem with the back and the menu keys not working and was solved with factory reset..
Apparently I just flashed the wrong firmware.. Got mine from samsfirmware.com or whatnot. But after a few hours of endless Googling I found this:
tsar300[dot]com/Joomla/index.php?option=com_content&view=article&id=629:samsung-i9020-i9023-google-nexus-s-firmwares&catid=55:samsung&Itemid=82 (can't post URLs yet..)
the GRI40 worked for me Now it's up and running again and going smooth as butter hope I can help a few people with this.
I got a Samsung Galaxy Tab (GT-P5110) of which the tablet did not startup anymore, and know nothing about the prehistory.
I downloaded stock firmware from samsung site: http://samsung-updates.com/device/?id=GT-P5110
and downloaded the latest EUR version named : P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5
With Odin 3.07 I installed that image in download mode with default options left on. After that I got the following screen message on the tablet:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Probably something went wrong. Then I downloaded Kies from samsung site, installed it with all extra drivers and I got the problem that Kies never recognized the tablet. Reinstalled many times, tried different options, but the problem persisted (took me 8 hours totally). Battery of the tablet was fully loaded and before this problem I saw that it was loading correctly.
Then I read this excellent document : http://forum.xda-developers.com/showthread.php?t=1652398
Tried again with Odin 3.07 and 1.85 and could install the image with only the reboot option on in Odin, flashed successfully the image, but still the problem:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I do not have much options left to look for. I was thinking about:
- driver issue
- wrong image
- wrong method
Can somebody help me to have this problem fixed ? I am willing to reinstall Windows 7 on this laptop.
Really nobody knows ?
never had problems here on Windows 8.
Maybe try flashing using Heimdall
But will I need a Heimdall image for that, because it does not accept the samsung image.
proconsoles said:
But will I need a Heimdall image for that, because it does not accept the samsung image.
Click to expand...
Click to collapse
But will I need a Heimdall image for that, because it does not accept the samsung image.
But when I use Odin 3.07 it looks like everything went fine:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But when I disconnect the usb cable after that, and hold the power button for a couple of seconds I still see:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
What could be the cause of this ?
proconsoles said:
But will I need a Heimdall image for that, because it does not accept the samsung image.
But when I use Odin 3.07 it looks like everything went fine:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But when I disconnect the usb cable after that, and hold the power button for a couple of seconds I still see:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
What could be the cause of this ?
Click to expand...
Click to collapse
I am located in The Netherlands, and downloaded the specific image for the Netherlands, region PHN, used Odin 3.07 to install it, but still the same problem.
What can I do, wait for somebody who can give me a hint ? This is the first time I do a recovery of a Samsung tablet, and don't know how to continue with it.
Your help will be very much appreciated.
Maybe not the ideal situation, but try installing a custom recovery and a custom rom
If this works, it's no hardware problem.
You can use this guide to install a custom recovery
Joery360 said:
Maybe not the ideal situation, but try installing a custom recovery and a custom rom
If this works, it's no hardware problem.
You can use this guide to install a custom recovery
Click to expand...
Click to collapse
I got still the same problem, did exactly this procedure : http://forum.xda-developers.com/showpost.php?p=50174804&postcount=3
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_CWM_6.0.4.7_Swipe-Edition.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
Even reinstalled the drivers, but the problem remains the same, still keeping the message:
Firmware upgrade encountered and issue. Please select recovery mode in Kies & try again.
proconsoles said:
I got still the same problem, did exactly this procedure : http://forum.xda-developers.com/showpost.php?p=50174804&postcount=3
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_CWM_6.0.4.7_Swipe-Edition.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
Even reinstalled the drivers, but the problem remains the same, still keeping the message:
Firmware upgrade encountered and issue. Please select recovery mode in Kies & try again.
Click to expand...
Click to collapse
Do you think that this problem is hardware related ??
Nobody knows ?
Same for me
I'm dealing with almost the same issue, except for my ODIN flashes it doesn't even succeed. I know this happened to it after I tried to use heimdall to update my CWM, but I have had no success getting anything to work. I've been without a tablet for like a week now, doing everything I can think of or find a walk through for. I mean for me, I wouldn't mind going back to stock as long as it works again. Here's what my ODIN is doing:
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm about to try the TWRP someone recommended above, I'll let you know how it goes
---------- Post added at 08:25 PM ---------- Previous post was at 08:20 PM ----------
I tried flashing a different version of TWRP and it looked like it was going to do something, but it isn't going. Here's what it did this time:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_TWRP_2.7.0.1.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..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Forgot to mention that I'm using Odin 3.09 on a p5113. Not that it makes huge difference.
Two things to try:
If you can boot into recovery, try the factory reset.
If not, have you tried Kies recovery mode?
The problem is that I can only boot into the special download mode, if I could get into recovery I think I could figure it out. I have tried the kies recovery, but it won't even read the device.
Maybe because Samsung / KIES Process running in background on your PC?
A Case of bad partitions
Deucethehero said:
The problem is that I can only boot into the special download mode, if I could get into recovery I think I could figure it out. I have tried the kies recovery, but it won't even read the device.
Click to expand...
Click to collapse
Try flashing with .pit file, partitioning set to on. Should correct partition problems. Somebody might have installed a non-android OS that botched. Look for a .pit file around the forum, you should find one. Good luck.
Thank you
Thanks for the tip, I'll give it a shot and post back with results!
Sorry for the late reply
Hey guys, I could have sworn that I posted back on Friday, but it's not here. Anyway, it's been a crazy few days for me traveling and school starting and all that.
About the tablet, I downloaded a pit file and it looked like it was going to work, but unfortunately it did not. I'm working on getting the tablet charged and set up to try again because I got a zip that had 2 pit files, so I'll try the other one soon. I'll post the results when I get them, thanks again for all the help!
Still not working, but I think some progress
Sorry to take so long responding, it's been a busy week.
So I just attempted to flash the .pit again, and it failed. Here's what Odin gave:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
It says, "There is no PIT," but that's what I'm trying to flash, right? I'm a little confused, but I hope someone knows what that means.
Thanks for all the help guys!
New info!
So today I was messing around with the .pit file that I had, and I used an editor to make it exactly the same as one I found in another forum. After Odin told me that it failed, I went to reset the tablet, and it showed me the Galaxy Tab 2 screen, which it has not done for a few weeks now. Then I plugged it in and it shows the battery charging symbol. Currently it is a 18%, so I'm going to let it charge and then try booting it up again and see what I get. Hopefully all is well now, but we shall see here in a few hours.
I also was not aware that I needed to flash the system along with the pit, and once I had that going it made a little more sense to me.
I'm going to try to post that pit here if anyone wants it. Hopefully it will help someone else in the future.
Odin Flashed, but failed
So I got into normal old download mode on the device using that .pit file. Yay! However upon attempting to flash the stock os back on Odin gave me this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5113UEBLH3_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> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm going to look into other avenues, but this did set me back to the "Firmware upgrade encountered an issue... blah blah"
Hello, I have serious problem can't flash any rom via odin 3.10.7 I tried yesterday and flash G920FXXU3COI9_G920FOXX3COI6_XEO
Today I tried install BTU and odin giving me sth like that. Cant update any new oryginal rom... Softbricked
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can't update vie SmartShare - device unknown.
Please help!
First a question since I am not very familiar with models, is the device G900F or G 920F, because fw is for 920 and title says 900.
Put phone in download mode:
Vol down+Home+Power button
then Vol Up to confirm Download mode after entrering dl mode.
In Smart Switch go to more, and choose Initialization from drop down menu, type model e.g. SM-G900F, s/n from back of the phone, and wait till it finishes download and flashing.
Then try flash TWRP and rom through Odin.
Hope that helps.
Hello at all!
First: Sorry for my english. I'm from Germany,but I hope you understand me. I these Forum I think you get the best tips,so I'm here.
My Device: A Samsung Galaxy S3 / GT-i9305
I got a big,big problem with my Phone. I wanted to root it at the beginning ... it doesn't match,because I had Android 4.4.4 and I don't find a solution,do root it with thissystem. So I wanted to downgrade it to a lower version. After ring this my device don't start, it hangs at the Samsung Logo (bootloop) and there is no recovery mode. Download Mode works just very rarely - I don't know the reason why.
If i get it to the Download Mode, I tried to flash in Odin Android 4.4.4 , but all the time there is the same message. You see here:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXBMD5_I9305DTMBMD1_I9305XXBMD5_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> SingleDownload.
<ID:0/003> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It shows every time the same error with 'sboot.bin'.
Now I bought a USB Jig to get at least to download mode.
Is there any solution or Idea to run my good,old S3?
I would be very thankful if someone could help me with my problem.
Sorry for my english, but I hope you know what I want to say
Nice Greets,Postmaschine