Database Users

[help] "firmware upgrade encountered an issue"

I was trying to install an Official Stock Samsung Galaxy S4 GT-I9505 firmware, from SAMMOBILE Link for the firmware I tried to use: http://www.sammobile.com/firmwares/3/?download=26516. So while flashing it with ODIN, I think it just randomly disconnected, but that just bricked my phone. I don't know whether it is a soft brick or a hard brick, but this is what happens to my phone, every time I turn on my phone whether it's done normally, the download mode or recovery mode method I will be stuck on that screen.
So now I typed in the error on Google to see how it can be fixed. Link to the method to fix the error: http://androidcentral.us/2013/09/how-to-fix-firmware-upgrade-encountered-an-issue-on-kies/
Firstly, my computer (running Windows 7 ULTIMATE 64-BIT) can detect my phone, saying the drivers have been installed successfully. However KIES doesn't detect mine. Anyways I still try to do this method where I have to go to Tools -> Firmware Upgrade and Initialization on KIES. I type in my model name: GT-I9505, that works, now I have to do my S/N or Serial Number: RF1DXXXXXXX, so when I press OK it says GT-I9505 doesn't support 'Intialising', so I am stuck have no idea what to do.
Also, while flashing I tried repartition my S4, to remove all of the stuff I had, none important, except my music which I transferred to my PC. Solved, just flashed Official firmware, it now works.
Just separately repartitioned my S4, it works but S4 is now stuck on boot loop, so have to flash a 4.4.2 Official Firmware.

Harnessful said:
I was trying to install an Official Stock Samsung Galaxy S4 GT-I9505 firmware, from SAMMOBILE Link for the firmware I tried to use: http://www.sammobile.com/firmwares/3/?download=26516. So while flashing it with ODIN, I think it just randomly disconnected, but that just bricked my phone. I don't know whether it is a soft brick or a hard brick, but this is what happens to my phone, every time I turn on my phone whether it's done normally, the download mode or recovery mode method I will be stuck on that screen.
So now I typed in the error on Google to see how it can be fixed. Link to the method to fix the error: http://androidcentral.us/2013/09/how-to-fix-firmware-upgrade-encountered-an-issue-on-kies/
Firstly, my computer (running Windows 7 ULTIMATE 64-BIT) can detect my phone, saying the drivers have been installed successfully. However KIES doesn't detect mine. Anyways I still try to do this method where I have to go to Tools -> Firmware Upgrade and Initialization on KIES. I type in my model name: GT-I9505, that works, now I have to do my S/N or Serial Number: RF1DXXXXXXX, so when I press OK it says GT-I9505 doesn't support 'Intialising', so I am stuck have no idea what to do.
Also, while flashing I tried repartition my S4, to remove all of the stuff I had, none important, except my music which I transferred to my PC.
Just separately repartitioned my S4, it works but S4 is now stuck on boot loop, so have to flash a 4.4.2 Official Firmware.
Click to expand...
Click to collapse
Hi,
Can you get into recovery?
Can you still see your phone in odin?
If so , disable kies (task manager) and try to flash the firmware again.
Wipe data and cache before and after flashing firmware.

[Q] i9505 Soft Brick Help - Stuck on Samsung logo (Rooted)

Okay first post on this website.
4.4.2, i9505
So, as i am a compete android n00b, i rooted my s4 with the KingoRoot tool as i thought it was an easy method, later i found out ChainFire made an easy auto root .
After i rooted with the kingo my device would randomly reboot, when i called someone, when i locked my phone and random stages throughout the day.
After some reading online i found the solution was to re-flash my phone to stock fireware. so i downloaded odin, drivers, fireware from sam and tried to re-flash it. however my phone failed after aboot.mbn. I then got the unexpected error saying the phone had to be plugged into kies etc.
I then used "philz_touch_6.07.9-i9300.tar.md5" to get rid of the error message which worked. however the phone still would radnomly restart.
Again i turnrf to the web to find a solution for the radnom booting and found this -
http://forum.xda-developers.com/showthread.php?t=2514703
telling me to delete everythinhg knox basically. after deleting everything outlined my phone is now stuck on the samsung logo.
i cannot access recovery mode! however can access download mode. but i have tried multiple times to re-flash to stock firmware to no avail...
Help, please
Recap
- Stuck on samsung logo
- Cant access recovery mode
- Can access download mode
- Deleted everything knox as specified
Thanks, Dylan

