Database Users

i9505 Softbrick Odin flash is failing [Resolved]

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.

[SOLVED] Flashed wrong recovery, now stuck in Odin mode: "Could not do normal boot"

[SOLVED] Flashed wrong recovery, now stuck in Odin mode: "Could not do normal boot"
First time venturing into rootin' 'n bootin' Android devices. Hopefully will have a long pleasant journey ahead, but due to a silly oversight, I flashed the wrong recovery file to my device (hangs head in shame). I'm an seasoned coder, but am somewhat new to Android.
Some info:
Model: SM-N910G (SnapDragon)
Device does not want to boot normally, stuck in downloading mode. The screen shows the following:
"Could not do normal boot. ODIN MODE (HIGH SPEED)" Reactivation lock is "OFF".
[x] device is rooted and was running stock TouchWizard (based on Lollipop 5.0.1)
[x] can't get the phone to enter recovery mode (by pressing PWR+Menu+Volume Up)
[x] device is not recognised in ADB (using "adb devices")
[x] Samsung Kies3 does recognise that there is a device but says it's unsupported
[x] device is recognised in Odin/Windows (blue comes up)
[x] device is recognised in Heimdall on OSX (however, I have not used Heimdall for flashing at all yet)
[x] I now have to pull the battery to turn device off
[x] my main computer is a fast MacBook Pro, but have access to older/slower Windows 7 laptops (with only 2GB RAM).
I had the device rooted and working fine except for the fact that I was getting "dm-verity verification failed" errors when trying to make a Nandroid backup. So I tried to reinstall TWRP recovery -- this time rather than going through Odin, I tried it with TWRP Manager (installed on device). I managed to select the wrong recovery file (SM-N910F instead of SM-N910G -- in TWRP Manager this was somewhat unlclear, as I selected the "Galaxy Note 4 INTERNATIONAL version"; my device could be considered "INTERNATIONAL version", I should have been MUCH more careful however).
What is the best course of action to take from here on? I have read a serious number of posts on XDA, but am somewhat unclear about best action to take from here on.
All help will be much appreciated: amazing Karma coming your way to all who can help get this device booting normally!

Have you tried to flash via ODIN the right version of TWRP?

_mone said:
Have you tried to flash via ODIN the right version of TWRP?
Click to expand...
Click to collapse
First of all, thank you for responding. Much appreciated.
One of the problems I keep running into is that Odin (various versions) gets stuck and is "Not Responding" when attempting to verify the MD5 hash of the recovery file. Mind you, this happens when the device is NOT plugged in.
Surely, verifying a 15mb recovery file should only take a few seconds (even on an older machine) ? I have tried re-downloading the same file. For now: I'll keep looking for good sources of the correct N910G TWRP recovery file.

Zef Vegas said:
First of all, thank you for responding. Much appreciated.
One of the problems I keep running into is that Odin (various versions) gets stuck and is "Not Responding" when attempting to verify the MD5 hash of the recovery file. Mind you, this happens when the device is NOT plugged in.
Surely, verifying a 15mb recovery file should only take a few seconds (even on an older machine) ? I have tried re-downloading the same file. For now: I'll keep looking for good sources of the correct N910G TWRP recovery file.
Click to expand...
Click to collapse
Correct me if I'm wrong.
Is the N910G called trltedt?
If it is like that you should download twrp-2.8.7.0-trltedt.img.tar from this official TWRP page and flash it via ODIN

I believe you are correct (and thanks for that link). I'm currently verifying whether the N910G is indeed called trltedt. There seems to be a bit of confusion out there over that specific model. Will report back shortly.

Zef Vegas said:
I believe you are correct (and thanks for that link). I'm currently verifying whether the N910G is indeed called trltedt. There seems to be a bit of confusion out there over that specific model. Will report back shortly.
Click to expand...
Click to collapse
N910G is indeed trltedt.

