So i recently updated to 4.3 on my i747 and i wanted to do an emergency firmware recovery, so i go to Kies and follow the steps, whenever i plug in my phone no matter what port windows will say device had a malfunction last time it was entered, but in kies i can still do the emergency recor but then it stops and says device not pulgged in gives me a note f error and tells me to reinstall drivers and restart my computer. Ive done that several times i even uninstalled and installed Kies but it wont work. Whenever i try to turn my phone back on it says: firmware upgrade encountered an issue. Please select recovery mode in kies and try again. Well i did that but it still wont work. I've unrooted my phone a while back ago and the stuff at the top left corner of the screen says:
Odin Mode
PORDUCT NAME:SGH-I747
CUSTOM BINARY DONWLOAD:YES (4 COUNTS)
CURRENT BINARY SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
QUALCOMM SECUREBOOT:ENABLE
WARRANTY BIT:0
BOOTLOADER AP SWAEV: 2
what do i do please i need help. Thank you in advance
I have a Sprint Samsung Galaxy s3 (Pebble Blue).
I downloaded Odin and tried to root it to CF-Root-SGS3, but using this tutorial video: youtube com watch?v=mndQZqom3Ac
Yes, I am a complete noob, therefore it failed. When I tried to turn it back on, it showed me this:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I did perform a full back up of my phone on Kies before starting, thankfully, but when I tried performing the emergency firmware recovery, it won't show my device in the list of devices requiring emergency recovery. I also don't know what the recovery code would be.
I also tried performing the firmware upgrade and initialization process, but it required my IMEI number, and I don't know how to find that without my phone working properly.
This is the other info my phone is showing:
ODIN MODE
PRODUCT NAME: SPH-L710
CUSTOM BINARY DOWNLOAD: Yes (4 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER RP SWREV: 1
Please help. Thank you so much in advance!
Did you get this taken care of? Hopefully you havent been phoneless for the past few days. Can you still boot into download mode? if you can you should try to Odin the stock tar file for the latest firmware/system update (ND8). It's in a thread here http://forum.xda-developers.com/showthread.php?t=2738533 You should be able try rooting again after this gets your phone up and running again. The only thing to worry about is that YOU CAN NOT DOWNGRADE FIRMWARE after MK3 or ND8 without bricking your phone.
Thank you!
I replied to your message, thanks again!
hey guys this is my first post. Really kind of freaking out about this phone. I successfully rooted the phone originally using the Towelroot one-click method. I then installed the necessary apps and .apks and tried to install a recovery via ClockworkMod and also with SafeStrap. When I did so it asked me to reboot, which having rooted plenty of phones before, using other methods, i thought piece of cake. Well the phone rebooted and rebooted into a recovery boot loop. I was finally able to get the phone into download mode and tried to flash some stock firmware to hopefully get out of this jam and be done with the whole mess. No dice, pulled battery and unplugged the cable. The phone now says when I turn it on
ODIN MODE
Product Name: SM-N900T
Current Binary: Samsung Official
System Status: Custom
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY 0X1
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
WRITE PROTECTION: ENABLE
it then says Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. But I cannot connect this phone to the PC via Kies 3 as my device 'is not supported' But i am able to boot into download mode and try to flash stuff. However when I flash anything via ODIN it fails in different areas such as AUTH (fail) and in a host of other ways. I cannot successfully flash anything. This phone is apparently a brick and I have NO IDEA what to do. This phone has no warranty either... I have no idea what to do has anyone gotten this problem solved??
it now says UDC START
I think the problem occurred because you installed two recovery modes. Safestrap and clockworkmod. Also Safestrap doesn't work well on T Mobile Note 3's. Only success I've seen with Verizon and At&t variants. Furthermore warranty wouldn't do you any justice since you tripped knox 0x1. Try pulling out the battery waiting a couple minutes. Make sure your battery has at least 50% juice. Use a genuine Samsung wire when you're flash with Odin if you haven't done so already. Uninstall your old drivers on your pc and reinstall the kies drivers. Get into download mode and flash the stock Samsung Note 3 T Mobile with your current android firmware.
Sent from my SM-N900T
So I recently bought a Note 2 and found out that it was bricked. Essentially what happens is, when I boot it up, the screen is black at first and the white and black lines appear, just like the old school TV static interference but they are lines, instead of dots. I can boot into download mode and that is it. When in download mode, it says this in the top left:
ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
KNOX WARRANTY VOID: 0
RP SWREV: *IT DOESNT SAY ANYTHING HERE.*
I tried to flash a stock ROM and Odin is saying "There is no PIT Partition." So I found the PIT file for it and tried to flash it. I get the error "Get PIT for mapping." I have tried full ROMs with bootloaders etc and they havent worked. I gives me an error and just stays stuck. I can try that again though, if need be. I have tried to flash a recovery and that seems to make the "ODIN Downloader" crash. I have tried multiple USB slots as well as cables, I am running W8, with the Samsung Drivers installed. I have been using multiple versions of ODIN but mostly ODIN 3.07.
I have taken this from a recent thread to save time. It is exactly the same as my phone, instead a different IMEI and S/N, obviously. And it says Made by Samsung, instead of "Made in Korea by Samsung," if that makes any difference.
http://dl-1.va.us.xda-developers.co....jpg?key=XStz_-9sOmr8gQVK5EJCJg&ts=1425326515
Thank you.
Hi all!
I've got a bricked Samsung S4 mini.
It's stuck in a bootloop and I've got no recovery mode (No command with dead droid). Kies doesn't recognize it.
I've tried:
- flashing CWM and TWRP to get recovery mode up and running but no luck. Odin completes fine and it restarts (tried to enter on first reboot as described) but still "No command".
- flashing stock firmware from sammobile.com. I completes fine but when i restart its no difference (bootloop and no recovery)
- flashing stock firmware (all files with pit file) https://forum.xda-developers.com/showthread.php?t=2751224. This gets error in Odin and "SW REV CHECK FAIL: FUSED 2 > BINARY 0" in on the phone. I suspect its the wrong firmware.
In download mode:
Code:
CURRENT BINARY: Samsung Official
SYSTEM STATYS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 2
WRITE PROTECTION: Enable
I'm all out of ideas and would love some help. I've found some similar threads on this but no solution.
How do i find out exactly what model number I've got. The back says GT-I9195 and the Samsung Warrany site says "cant find product". I guess its because its a Scandinavian phone.
Any help much appreciated.
/Daniel
Reply.
What was the last thing you did that caused the boot loop and made recovery inaccessible?
Exanneon said:
What was the last thing you did that caused the boot loop and made recovery inaccessible?
Click to expand...
Click to collapse
I got it from a friend and he said that it started to behave strange. So he decided to try flashing a custom rom.
It seems to have been a little bit to custom for this device Maybe he flashed the wrong version.
Reply.
Flashing a "wrong version" can be fatal to an android device, this has happened to 2 of my phones to my younger, more inexperienced self (around 4 years ago), for one of the phones recovery and download mode became corrupted (inaccessible), and the other phone became a complete and utter "brick" (useless), it was unable to even be turned on!
My point is that if he had flashed a rom, or even worse; a stock firmware for his phone this can seriously kill it, I suggest asking him what rom and what model the rom was built for.
Update me once you find out.
Exanneon said:
Flashing a "wrong version" can be fatal to an android device, this has happened to 2 of my phones to my younger, more inexperienced self (around 4 years ago), for one of the phones recovery and download mode became corrupted (inaccessible), and the other phone became a complete and utter "brick" (useless), it was unable to even be turned on!
My point is that if he had flashed a rom, or even worse; a stock firmware for his phone this can seriously kill it, I suggest asking him what rom and what model the rom was built for.
Update me once you find out.
Click to expand...
Click to collapse
He said that he doesn't know exactly. He tried a few but all should have been for the GT-I9195.
Reply.
If all of them were for the GT-I9195, then please list them for me, or at least the last one that was flashed, as I can't help you if I'm told that everything was done correctly.
Sure
- I9195XXUCPE1 (https://www.sammobile.com/firmwares/galaxy-s4-mini/GT-I9195/NEE/download/I9195XXUCPE1/78908/)
- I9195XXSCQA3
- I9195XXUBML4-D-BT (4 files + PIT-file CSB_signed_SERRANOLTE_ONEPIT_OPEN_130523)
Reply.
So you haven't been flashing roms, but rather stock firmwares, what odin were you using?
Exanneon said:
So you haven't been flashing roms, but rather stock firmwares, what odin were you using?
Click to expand...
Click to collapse
My friend said that he initially flashed a Cyanogenmod rom and it worked but he didin't like it and the troubles started when he tried to revert to stock.
Odin version: 3.09
Thanks.
Reply.
That's unusual, flashing stock firmware is very unlikely to cause any problems but fix everything...Could you please give me the link to the stock firmware your friend was flashing? (If you have it)
standarggbg said:
Hi all!
I've got a bricked Samsung S4 mini.
It's stuck in a bootloop and I've got no recovery mode (No command with dead droid). Kies doesn't recognize it.
I've tried:
- flashing CWM and TWRP to get recovery mode up and running but no luck. Odin completes fine and it restarts (tried to enter on first reboot as described) but still "No command".
- flashing stock firmware from sammobile.com. I completes fine but when i restart its no difference (bootloop and no recovery)
- flashing stock firmware (all files with pit file) https://forum.xda-developers.com/showthread.php?t=2751224. This gets error in Odin and "SW REV CHECK FAIL: FUSED 2 > BINARY 0" in on the phone. I suspect its the wrong firmware.
In download mode:
Code:
CURRENT BINARY: Samsung Official
SYSTEM STATYS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 2
WRITE PROTECTION: Enable
I'm all out of ideas and would love some help. I've found some similar threads on this but no solution.
How do i find out exactly what model number I've got. The back says GT-I9195 and the Samsung Warrany site says "cant find product". I guess its because its a Scandinavian phone.
Any help much appreciated.
/Daniel
Click to expand...
Click to collapse
same problem. did you find any luck fixing your phone? wanna try it too if so :good:
He doesn't remember but think it was I9195XXSCQA3.
ddikere said:
same problem. did you find any luck fixing your phone? wanna try it too if so :good:
Click to expand...
Click to collapse
Nope. Not yet.