1. The error that give u ODIN is coz you are trying to flash an older firmware that the one you have installed in your device.
2. You have to flash a STOCK recovery. Flash this file via ODIN in PDA/AP (like in the pic 1 attached): HERE.
3. Turn off your device manually when the process finish. Boot it into STOCK RECOVERY by pressing and holding Volume Up, Home and Power.
4. Take a look the CSC (pic 2). "Applied the CSC-code: ............" <- This is your REAL CSC. Turn off your device again manually and boot it into DOWNLOAD MODE by pressing and holding Volume Down, Home and Power.
5. Go to Sammobile and download the LATEST firmware for your device with correct CSC and flash it via ODIN.
6. About KNOX and reboots: Delete all KNOX reminds less "Lib = libknox_encryption.so".
7. Good luck

6.0.1 bootloader back to 5.1.1

Does anyone know if it is possible to downgrade back to 5.1.1 bootloader after flashing the 6.0.1 one?
With the Note 3 I lost the imei and baseband etc trying to downgrade certain bits, so I don't want the hassle if that is going to be the case with 6.0.1 and 5.1.1.

i tried flashing also 6.0.1 and ended bricking my phone. would love to see if you find a solution for that.

mrelie007 said:
i tried flashing also 6.0.1 and ended bricking my phone. would love to see if you find a solution for that.
Click to expand...
Click to collapse
Can you still get into download mode?
When I put bobcat rom on mine I didn't change the bootloader to the older one, I was stuck on the s6 edge+ bootscreen, I have to plug USB into pc and then hold the power+home+vol down for a few seconds and that rebooted into download mode where I managed to flash the correct bootloader. You can also then restart the phone and use power+home+vol up to get into recovery to restore a back up. Not sure why I had to plug in USB cable though but if I didn't I couldn't reboot at all and was stuck on the bootscreen.

hi yes i can go in download mode and i can go in twrp. but flashing a new rom always fails for me. stock firmwares as well. can u attach me ur bootloader plz so i can try it?

https://mega.nz/#!ScsAwbIC!hH4Djamv7FoeAUyDbHElKjaIlXLqvTZynPRqdJPwDas
This is the link to the bootloader I used (taken from bobcat thread)
Use download mode and put it in the BL part in odin.

can help me with bootloader 5.1.1
sm g928c

My Galaxy S5 appears to be unflashable/unrootable, any advice?

Hi,
I recently got me a Galaxy S5 (SM-G900F) and the first thing i wanted to do was installing CM13 as I always do with my new phones. However, when i followed te steps on CM wiki using Heimdall to flash TWRP the blue bar of the downlaod mode increases a small bit, then stops and in the command promt it says something about error with finding PIT. After trying this for three times i decided to go with Odin, which I do prefer anyways.
I tried flashing TWRP , the blue bar is filling to 100% but then on the little screen where Odin usually states FAIL! or PASS! it just says RESET! and my phone is restarting. Shortly after it restarded you can see the RESET! turning to PASS!, but when I tried checking in TWRP is installed, it wasn't. I tried it again and then Odin suddenly says FAIL! After restarting my phone it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I couldnt even enter download mode anymore till I tried if getting out the battery would work. I could enter download mode again and flashed the same TWRP on my phone again, and aigain it says RESET! but after that my phone worked again. I tried flashing with another version of Odin and TWRP but same thing happened - First run it said RESET!, second run FAIL!.
I thought maybe rooting the device and installing TWRP via their app afterwards could do the trick. So i tried flashing Autoroot with Odin but it made my phone showing a screen with Samsung logo and in the upper left corner something about recovery mode, seemed to be a loop/freeze. So i took out the battery again and flashed TWRP and that solved the problem again. At last I tried rooting by using TowelRoot but it says the service is not available for my device, even though S5 is listed as a supported device.
I really have no idea what to do anymore, would be very grateful if someone could come up with a solution.
BTW: Is it possible to flash CM13 without using custom recovery by using stock recovery?
Greetings
Khalitas

