Related
Phone: S4 Active GT-I9295
This is a collection of knowledge from xda-forum and own experience. Consider information found here as advise to avoid possible issues.
Please give feedback if material presented here helped or need correction. Contributors are welcome and due credit will be placed.
Remember to give credit when you copy advice from my thread.
Qcomm based phones i9295 and i9505 need same procedure when flashing. Files to flash is not interchangeable between the phones. Method to flash any item SUCCESSFULLY in Download Mode using Odin is described in this thread.
Some guides may tell you to flash firmware, baseband or modems twice using Odin in Download Mode to "make it stick" or say there is an "unknown bug somewhere". People usually loose IMEI and/or WiFi because they have entered download mode using wrong method and started flash of modem, non-hlos.bin or firmware.
The reason the flashed file won't stick on first attempt is that you have entered download mode by software reboot menu or holding Vol- while rebooting. Don't enter download mode when phone is rebooting.
Remember that you are responsible for every action you do to your phone.
If you don't have Samsung Kies the Samsung USB drivers is reccomended to install before running Odin and connecting PC-USB-PHONE.
Never run Odin to flash phone in Download Mode on the same PC where Samsung Kies is running. Odin and Kies will fight to gain control of USB connected device. Close all running Kies processes in Task Manager or uninstall Kies.
Some Windows installations need to run a Fix It from Microsoft Support to properly detect Samsung phone even after installation of Samsung Android USB driver.
Always connect phone directly to 5V-powered PC USB port - never USB hub.
Use original USB cable or make sure it is in good condition. Cable working for charging can have broken wire making it unusable for communication and file transfer.
GSM modem (modem.bin, *.tar, *.tar.md5) or LTE modem (NON-HLOS.bin, *.tar, *.tar.md5 ) can be flashed using Odin form PHONE/CP without repeating the flash twice.
Download Mode
Why
To flash (change/update) phone recovery, firmware, kernel, bootloader or modem using computer software Odin or Heimdall with phone connected by USB to computer.
How
Completely Power Off , wait at least 5 seconds after vibration or led stop blinking. Now you can enter download mode:
Power + VolDown buttons pressed
Release Power after vibration
Release VolDown when screen turn on
VolUp to confirm
Start Odin as Administrator
Connect USB cable PC-PHONE and make sure ID:COM confirm "Added" phone in Odin
Remark: Home button is NOT USED
Recovery Mode
Why
To flash (change/update) phone custom recovery, custom ROM, SuperSU or kernel by install zip from Custom recovery like TWRP or CWM.
How
Can be entered from the phone reboot menu OR from phone in powered off state:
Power + VolUp buttons pressed
Release Power after vibration
Release VolUp when you see blue text RECOVERY BOOTING.... in upper left corner of screen
Remark: Home button is NOT USED
ROOT
When you have stock recovery and plan to flash a custom recovery like TWRP or CWM (ClockWorkMod) the first time, you need to enter Recovery Mode immediately on first boot after Odin flash custom recovery.
The steps are independent of the stock Android version currently installed on your phone, this is how it's done for both Kitkat 4.4x and Lolipop 5.0x
The steps are also independent of which custom recovery (CWM-based or TWRP)
you prefer.
Advice to use the latest version custom recovery built for i9295 - linked in post #3
WARNING: The CWM built by LeJay back in 2013 on CM10.2 source (=CWM-Recovery-gt-i9295_v1-2.tar.md5) do not support external SD card or Nandroid backup/restore for Samsung Kitkat 4.4x or Lolipop 5.0.x. That recovery is outdated.
Make sure you have minimum 60% battery capasity
1st step - Install custom recovery
Copy SuperSU(latest).zip to phone storage
Power off, Boot phone to Download Mode
Start Odin with AutoReboot disabled, Re-Partition disabled
Connect USB cable PC-PHONE
Odin flash (CUSTOM-RECOVERY).TAR.MD5 as PDA
Disconnect USB cable
Remove phone battery - wait - insert battery
Enter Recovery Mode
2nd step - Install SuperSU from custom recovery, TWRP or CWM
TWRP touch "install" / CWM go to "install zip" by VOLUME buttons
TWRP touch-select / CWM select by pressing POWER button
Browse to and select SuperSU(latest).zip
Reboot
Download files from links in post #3:
(USB drivers, Odin, Custom recovery, SuperSU)
If you wonder what is baseband, baseband version, GSM modem, LTE/4G modem, and find time to read and courtesy to suppress the urge to ask same question recently explained -
... here is a treat for you:
MODEM.BIN and NON-HLOS.BIN HOW-TO flash using Odin
Alternative solution
Thanks @Formhault
What version of modem.bin can you flash?
Thanks @hawkerpaul
Make sure you have non-hlos.bin and bootloader version match:
http://forum.xda-developers.com/showthread.php?p=62994941
Samsung lettercode decoded for firmware/bootloader/modem
Example: I9295XXUCNE4
I9295 = phone model
XXU = baseband (XXU is Global, valid almost everywhere, any country regardless of carrier)
C = baseband build version
NE4 = datecode
Datecode
N = year = 2014 (14th letter of alphabet)
E = month of year (May in this case, 5th letter of the alphabet)
A = build # of that month (10th for, "A", as they start 1-9, then letters)
NE4 = 2014, May, Build 4
NE5 = 2014, May, Build 5
NH2 = 2014, Aug, Build 2
Identify your bootloader
Make sure you have LTE/ audio/ network certificate (=NON-HLOS.bin) version matching your bootloader (=ABOOT, SBL*, TZ) version. Reason explained in 1st post.
NON-HLOS.bin inside the apnhlos partition /firmware and the bootloader is never updated or downgraded by AOSP/CM ROMs or custom recovery flashing. Some customized stock ROMs may mess with the relationship between bootloader and NON-HLOS.bin. Or you have messed up because you wanted to have the latest modem and flashed a *N-- version NON-HLOS.bin on your *M-- version bootloader. This will have bad impact on sound and WiFi functionality leading to you can not activate WiFi.
Earlier versions of PhilZ CWM recovery had an option to wipe partitions
/firmware
(LTE, audio, network certificate, NON-HLOS.bin)
/firmware-mdm
(GSM-modem, MODEM.BIN)
This wipe was not needed because flashing to this partitions overwrite the existing content. Wiping the same partitions without flashing modem or complete stock ROM can render telephone, audio and network functionality useless.
The partitions /firmware and /firmware-mdm is removed from later PhilZ Recovery fstab.
Ref. PhilZ Recovery 6.23.9 change log http://forum.xda-developers.com/showpost.php?p=51389599&postcount=3520
Identify bootloader and select corresponding NON-HLOS.bin
NON-HLOS.bin is also called LTE-modem or WiFi-fix when discussed in xda-forum
1. Connect phone from ADB or use Terminal app and do this command:
Code:
getprop ro.bootloader
( ADB =Android Debug Bridge )
The output is Samsung lettercode and will tell what version of bootloader you currently have.
2. Select version of NON-HLOS.bin to flash according to 3rd last letter of Samsung lettercode bootloader:
BOOTLOADER 3rd last letter = NON-HLOS.bin 3rd last letter
I9295xxxxMxx = I9295xxxxMxx JellyBean 4.2.x
I9295xxxxNxx = I9295xxxxNxx KitKat 4.4.x
I9295xxxxOxx = I9295xxxxOxx Lollipop 5.0.x
Not known exactly what's first version of i9295 firmware/bootloader that has Knox feature. Strong indications nominate all KitKat 4.4.x to have it on QualComm based phones. And GT-I9295 has QualComm chipset.
Updating bootloader to a higher version should not trigger Knox 0x1, but downgrade Knox featured bootloader may cause that.
Status of KNOX is shown in Download Mode upper left corner of screen.
This S4 thread discuss the limitation introduced by Knox:
http://forum.xda-developers.com/showthread.php?p=45666586
Samsung firmware
Sammobile and Samdownloads links removed for violating XDA rules 11 & 13
7-zip v9.3x beta
- Bootloader, modem.bin, NON-HLOS.bin can be extracted from firmware tar package using 7-zip. The extracted files can be flashed one-by-one using Odin or Heimdall.
Heimdall
- a cross-platform open-source tool suite used to flash firmware (aka ROMs) onto Samsung mobile devices.
Odin v3.07
- Samsung (leaked) tool to flash firmware files to phone from Windows.
- default setup with unticked Auto Reboot, best setting for recovery 1st time flash.
- faster summary of flash results, 10 seconds.
(attachment)
Samsung USB Drivers for Mobile Phones (v1.5.45.0)
MultiROM TWRP
- custom recovery
[quote name="O-T" post=57277967]Interested in replace CWM 6.0.5.0 with TWRP. Not sure if ready to use the rest of mulirom setup yet. Is TWRP stand-alone capable of replacing CWM in a single ROM setup?[/QUOTE]
Developer spegelius reply:
"Yes, TWRP works without MultiROM. There are few checkboxes, like Inject MultiROM that need to be disabled when installing roms for example, but basic stuff works without multirom."
CF-Auto-Root
- install and enable SuperSU on your system, so apps can gain root access.
- Odin included and pre-setup to flash root to phone from Windows.
What's installed
SuperSU binary and APK
Stock recovery (note that any other recovery you may have installed will be overwritten !)SuperSU
- install and enable SuperSU on your system, so apps can gain root access.
- SuperSU flashable zip is installed using custom recovery (like TWRP)
What's installed
SuperSU binary and APK
Credits
@spegelius MultiROM TWRP
@Chainfire CF-Auto-root, SuperSU
Bevare the Thanks Button under each post - it's there for you to show you are happy to receive help
Dear friend,
I read carefully all the tread but was unable to determine weather my device can be TWRP recovered via Odin or not (multirom_twrp_20150215_000001.zip - from your repository).
I feel a bit dumb to ask but would really appreciate some help.
GT-I9295
4.4.2
I9295XXUCNI1
Default KARNEL
Already ROOTED - CF-Auto-Root-jactivelte-jactiveltexx-gti9295.zip
Thanks in advance and sorry for bothering you
Thomas.A.A said:
Dear friend,
I read carefully all the tread but was unable to determine weather my device can be TWRP recovered via Odin or not (multirom_twrp_20150215_000001.zip - from your repository).
I feel a bit dumb to ask but would really appreciate some help.
GT-I9295
4.4.2
I9295XXUCNI1
Default KARNEL
Already ROOTED - CF-Auto-Root-jactivelte-jactiveltexx-gti9295.zip
Thanks in advance and sorry for bothering you
Click to expand...
Click to collapse
If you're still running Samsung default recovery start to flash multirom_twrp_20150215_000001.tar.md5 in Download Mode using Odin. Zip packed twrp recovery has built in update script made for updating from custom recovery only. You can use zip packed to update or change only after custom CWM based or TWRP recovery is installed in phone. Zip file can then be copied to phone internal storage or SD card and run from custom recovery to update when you want to update/downgrade or change to a different recovery.
Custom recovery doesn't run tar or tar.md5 files. They are made for Odin or Heimdall flashing.
O-T said:
If you're still running Samsung default recovery start to flash multirom_twrp_20150215_000001.tar.md5 in Download Mode using Odin.
Click to expand...
Click to collapse
Thanks for the quick reply (really appreciated!)
Though... I am now even more confused X*X*X!!
Still I will follow your lead:
1. I will Flash multirom_twrp_20150215_000001.tar.md5 in Download Mode using Odin
2. I will do NOT Flash multirom_twrp_20150215_000001.zip in Download Mode using Odin, because...
O-T said:
Zip packed twrp recovery has built in update script made for updating from custom recovery only.
Click to expand...
Click to collapse
and also because...
Custom recovery doesn't run tar or tar.md5 files. They are made for Odin or Heimdall flashing.
Click to expand...
Click to collapse
3. Afterwards, I can freely do the hack I want with ZIP packed, since:
You can use zip packed to update or change only after custom CWM based or TWRP recovery is installed in phone. Zip file can then be copied to phone internal storage or SD card and run from custom recovery to update when you want to update/downgrade or change to a different recovery.
Click to expand...
Click to collapse
Sorry I am so dumb.... Thanks for posting
Really appreciated
1 yes
2 yes
3 yes. Perhaps update root to latest SuperSU 2.46 by recovery flashing.
http://forum.xda-developers.com/showthread.php?p=23427715
All right. Read some posts about TWRP in that thread to learn how to use recovery.
Is it possible to downgrade from 5.0.1 bootloader to 4.2.2?
tasken said:
Is it possible to downgrade from 5.0.1 bootloader to 4.2.2?
Click to expand...
Click to collapse
The link in 1st post to investigation by Chainfire is for S4 i9505 from 442 to 422.
Did you read that?
I was able to do it through odin without breaking knox
tasken said:
I was able to do it through odin without breaking knox
Click to expand...
Click to collapse
If you have been recovery flashing CM12 5.0.1 lately the bootloader is never touched or updated to any version.
Are you sure you had OB4 lollipop 5.0.1 bootloader?
Update
Add confirm step in download mode
Rearrange paragraph in OP
Update
add SuperSU and TWRP to recovery Why
Update:
- added link to latest Samsung USB drivers
- tidy up post #3 with inline links
Bevare the Thanks Button under each post - it's there for you to show you are happy to receive help [emoji106]
Update :
- rooting steps in post #1
The steps are independent of the stock Android version currently installed on your phone, this is working for both Kitkat and Lolipop.
The steps are also independent of which custom recovery (CWM-based or TWRP)
you prefer. Advice to use the latest version built for i9295 - linked in post #3.
CWM and TWRP steps added to post #1
to Root ANY version of Android
MODEM.BIN and NON-HLOS.BIN
- rewrite how to flash correct version
Hi.
I have a i9295 and I experience problems with log-offs or sim disconnects while wifi is working well.
Will a reflash of modem.bin help?
If yes: where can i get the file required for odin of recovery flash?
Thanks in advance
augek said:
Hi.
I have a i9295 and I experience problems with log-offs or sim disconnects while wifi is working well.
Will a reflash of modem.bin help?
If yes: where can i get the file required for odin of recovery flash?
Thanks in advance
Click to expand...
Click to collapse
Shouldn't be needed if you did this http://forum.xda-developers.com/showthread.php?p=61418876
correctly.
You can do a factory reset.
Read post 1-3 slowly if you need modem.bin, non-hlos.bin or bootloader of right version for you.
ThumbsUp button under every post is free to use in case you're in the mood to show appreciation.
Hi.
I did read and still am not sure about it.
I've done factory reset with every flash but still the problem persists.
Tried a different sim, still on joy.
From the thread linked i can not see where to find the modem for lollipop.
When the mobile disconnects phono tells me ihre some 14 - 16 asu. So service is available.
Drives me nuts.
TWRP 3.0.2-1. for the Samsung Galaxy A9 pro SM-A910/9100 - Qualcomm MSM8976
Please note I don't own this device.
Stock Recovery is posted below if required.
NOTE:
FLASHING CUSTOM STUFF VOIDS YOUR WARRANTY. THIS WILL TRIP THE KNOX FLAG.
Install:
Boot to download mode.
Flash with Odin using the AP slot.
Uncheck Auto-reboot.
Reboot to recovery immediately after flashing using POWER + HOME + VOL DOWN, as soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
TWRP should now boot.
NOTE: ON SOME ANDROID 5.1.1 and 6.01 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Install with ODIN:
twrp_3.0.2-1_sm-a910f_25716
Update 8/2/2017
Fixed build for latest firmware :
twrp_3.0.2-1_sm-a910_a9100_7217
Stock recovery:
A910FXXU1APFC_stock_recovery
IMPORTANT
At the moment TWRP isn't working with encryption, this means the DATA Partition and internal storage cannot be mounted.
To mount the Data partition encryption needs to be removed and the boot image patcher needs to be flashed below
This can be done via the FORMAT DATA button under the WIPE option in TWRP.
Please note this will erase all user data.
The boot image patcher can be flashed with TWRP.
The boot image patcher MUST be flashed before booting the device to system or the DATA partition will be re-encrypted at boot time.
BOOT IMAGE PATCHER
Boot image patcher to remove DM-verity and Forced encryption.
Instead of flashing one of the boot images above flash the zip below with TWRP.
This was built by jcadduono not me, so props to him, I just modified it to work for this device and to remove the SEANDROID ENFORCING message.
Steps:
1. BOOT TO TWRP
2. FORMAT DATA
3. FLASH SUPERSU
4. FLASH THE BOOT IMAGE PATCHER
5. REBOOT TO RECOVERY
6. CHECK DATA IS STILL MOUNTABLE
no-verity-no-encrypt_ashyx
TO ROOT
Flash the file below in twrp.
http://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Reserved
Thanks mate
everything is working
---------- Post added at 12:49 ---------- Previous post was at 12:43 ----------
may you know how to do Custom Boot Splash for A9100 pro ?
Hi, I'm on firmware A9100ZCU1APD5 so these boot images wont work right. So now to be able to mount data, what I got is that I'll have to first wipe data in twrp and then flash the boot image patcher in order to get full access to twrp?
omar.abbas said:
Hi, I'm on firmware A9100ZCU1APD5 so these boot images wont work right. So now to be able to mount data, what I got is that I'll have to first wipe data in twrp and then flash the boot image patcher in order to get full access to twrp?
Click to expand...
Click to collapse
TWRP >BOOT IMAGE PATCHER >FORMAT DATA >SUPERSU
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
ashyx said:
TWRP >BOOT IMAGE PATCHER >FORMAT DATA >SUPERSU
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Thanks I'll try now and get back to you
Sent from my SM-A9100 using XDA-Developers mobile app
Wow thanks a lot it works. Dont have to change the language to English everytime I boot into recovery ? and can finally make backups. Thanks once again, you're the man!!
Sent from my SM-A9100 using XDA-Developers mobile app
Thanks, hope for more development.
Thanks for the development, not much out there for the A9100/A910f. Own a A9100(CH), which came without any Google apps and full of Chinese applications and region locked. Was able to load recovery and unencrypt boot, root, sideload Google apps. Is there a way to remove my region lock? Wish someone would develope the A910f international firmware to port over to the A9100. The A9 phone has some pretty impressive specs, hope for more development. Thank you.
gsnewport said:
Thanks for the development, not much out there for the A9100/A910f. Own a A9100(CH), which came without any Google apps and full of Chinese applications and region locked. Was able to load recovery and unencrypt boot, root, sideload Google apps. Is there a way to remove my region lock? Wish someone would develope the A910f international firmware to port over to the A9100. The A9 phone has some pretty impressive specs, hope for more development. Thank you.
Click to expand...
Click to collapse
By region lock you mean unable to flash with ODIN?
You can use FLASHFIRE to flash the stock firmware.
Sent from my SM-T280 using XDA-Developers mobile app
ashyx said:
By region lock you mean unable to flash with ODIN?
You can use FLASHFIRE to flash the stock firmware.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
No, flashed recovery with Odin. I mean by region locked is the csc file is just for China and it's the only csc on the phone. So I'm seeing some Chinese in some of the stock apps still even though I changed the language to english. Location is working for me. But some of the apps still show Chinese
gsnewport said:
No, flashed recovery with Odin. I mean by region locked is the csc file is just for China and it's the only csc on the phone. So I'm seeing some Chinese in some of the stock apps still even though I changed the language to english. Location is working for me. But some of the apps still show Chinese
Click to expand...
Click to collapse
So what's actually stopping you from flashing another rom? Like I say you can use Flashfire.
Would like to stay stock Marshmallow 6.0.1. Tried to flash the rom for the A910f but if failed, same with the A9000(Android L). Both of these roms have multiple crc files for other regions. I think the failure is being caused by partition size. Didn't want to mess with for fear of bricking.
ashyx said:
So what's actually stopping you from flashing another rom? Like I say you can use Flashfire.
Click to expand...
Click to collapse
Have you tried it? Does it work? I tried using Odin but got some partition size errors and soft bricked my phone. So just need to make sure before I give Flashfire a go.
Sent from my SM-A9100 using XDA-Developers mobile app
So the actual failure to flash is the partition size, but which partition is failing?
More info needed here.
There are ways of adjusting the partition size on the device by simply flashing with the required PIT file.
Or the actual image itself can be resized to fit.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
ashyx said:
So the actual failure to flash is the partition size, but which partition is failing?
More info needed here.
There are ways of adjusting the partition size on the device by simply flashing with the required PIT file.
Or the actual image itself can be resized to fit.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
I can't remember which partition size error it was as it was a few days ago. So do you know anyone who has done that on this phone successfully? Because if it is possible then thats all I'd want right now.
Sent from my SM-A9100 using XDA-Developers mobile app
omar.abbas said:
I can't remember which partition size error it was as it was a few days ago. So do you know anyone who has done that on this phone successfully? Because if it is possible then thats all I'd want right now.
Sent from my SM-A9100 using XDA-Developers mobile app
Click to expand...
Click to collapse
It is possible as I myself have done it with other devices.
If you can try the flash again with ODIN and then post the output log then we can find out which partition fails.
Just reflash your stock firmware after the failure.
By the way I don't own this particular device.
In the meantime I'm going to download the stock A9100 firmware and check the image sizes against the a910f firmware.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
I tried to flash the A910F with Odin and It's give Auth fail on pitfile and stops there. I downloaded the firmware via samfirm 0.36 with binary to get the full 4 firmware files. Extract the pit file, point to it in Odin and BL, CSC, CP, AP in their slots and it always fail. Also does not work with flashfire with a single firmware file.
But now there is another way, I did it yesterday and works great. No Chinese! Credits to @dadimon29. You flash the full A9100 firmware but untick autoreboot. Once finished you boot back in download mode and flash @ashyx TWRP with Odin with no reboot. Reboot again to TWRP, flash the no-verity-no-encrypt_ashyx.zip, reboot again to twrp, now format data not wipe! Mount system and flash Supersu, your own CSC file and GPS.conf for your region and the GAPPS micro package. Now reboot to samsung and you will find everything is English or whatever language you prefer. And Google works out of the box, no permission errors. Now I can keep this phone!
steberg said:
I tried to flash the A910F with Odin and It's give Auth fail on pitfile and stops there. I downloaded the firmware via samfirm 0.36 with binary to get the full 4 firmware files. Extract the pit file, point to it in Odin and BL, CSC, CP, AP in their slots and it always fail. Also does not work with flashfire with a single firmware file.
But now there is another way, I did it yesterday and works great. No Chinese! Credits to @dadimon29. You flash the full A9100 firmware but untick autoreboot. Once finished you boot back in download mode and flash @ashyx TWRP with Odin with no reboot. Reboot again to TWRP, flash the no-verity-no-encrypt_ashyx.zip, reboot again to twrp, now format data not wipe! Mount system and flash Supersu, your own CSC file and GPS.conf for your region and the GAPPS micro package. Now reboot to samsung and you will find everything is English or whatever language you prefer. And Google works out of the box, no permission errors. Now I can keep this phone!
Click to expand...
Click to collapse
Could you tell me what firmware files you downloaded exactly? When you reboot your phone, does it show Galaxy A9 Pro in english? I'm still a little confused on the procedure too
Sent from my SM-A9100 using XDA-Developers mobile app
In order to get rid of the Chinese when you boot up I guess you have to flash the bootloader from A910F but you can't.
Download Samfirm 0.36 and download the latest SM-A9100 firmware.
http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Be sure to tick Binary Nature.
gsnewport said:
Thanks for the development, not much out there for the A9100/A910f. Own a A9100(CH), which came without any Google apps and full of Chinese applications and region locked. Was able to load recovery and unencrypt boot, root, sideload Google apps. Is there a way to remove my region lock? Wish someone would develope the A910f international firmware to port over to the A9100. The A9 phone has some pretty impressive specs, hope for more development. Thank you.
Click to expand...
Click to collapse
You can try this out.
I have repacked the A910F firmware so it will be flashable on the A9100. I have replaced the A910F build.prop with the A9100 build.prop to help prevent boot issues.
It is the system image only. It should flash fine with ODIN in the AP slot. Whether it will boot or not is another matter, but I should think it will. If everything will be working, I don't know.
It may also be necessary to flash the A910F kernel boot.img. NOTE: this boot.img does not support encryption.
A910FXXU1APFC_no_encryptable_boot
Make sure you have a TWRP backup of the system partition or the stock firmware before flashing just in case you need to restore.
sm-a9100_system.img.tar.zip
.
.
I'm having the the problem after try to flash (N920LKLU2DQC7_N920LLUC2DQC7_N920LKLU2DQC4_HOME.ta r). Odin3 v3.12 stuck at initialization step as image attached. Also try with Odin3 v3.07 and Odin3 v3.10.6 with the same problem. Maybe because FRP lock in ON status or anything else? Need help ASAP
Screen info on Download Mode
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-N920L
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
Secure Download: Enable
KNOX WARRANTY VOID: 0 (0х0000)
RP SWREV: B:2 K:0 S:0
Try again after enabling 'OEM Unlock' in the Developer Options. By doing so FRP lock will be off.
And what exactly are you trying to do...?
Shiv Parmar said:
Try again after enabling 'OEM Unlock' in the Developer Options. By doing so FRP lock will be off.
And what exactly are you trying to do...?
Click to expand...
Click to collapse
Actually, this is phone come from stock official rom, which is received OTA update from samsung then try to download the updates but it's stuck during updating. Now this phone, can boot into download mode only.
I can't boot into system anymore and turn the on the OEM unlock function in developer mode.
Is there solution to resolve this. TIA
Im just guessing; since the OP doesn't flash a custom stuff like twrp recovery, OEM unlocking is not necessary. And the knox is hasn't tripped yet as i see. I would try another usb port, different version of odin(run as administrator) and be sure usb drivers are correctly installed on the PC. If all is OK; just try flashing the fw version which came installed on the device. If it success, enable oem unlock then try flashing latest fw and keep the OEM unlock enabled for future plans like rooting etc.
Mi MIX
7.5.4 Épic
Konsstantine34 said:
Im just guessing; since the OP doesn't flash a custom stuff like twrp recovery, OEM unlocking is not necessary. And the knox is hasn't tripped yet as i see. I would try another usb port, different version of odin(run as administrator) and be sure usb drivers are correctly installed on the PC. If all is OK; just try flashing the fw version which came installed on the device. If it success, enable oem unlock then try flashing latest fw and keep the OEM unlock enabled for future plans like rooting etc.
Mi MIX
7.5.4 Épic
Click to expand...
Click to collapse
FYI, I already try to flash with different Odin like v3.12, v3.07 and v3.10.6 but still same stuck at initialization step but I'm not flash the fw which is came at first because I dont know what the previous fw. The fw that I try to flash is original samsung fw from sammobile which is the latest ones (Nougat 7.0), actually this device is not mine, its my friend device that need my help to resolve it.
Maybe this device is from 5.0 and received OTA update for 6.0, maybe I should try to flash with 5.0 version first the try 6.0 later. Anyway thanks for advice @Konsstantine34
Do refer attachment, which version should I flash it?
antuketot76 said:
FYI, I already try to flash with different Odin like v3.12, v3.07 and v3.10.6 but still same stuck at initialization step but I'm not flash the fw which is came at first because I dont know what the previous fw. The fw that I try to flash is original samsung fw from sammobile which is the latest ones (Nougat 7.0), actually this device is not mine, its my friend device that need my help to resolve it.
Maybe this device is from 5.0 and received OTA update for 6.0, maybe I should try to flash with 5.0 version first the try 6.0 later. Anyway thanks for advice @Konsstantine34
Do refer attachment, which version should I flash it?
Click to expand...
Click to collapse
Upgrading from X to latest fw; shouldn't be a problem, downgrade could. In my opinion it's about the usb port/cable. Try different ones of them. Side note: If odin fails/freezes once; you have to reboot into download mode again to start a new session.
Also can you please post the screenshot of Options tab in Odin? Perhaps partition stuff or others are checked which supposed to be not.
Konsstantine34 said:
Upgrading from X to latest fw; shouldn't be a problem, downgrade could. In my opinion it's about the usb port/cable. Try different ones of them. Side note: If odin fails/freezes once; you have to reboot into download mode again to start a new session.
Also can you please post the screenshot of Options tab in Odin? Perhaps partition stuff or others are checked which supposed to be not.
Click to expand...
Click to collapse
See the screenshot attached for option tab, its stuck at initialization inside log
antuketot76 said:
See the screenshot attached for option tab, its stuck at initialization inside log
Click to expand...
Click to collapse
Well, i have no idea more than that. Perhaps another pc or Kies way(never used). What's the P7500 though?
Konsstantine34 said:
Well, i have no idea more than that. Perhaps another pc or Kies way(never used). What's the P7500 though?
Click to expand...
Click to collapse
opps, wrong photo. P7500 is for my galaxy tab 10.1... actually now Im flash a galaxy tab.
Its should be N920LKLU2DQC7_N920LLUC2DQC7_N920LKLU2DQC4_HOME.tar.md5
Guys, really need your help on this problem, do you have any ideas on this.
Sorry for disturbing you guys, so sorry.
@CodeNameRedNeck
@LiL_Assassin
@Art Vanderlay
antuketot76 said:
Guys, really need your help on this problem, do you have any ideas on this.
Sorry for disturbing you guys, so sorry.
@CodeNameRedNeck
@LiL_Assassin
@Art Vanderlay
Click to expand...
Click to collapse
If Odin is seeing the phone in download mode my guess would be that your drivers are fine (I could be wrong) so I can't help but wonder why it sticks on initialization. I flash firmware on my device with FRP on all the time. I can only suggest using smart switch. When you connect your phone with smart switch running it will tell you that your device is not supported. It will still work. You will need the serial number and you must use capital letters and the dash in the model number.
CodeNameRedNeck said:
If Odin is seeing the phone in download mode my guess would be that your drivers are fine (I could be wrong) so I can't help but wonder why it sticks on initialization. I flash firmware on my device with FRP on all the time. I can only suggest using smart switch. When you connect your phone with smart switch running it will tell you that your device is not supported. It will still work. You will need the serial number and you must use capital letters and the dash in the model number.
Click to expand...
Click to collapse
Im try with Samsung Kies but not try yet with Smart Switch.
Maybe I can try it with Smart Switch, look if this successful.
Anyway thanks
Try to download latest stock firmware update N920CXXU3CQE1 from samupdate or Samsung mobile and install it via odin that should work .....
mala96 said:
Try to download latest stock firmware update N920CXXU3CQE1 from samupdate or Samsung mobile and install it via odin that should work .....
Click to expand...
Click to collapse
As u mention above is fw for model N920C not same as model inside this thread.
Refer photo attached, my model is N920L korean version LG U+
antuketot76 said:
As u mention above is fw for model N920C not same as model inside this thread.
Refer photo attached, my model is N920L korean version LG U+
Click to expand...
Click to collapse
But did you tried to download the latest version N920LKLU2DQE1 and install it .....
antuketot76 said:
As u mention above is fw for model N920C not same as model inside this thread.
Refer photo attached, my model is N920L korean version LG U+
Click to expand...
Click to collapse
If you have adb installed on your pc you don't even need odin.. Just go into recovery mode and select flash from adb then open a command prompt and (first make sure your firmware is in the SAME exact folder as adb is) then type adb sideload firmwarename.md5
Try that.
mala96 said:
But did you tried to download the latest version N920LKLU2DQE1 and install it .....
Click to expand...
Click to collapse
Yes, I already try flash both latest fw as below but failed.
7.0 version - N920LKLU2DQC7_N920LLUC2DQC7_N920LKLU2DQC4_HOME.tar.md5
GALAXY Note 5 SM-N920L 15.01.2017 6.0.1 Korea (LG Uplus) (LUC) N920LKLU2CPL5
--------------------------------------------------------------------------------------------------------------------
6.0.1 version - N920LKLU2CPL5_N920LLUC2CPL5_N920LKLU2CPL5_HOME.tar.md5
GALAXY Note 5 SM-N920L 15.01.2017 6.0.1 Korea (LG Uplus) (LUC) N920LKLU2CPL5
As I mention below that this device only can boot into Download Mode only, can't boot into system or recovery screen at all even use the combination button.
MrMike2182 said:
If you have adb installed on your pc you don't even need odin.. Just go into recovery mode and select flash from adb then open a command prompt and (first make sure your firmware is in the SAME exact folder as adb is) then type adb sideload firmwarename.md5
Try that.
Click to expand...
Click to collapse
Fyi, this device can boot into download mode ONLY even I try several times with button combination.
My pc already have ADB install on it. Is it using adb method gonna work in download mode or just in recovery mode only? I also dont know what fw is it in this device due to I can view download mode only.
antuketot76 said:
Fyi, this device can boot into download mode ONLY even I try several times with button combination.
My pc already have ADB install on it. Is it using adb method gonna work in download mode or just in recovery mode only?
Click to expand...
Click to collapse
Sorry adb sideload only works in recovery.. Try using my version of odin.. Sometimes odin will freeze and say Not Responding when it's first checking the MD5 file but if you leave it alone for 5 minutes I'll respond again.. Don't connect the phone until after odin finishes checking the md5 file..
My odin version is here you just need to unzip it..
odin-here
MrMike2182 said:
Sorry adb sideload only works in recovery.. Try using my version of odin.. Sometimes odin will freeze and say Not Responding when it's first checking the MD5 file but if you leave it alone for 5 minutes I'll respond again.. Don't connect the phone until after odin finishes checking the md5 file..
My odin version is here you just need to unzip it..
odin-here
Click to expand...
Click to collapse
Thanks for your advice, will try it now and will let u know after this...
PLEASE HELP Note8 hang the logo
The problem is as follows:
When I make a software update for the SM-950f / DS, the phone hangs on the samsung logo
I searched and flashed again with Odin but the result was an error
At startup the error message: kernel rev check fail device 2 binary 1
I flash twrp-3.1.1-0-greatlte_V3 the error: flash fail
Flashing TWRP-3.2.3-TwrpBuilder-greatlte-2018-08-21_17-30 similar results
Now I do not know how to start
I think you use the wrong Odin Version. You need Odin v3.13.1.
You used twrp already before your Software Update? Or why you want to flash TWRP?
Normally it's enough to flash a 4 part stock firmware to get your device working again. Use the "home CSC" file to don't lose your own files.
Edit:
on your first try it looks like you tried to flash an older firmware version. You can't downgrade the bootloader. Flash the same or a newer firmware.
Don't be afraid to hit the "Thanks" button if someone helped you. It don't hurts
m4gicvn said:
PLEASE HELP Note8 hang the logo
The problem is as follows:
When I make a software update for the SM-950f / DS, the phone hangs on the samsung logo
I searched and flashed again with Odin but the result was an error
At startup the error message: kernel rev check fail device 2 binary 1
I flash twrp-3.1.1-0-greatlte_V3 the error: flash fail
Flashing TWRP-3.2.3-TwrpBuilder-greatlte-2018-08-21_17-30 similar results
Now I do not know how to start
Click to expand...
Click to collapse
For the TWRP error, are you wiping data (where you have to type yes) first? If you do not do that TWRP won't work. There is also newer versions of TWRP available.
Logel said:
I think you use the wrong Odin Version. You need Odin v3.13.1.
You used twrp already before your Software Update? Or why you want to flash TWRP?
Normally it's enough to flash a 4 part stock firmware to get your device working again. Use the "home CSC" file to don't lose your own files.
Edit:
on your first try it looks like you tried to flash an older firmware version. You can't downgrade the bootloader. Flash the same or a newer firmware.
Don't be afraid to hit the "Thanks" button if someone helped you. It don't hurts
Click to expand...
Click to collapse
Previously my phone was not rooted or installed TWRP, everything original.
The phone announces a new software update, I make updates and the result is a phone hang on the samsung logo
I downloaded a stock rom, I made Flash with Odin 3.13.1 but the result was a bug, now I do not have a Bootloader. I found out that I was flashing an old version.
So I need Flash recovery, I was trying to find a new version but as a result I could not successfully flash.
I have been trying to find a newer Fimware (such as Android 8) but now I'm still not successful
Logel said:
Edit:
on your first try it looks like you tried to flash an older firmware version. You can't downgrade the bootloader. Flash the same or a newer firmware.
Don't be afraid to hit the "Thanks" button if someone helped you. It don't hurts
Click to expand...
Click to collapse
m4gicvn said:
Previously my phone was not rooted or installed TWRP, everything original.
The phone announces a new software update, I make updates and the result is a phone hang on the samsung logo
I downloaded a stock rom, I made Flash with Odin 3.13.1 but the result was a bug, now I do not have a Bootloader. I found out that I was flashing an old version.
So I need Flash recovery, I was trying to find a new version but as a result I could not successfully flash.
I have been trying to find a newer Fimware (such as Android 8) but now I'm still not successful
Click to expand...
Click to collapse
What do you mean you cannot flash and you don't have a bootloader?
"kernel rev check fail device 2 binary 1" means your device is binary 2 and you're trying to flash binary 1 onto your device.
e.g the latest version firmware for note 8 is N950FXXU4CRGA - U4 shows this firmware is binary 4. On the bootloader - SWREV B:1 - this should show if your device is binary 1.
You will need to first oem unlock the device to flash TWRP/custom img. Warning- flashing TWRP will result in KNOX 1.
Note - bootloader should still be there (you might just have drained all your battery) unless the flash failed during flashing bootloader (bootloader is download mode).
Download firmware here (same firmware for n950fd and n950f) - use samfirm program for faster download (only latest ver).
bluecub1st said:
What do you mean you cannot flash and you don't have a bootloader?
"kernel rev check fail device 2 binary 1" means your device is binary 2 and you're trying to flash binary 1 onto your device.
e.g the latest version firmware for note 8 is N950FXXU4CRGA - U4 shows this firmware is binary 4. On the bootloader - SWREV B:1 - this should show if your device is binary 1.
You will need to first oem unlock the device to flash TWRP/custom img. Warning- flashing TWRP will result in KNOX 1.
Note - bootloader should still be there (you might just have drained all your battery) unless the flash failed during flashing bootloader (bootloader is download mode).
Download firmware .
Click to expand...
Click to collapse
Very thank you
I downloaded the android version 8, I successfully flashed. But this time it was like the beginning. the phone is moving, into the upgrade and error, android child back
Then the phone automatically enters recovery mode
I implemented the wipe cache and wipe data but could not change the result
bluecub1st said:
What do you mean you cannot flash and you don't have a bootloader?
"kernel rev check fail device 2 binary 1" means your device is binary 2 and you're trying to flash binary 1 onto your device.
e.g the latest version firmware for note 8 is N950FXXU4CRGA - U4 shows this firmware is binary 4. On the bootloader - SWREV B:1 - this should show if your device is binary 1.
You will need to first oem unlock the device to flash TWRP/custom img. Warning- flashing TWRP will result in KNOX 1.
Note - bootloader should still be there (you might just have drained all your battery) unless the flash failed during flashing bootloader (bootloader is download mode).
Download firmware
Click to expand...
Click to collapse
How to oem unlock the device?
To oem unlock (like all the new samsung devices) you must enable it in the developer options in settings.
As your phone would not boot oem unlock is not available. you must first ensure the phone can boot to stock firmware
Hello,
I am new to Samsung devices and have tried to install twrp on my note 9.
Firstly I enabled OEM Unlock in dev options and let the phone reset.
I then went into download mode and went to odin3 and selected the correct twrp file in AP and clicked Flash.
It passed and the phone rebooted to the system.
I then tried to get into twrp but it just took me to the stock recovery so I tried reflashing it and now I get the following error:
"Only official released binaries are allowed to be flashed(recovery)"
I have tried going back to dev options to make sure OEM unlock is enabled but it has completely disappeared!!!
I have tried completely reflashing the stock ROM using Odin with no luck!
Does anyone know what I'm doing wrong? This is getting super frustrating because I have never had this issue on any other android phone.
Any help is Very Appreciated Thank You.
VortexHD said:
Hello,
I am new to Samsung devices and have tried to install twrp on my note 9.
Firstly I enabled OEM Unlock in dev options and let the phone reset.
I then went into download mode and went to odin3 and selected the correct twrp file in AP and clicked Flash.
It passed and the phone rebooted to the system.
I then tried to get into twrp but it just took me to the stock recovery so I tried reflashing it and now I get the following error:
"Only official released binaries are allowed to be flashed(recovery)"
I have tried going back to dev options to make sure OEM unlock is enabled but it has completely disappeared!!!
I have tried completely reflashing the stock ROM using Odin with no luck!
Does anyone know what I'm doing wrong? This is getting super frustrating because I have never had this issue on any other android phone.
Any help is Very Appreciated Thank You.
Click to expand...
Click to collapse
ARE YOU EXYNOS OR SNAPDRAGON ?? Below guide is for EXYNOS!!
Did you follow this guide --> https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143 ??
And did you do step 3 ? 3.Download and copy N9_S9_Root_for_OEM_issue_devices_V*.zip to Ext SD card ??i haven't rooted my Note 9 yet but i think that's where you messed up!
Same problem I tray flash twrp say Only official released binaries are allowed to be flashed(recovery)
I flash FIRMWARE UK...and Germany...but not result...my drives N960f
rana14301 said:
Same problem I tray flash twrp say Only official released binaries are allowed to be flashed(recovery)
I flash FIRMWARE UK...and Germany...but not result...my drives N960f
Click to expand...
Click to collapse
read dr ketans guide in the general discussion thread.