Battlehero said:
N910G is indeed trltedt.
Click to expand...
Click to collapse
Thanks for confirming that. I had just come to the same conclusion. Am now looking for best source for Odin that works with my N910G device. As soon as I have found that, I'll flash the recovery file (from source suggested by _mone) on a PC w/ official Samsung USB drivers & w/ Kies uninstalled.

With ODIN 3.10.x you should be ok.

_mone said:
With ODIN 3.10.x you should be ok.
Click to expand...
Click to collapse
I am VERY happy to report that the flash worked: device booted up nicely. Thanks guys! As promised: seriously good Karma coming your way.
Now, what has made this all a fair bit trickier up to this point: each time I tried to let Odin read the MD5 hash associated with its TAR recovery file, Odin borked and became unresponsive. The recovery file suggested by _mone was processed by Odin just fine and the whole thing was done in seconds. Yay!
Think I'll have a beer now, take a breather, and toast to you guys (wish I could drink it with you two).
[EDIT] I was initially using a different recovery file to the one suggested by _mone. The recovery file I was using at first included a MD5 hash and caused Odin to become unresponsive.

Happy if you managed to solve the problems with your phone!
I'll have a beer too now! lol :cheers:

Purchased a Note3, stuck on Custom ROM boot screen

Haven't rooted a phone in a little but am generally pretty savvy. I can get into recovery, tried restoring factory settings and clearing cache, same result unfortunately. I tried running an Odin .exe I found in another thread but it just opens and closes.. :/
When in download mode, product name: SMN900V, System Status: Custom
Knox Kernel Lock: 0x0, Knox Warranty Void: 0x0, Qualcomm Secureboot: Enable (CSB), RP SWREV: S1, T1, A3, P1
Write Protection: Enable, UDC START
Any help anyone can offer or provide a working rom or flashable file to get me booted would be most appreciated! No idea what ROM or Android version he put on this thing (purchased from Swappa).
TIA!!

Re download Odin and tar file. Have you gotten Odin to flash anything or does it fail or do you mean Odin itself isn't working? It sounds like you didn't extract Odin files and just opened it.
Sent from my SM-N900V using XDA-Developers mobile app

I was able to flash a Verizon firmware (thru Odin) and get it booted but I don't have root (seller claimed he did beforehand). Sounds like I should start with unlocking bootloader or root first? Thanks for the response man, I appreciate all the help I can get!
Sent from my SM-N900V using XDA-Developers mobile app

Start with the root first. Can't unlock the bootloader without it.

Awesome is there a one click by chance or is it complicated?
Sent from my SM-N900V using XDA-Developers mobile app

DNak206 said:
Awesome is there a one click by chance or is it complicated?
Sent from my SM-N900V using XDA-Developers mobile app
Click to expand...
Click to collapse
I had installed jasmine rom and ended up having problems with certain apps not working due to the modified framework he was using. I used odin to flash the new OB6 & pit (returns to locked boot loader with stock lollipop rom). I took the OTA to OF1, then used the yemen 1 click root. At this point the only issue I have is trying to get a customer bootloader installed. The TWRP version 3.0.2-0 just leaves me stuck at boot loader and I had to reinstall the pit file to get phone to boot again. Hope that helps you. I like stock rom but am trying to get native tether to work, without customer bootloader I can't flash anything.

I just got note3 Verizon, I rooted it couple days ago. I am on tmobile, so far everything works with stock lollipop except hotspot. Contemplating on unlocking boot loader at the moment.

