Database Users

[Q] Bricked N9007?

Ok, so today I tried to root my Note 3 N9007 via Odin 3.07 and autoroot files from chainfire. BUT, it seems like it doesnt worked... I did everything what was said in the tutorial here in the forum but no luck... Now I am stuck in Odin mode:
Current binary: Custom
System status: Official
Reactivation lock: OFF
Knox kernel lock: 0x0
Knox varanty: 0x0
Qualcomm secureboot: Enable
Write protection: Enable
Now log the from odin:
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-htdlte-htdltedi-smn9007.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks........

mkotruch said:
Ok, so today I tried to root my Note 3 N9007 via Odin 3.07 and autoroot files from chainfire. BUT, it seems like it doesnt worked... I did everything what was said in the tutorial here in the forum but no luck... Now I am stuck in Odin mode:
Current binary: Custom
System status: Official
Reactivation lock: OFF
Knox kernel lock: 0x0
Knox varanty: 0x0
Qualcomm secureboot: Enable
Write protection: Enable
Now log the from odin:
Removed!!
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
CF-Auto-Root-htdlte-htdltedi-smn9007.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
recovery.img
NAND Write Start!!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Thanks........
Click to expand...
Click to collapse
You tried root made for N9007 ??? Maybe a curropt dowload .try flashing again.
Btw to get back your device to work flash your official firmware through odin.
Sent from my SM-N9005 using Tapatalk

yep, it was a direct download from chainfire... IDK, hope the reflash will work... I am going to hang myself if it wont.

There are different files for 4.3 and 4.4

but not for 9007 bcs there is just Jelly Bean, no KitKat yet...
ok update, I am stuck with writing error... tried to flash official JB but still got the same error... anyone could help?

Used Odin 1.85? And right instructions.
Wipe cache and data reset

mkotruch said:
yep, it was a direct download from chainfire... IDK, hope the reflash will work... I am going to hang myself if it wont.
Click to expand...
Click to collapse
I'm guessing you have the Australian Optus device. If so I have the same one and successfully rooted mine (SM-N9007) last night without a problem! (Been running root apps ie. Titanium Backup and xposed framework)
I jumped on 'AndroidXDA.com' and downloaded CF-Auto-Root File from their guide. If your phone is bricked then download official firmware for SM-N9007 from sammobile and install using ODIN 3.09. Hopefully you'll be able to get it working.

Thanks, I managed to reinstall the stock rom and root it - the problem was with the usb connection, my pc has got problems with usb ports from time to time. So I switched to another pc and got it working

[Q] S5 G900X Demo Unit - I can need your help please :)

Dear members,
As following: i have a demo unit which i am trying too install with a original firmware.
I make use of the following tutorial http://forum.xda-developers.com/showthread.php?t=2733083
Downloaded the firmware from The Netherlands for the G900F (G900FXXU1ANCE_G900FPHN1ANC7_PHN)
I've made a backup of the demo-software and set it back for now since i can't get this firmware working on my phone.
When i am trying too send the file with Odin i do get the following error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANCE_G900FPHN1ANC7_G900FXXU1ANCE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Hopefully somebody can tell me what i do wrong?
The phone was wiped totally.
In download mode it says: (after trying with odin)
ODIN MODE
PRODUCT NAME: SM-G900X
CURRENT BINARY: Custom
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: 0xf (CSB)
WRITE PROTECTION: Enable
UDC START
SECURE CHECK FAIL : sbl1
When i see the above and i look to ''write protection'' it says that i can't send a new firmware to my phone, is that right?
I do really appreciate your answers and i will send a small donation via paypal to the person who has the golden answer for me :good:
Thanks in advance!

It is done now, download a custom recovery made by user: shebi
How can i change the bootloader image which says live demo unit?

I got a demo unit, installed stock s5 rom on it and had the same result. Then went on and installed cyanogenmod on it and everything worked but connecting to the mobile network.

wamelwamel said:
It is done now, download a custom recovery made by user: shebi
How can i change the bootloader image which says live demo unit?
Click to expand...
Click to collapse
Hi wamelwamel, I've been struggling with the exact same problem that you had, with my G900X. What did you do to solve the problem with yours?
D

does samsung galaxy g900f firmware work on samsung galaxy g900x
Answer me fast guys

SM-G900A boot-looping, odin failure.

