Database Users

[Q] Recovery Mode Disappeared

Running Samsung-SGH-I337 Galaxy S4 AT&T with 4.2.2, rooted and encrypted of course, I've been trying to flash a custom recovery such as CWM via ROM Manager and also TWRP via GooManager as well as other attempts to get the custom recovery working. When ROM Manager or GooManager tries to set things up it says it works, but when I reboot into recovery mode it actually goes into Download/Odin mode instead. Even if I use the volume up method of getting into recovery mode (download mode is volume down) it goes to download mode instead. I've even rebooted to recovery mode via adb, still goes to download instead. What?

Try flashing it with Odin.

I haven't found a TWRP method that works for the ATT I337 via ODIN. Not sure how that would make a difference either though.

i dont about twrp why not use Philz Touch CWM ?
i can send your a link, pm me if you're interested

I tried flashing the version from here: goo. im/devs/philz_touch/CWM_Advanced_Edition/jflteatt but it fails every time. I've tried different verions of the ATT CWM Advanced Edition as well as different versions of Odin. I've read maybe it had something to do with a locked bootloader? Haven't been able to find much good information on that for my phone.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Parad0x86 said:
I tried flashing the version from here: goo. im/devs/philz_touch/CWM_Advanced_Edition/jflteatt but it fails every time. I've tried different verions of the ATT CWM Advanced Edition as well as different versions of Odin. I've read maybe it had something to do with a locked bootloader? Haven't been able to find much good information on that for my phone.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
have you tried other versions of Odin?

Hi,
I'd like to remember you that you have a specific forum for your device
http://forum.xda-developers.com/galaxy-s4-att
People there should be of better help than here .
~Lord

XxLordxX said:
Hi,
I'd like to remember you that you have a specific forum for your device
http://forum.xda-developers.com/galaxy-s4-att
People there should be of better help than here .
~Lord
Click to expand...
Click to collapse
Thanks, I didn't realize I had to look at "All" forums to find my device's forum since the default is just "Top Devices" and didn't see it. If this can be moved please do.
I've been reading and from what I've gathered, since I have MF3 firmware my bootloader is locked down and my only bet is to use Safestrap. I'll be looking into this.
Edit: Also I use encryption which is apparently not a good idea with Safestrap so I'm probably SOL. Awesome.

[Q] SOFT BRICK - Fail flashing Stock ROM at hidden.img ODIN

SOFT BRICK - Fail flashing Stock ROM at hidden.img ODIN
Guys hello.
I have rooted and successfully flashed custom recovery and custom firmwares on my Note 3 (9005 Qualcomm LTE), however the last flash (stock ROM 4.4.2 N9005XXUENB4) attempt with Odin (v 3) failed at the end of the flash process ( hidden.img.ext4 -> FAIL! (ext4)):
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now the phone wouldn't boot any more....
Than I try the pit file ........sorry the some situation......................................
Can somebody help or advise me?:crying::crying:
Cheers Shark001

This is possible coz the firmware you have installed (maybe you upgrade your bootloader flashing that custom roms) is newer that the one you are trying to flash.

Joku1981 said:
This is possible coz the firmware you have installed (maybe you upgrade your bootloader) is newer that the one you are trying to flash.
Click to expand...
Click to collapse
Thank you for your quick answer.......
I had this ROM [SM-N9005][XXUGNI4]_BoBCaTROM_EVO_v12 multi density........
Is there a way how I can solve it?

Shark001 said:
Thank you for your quick answer.......
I had this ROM [SM-N9005][XXUGNI4]_BoBCaTROM_EVO_v12 multi density........
Is there a way how I can solve it?
Click to expand...
Click to collapse
Ni4 is much newer....so flash a Ni4 room. ...

Shark001 said:
Thank you for your quick answer.......
I had this ROM [SM-N9005][XXUGNI4]_BoBCaTROM_EVO_v12 multi density........
Is there a way how I can solve it?
Click to expand...
Click to collapse
Are you using a branded device? Where is your device from? Do you know the CSC of your device?
Go to Sammobile.com and take a look the firmwares GNI4. Download and flash it. Done.

HI
My Phone was brandet by T-Mobile (Note3 is rooted) but I used a custom Rom the BobCat Rom and the reported Error happend during the tryed to reinstall the xxxGNI4 version from Sammobile.
Therefore I'm confused . Sorry I wrote the wrong version in my first post....

Shark001 said:
HI
My Phone was brandet by T-Mobile (Note3 is rooted) but I used a custom Rom the BobCat Rom and the reported Error happend during the tryed to reinstall the xxxGNI4 version from Sammobile.
Therefore I'm confused . Sorry I wrote the wrong version in my first post....
Click to expand...
Click to collapse
I found the CSC Version of the BObCatROm ............it is N9005AXXGNJ1
Cheers

Shark001 said:
I found the CSC Version of the BObCatROm ............it is N9005AXXGNJ1
Cheers
Click to expand...
Click to collapse
T-mobile of what country?

[Q] Having issues booting up my N9005 after a failed 5.0 Official Lollipop Update

Hello, I have tried updating my N9005 to the latest firmware 5.0 provided on Sammobile. After attempting to flash it via ODIN, the following error occurs:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Retried this step several times, but i have received the same error.
Following a few instructions found on the XDA forums, I tried using PIT file in order to re-partition.
The phone now reboots but will not go past the first boot screen "Samsung Galaxy Note3 N9005".
I tried pulling out the battery and performing a factory reset (along with wiping caches), but the situation is still the same after rebooting the device.
Also I have noticed that upon accessing "recovery mode", a error stating " Failed to mount /system (Invalid argument)" error is displayed.
I'm pretty new at upgrading phones and I've bought this phone recently and was unaware of the consequences of flashing ROMS via Odin.
The initial fw. on the device was 4.4.2 Official Samsung. Is there any way that I can make the phone reboot normally with fw. 4.4.2? Or any other firmware for that matter?
Thanks in advance.