santas16 said:
I had installed jasmine rom and ended up having problems with certain apps not working due to the modified framework he was using. I used odin to flash the new OB6 & pit (returns to locked boot loader with stock lollipop rom). I took the OTA to OF1, then used the yemen 1 click root. At this point the only issue I have is trying to get a customer bootloader installed. The TWRP version 3.0.2-0 just leaves me stuck at boot loader and I had to reinstall the pit file to get phone to boot again. Hope that helps you. I like stock rom but am trying to get native tether to work, without customer bootloader I can't flash anything.
Click to expand...
Click to collapse
[threadjack]
I was fooling around with flashing custom recoveries from within a rooted ROM today, and found something useful - when I "got stuck at bootloader" because TWRP failed to boot. So long as the main ROM is still bootable and is rooted, you can clear the "always tries to boot the recovery" behavior the following way:
1) Pull the battery (and plug back in after a couple seconds)
2) Vol-Down+Home+Power (as if you are trying to enter Download mode)
3) When you get the Custom ROM Warning menu, choose Cancel (not Continue)
This clears the BCB (Boot Communication Block) in eMMC and the phone will thereafter attempt to boot normally, rather than continuing to try to boot the recovery again. The sequence #2-3 does not work if you don't start by pulling the battery - if you soft-boot by holding the Power button down (~ 15 seconds), the phone will always attempt to boot the (broken) recovery, whether you enter Odin mode or Cancel.
Well, that's the way my phone behaves at this moment. (I am using a older bootloader however - it is always possible that this is a bootloader behavior that changed in later versions). Anyway - if you get "stuck" again, this could save you some labor, rather than having to go back to Odin, flash everything, and re-root.
Having said that, I'm not sure what you would use as alternative custom recovery. You could do something like pull just the stock kernel from the OF1 and re-pack it into your own customization of TWRP to see if that changes anything. Thing is, I could have sworn I saw a report from someone who said they are using TWRP 3.0.2 with the OF1 bootloader successfully.
Are you using "twrp-3.0.2-0-hlte.img" ?
[/threadjack]

bftb0 said:
[threadjack]
I was fooling around with flashing custom recoveries from within a rooted ROM today, and found something useful - when I "got stuck at bootloader" because TWRP failed to boot. So long as the main ROM is still bootable and is rooted, you can clear the "always tries to boot the recovery" behavior the following way:
1) Pull the battery (and plug back in after a couple seconds)
2) Vol-Down+Home+Power (as if you are trying to enter Download mode)
3) When you get the Custom ROM Warning menu, choose Cancel (not Continue)
This clears the BCB (Boot Communication Block) in eMMC and the phone will thereafter attempt to boot normally, rather than continuing to try to boot the recovery again. The sequence #2-3 does not work if you don't start by pulling the battery - if you soft-boot by holding the Power button down (~ 15 seconds), the phone will always attempt to boot the (broken) recovery, whether you enter Odin mode or Cancel.
Well, that's the way my phone behaves at this moment. (I am using a older bootloader however - it is always possible that this is a bootloader behavior that changed in later versions). Anyway - if you get "stuck" again, this could save you some labor, rather than having to go back to Odin, flash everything, and re-root.
Having said that, I'm not sure what you would use as alternative custom recovery. You could do something like pull just the stock kernel from the OF1 and re-pack it into your own customization of TWRP to see if that changes anything. Thing is, I could have sworn I saw a report from someone who said they are using TWRP 3.0.2 with the OF1 bootloader successfully.
Are you using "twrp-3.0.2-0-hlte.img" ?
[/threadjack]
Click to expand...
Click to collapse
I get a different kind of stuck, I'm not going to try it again but it said the phone has detected software that is not authorized or something along those lines. I cannot just pull battery as it just repeats over and over. I actually do not ever get to enter any recoveries at all, it automatically detects that's it's not the original bootloader and tells me such. anyways, I had to reload the image and take the OF1 update again... all is working back to normal.
I had used "twrp-3.0.2-0-hltevzw-4.4.img" from the twrp manager app, flashed via app, restarted to end up having the error message immediately on bootup of device... no recoveries or anything could load. I would have to assume the 4.4 means kk version and that's why it didn't work?