I took this Galaxy S5 from my friend to fix as it was boot looping on him. A factory reset in recovery didn't help at all.
He told me he got the device second hand but here is the confusing bit. The model on the battery sticker states it's a G900F, the about device screen shows it's a G900F. However download modes is showing it's a G900A. Furthermore the device is running the firmware for the united arab emirates, my friend being from the UK. I have tried various firmwares however all fail in odin with the same problem:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> aboot.mbn
<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)
<ID:0/004> Removed!!
Click to expand...
Click to collapse
About System:
Model Number - SM-G900F
Android Version - 4.4.2
Baseband Version - G900FZHU1ANG1
...
Build number - KOT49H.G900FZHU1ANG1
...
Click to expand...
Click to collapse
Download Mode:
ODIN MODE
PRODUCT NAME: SM-G900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A2, P1
UDC START
Click to expand...
Click to collapse
Thanks.

If Download mode states G900A, then the phone is a G900A
All the other model versions, Settings > About, Phone info, stickers, etc, can all be changed, and often are changed to say G900F to sell the phone quicker as it is the more popular model
AT&T lock their bootloaders, you could try flashing a newer version of Android, 5.0 >
Or try KIES firmware recovery
Here is a 5.0 one click firmware recovery to try too
Code:
http://downloadmirror.co/android/KR/Copy-of-G900AUCU3BOC4-OneClick.zip

Soft Bricked and Odin stuck?

I tried installing a custom ROM on my Galaxy J5 SM-j500FN but i got stuck for about 3 hours on the samsung blinking logo so i decided to flash the stock ROM again. After downloading it and trying to flashing via ODIN I keep getting the same error over and over.
Error on ODIN:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1203)..
<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> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Error on the Download mode in the phone:
ODIN MODE
PRODUCT NAME: SM-J500FN
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
WARRANTY VOID: 0x1 (1)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, H1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
SECURE CHECK FAIL : aboot
Any kind of help is appreciated. Thanks in advance for every reply!

Tenebrific said:
I tried installing a custom ROM on my Galaxy J5 SM-j500FN but i got stuck for about 3 hours on the samsung blinking logo so i decided to flash the stock ROM again. After downloading it and trying to flashing via ODIN I keep getting the same error over and over.
Error on ODIN:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1203)..
<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> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Error on the Download mode in the phone:
ODIN MODE
PRODUCT NAME: SM-J500FN
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
WARRANTY VOID: 0x1 (1)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, H1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
SECURE CHECK FAIL : aboot
Any kind of help is appreciated. Thanks in advance for every reply!
Click to expand...
Click to collapse
I went through this model, but the model is the J500M.
After spending all day trying, late in the afternoon I ended up deciding to change the USB cables.
I tried 5 different ones being one of them that came with the ...
I got it with an old motorola cable ... lol
After that I also changed a stock rom because one that I had downloaded was from another version of J500M
Another thing I noticed is that at least in my device, after installing the rom stock I can not do root in it anymore.
I can install TWRP but when installing SuperUser it stays on this screen by running only the logo intermittently = x
I'm looking for a solution to this yet ...

Go to developers options in setting and click on OEM unlock then flash

It its stock no need to enable oem
Sent from my SM-J500F using Tapatalk

Tenebrific said:
I tried installing a custom ROM on my Galaxy J5 SM-j500FN but i got stuck for about 3 hours on the samsung blinking logo so i decided to flash the stock ROM again. After downloading it and trying to flashing via ODIN I keep getting the same error over and over.
Error on ODIN:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1203)..
<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> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Error on the Download mode in the phone:
ODIN MODE
PRODUCT NAME: SM-J500FN
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
WARRANTY VOID: 0x1 (1)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, H1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
SECURE CHECK FAIL : aboot
Any kind of help is appreciated. Thanks in advance for every reply!
Click to expand...
Click to collapse
This error usually pops up when the firmware image you are flashing is for another phone's model/variant instead. Could you pop off the battery and have a look at the sticker for your model and verify that it is correct?