AndreiRonaldo said:
Thanks in advance.
Click to expand...
Click to collapse
Reflash the firmware again now via ODIN without the .pit file.

Joku1981 said:
Reflash the firmware again now via ODIN without the .pit file.
Click to expand...
Click to collapse
I've tried that several times without success. But the issue was fixed. Apparently the PIT file I was using did not match the ROM i was flashing. I just had to find a matching pair of both ROM and PIT and now I've successfully booted my device. Hope that this thread might help others in need for answers to similar questions.

Alright, this is taking alot more than i had expected, after finally managing to boot my device, I've noticed that flashed rom behaves awfully, my phone is stuttering, and i have no sound. Also, my IMEI is displayed as "Unknown" in the "Status'" section of the device's Settings. Any suggestion on how to fix this issue?

flash the stock the rom you have before

[Q] How to chage CSC?

Hi
My phone is N910U and it's CSC code is BRI (Thailand)
I was waiting for lollipop update, but it seems that only some countries have received the update.
So I decided to chage CSC to whatever the New Zealand CSC is to get the official update.
My phone isn't rooted and it runs stock rom.
While I was trying to flash recovery.tar via odin, it shows an error:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I used correct recovery file, and this happens when I want to flash autoroot too.
USB debugging on, download mode, stock USB cable, reinstalled driver
Does anyone know how to resolve this issue?
Also, can I just download New Zealand firmware and flash it via odin?
Will my phone not brick and be able to use it in the UK?
Any help would be very appreciated
EDIT: FIXED - Disable reactivation lock

Do you have reactivation lock enabled? If so, disable it before flashing stuff in odin

absinthesummer said:
Do you have reactivation lock enabled? If so, disable it before flashing stuff in odin
Click to expand...
Click to collapse
Thanks for your reply
the reactivation lock was enabled, so I disabled it. But it is still not working.
It shows slightly different error
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I really have no idea what went wrong.
Do you have any clue?

Have you tried flashing cf auto root since disabling reactivation lock? Typically in my experience you need to have root access before you flash a custom recovery.
Edit: that's not always the case, but when it comes to Samsung devices and odin, you should try to follow the usual steps: root then recovery.

absinthesummer said:
Have you tried flashing cf auto root since disabling reactivation lock? Typically in my experience you need to have root access before you flash a custom recovery.
Edit: that's not always the case, but when it comes to Samsung devices and odin, you should try to follow the usual steps: root then recovery.
Click to expand...
Click to collapse
Thank you for your suggestion.
I tried to root it first, and it gave me the same error(new one) as above.
I never had an issue when I was playing around with my SGS3 couple of years ago. Rooting, recovery, custom rom all flashed well via odin.
Any idea?

Thank you very much.
I was just redoing all the procedures, and found out that the reactivation lock is reactivated!
I disabled, again, and it worked!
Thank you again XD

cosmostronomer said:
Thank you very much.
I was just redoing all the procedures, and found out that the reactivation lock is reactivated!
I disabled, again, and it worked!
Thank you again XD
Click to expand...
Click to collapse
Very glad to hear it! That reactivation lock is the number one issue when odin fails (on this device anyway)

Possible soft brick when trying to revert to stock rom

Hello everyone!
Apologies in advance if I broke any forum rules by accident, first time posting here.
I have some experience with rooting galaxy devices as well as flashing roms and recovery, and have done this many times before, so I didnt put much thought in the firmware update process.
I decided to revert my S5 (SM-G900F) to its original stock firmware.
Before the failed attempt I was running Resurrection Remix 5.5.0 with TWRP recovery.
I simply went ahead and downloaded the last firmware released that is supported for my country (G900FXXU1BPA2_G900FOJK1BPA1_ILO) and proceeded with flashing it via ODIN and received the following log messages:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Size)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Currently the device is stuck during the boot process (most likely still in download mode) with the following message displayed on the screen:
Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
Kies does not seem to able to recognize the device at all.
It is worth mentioning that I have the original ROM files on the internal SD card, as well as an external SD card if needed for troubleshooting.
I would really appreciate if you can help me with this, I really hope that what I done so far is reversible.
Thanks in advance!

Does it say G900F in download mode?
If yes, try flashing this with ODIN 3.10.7
Code:
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM

*Detection* said:
Does it say G900F in download mode?
If yes, try flashing this with ODIN 3.10.7
Code:
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
Click to expand...
Click to collapse
Thank you for the quick reply!
Indeed it shows SM-G900F, ill try the link with the new Odin (mine is 3.10) and will updated soon.

SpectreSR said:
Thank you for the quick reply!
Indeed it shows SM-G900F, ill try the link with the new Odin (mine is 3.10) and will updated soon.
Click to expand...
Click to collapse
It worked! Thanks a lot!
Care to share what might have went wrong?
What is differant between the firmware you provided between the one I tried in the first place?
I understand this is a firmware for the UK, how can I confirm that the modem that comes with this firmware is compatible with my country's network?

Not sure what went wrong, I just know that ROM works for the G900F, so if it had failed with that one too, we would know it wasn't a ROM issue
As for your networks, only one way to find out