Hi guys,
I have a recently purchased Bell Galaxy S Vibrant, running 2.2 JL2.
I installed Kies, updated it to the latest version, plug in my phone and a message says new firmware upgrade available.
So I proceed and everything goes fine until the download mode. I see a little yellow Android construction icon on my phone (looks like in download mode), but on my PC, it always says:
"Failed to Convert to Upgrade Mode".
I have searched the internet for a week and tried everything and anything I found...but still no luck.
Any suggestions? Thanks.
Hi . I bet that the update is KC1 . You can find it here on xda and install it with odin if you can acces download mode ( VOL DOWN + HOME + POWER ).
Hi Omerx,
Thanks for the reply. Yes, it is KC1.
Regarding Odin...I've seen a few people mention it. Are there any downsides to using it? Would it be complicated to upgrade to gingerbread when it finally comes out if I use odin right now?
Also, I have to download the KC1 manually to use odin right?
Thanks.
no downsides: it is actually more transparent than kies on that you as suer set the parameters and identify the files you want to load
check around there are a couple of good threads posted on using odin and the basics of how to root and flash your own phone
kc1 is a good modem and a worthwhile update
hi guys,
I found some tutorial here on odin, but can't seem to find kc1 manual download for a bell vibrant, any suggestions?
Also, when I do it with odin, will it wipe everything I have on the phone (apps, settings, etc)?
Thanks.
nvm i got it to work in KIES finally!
Turns out it just doesn't work on Windows 7. I did the same process on an old XP machine and upgraded flawlessly.
Cheers.
the upgrade to KC1 worked fine on windows 7 64 bit here
This evening, due to some slightly buggy behavior that I attribute to removing too many things during a recent "debloat session", I attempted to restore my rooted N3 to stock using the most current firmware and Odin. Something went very wrong and the flash failed. My N3 now advises that "Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again". So I tried Kies Emergency Device Recovery, but Kies will not connect to my phone in any screen I am able to access. The phone will only boot to the Odin Mode screen. I can't get to the recovery, either.
I've tried Kies in both Windows 7 and Mac OS Mavericks, tried different cables and USB ports, updated Kies as well as drivers, but I'm not making any headway.
I've tried using Kies option to upgrade the firmware, but my N3 doesn't have the S/N printed anywhere on the phone. I'm away from home, but I have a call in to a friend to get the S/N off the box... But I'm not holding my breath that this path will succeed.
I'd bite the bullet and go to Sprint, but as I'm sure you are aware, a rooted Note 3 clearly shows 0x1 under Knox Warranty Void on the Odin Mode screen (which again, is the only screen I can access).
I'm well and truly stuck. Are there any options I'm missing? Something I've overlooked?
nathanotis said:
This evening, due to some slightly buggy behavior that I attribute to removing too many things during a recent "debloat session", I attempted to restore my rooted N3 to stock using the most current firmware and Odin. Something went very wrong and the flash failed. My N3 now advises that "Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again". So I tried Kies Emergency Device Recovery, but Kies will not connect to my phone in any screen I am able to access. The phone will only boot to the Odin Mode screen. I can't get to the recovery, either.
I've tried Kies in both Windows 7 and Mac OS Mavericks, tried different cables and USB ports, updated Kies as well as drivers, but I'm not making any headway.
I've tried using Kies option to upgrade the firmware, but my N3 doesn't have the S/N printed anywhere on the phone. I'm away from home, but I have a call in to a friend to get the S/N off the box... But I'm not holding my breath that this path will succeed.
I'd bite the bullet and go to Sprint, but as I'm sure you are aware, a rooted Note 3 clearly shows 0x1 under Knox Warranty Void on the Odin Mode screen (which again, is the only screen I can access).
I'm well and truly stuck. Are there any options I'm missing? Something I've overlooked?
Click to expand...
Click to collapse
Hi mate try and flash this rom it's like a super rom it fixes anything http://forum.xda-developers.com/showthread.php?t=2461929
It's got me out of trouble a few times
jaythenut said:
Hi mate try and flash this rom it's like a super rom it fixes anything http://forum.xda-developers.com/showthread.php?t=2461929
It's got me out of trouble a few times
Click to expand...
Click to collapse
These seem to be only 9005 and 900 ROMS, ie, not for the N900P (Sprint).
nathanotis said:
These seem to be only 9005 and 900 ROMS, ie, not for the N900P (Sprint).
Click to expand...
Click to collapse
Oh bugger
What about Cwm can you flash that then flash a custom rom
nathanotis said:
...
I've tried using Kies option to upgrade the firmware, but my N3 doesn't have the S/N printed anywhere on the phone.
...
Click to expand...
Click to collapse
My N9005 (and to be honest every single original Samsung phone that I have seen in last year, and the number is pretty big) have BOTH the IMEI and the SN written on a sticker under the battery.
xclub_101 said:
My N9005 (and to be honest every single original Samsung phone that I have seen in last year, and the number is pretty big) have BOTH the IMEI and the SN written on a sticker under the battery.
Click to expand...
Click to collapse
I know where it's *supposed to be*, but the only numbers on said sticker are; DEC, HEX, Model and FCC ID (which I tried, just in case). There is NOTHING else on that sticker.
jaythenut said:
Oh bugger
What about Cwm can you flash that then flash a custom rom
Click to expand...
Click to collapse
Last night I tried flashing the most current firmware and when that failed, I tried an older copy I have that has worked before. Neither succeeded and both result in the Odin screen on the phone saying: "sw rev check fail fused 2 binary 1" (which I've been googling but found no working answers yet).
The message Odin gives is "FAIL! (Auth)". I've read this morning about how the most current firmware (MI3) removes root and plugs some security holes. Some think it won't be rootable...
Is this my problem?
nathanotis said:
This evening, due to some slightly buggy behavior that I attribute to removing too many things during a recent "debloat session", I attempted to restore my rooted N3 to stock using the most current firmware and Odin. Something went very wrong and the flash failed. My N3 now advises that "Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again". So I tried Kies Emergency Device Recovery, but Kies will not connect to my phone in any screen I am able to access. The phone will only boot to the Odin Mode screen. I can't get to the recovery, either.
I've tried Kies in both Windows 7 and Mac OS Mavericks, tried different cables and USB ports, updated Kies as well as drivers, but I'm not making any headway.
I've tried using Kies option to upgrade the firmware, but my N3 doesn't have the S/N printed anywhere on the phone. I'm away from home, but I have a call in to a friend to get the S/N off the box... But I'm not holding my breath that this path will succeed.
I'd bite the bullet and go to Sprint, but as I'm sure you are aware, a rooted Note 3 clearly shows 0x1 under Knox Warranty Void on the Odin Mode screen (which again, is the only screen I can access).
I'm well and truly stuck. Are there any options I'm missing? Something I've overlooked?
Click to expand...
Click to collapse
this happened with me too "Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again".
If you can still go to ODIN/Download mode everything is fine.
Just download the latest firmware for your phone, old firmware won't do as you can not downgrade bootloader. Then flash it in ODIN.
vikas724 said:
this happened with me too "Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again".
If you can still go to ODIN/Download mode everything is fine.
Just download the latest firmware for your phone, old firmware won't do as you can not downgrade bootloader. Then flash it in ODIN.
Click to expand...
Click to collapse
I can get into Odin mode, so that's great news... Unfortunately I tried to flash the most current firmware and got the same result. The failure message in Odin is "Fail (Auth)". at the same time the device says something in red text about a "SW REV" issue.
I'm downloading the most current FW again from Samsung. (WHY DOES IT TAKE SO LONG?!) I'll post back when I try again.
I'm back up and running! I had downloaded a firmware ending in mi3, the MOST current is mj4, which flashed over to my N3 without issue.
Thanks all for the assist.
nathanotis said:
I know where it's *supposed to be*, but the only numbers on said sticker are; DEC, HEX, Model and FCC ID (which I tried, just in case). There is NOTHING else on that sticker.
Click to expand...
Click to collapse
Sprint is CDMA right? CDMA phone got no IMEI.
It got the same purpose of IMEI called MDN or something. But it got NO IMEI.
Try latest stock ROM, coz if you're on newer bootloader, it wont allow you to flash downgrade....
My AT&T S4 was still on 4.4.2 and I wanted to upgrade to lollipop via OTA however everytime I went to software update it kept stating that it was interrupted and failed to update.
I decided to goto the forums and found an update to goto 4.4.4 so I downloaded the tar.md5 file for the NB1 and used ODIN 3.10.6 to upgrade to it however during the upgrade it failed almost toward the end. I rebooted the device and it came up with a soft-brick ( one with the yellow triangle in front) I again looked in the forums and found another link for ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_user_low_ship_MULTI_CERT.tar.md5 and tried to use it with ODIN again and it starts off however toward the end it fails again.
I also tried with I337UCUAMDB_I337ATTAMDB_ATT.tar.md5 but it also failed.
Now the phone is in the soft-brick mode and I am unable to install any of the stock roms using ODIN. I tried multiple different computers and cables and removed the SD card and did multiple resets already.
What can I do to get out of this situation?
Thanks!
So I recently got a Galaxy S4 last night, I rooted it with Kingoroot and it worked great. I then went to sleep and left it alone to wake up to it trying to install a AT&T update and then turning off and booting to a screen that says "Samsung Custom" and does the same processs again.
I have spent more than 2 hours trying to fix this with no avail.
I tried to install stock 4.2.2 but I receive as Fail in Odin which I learned is because you can't install older Android OSes.I then tried to install stock recovery because when I try to boot to recovery it tries to install the update again.
No luck.
I heard of something called a MF3 and downloaded the files but not sure how to use them...
I can still get into Download Mode
This is my main phone so I really need help.
I've read people got soft brick while updating their phones rooted with kingroot!
Try flashing the stock kernel
Google everything before you make sensitive changes in your phone!
Although rooting isnt that sensitive these days!
Sent from my MT27i using XDA Free mobile app
Piyush jaiswal said:
I've read people got soft brick while updating their phones rooted with kingroot!
Try flashing the stock kernel
Google everything before you make sensitive changes in your phone!
Although rooting isnt that sensitive these days!
Sent from my MT27i using XDA Free mobile app
Click to expand...
Click to collapse
After playing around with it, It I am now hit with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I connect to Kies and It claims the Galaxy S4 isnt supported.
PCiE said:
After playing around with it, It I am now hit with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I connect to Kies and It claims the Galaxy S4 isnt supported.
Click to expand...
Click to collapse
Use this guide. You can stop at section 2 if you want to stay at Kitkat or go to section 3 if you want to update to Lollipop.
You can definitely install older versions, but you have to start with a full ROM like NB1. My guess is you flashed an incremental update like NC1, NJ4, etc. so Odin failed. When you Odin though, make sure Kies is completely closed or better yet, uninstall it as they hate each other
PS: This is assuming you have AT&T S4. I have no clue about other variants.
I have a Galaxy S8 SM-G950U on Verizon.
In March I flashed my phone with the following ROM so I could get the S9 messanger,
https://forum.xda-developers.com/galaxy-s8/development/rom-pixelish-s9-rom-custom-snapdragon-s8-t3766891
Everything worked for a few months, including system updates. But as of roughly two months ago I am unable to install any system updates, they always fail. The rest of the phone works fine, its just the updates.
I have tried to use Smart Switch to install the update through my PC, but the process would freeze after downloading the update. The same happened when I tried emergency software recovery through Smart Switch.
I also tried using Verizon's software update utility to both update and recover the phone, but the program would freeze just like Smart Switch.
I have also tried flashing both stock firmware and re-flashing the ROM to the phone with no success. I have tried flashing with the following 4 versions of Odin:
- Odin3-v3.12-PrinceComsy-
- Modded Odin v3.13.1 Raymonf
- Odin3 v3.13.1_3B_PatcheD
- Odin3_v3.12.3
No matter what version I tried, Odin would either outright fail or freeze at either "SetupConnection" or "Intializing". I tried plugging my phone into both USB 3.0 and USB 2.0 ports. I was very careful to get the correct stock firmware for my phone. I downloaded the stock firmware from both sammobile.com and samsung-firmware.org
I also tried simply restting the phone to factory setting both from inside Android and from Recovery Mode.
Does anybody have any clue what might be causing this and what I can do to fix it?
I really dont want to be stuck with a phone that can't get updates.