Hi, I have j510fn and I was a rom tester,
I have a problem since I flashed
J510FNXXU2APK6_J510FNODD2APK2_J510FNXXU2APK2_HOME.tar.md5
to test light stock rom v3 from Kingraheel
what happens is that NOW I can't flash any other firmware by odin... when I click START it says FAIL and in my device there is this text in red
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
I just want to flash my OFFICIAL firmware
J510FNXXU1APG1_J510FNPHE1APG1_J510FNXWU1APFC_HOME.tar.md5
but I can't... only APK6 firmware works on odin... any other firmware works.... can you help me?
I don't have any NANDROID backup of previous versions... only of my actual firmware... APK6
My computer does not detect my device... I have the drivers installed, and I tried on all the USB ports... it charges but not open files.... PLEASE HELP
---------------------------------------
SOLVED, SAME PROBLEM? CONTACT ME

Here is HOW I SOLVED IT:
This error happens when you before have updated from "U1" to "U2" and then you try to flash a firmware with "U1" (UX appears in the firmware "name")
So, the simple solution is to flash the stock firmware with the same "UX" that you had before your device gor bricked.
In my case, testing KingRaheel's ROMS I flashed an Indian firmware (...U2APK6...) at this moment I didn't know I ****ed up. But don't worry, I simply had updated the "U" and how I didn't know it, I tried to flash lots and lots of firmwares with "U1" without knowing what was happening. After long nights, I tried to flash my last firmware from SPAIN (PHE) with "U2" and it worked.
I hope I helped you. I used SM-J510FN (J5 2016)
If you have another device, try the same but with your current model, any questions, ask by twitter/dm
Sent from my SM-J510FN using XDA Labs

Samsung Galaxy Grand Prime SM-G530R4 Build LMY47X.G530R4TYS1AQF1 fails CF-Auto-Root

Hi:
I`m new to smartphones but was a firmware engineer in the early 90`s. Recently I was given a Samsung Galaxy Grand Prime SM-G530R4 Build LMY47X.G530R4TYS1AQF1. I want to use a USB-connected device that needs OTG ability and this phone does not have it, but I read it could be turned on with root access. I have Odin on my system and I have the correct CF-Auto-Root from your related website, zip=cfar_samsung_sm-g530r4_gprimelteusc_lmy47x.g530r4tys1aqf1_t0. I`ve followed all the procedures I could find to allow the firmware to load without success. Using odin the load of the CF-Auto-Root image run about 33% then fails. The phone hangs then I need to load the recovery & boot image via odin which fixes it. This seems like a simple process but I am stumped... any help appreciated. Probably an easy fix for someone with experience.
Tom
On Phone Screen for Downloading...
ODIN MODE
PRODUCT NAME: SM-G530R4
CURRENT BINARY: Samsung Official
FRP LOCK: OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, H1, R1, A1, P1
SECURE DOWNLOAD : ENABLE
Unsupport dev_type
Added Failure Data from Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<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> cache.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Not Failure but no Root found on phone... yet
Since the info from Odin indicated Qualcomm SecureBoot I decided to create a CF-Auto-Root with the option for a cache file named cache.img.ext4. This allowed the load of the CF-Auto-Root image (I think) but after restarting the phone there is still no root found. What am I missing here? Below is the log info from Odin and the download screen of the phone AFTER the load attempt. superSU is not being installed or is not evident.
Odin log (image specifies cache.img.ext4.)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<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> cache.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/003> Added!!
Phone Download Screen After image (above) loaded.
ODIN MODE
PRODUCT NAME: SM-G530R4
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, H1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
Also noticed is that when powering on with the Power, Vol. up and Home keys pressed simultaneously the screen only shows:
Recovery is not Seandroid enforcing
Set warranty bit: Recovery
What does this mean?

SM-G530AZ
Anybody with an idea on how to root the Galaxy Grand Prime(SM-G530AZ)? Ive tried kingo root to no avail, really need help ASAP! thank you

Tried all CF-Auto-Root variants, no rooting of phone
teranz said:
Since the info from Odin indicated Qualcomm SecureBoot I decided to create a CF-Auto-Root with the option for a cache file named cache.img.ext4. This allowed the load of the CF-Auto-Root image (I think) but after restarting the phone there is still no root found. What am I missing here? Below is the log info from Odin and the download screen of the phone AFTER the load attempt. superSU is not being installed or is not evident.
Odin log (image specifies cache.img.ext4.)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<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> cache.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/003> Added!!
Phone Download Screen After image (above) loaded.
ODIN MODE
PRODUCT NAME: SM-G530R4
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, H1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
Also noticed is that when powering on with the Power, Vol. up and Home keys pressed simultaneously the screen only shows:
Recovery is not Seandroid enforcing
Set warranty bit: Recovery
What does this mean?
Click to expand...
Click to collapse
I`ve tried all the variants of CF-Auto-Root and none actually loaded root on my phone. I suspect I`m doing something simple wrong here, any suggestions appreciated.
Thanks, Tom

teranz said:
I`ve tried all the variants of CF-Auto-Root and none actually loaded root on my phone. I suspect I`m doing something simple wrong here, any suggestions appreciated.
Thanks, Tom
Click to expand...
Click to collapse
I`ll ask the obvious... If I loaded CF-Auto-Root properly to the phone wouldn`t it be rooted? If not what am I not seeing/doing? There is not a version of TWRP for it so do I have any other options?
Thanks much- Tom

teranz said:
I`ll ask the obvious... If I loaded CF-Auto-Root properly to the phone wouldn`t it be rooted? If not what am I not seeing/doing? There is not a version of TWRP for it so do I have any other options?
Thanks much- Tom
Click to expand...
Click to collapse
Success at last!!!
Follow this link to a webpage that can download a .tar.md5 file that actually sets the phone ROOTed and loads the SU app: https://androidfilehost.com/?fid=673956719939823811. ROOT status was verified with a RootChecker app. The file you are looking for is in: CF-Auto-Root-gprimelteusc-gprimelteusc-smg530r4.zip
I am open to questions.... I do not know if it mattered but I did a full factory wipe/reset and made sure the USB debug was on and the system allows OEM changes, and no google account for FRP.
Tom
Update....
Now that I have root access I tried some simple changes to the build properties I read about that did nothing to turn on OTG function. I`m not sure of drivers or other updates that may be possible, I can run the Android Studio and will investigate creating something that can be used to implement OTG functionality. Please post here if you have ideas about this.

