Database Users

[Q] Cant flash custom recovery on i9506 with stock 5.0.1

I have a i9506 with the official 5.0.1 rom, and due to my device becoming ridicilously slow after flashing the official rom, I want to try an alternative rom. I have tried flashing custom recovery to root my phone, using Odin 3.0.9 and Odin 3.10, I have tried flashing CWM_6.0.4.6_Non-Touch_GT-I9506 and Philz_Touch__CWM_6.3.7_V5.15.0_unofficial_(fixed_preload), but the phone just reboots like nothing happened, and the knox flag is 0x0.
Odin 3.10 says:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<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> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
I have enabled USB troubleshooting in developers settings.
Any hints on what I might have done wrong?

Usually you have to root your phone first, then flash the custom recovery.

try this auto root.
http://forum.xda-developers.com/showthread.php?t=2597058&page=190 post number 1897 by dehawk
I have just rooted with this and flashed twrp2850 recovery

GDReaper said:
Usually you have to root your phone first, then flash the custom recovery.
Click to expand...
Click to collapse
adrenalinas said:
try this auto root.
http://forum.xda-developers.com/showthread.php?t=2597058&page=190 post number 1897 by dehawk
I have just rooted with this and flashed twrp2850 recovery
Click to expand...
Click to collapse
Incorrect.
Root has nothing to do with a custom recovery. It are two completely separate things. You never need to be rooted to flash a custom recovery.
You probably just need to uncheck auto-reboot before flashing.

I always rooted before flashing a custom recovery.
And in every guide it said that I have to be rooted first. Or it just gave me that impression..

GDReaper said:
I always rooted before flashing a custom recovery.
And in every guide it said that I have to be rooted first. Or it just gave me that impression..
Click to expand...
Click to collapse
A binary has no relevance on a separate partition
Rooting before flashing a custom recovery is not required

GDReaper said:
I always rooted before flashing a custom recovery.
And in every guide it said that I have to be rooted first. Or it just gave me that impression..
Click to expand...
Click to collapse
Yes, guide makers tend to do that. But it's never needed.

I did a noob mistake, I pressed power, home and volume down. When I pressed power, home and volume up, it worked. Thank you for the feedback!

[Q] [GT-I9506] Can't flash any recovery via Odin

Just bought a phone, already upgraded to latest Lollipop firmware from Samsung.
Knox warranty is 0x0.
Now I want to flash Cyanogenmod, and first I tried to install recovery (CWM/TWRP). Downloaded odin 3.09.3, did everything according to tutorial, odin says everything is ok:
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Phone reboots into samsung firmware. Turning it off and holding vol up + home + power on brings stock recovery, no changes.
What should I do? Maybe bootloader is locked somehow? How to check and unlock? I did it once on a Nexus 10 tablet. Thanks!

Uncheck auto-reboot in Odin before flashing. That should fix it.

Lennyz1988 said:
Uncheck auto-reboot in Odin before flashing. That should fix it.
Click to expand...
Click to collapse
Thank you. Helped!

[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)

S4 does not run anymore after flashing TWRP

Hey guys,
i gut some serious problems with my Galaxy S4 (GT-I9505)
I was running Cyanogen Mod 12.1 with CWM Recovery. After trying to update to CM13 and the appropriate Gapps i noticed some problems installing gapps with CWM. After searching the internet i decided to try it with TWRP instead of CWM. So i used the App Rashr Flash Tool to Flash the latest TWRP Recovery.
After flashing TWRP i rebooted the device and got stuck at the Samsung welcome screen. In the right upper corner is displayed the following:
RECOVERY BOOTING. . . .
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Unfortunatelly the phone does not load the recovery or start the OS. The only option i recognized is to enter the download mode by pushing Home + Vol.Down + PWR.
So i tried to use Odin to reinstall TWRP correctly over download mode and this is what Odin puts out.
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
When i now restart the phone i got following message on the screen:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again
After installing Kies it says that my device is not supportet...
So no i have no idea what else i can do to get my phone running again...
Does anyone has an idea?
Best Regards and thanks

Did you try flashing the latest stock ROM from sammobile.com?
Maybe use Odin to flash the latest version of TWRP to see if you can enter recovery?

The solution is easy. Use a different usb port / different usb cable.

Well a different USB-Port got me one step further.
It seems that odin flashed the recovery successfully:
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1100)..
<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> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
After that my phone booted back into my current android / cm OS
Unfortunatelly, if i try to reboot directly into the recovery, i get stuck in the samsung welcome screen again. Means i can not access the recovery...

Use a different recovery thats my advice, i have a same issue as you maybe someone could help me, i open a new thread there also

Try this: unchecked everything except f.reset time in Odin before flashing TWRP, connect phone, flash TWRP, when you see the word "RESET" in the status windows, remove USB cable, remove battery, replace battery, use button combination to boot into recovery. When the phone powers up, let the power button go but keep holding home and volume up.

somehow i fixed it...
i re-re-reflashed twrp and suddenly everything went fine.
Thanks for your help and real quick responses!
great forum!

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