Khalitas said:
Hi,
I recently got me a Galaxy S5 (SM-G900F) and the first thing i wanted to do was installing CM13 as I always do with my new phones. However, when i followed te steps on CM wiki using Heimdall to flash TWRP the blue bar of the downlaod mode increases a small bit, then stops and in the command promt it says something about error with finding PIT. After trying this for three times i decided to go with Odin, which I do prefer anyways.
I tried flashing TWRP , the blue bar is filling to 100% but then on the little screen where Odin usually states FAIL! or PASS! it just says RESET! and my phone is restarting. Shortly after it restarded you can see the RESET! turning to PASS!, but when I tried checking in TWRP is installed, it wasn't. I tried it again and then Odin suddenly says FAIL! After restarting my phone it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I couldnt even enter download mode anymore till I tried if getting out the battery would work. I could enter download mode again and flashed the same TWRP on my phone again, and aigain it says RESET! but after that my phone worked again. I tried flashing with another version of Odin and TWRP but same thing happened - First run it said RESET!, second run FAIL!.
I thought maybe rooting the device and installing TWRP via their app afterwards could do the trick. So i tried flashing Autoroot with Odin but it made my phone showing a screen with Samsung logo and in the upper left corner something about recovery mode, seemed to be a loop/freeze. So i took out the battery again and flashed TWRP and that solved the problem again. At last I tried rooting by using TowelRoot but it says the service is not available for my device, even though S5 is listed as a supported device.
I really have no idea what to do anymore, would be very grateful if someone could come up with a solution.
BTW: Is it possible to flash CM13 without using custom recovery by using stock recovery?
Greetings
Khalitas
Click to expand...
Click to collapse
RESET! is basically the same thing as PASS! What version of TWRP are you installing? The keis screen you got is the same as download mode. Why are you using heimdal? your idea to go with Odin was a good one. Anyways, download TWRP 3.0.2 (not 3.0.2-1 or 3.0.2-2 as they are buggy) and flash it in Odin, reboot to recovery and install the ROM you like, of course following its specific install instructions. No, you cant install a custom rom with stock recovery

Thanks for your answer, meanwhile i managed to fix this problem. Had to flash the latest Firmware because twrp (could just install the oldest version otherwise I had no option to boot into recovery at all) said no OS installed. After rooting via Odin worked like it's supposed to.
Why did I use Heimdall? Because I wanted to stick to CM-wikis instruction and they used Heimdall.

S7 Edge G935F // Faulty ODIN flash // Stuck in Bootloader [SOLVED]

Hi Guys,
today I wanted to flash the latest Stock ROM for my device via ODIN. I've done this many times before and (thought) I knew what I was doing. It is my third Phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly I wasn't aware that this particular device was locked.
After downloading the international firmware I tried to install it and ODIN got stuck while writing the system.img. After that my phone did not boot up (of course). After that I downloaded and tried to isntall the firmware of the carrier, but I had the exact same issue. When I turn my device on I get to an error screen which tells me to execute an "emergency recovery" via the Samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
FRP hinders me to install a custom recovery and the stock one does not allow any isntallations via ADB or SD card.
My qustion is: Does anyone know how I can install a rom from here?
I know that I had to have made some changes prior to the flashing, but as I said I was not aware and an Idiot for not double checking.
Since it is not bricked yet I suppose there must be an answer but I can't find anything.
Thanks in advance
Edit:
After only installing the stock bootloader, I am autmaticly entering it when I boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"

Fix
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.

fabivons said:
hi guys,
today i wanted to flash the latest stock rom for my device via odin. I've done this many times before and (thought) i knew what i was doing. It is my third phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly i wasn't aware that this particular device was locked.
After downloading the international firmware i tried to install it and odin got stuck while writing the system.img. After that my phone did not boot up (of course). After that i downloaded and tried to isntall the firmware of the carrier, but i had the exact same issue. When i turn my device on i get to an error screen which tells me to execute an "emergency recovery" via the samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
Frp hinders me to install a custom recovery and the stock one does not allow any isntallations via adb or sd card.
My qustion is: Does anyone know how i can install a rom from here?
I know that i had to have made some changes prior to the flashing, but as i said i was not aware and an idiot for not double checking.
Since it is not bricked yet i suppose there must be an answer but i can't find anything.
Thanks in advance
edit:
After only installing the stock bootloader, i am autmaticly entering it when i boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Click to expand...
Click to collapse
have u solved your problem ? This problem i am facing on the s7edge nougat ? Plz help ?

Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might be worth a try!
Good luck!

Fabivons said:
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might me worth a try!
Good luck!
Click to expand...
Click to collapse
y i have done that and the device boots up but some applications force close and when i insert the memory card , the phone gets restarted everytime

Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Tell us in detail now.

SjDU said:
Tell us in detail now.
Click to expand...
Click to collapse
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.

Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?

suhaibahmad said:
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
Click to expand...
Click to collapse
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.

Fabivons said:
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Click to expand...
Click to collapse
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally

suhaibahmad said:
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
Click to expand...
Click to collapse
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.

Fabivons said:
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Click to expand...
Click to collapse
thats your kindness , yes i have performed the factory reset several times from recovery , but when i trying to reset it from settings , it goes after restart to recovery with dm-verity error , then i wipe and factory reset from there

Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model

SjDU said:
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
Click to expand...
Click to collapse
Well FRP has to be turned off (the button in the menu is called "OEM unlock, the button has to be set to on which deactivates FRP). You don't mention using a PIT file - did you use one?