H
Sent from my Samsung Galaxy Core Prime using XDA Labs

Investigating Kernel mod for USB/OTG
teranz said:
Success at last!!!
Follow this link to a webpage that can download a .tar.md5 file that actually sets the phone ROOTed and loads the SU app: https://androidfilehost.com/?fid=673956719939823811. ROOT status was verified with a RootChecker app. The file you are looking for is in: CF-Auto-Root-gprimelteusc-gprimelteusc-smg530r4.zip
I am open to questions.... I do not know if it mattered but I did a full factory wipe/reset and made sure the USB debug was on and the system allows OEM changes, and no google account for FRP.
Tom
Update....
Now that I have root access I tried some simple changes to the build properties I read about that did nothing to turn on OTG function. I`m not sure of drivers or other updates that may be possible, I can run the Android Studio and will investigate creating something that can be used to implement OTG functionality. Please post here if you have ideas about this.
Click to expand...
Click to collapse
From what I can determine my phone has the hardware needed for USB/OTG ability. The "easy fixes" don`t seem to hold much hope, so I am thinking that a kernel modification is the only realistic way to go. If someone can point me in the right direction to get that started that would be appreciated.
Thanks! Tom

teranz said:
Hi:
I`m new to smartphones but was a firmware engineer in the early 90`s. Recently I was given a Samsung Galaxy Grand Prime SM-G530R4 Build LMY47X.G530R4TYS1AQF1. I want to use a USB-connected device that needs OTG ability and this phone does not have it, but I read it could be turned on with root access. I have Odin on my system and I have the correct CF-Auto-Root from your related website, zip=cfar_samsung_sm-g530r4_gprimelteusc_lmy47x.g530r4tys1aqf1_t0. I`ve followed all the procedures I could find to allow the firmware to load without success. Using odin the load of the CF-Auto-Root image run about 33% then fails. The phone hangs then I need to load the recovery & boot image via odin which fixes it. This seems like a simple process but I am stumped... any help appreciated. Probably an easy fix for someone with experience.
Tom
On Phone Screen for Downloading...
ODIN MODE
PRODUCT NAME: SM-G530R4
CURRENT BINARY: Samsung Official
FRP LOCK: OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, H1, R1, A1, P1
SECURE DOWNLOAD : ENABLE
Unsupport dev_type
Added Failure Data from Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<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> cache.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try downloading the TWRP recovery for the s920l variant it works perfectly with this variant and install SuperSU or natural using this custom recovery
---------- Post added at 08:43 PM ---------- Previous post was at 08:39 PM ----------
After you install the TWRP look into a custom ROM for the s920l with otg support but TWRP also has otg support