i9505 Softbrick Odin flash is failing [Resolved] - Galaxy S 4 Q&A, Help & Troubleshooting

Hi All, I'm in desperate need of some help. For the past few days I've been going down the road of getting the latest Phoenix ROM working properly and I've been taking a step backwards with everything I've attempted, now I'm stuck at a soft-brick stage on my i9505
My current issue:
I can get into download mode. Not recovery, definitely not boot, only download mode.
Odin correctly identifies the phone but attempts to flash to the phone fail. It spits out the following:
Code:
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The phone then shows the progress bar completely stalled either at what looks like 99% for small writes (Like my attempt to flash TWRP), or at what looks like 1% (when I flash a full firmware). When I get home tonight I'll list the codes on the screen when it does it but I see a "START", and a "BBA" (I think), but I never get to the "END" command.
Has anyone experienced something similar?
What got me to this stage:
1. Flashed new Phoenix rom v10 upgrading from v9.4.
2. On sleep the cell dropped out constantly and so did WiFi so someone suggested I install a WiFi fix.
3. Installed the modem for XXUGNJ8 (I think). Combined package for LTE and GSM.
4. Every time the modem activated the phone had problems. Locked up when I open the phone app, reboot if someone called me, no sound when calls did "work", and the phone never sleeps and chews the battery after a simple text message.
5. Attempted to revert modem to XXUEMK4 (the other Galaxy S4 still on stock Android 4.3 had this modem). FAILED!
At this point my phone said the last firmware update failed and I was effectively in a softbrick scenario. I can still get into download mode.
6. Attempted to flash Optus carrier firmware 4.4.2 XXUGNH6. This failed, but the download screen changed now and says Samsung Official Firmware on it.
All other attempts to write to the phone have failed.
I've tried a different USB cable.
I've tried a different version of Odin.
I've tried flashing TWRP.
I tried installing Heimidall but have yet to get it working. (Visual studio runtime issues).
I installed Keis just to waste a bit of time.
I tried reinstalling drivers.
I just can't seem to write to the phone. Has anyone experienced anything similar and figured out a fix? When I get home tonight I'll post some pictures / screenshots of the errors I'm getting.
Cheers.

Are you trying to flash an older version of 4.4.2 that you had downloaded earlier?
Flash the LATEST 4.4.2 version for your phone.
"If someone helps, never forget to hit thanks ?"

Latest for my carrier? Or the latest version of stock there is?
By the way for the record here's some more info. Attached is a screenshot of my Odin after it fails. This was after attempting to install Philz recovery.
My phone has the following on the screen:
Code:
Odin MODE
Product Name: GT-i9505
Current Binary: Custom *note this said Samsung Official yesterday
System Status: Custom
Knox Kernel Lock: 0xfffffffc
Knox Warranty Void: 0xfffffffc
CSB-Config-LSB: 0x30
Write Protection: Enable
eMMC Burst Mode: Enable
and then the bits from the actual download attempt:
Code:
START [224, 1448]
BAR [240,1440]
That's it. The progress bar is sitting at what looks like the 99% mark.

No sure if this will help but I solved my issues by running odin as admin and make sure usb debugging is ticked.