santas16 said:
I had installed jasmine rom and ended up having problems with certain apps not working due to the modified framework he was using. I used odin to flash the new OB6 & pit (returns to locked boot loader with stock lollipop rom). I took the OTA to OF1, then used the yemen 1 click root. At this point the only issue I have is trying to get a customer bootloader installed. The TWRP version 3.0.2-0 just leaves me stuck at boot loader and I had to reinstall the pit file to get phone to boot again. Hope that helps you. I like stock rom but am trying to get native tether to work, without customer bootloader I can't flash anything.
Click to expand...
Click to collapse
Hmmm. Maybe I was reading something into your post that wasn't there. I assumed that you had also performed the retail-to-dev edition CID change "unlock" after you gained root on OF1. Is that wrong - did you simply flash a recovery after getting root?
In my case I flashed a non-bootable TWRP (dd of=/dev/block/mmcblk0p15...) onto the recovery; doing this tripped my Knox Warranty flag, but otherwise the bootloader didn't complain about unauthorized software. After figuring out how to clear the "always try to boot the recovery" near-disaster, I used a 2.8.x TWRP series custom recovery successfully (In addition to flashing the stock recovery back into place and verifying that it still worked) But this is on a truly ancient bootloader (MJ7), so maybe all bets are off about expecting later bootloaders to behave in this same fashion.
Still, the point of developer edition functionality is to allow for custom boot (& recovery) partitions, so it's surprising that you were getting warnings like that if your phone was in developer mode.

