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

SM-N910F won't install TWRP after reinstalling stock firmware

Hello, I wonder if someone will be able to help with the following problem please.
I made the bad decision of installing Quick Boot on my rooted SM-N910F with stock firmware and it rendered my phone unbootable. I couldn't get to TWRP or anything, so I went in Odin and installed my N910FXXU1BOB4_N910FOXA1BOB4_DBT firmware, but now I don't have a custom recovery anymore and I don't have root.
I've tried to flash twrp-2.8.7.0-trltexx.img.tar with Odin3_v3.10.6 (tried other versions of both as well), but it keeps failing.
The phone says:
Code:
SECURE CHECK FAIL : recovery
Odin log:
Code:
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<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>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone screen and Odin screenshot, etc. (sorry, noob with no permission to post links yet):
imgur.com/a/SO6r0
Do you know what I can do to root the phone?

[SM-N910*] CF-Auto-Root

_mone said:
[SM-N910*] CF-Auto-Root
Click to expand...
Click to collapse
same deal
Code:
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img.ext4
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

same here, flashing with odin and passes, reboot into recovery and it comes up with installing an update. fails and back to stock.

scrott901 said:
same here, flashing with odin and passes, reboot into recovery and it comes up with installing an update. fails and back to stock.
Click to expand...
Click to collapse
I really hope there's a solution, because I can't even back up my phone without root now...

mkirilov said:
I really hope there's a solution, because I can't even back up my phone without root now...
Click to expand...
Click to collapse
Is your reactivation lock turned off?

no my reactivation lock is off. has anyone been able to root? dont want to try encase it ***** up
ok just did cf-root and this worked fine. anyone tried TWRP Manager from playstore?

I have been able to install twrp
First root phone with cf-root via odin and confirm root was successful.
Download the .img file from here https://dl.twrp.me/trltexx/
Then install Flashify from Playstore. Make a backup of your recovery first to be safe.
Now select Flash, recovery image and then choose file. Navigate to the .img file and flash away.
Job done, time for a custom rom

_mone said:
Is your reactivation lock turned off?
Click to expand...
Click to collapse
I'm a noob, I didn't realize it was switched on. Thank you! I've now been able to install TWRP and SuperSU :highfive:

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!

Please Help to Flash Samsung Grand Prime G530H/DS KitKat XSE

Guys, i need your help..
my device bootloop.
Product Name: SM-G530H
Current Binary : Custom
System Status: Custom
here'e some information about the device and the tools:
1. debugging mode : OFF
2. root status : Unroot
3. Firmware : Official KitKat 4.4.4. G530HDCU1AOF1 (Indonesia)
4. Windows 7 SP1 32-bit
5. Samsung-USB-Driver-v1.5.63.0
6. (Odin 3.04, Odin 3.07, Odin 3.12 )
I try to :
1. wipe data/ cahe, the result is none...
2. root device via Odin, failed.
3. Flash via odin with some firmware ( HDC, HXX, HXC) the result also failed..
=============================================================
<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> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> sec.dat
<ID:0/003> boot.img
<ID:0/003> FAIL! (Erase)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
==================================================================
4. Change usb port, change usb cable, still not fix the problem..
Why i can't flash the device via Odin? and how to fix it?
Please help me...

Hi..
Ok I have a couple of Questions.
Have u try flashing Stock ROM into it?
Remove the battery first and insert it back and enter Download Mode manually by pressing HOME, Vol DOWN and Power button. It will ask u to press Vol UP to confirm.
I had this experience before and manage to fix it by entering download mode manually and not from adb command.
If that not fixing or u still get stuck, please revert back here.
Gudluck!

RidzVarn said:
Hi..
Ok I have a couple of Questions.
Have u try flashing Stock ROM into it?
Remove the battery first and insert it back and enter Download Mode manually by pressing HOME, Vol DOWN and Power button. It will ask u to press Vol UP to confirm.
I had this experience before and manage to fix it by entering download mode manually and not from adb command.
If that not fixing or u still get stuck, please revert back here.
Gudluck!
Click to expand...
Click to collapse
"Have u try flashing Stock ROM into it? "
how can i do that?
yeah im flashing just like that you mention above...im not have any idea to do another way..

zayra.qu33n said:
"Have u try flashing Stock ROM into it? "
how can i do that?
yeah im flashing just like that you mention above...im not have any idea to do another way..
Click to expand...
Click to collapse
Alright.. please try with this stock ROM.
http://www.mediafire.com/file/ez4d3zhhoz94gcc/G530HDCU1AOA2_G530HOLB1AOA2_v4.4.4_4File.zip
Flash using Odin and follow earlier steps.
Best of luck! :good:

Still failed to flash... using the firmware above
================
<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> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> sec.dat
<ID:0/003> boot.img
<ID:0/003> FAIL! (Erase)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

zayra.qu33n said:
Still failed to flash... using the firmware above
================
<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> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> sec.dat
<ID:0/003> boot.img
<ID:0/003> FAIL! (Erase)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Sorry to hear that.
Which version of Odin u use? try with Newest version 3.12.x Odin and other different versions too.. It does the trick sometimes..
And in option TAB, tick on Repartition mode.

RidzVarn said:
Sorry to hear that.
Which version of Odin u use? try with Newest version 3.12.x Odin and other different versions too.. It does the trick sometimes..
And in option TAB, tick on Repartition mode.
Click to expand...
Click to collapse
i tried with Odin v1.85, v3.04, v3.07, v3.10, v3.12.5, v3.12.2, v3.12.3, v3.13.1B_Patched but no different result .... still failed with same error message..
just stuck in boot.img.....
maybe the problem is debugging mode on my device is disabled and i dont know how to enabled it because the device stuck in Odin Mode.
i found this article to enabled debugging mode but i dont know how to using ADB – USB Debugging.
https://www.isrgrajan.com/how-to-enable-usb-debugging-in-android-using-recovery-mode.html

zayra.qu33n said:
i tried with Odin v1.85, v3.04, v3.07, v3.10, v3.12.5, v3.12.2, v3.12.3, v3.13.1B_Patched but no different result .... still failed with same error message..
just stuck in boot.img.....
maybe the problem is debugging mode on my device is disabled and i dont know how to enabled it because the device stuck in Odin Mode.
i found this article to enabled debugging mode but i dont know how to using ADB – USB Debugging.
https://www.isrgrajan.com/how-to-enable-usb-debugging-in-android-using-recovery-mode.html
Click to expand...
Click to collapse
I dont think so.. Debugging mode is not needed when flashing via Odin. but I'm more to doubt of corrupted bootloader.
Can u enter Recovery mode by any chances? Vol Up + HOME + Power.
And if yes, are u using Custom Recovery or stock?
Try to flash only recovery to TWRP
REFER HERE :
https://forum.xda-developers.com/grand-prime/general/twrp-odin-flashable-tar-md5-official-t3550153

The recovery mode was missing..i cant accsess anymore to recovery mode...

zayra.qu33n said:
The recovery mode was missing..i cant accsess anymore to recovery mode...
Click to expand...
Click to collapse
Try to flash Recovery.img only using Odin. Dowmload TWRP recovery.img from link given above and see if it work.
Best of luck!