I don't see you tried a different usb port/different pc.
For using heimdall your don't need the frontend interface. You only need to make sure you use the correct drivers for heimdall and then use the terminal to flash the recovery.
"heimdall flash --recovery recovery.img --no-reboot" (it's case sensitive.)

Ok success.
I used the i9505 pit file and re-parition and with that I can successfully flash twrp or philz recovery. Which brought up an error saying non-official firmware detected.
I tried flashing XXUGNJ8 downloaded straight from Samfirmware but it failed. I tried it both with and without repartitioning.
So I tried twrp again and failed.
Then I tried XXUGNJ8 again and it failed but got all the way to the image stage.
I read about swapping cables, drivers, USB ports, well I did all of that to no avail.
Finally I took the entire mess to work and used a new computer there, fresh drivers, fresh everything, and everything worked just fine. I have no idea what's wrong with my computer, but it was not happy.
Thank god these phones are hard to brick. I'm willing to bet my USB connection dropped out while flashing which caused the issue to begin with.

Related

[Q] Can't flash I9500 stock rom?

So here's a run down of what has happened:
1) My phone prompts me to upgrade to 4.3
2) Following the update, the phone boots but is unresponsive; (just keeps on saying that app has crashed)
3) Tried to go into recovery mode, but it didn't
4) Used the Kies Emergency Firmware Upgrade method but it stopped and said that an error has occured
5) Now my phone is in a state where booting brings me to an error message that says "Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again"
I have already tried to use Odin to flash a stock rom onto it several times already. I used both 3.04 and 3.07 versions with the 4.22 ser and 4.3 ser roms and they have all failed at Nand write or Can't open the serial(COM) port. or etc.
I've been browsing the forums for a day now and no help. Do you guys have any suggestions?
(I can still enter download mode.)
Bump.
Does anyone have any alternative methods other than flashing stock with Odin until it works? I'm just getting fail messages

[HELP] SM-G900F stuck in a recovery bootloop

Hi,
I'm from Singapore and I believe I have the international s5 (SM-G900F), at least that's what it says in download mode. My phone was running CM13 nightly and till last night it was working fine. Last night when I charged it, I woke up this morning and my battery was incredibly overheated. I changed my battery and tried booting, but now it gets stuck in a bootloop. I flashed stock 5.0 lollipop from sammobile via odin, but it still is stuck. I can boot perfectly into download mode with the android logo. Here are the details:
PRODUCT NAME: SM-G900F
CURRENT BINARY: Custom
System Status: Custom
Reactivation Lock (KK): OFF
KNOX WARRANTY LOCK: 0x1 (04)
QUALCOMM SECUREBOOT: ENABLE(CSB)
RP SWERV: S1, T1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC START
I would really appreciate any help. Thanks!
Boot into recovery and factory reset, then try booting again
Sounds like the DATA partition got corrupted, or something installed to it did, flashing with ODIN doesn't wipe anything, so you'll still be bootlooped unless you wipe DATA / Factory Reset
When you go from cyanogenmod back to stock samsung firmware, a wipe data / factory reset is required in recovery or else the phone will be stuck in a boot loop or not boot up.
Hi, the problem is I cant access the recovery any more. Every time I hold power, volume up and the home button, it says recovery booting, warranty bit:kernel, kernel is not se android enforcing (the usual) but doesn't actually enter recovery.
imbtrthanu said:
Hi, the problem is I cant access the recovery any more. Every time I hold power, volume up and the home button, it says recovery booting, warranty bit:kernel, kernel is not se android enforcing (the usual) but doesn't actually enter recovery.
Click to expand...
Click to collapse
Flash TWRP 3.0.0.0 with ODIN and wipe from there, then flash stock again
https://dl.twrp.me/klte/twrp-3.0.0-0-klte-klte.img.tar.html
Hi I tried flashing twrp but that didn't work. It doesnt enter recovery, it still just restarts.
Is there any other way I can do a wipe? Through adb or something? Or should I select a specific option in Odin (3.09) ? Like bootloader update, etc or something?
imbtrthanu said:
Hi I tried flashing twrp but that didn't work. It doesnt enter recovery, it still just restarts.
Click to expand...
Click to collapse
Uncheck "Auto Reboot" in ODIN, flash TWRP again, when it completes, disconnect USB and pull the battery to power off the phone
Replace the battery, and boot immediately into recovery with Vol Up & Home & Power
Hi that's not working as well. Should I reflash stock and then flash twrp in the way you suggested?
Try, but something seems wrong because you should be able to flash TWRP with ODIN
Have you got the drivers installed and does ODIN give you a COM port at the top when the phone is in download mode?
You are putting the phone in download mode to flash TWRP right?
Vol Down & Home & Power
Yes I'm using Odin 3.09. I'm flashing via the AP slot. I only have F Reset time checked. My S5 is definitely in downloading mode. Looks similar to this:
http://cdn.androidblog.gs/wp-content/uploads/2014/12/Samsung-Galaxy-S5-Stuck-In-Download-Mode.png
Also, I think the drivers may be the issue here. Could you advise me on how to check and how to fix it? Thanks so much! Also, yes, the COM port lights up
imbtrthanu said:
Yes I'm using Odin 3.09. I'm flashing via the AP slot. I only have F Reset time checked. My S5 is definitely in downloading mode. Looks similar to this:
http://cdn.androidblog.gs/wp-content/uploads/2014/12/Samsung-Galaxy-S5-Stuck-In-Download-Mode.png
Also, I think the drivers may be the issue here. Could you advise me on how to check and how to fix it? Thanks so much! Also, yes, the COM port lights up
Click to expand...
Click to collapse
If the COM port lights up, the drivers are installed and working
Try ODIN 3.10.7, that's the latest version
Code:
https://mega.nz/#!vcIGmBTQ!Yr00OrGvUslQouU9E-zPf4SmpyVwL7mwIjeSG-0EAZg
Hi, that also didn't work. Any other advice?
Use a different PC / USB lead, everything you have tried should have worked fine on a G900F
Hi, I tried using a different PC and USB cable. Still nothing. Could it be because I flashed a different PIT file previously? There was a thread where someone suggested flashing a pit file, so
imbtrthanu said:
Hi, I tried using a different PC and USB cable. Still nothing. Could it be because I flashed a different PIT file previously? There was a thread where someone suggested flashing a pit file, so
Click to expand...
Click to collapse
Didn't you flash the G900F PIT?
Flash this in the PIT section of ODIN along with the stock ROM
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit first
Hi, I tried flashing the stock rom with the PIT you gave me but it gave me the following response:
<ID:0/005> FAIL! (Size)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas what I should do now? Also, which stock rom should I be flashing? KK or Lollipop?
I don't know what you've done to your phone, and from your main post, it is definitely a G900F if that is what it says in download mode
Which PIT did you flash the first time? And did it flash successfully?
Any stock ROM should work, but might as well go for Lollipop, I know 100% this one works
Code:
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
The only thing I can think of for now is to tell KIES3 to perform a firmware recovery
Code:
http://www.samsung.com/uk/support/usefulsoftware/KIES/
If you already have KIES installed, remove it and try ODIN again, people have reported it interferes with ODIN
If not, install KIES3, go to the firmware recovery setting and see if it can fix your phone
Other than that, it looks like it's going to need someone with knowledge of manual partitioning via adb shell or something, if the phone can enter a mode the PC can use that with
EDIT - You are using a native PC running Windows 7 or later right? Not a mac running Windows? Macs don't install the drivers properly and fail
Yup I'm running Windows 10. I'll try KIES and see if that works!
Which PIT did you originally flash? And did it actually flash?