@santas16
Hey. For what it's worth, I was able to boot twrp-3.0.2-hltevzw-4.3.img from my SM-N900V ... with a MJ7 bootloader!
But not the hltevzw-4.4.img. (That could be due to the old bootloader however, I don't know for sure)
Note that my phone has the retail-to-deved CID change that puts it into developer mode. (I used @donc113 's executable with adb)
This allows unsigned boot or recovery partitions to proceed to load/execute, but it will burn your Knox Warranty flag (which is unimportant to me at this point). I think that is actually the expected behavior when the phone is in developer mode.
I've been flashing all sorts of recoveries without worrying whether they will boot or not (as I know I can get back into the rooted ROM to flash into place a working version)**
Probably the best advice about not getting stuck in the "continually tries to re-enter the recovery" mode is to NOT use "reboot to recovery" methods (in Safestrap, other recoveries, or root-privileged Apps (flashfire?)), but to always shut the phone down to a powered-off state, and just use the three-button startup method (Vol-Up+Home+Power) to enter the recovery. That way nothing is being written into the BCB that will make it want to loop back to a failed recovery.
cheers
** what was interesting is that I could successfully boot any of the MI9, MJ7, MJE stock recoveries on my MJ7 phone. Moreover, the bootloader would not pop up the yellow "Set Warranty Bit: recovery" message right before they loaded. The NC4 recovery would not boot to a menu, but it also did not present a "Set Warranty Bit: recovery" message. I presume this means that the boot layer is not looking for exact version matches, but rather just checking that the Samsung signing operation is correct. I could not boot OB6 or OF1 recoveries; somewhat curiously though, these attempts *would* throw the "Set Warranty Bit: recovery" error message even though they are validly signed Samsung recoveries. I don't know if it is a reasonable hypothesis, but I think that indicates that Samsung may have altered the details of their signing verification method someplace between NC4 and OB6 so that earlier bootloaders fail this check. Ugh. As if there weren't enough details already.

If your bootloader is still 0F1 then download flashify from Google and hit recovery and tap top twrp.. Your all set...sounds like a lot of craziness for nothing.
Sent from my SM-N900V using XDA-Developers mobile app

santas16 said:
I get a different kind of stuck, I'm not going to try it again but it said the phone has detected software that is not authorized or something along those lines. I cannot just pull battery as it just repeats over and over. I actually do not ever get to enter any recoveries at all, it automatically detects that's it's not the original bootloader and tells me such. anyways, I had to reload the image and take the OF1 update again... all is working back to normal.
I had used "twrp-3.0.2-0-hltevzw-4.4.img" from the twrp manager app, flashed via app, restarted to end up having the error message immediately on bootup of device... no recoveries or anything could load. I would have to assume the 4.4 means kk version and that's why it didn't work?
Click to expand...
Click to collapse
If you get the " not authorized or something along those lines" error, it means you're not unlocked.

Help with rooting G906S Marshmallow 6.0.1 (tried CFire, TWRP and kingroot)

Hi, I've just recently switched over from iphone to android so I'm still new to the whole system. Anyway I've been trying to root my phone for the past 2 days to no avail so I'm at my wits end here. Before I start my phone is from korea which I don't know if whether or not impacts its ability to be rooted, I've done all the basics like enable USB debugging from dev mode, install samsung usb drivers, open ODIN in admin mode and allow MTP to computer. My Device details are below:
>Baseband version : G906SKSU1CPF1
>KERNEL : 3.10.40-8533426
>BUILD NUMBER : MMB29M.G906SKSU1CPF3
So anyway I first tried flashing using CF autoroot for sm-G906S with odin which while it said it was passed and was successful on pc it would be stuck on the samsung logo with a message at the top left that said :
>Recovery booting
>Recovery is not seandroid enforcing
>set warranty bit recovery
So then I tried flashing TWRP custom recovery and putting Super user zip in the internal storage which although got my phone back to working order still wouldnt let me root as the process required me to go to recovery mode from the fastboot mode after it was done flashing (I tried both with and without autoreboot), however once the flashing was done on fastboot I couldn't get to recovery mode no matter how long I held the Vol up/power/home button combination and when i tried it after rebooting it would show normal recovery mode hence there was no way to install the Super User. (Also attempted this with phils recovery)
I then tried to do the TWRP method using adb with command prompt however it would get stuck saying waiting for device when i tried to flash and needless to say kingroot also failed.
At this point as far I've gone through all the methods I could find for my particular device. Would greatly appreciate any insight or advice regarding this problem.
Thanks

start reading from here http://forum.xda-developers.com/gal...ner-thread-t2807639/post68725608#post68725608

(Help needed) Soft bricked Tmobile Note 4 with way way WAY too many error messages.

So, I have here a great old Note 4.
It has the generic mmc errors that cause it issues when booting and sleeping so I decided to give it a new rom. I bumped it into developer options, enabled usb debugging and fastboot and turned it off. I opened up odin, found the right twrp file to flash as well as a stock rom. I loaded it up and fired. The issue then was that the PIT partition had issues. Pit partition failed on odin's side, and flash read failure as well as a pit error of some sort on the phone's side. So I did my homework. I then tried to flash a new .pit file, I made sure the boxes were filled out correctly, had the right pit file as well as a correct stock rom, and the right drivers. It failed again with exactly the same errors. I don't know how you can manage saying that you can't flash the file your trying to fix but whatever. So I did more research and continued to change the usb cable to the original one that came with the phone, change the usb port, change versions of odin, use administrator privileges, find another .pit file, and change the pc. None of these worked, they all gave the same errors no matter what I did. So I moved on to see what else I could do, there was only one more issue though, the phone wouldn't boot up to an OS, if I tried to boot up normally it would boot into recovery, and if I booted into recovery it would boot into download mode with a message saying that the mme error caused it to. SO I couldn't do anything like flashfire or rom manager nor could I do something like root the device! So I did more homework, I turned to adb, because I saw something about an alternative to odin. Unfortunately, the phone has to boot up so you can connect it properly before you boot into download mode. So I did more homework and can't get anywhere, I am completely lost as to what to do because I can't flash odin or adb and sd card can only flash .zip files. I have no idea where to find a .zip for cwm or twrp that will work for my phone and the 2 files that I thought would work only gave me errors. I definitely am drowning in error messages and hope someone who knows what in the world is going on can help me get out of this mess.
Sincerely,
TiffPiff