Unable to flash custom recovery, and unable to use fastboot/heimdall in download mode

Hi
So bear with me - my question may be simple, however I'm at a loss, and countless hours of searching xda and the web in general has gotten me nowhere.
The task at hand, in all its simplicity is to install a custom rom - CM13 to be precise. Now the weapon of choice, as with past models (S2, S3, S3 minis etc), is to flash the recovery, copy the zip to SDCARD, and install it via recovery... simple... or no not really it appears.
I have installed ADB, and I can communicate with the phone fine here, reboot it to download mode etc. Now - at the very time it goes into download mode, its game over. Fastboot will not recognize the device, and whatever commands being used, it will be stuck in "<waiting for device>". Heimdall will not complete a print-pit command, regardless of driver instantiated using Zadig, however the outcome varies to some degree. Odin detects the phone using Samsung USB drivers and Naked Universal USB drivers, it will even proceed to flash the recovery, and deem the flash succesful, however nothing has happened in reality (and I do think the flash runs rather quick, in comparison to the time it normally uses - if memory serves me well - it IS a few days since I did this last time). The system status DID change to Custom in download mode after Odin flash tho'.
Now to the details:
-----------------------------
OS Used: Windows 8.1 x64
Heimdall error messages:
============
Using WinUSB:
libusbx: error [init_device] device '\\.\USB#VID_046D&PID_C52B&MI_01#6&30F7B376&0&0001' is no longer connected!
libusbx: error [init_device] device '\\.\USB#VID_046D&PID_C52B&MI_02#6&30F7B376&0&0002' is no longer connected!
libusbx: error [windows_transfer_callback] detected I/O error 87: [87] The parameter is incorrect.
Using libusbK (only visible with verbose parameter):
WARNING: Control transfer #6 failed. Result: -9
ERROR: libusb error -7 whilst sending packet. Retrying...
Finally bailing with unable to download PIT
Using libusb0 (still only visible with verbose parameter):
WARNING: Control transfer #6 failed. Result: -1
ERROR: libusb error -7 whilst sending packet. Retrying...
Finally bailing with unable to download PIT
Fastboot simply doesn't recognize the device at all.
Odin recognizes the phone, flashes the recovery and reports succes, but the recovery is not active (I'm suspecting a silent flash failure somehow).
Recovery image used flashing with Odin: twrp-3.0.2-2-klte.img.tar
Steps taken to try and remediate:
- Different USB ports.
- (Many) different USB cables.
- Another PC with USB 2.0 ports. (Still Win 8.1 x64)
- Various versions of Samsung USB drivers
- Naked Universal drivers
- Various versions of Odin.
Download mode shows the following data:
Product Name: SM-G900F
Current Binary: Custom (This changed after flashing with ODIN)
System Status: Custom (This changed after flashing with ODIN)
Knox Warranty Void: 0x0
Qualcomm Secureboot: Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
Secure Download : Enable
UDC START
I havent had the balls to try and do a complete stock firmware flash with Odin, since the connection seems unstable at best.
Additional info: I originally thought it was system specific (my combination of OS and USB drivers), however attaching a Galaxy S3 Mini works like a charm - Heimdall prints PIT without any issue at all.
Aight... I'm absolutely at a loss here... any help will be greatly appreciated.
- Cheers
Flash TWRP recovery with ODIN
Flash custom ROM from TWRP
Forget Heimdall
Uncheck "Auto reboot" in ODIN, pull USB and battery to power off after flash, replace battery and boot immediately into recovery
*Detection* said:
Flash TWRP recovery with ODIN
Flash custom ROM from TWRP
Forget Heimdall
Uncheck "Auto reboot" in ODIN, pull USB and battery to power off after flash, replace battery and boot immediately into recovery
Click to expand...
Click to collapse
You sire - is da' man! Thx a lot for this reply. So simple - I thought so... It worked like a charm.... *sigh* so many hours, and this I never found anywhere - or simply didn't see.
Regardless - it worked and I'm very grateful!
- Regards
sharza said:
You sire - is da' man! Thx a lot for this reply. So simple - I thought so... It worked like a charm.... *sigh* so many hours, and this I never found anywhere - or simply didn't see.
Regardless - it worked and I'm very grateful!
- Regards
Click to expand...
Click to collapse
Good stuff :good:
Some S5s are fine with normal ODIN TWRP flash, some need battery pull
*Detection* said:
Good stuff :good:
Some S5s are fine with normal ODIN TWRP flash, some need battery pull
Click to expand...
Click to collapse
Hmm I assume some models are simply overwriting recovery with the one in-memory on softboot? Or what else might be happening there? Now well - I'm a lesson richer here, and for that I'm grateful, now onto marshmellow and see whatever peculiarities Google has decided on this time
Not 100% sure, but I believe it's some sort of self protection built in, the original recovery is still on the phone, custom gets replaced on reboot from stock backup, which would be handy if your recovery partition got corrupted for whatever reason, but a PITA for flashing custom
So flashing TWRP is working, but the phone replaces it with stock again on the next boot unless you pull the battery to prevent it happening, meaning when you boot immediately into recovery once you've replaced the battery, the phone hasn't had the chance to replace it with stock, and I assume it only tries to replace it that first time, as it won't do it with subsequent boots

T280 - Can not flash back to stock, secure check fail (boot)

Summary: My tablet is soft-brick now. Can only access to Download (ODIN) mode. I have tried 2,3 different firmwares, tried 3 versions of ODIN. But it doesn't work.
Here is the story:
I bought this tablet from bestbuy (USA)
I only wanted to root my tab A 7.0 SM-T280.
I enabled the OEN unlock from the developer mode.
Then I tried to flash the TWRP by the tutorial from this topic by @ashyx :
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
TWRP_3.0.2-1_SM-T280_261016
Click to expand...
Click to collapse
After flashing, on the download mode it showed: "SECURE CHECK FAIL: (RECOVERY)", then I reboot into recovery mode to access the TWRP but it said: "RECOVERY IS NOT SEANDROID FORCEFUL (although in ashyx topic said the SECURE FAIL is fine).
I still was able to reboot into the system this time.
And then I thought I should try another way. And then I came up with the TINKER ROM.
I tried to flash the Rom (v5) but somehow ODIN said FAIL.
I COULD NOT access the system since then.
Bu @zenful 's advices, I tried some different stock firmwares and different versions of ODIN just to get back to normal, but it never works.
Every time I flash, it always has the same problem:
- First try, ODIN fails at:
sboot.img
sboot2.img
complete (write) failed... (I don't remember though)
And in the download mode screen (from the phone) said:
SECURE CHECK FAIL (SBOOT)
SECURE CHECK FAIL (SBOOT2)
- Second try, ODIN fails at:
boot.img
system.img
Complete (write) fail...
And in the screen said:
SECURE CHECK FAIL (BOOT)
SECURE CHECK FAIL (RECOVERY)
I also tried emergency recovery mode in smart switch but it didn't solved the problem. One good thing (after I entered the tablet model and serial number) is that it showed "PHONE: QA4 CSC: PH3 (XAR)"
______________
I'm pretty sure that the problem doesn't come from fw nor from ODIN since I downloaded the fws from sammobile and updato and downloaded ODIN from xda (the latest version from samsungodin.com)
I'm seriously need a help right now. I just wanna have a rooted tablet so I can play game with my ps4 controller.
I have experienced with these flashing business. I rooted my galaxy s2, HTC desire c, HTC evo, etc. and so on, but have never done rooting in the last 1 year. I can attach some snapshots if you guys request
ngvhoang96 said:
Summary: My tablet is soft-brick now. Can only access to Download (ODIN) mode. I have tried 2,3 different firmwares, tried 3 versions of ODIN. But it doesn't work.
Here is the story:
I bought this tablet from bestbuy (USA)
I only wanted to root my tab A 7.0 SM-T280.
I enabled the OEN unlock from the developer mode.
Then I tried to flash the TWRP by the tutorial from this topic by @ashyx :
After flashing, on the download mode it showed: "SECURE CHECK FAIL: (RECOVERY)", then I reboot into recovery mode to access the TWRP but it said: "RECOVERY IS NOT SEANDROID FORCEFUL (although in ashyx topic said the SECURE FAIL is fine).
I still was able to reboot into the system this time.
And then I thought I should try another way. And then I came up with the TINKER ROM.
I tried to flash the Rom (v5) but somehow ODIN said FAIL.
I COULD NOT access the system since then.
Bu @zenful 's advices, I tried some different stock firmwares and different versions of ODIN just to get back to normal, but it never works.
Every time I flash, it always has the same problem:
- First try, ODIN fails at:
sboot.img
sboot2.img
complete (write) failed... (I don't remember though)
And in the download mode screen (from the phone) said:
SECURE CHECK FAIL (SBOOT)
SECURE CHECK FAIL (SBOOT2)
- Second try, ODIN fails at:
boot.img
system.img
Complete (write) fail...
And in the screen said:
SECURE CHECK FAIL (BOOT)
SECURE CHECK FAIL (RECOVERY)
I also tried emergency recovery mode in smart switch but it didn't solved the problem. One good thing (after I entered the tablet model and serial number) is that it showed "PHONE: QA4 CSC: PH3 (XAR)"
______________
I'm pretty sure that the problem doesn't come from fw nor from ODIN since I downloaded the fws from sammobile and updato and downloaded ODIN from xda (the latest version from samsungodin.com)
I'm seriously need a help right now. I just wanna have a rooted tablet so I can play game with my ps4 controller.
I have experienced with these flashing business. I rooted my galaxy s2, HTC desire c, HTC evo, etc. and so on, but have never done rooting in the last 1 year. I can attach some snapshots if you guys request
Click to expand...
Click to collapse
Try this: download your desire firmware via samfirm (BL+AP+CP+CSC when extracted) plus you need a pit file for your model with the same region as firmware and then flash (with 4 firmware files incl pit) via odin autoreboot+repartition+nand erase+f.reset time. At least you will get working stock tablet. It worked on my note 4 soft bricked.
Stixas said:
Try this: download your desire firmware via samfirm (BL+AP+CP+CSC when extracted) plus you need a pit file for your model with the same region as firmware and then flash (with 4 firmware files incl pit) via odin autoreboot+repartition+nand erase+f.reset time. At least you will get working stock tablet. It worked on my note 4 soft bricked.
Click to expand...
Click to collapse
Last time I tried download fw by using samfirm was last week and it didnt work. Can you test yours again?
And whre can I found the pit file? I dont think there is one in the internet right now.

Noob needs help flashing Android 6.0 or higher.

Noob here: I need help with my Note 3 (SM-N900V).
I bought a used phone to replace a stolen one; it came with Android 4.0. A few years ago I successfully used Odin to flash TWRP 3.1.0.0 and the stock OF1 Android 5.0 rom, followed by a root with ArabicTool.
Phone works fine for everyday use, including root-requiring apps, but several apps are now requiring a more recent version of Android. Also, I can no longer boot into recovery mode; instead I get a message saying "System software not authorized by Verizon Wireless has been found on your phone".
I thus decided to try to flash the phone from scratch.
First I tried to use ADB and Fastboot to make sure the bootloader is unlocked. Unfortunately, while ADB worked fine, I was never able to get Fastboot to see the phone, despite following the advice of several web pages addressing this issue, and trying several different drivers.
Pressing on, I decided to try to install TWRP again. Booted phone with VolDown, Home, Power. First I tried using Heimdall 1.4, both with drivers from Samsung, and then with the MSM8960 drivers that came with Heimdall, using this command:
heimdall flash --RECOVERY twrp-3.3.1-0-hlte.img --no-reboot
In both cases, all I got was "ERROR: Failed to access device. libusb error: -12"
Therefore, decided to try it with Odin. Booted phone with VolDown, Home, Power. Run Odin 3.12.4_4, which immediately shows "Added". Load TWRP 3.3.1.0 with AP button, click Start...and get a red Fail flag within a few seconds. Log shows "FAIL! (Auth). Phone shows "SYS REV CHECK FAIL: No Version" and "SECURE MAGICCODE CHECK FAIL: recovery".
I didn't even bother trying to flash the LineageOS ROM.
Can someone please tell me what I'm doing wrong? Please don't assume I know anything about what I'm doing.
--
*not an expert*
Verify that you are using the correct build of twrp-3.3.1.
I am using the hlte build of 3.3.1 on my phone (SCL22)... but my gut tells me that you and I wouldn't share the same build.
Nope basic problem is that OP is in the wrong forum for a Verizon phone .
Assuming that download mode still works (if it is, lucky you); I'd suggest reflashing the stock firmware for your Verizon device.
Flashing a stock firmware would *hopefully* fix your recovery and download issues.
Perhaps the errors you described may have been caused by installing the wrong ROM/firmware.
So, NEVER INSTALL/FLASH a custom or stock ROM that is not tested to work on your device. The main reason is because different variants of the same device (N9000, N900A, N900V) use different chipsets, software and drivers. Also, flashing a wrong ROM/kernel/firmware may cause application errors, boot loops, broken recovery/download mode, or a hard brick.

Categories

Resources