Database Develop

[HOW-TO] ROOT/MODEM/FIRMWARE flash GT-I9295 using Download Mode, Recovery Mode

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.

Help rooting 5.1.1 925T

I installed 5.1.1 via smart switch and lost root. I enabled allow OEM unlock and tried the CF autoroot technique. It flashed fine but it gets stuck on the Galaxy S6 splash screen with the message "bootloader is not SEandroid enforcing" (duh....) I found another thread that said to try the 920t cf autoroot which I did and it had the same result. I have since recovered my phone back to stock 5.1.1 but I would really like to join the club and get root working once again. Is there a current solution for this or is it just a waiting game now?
thanks for any help.

If you are on stock 5.1.1 all you have to do now is either flash the 5.1.1 unikernel (in unified development section) or flash the rooted stock debloated rom posted in the Looper thread. If that was confusing just let me know lol I'll try to help you locate

Odin flash the new 2.8.7.1 TWRP and you'll be all set.

guyd said:
Odin flash the new 2.8.7.1 TWRP and you'll be all set.
Click to expand...
Click to collapse
Does this and or the kernel go into the PA box? PA is what used to be labeled PDA correct?

guyd said:
Odin flash the new 2.8.7.1 TWRP and you'll be all set.
Click to expand...
Click to collapse
Odin flashing just twrp does not root
the phone. If you do it that way, and don't flash the rooted kernel before booting, you will boot and stock recovery will replace twrp
badtoy1986 said:
Does this and or the kernel go into the PA box? PA is what used to be labeled PDA correct?
Click to expand...
Click to collapse

So, flash TWRP then flash the kernel with TWRP?

badtoy1986 said:
So, flash TWRP then flash the kernel with TWRP?
Click to expand...
Click to collapse
Correct. First make sure you're on 5.1.1 already. Then flash twrp in odin. Then immediately boot into twrp and flash the unified kernel for 5.1.1

Wrong firmware/bootloader verision, CyanogenMod already installed.

HEEELP!
I downloaded CyanogenMod (11) but I've got wrong firmware.
I cannot update firmware tried MicroSD (T4_SDUPDATE.zip), tried 2 go back 2 stock (Stock recovery.img+ jb-4.3_ota-full_tf701t-macallan.zip), nothing works.
I got firmware ww_epad-10.26.1.7 , need atleast 2 be on bootloader/firmware version 10.26.1.18 or higher!
I really need your help.

If your computer can detect the tablet in fastboot mode then you should be able to flash an image. If not then oops! You need to download the latest WW firmware from the ASUS website and flash it with your computer...

K94U said:
If your computer can detect the tablet in fastboot mode then you should be able to flash an image. If not then oops! You need to download the latest WW firmware from the ASUS website and flash it with your computer...
Click to expand...
Click to collapse
Well Thanks. I've alredy tried 2 download the lastest WW firmware (10.26.1.18 SKU renamed it T4_SDUPDATE.zip) and even tried via MicroSD card. I've also tried 2 "go back" - stock recovery - 2 update my bootloader/firmware, did not work either. (Used jb-4.3_ota-full_tf701t-macallan.zip + stock recovery.img).
Iam wondering if it might be my MicroSD card, do you need 2 format microSD to FAT32? Will it make so much difference?
Very grateful for any help, feels like I've tried everything.

To update your bootloader on your www region tab:
http://forum.xda-developers.com/showpost.php?p=61045480&postcount=2
I believe that will flash TWRP along with it (you can boot CWM to flash it).
If you want to put back the stock recovery after flash, fastboot flash recovery recovery.img using the latest stock recovery from droidbasement. You can also flash in the latest CWM (from droidbasement) if you like, if you are intending to stay with CM11.

pershoot said:
To update your bootloader on your www region tab:
http://forum.xda-developers.com/showpost.php?p=61045480&postcount=2
I believe that will flash TWRP along with it (you can boot CWM to flash it).
If you want to put back the stock recovery after flash, fastboot flash recovery recovery.img using the latest stock recovery from droidbasement. You can also flash in the latest CWM (from droidbasement) if you like, if you are intending to stay with CM11.
Click to expand...
Click to collapse
Thanks alot again. will try!

MiNnLi said:
Thanks alot again. The link/download page for the lastest BOOTLOADER FOR WW (zip) does not work for me tho. Does it work for you?
Click to expand...
Click to collapse
Doesn't appear so. Please liaise with sbdags for it.

Heeelp
I really need help again.
The Link to the ww firmware did not work.
I would be so so grateful if someone could explain (in steps) what I should/could do.
I cannot use My transfomer tab it laggs to much couse of the wrong firmware.
How can I get the newest firmware when i already downloded cyanogenmod (custom rom)
Thanks!

The latest firmware version for you is ww 11.4.1.30
Try this link: http://forum.xda-developers.com/devdb/project/dl/?id=13428

pershoot said:
Doesn't appear so. Please liaise with sbdags for it.
Click to expand...
Click to collapse
I need 2 find my old stock version, go back to it and the OTA. All I really need is the pure img files for system, recovery and boot.
Can you help me?

[TWRP 3.0.2-1][ROOT] Samsung galaxy A9 pro SM-A910F/9100 - 26/7/2016

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
.
.

Stuck on Odin download

Haven't been on android in a while.
Picked up a galaxy tab a for free.
Tried to load unlock bootloader / install driver / install odin and twrp
now the unit only boots into odin download or samsung download
got patched odin and tried to install the firmware from sam site. Fails every time. Computer sees the device.
Any tips?

22350 said:
Haven't been on android in a while.
Picked up a galaxy tab a for free.
Tried to load unlock bootloader / install driver / install odin and twrp
now the unit only boots into odin download or samsung download
got patched odin and tried to install the firmware from sam site. Fails every time. Computer sees the device.
Any tips?
Click to expand...
Click to collapse
Not nearly enough info. What steps did you take? Did you succeed in unlocking the bootloader? Did the tablet reboot after that? Did in factory reset? Did you re-enable Dev mode and OEM? What version of Odin? What version of stock ROM do you have? Did you flash VBmeta Disabler?

lewmur said:
Not nearly enough info. What steps did you take? Did you succeed in unlocking the bootloader? Did the tablet reboot after that? Did in factory reset? Did you re-enable Dev mode and OEM? What version of Odin? What version of stock ROM do you have? Did you flash VBmeta Disabler?
Click to expand...
Click to collapse
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.

22350 said:
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
Click to expand...
Click to collapse

this is what the screen says when i try to flash

no content in your post

22350 said:
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
Click to expand...
Click to collapse
You need to do a lot more reading. Forget everything you know about rooting because it won't help with this tablet. There is a link in the first post in this tread about how to unlock the bootloader and enabling Dev mode and OEM is only the very first step. You can't do anything else until that is complete and each step is important. Also in the first post is the stock version you'll need to flash before flashing VBmeta and TWRP.

lewmur said:
You need to do a lot more reading. Forget everything you know about rooting because it won't help with this tablet. There is a link in the first post in this tread about how to unlock the bootloader and enabling Dev mode and OEM is only the very first step. You can't do anything else until that is complete and each step is important. Also in the first post is the stock version you'll need to flash before flashing VBmeta and TWRP.
Click to expand...
Click to collapse
Ok I will do that, but since I am stuck in odin download will I be able to get supersu installed anymore?
I installed twrp with Odin, but that’s when everything went sideways

22350 said:
Ok I will do that, but since I am stuck in odin download will I be able to get supersu installed anymore?
I installed twrp with Odin, but that’s when everything went sideways
Click to expand...
Click to collapse
Actually the thread you need to read is here. That has the link to instructions for unlocking the bootloader. Your next step will be to use Sammobile to download the stock version shown in that thread and flash it with Odin. That should get you back to a bootable ROM. Also, forget about supersu. Magisk is used to root these tablets.
edit: MY BIG MISTAKE. I thought you had a T500 tablet but looking closer to your post, you must have a T380 and the thread I linked won't work for a T380. You'll have to search for a thread for rooting your tablet. Sorry about that. I don't even know if the T380 has a locked bootloader. But your next step will be to flash the stock ROM you downloaded to get back to a bootable ROM.

lewmur said:
Actually the thread you need to read is here. That has the link to instructions for unlocking the bootloader. Your next step will be to use Sammobile to download the stock version shown in that thread and flash it with Odin. That should get you back to a bootable ROM. Also, forget about supersu. Magisk is used to root these tablets.
edit: MY BIG MISTAKE. I thought you had a T500 tablet but looking closer to your post, you must have a T380 and the thread I linked won't work for a T380. You'll have to search for a thread for rooting your tablet. Sorry about that. I don't even know if the T380 has a locked bootloader. But your next step will be to flash the stock ROM you downloaded to get back to a bootable ROM.
Click to expand...
Click to collapse
Yea, well that's the issue. i am in odin downloading, with the correct rom from samobile, but the flash fails each time

i ended up using these two
Stock ROM for the SM-T380 Android 9, Bloatware free TWRP backup
Since there aren't any Custom ROM for the SM-T380 I made this TWRP back from my tablet, running on stock Pie I took all the bloatware, Knox out to add some root mods, and latest updates with Magisk root with Safetynet Passing. No other personal...
forum.xda-developers.com
[TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018
Unofficial release -TWRP recovery for the Galaxy Tab A - T380/T385, Qualcomm MSM8917 TWRP 3.2.1-0 Released Dec 9, 2017 TWRP 3.2.1-0 is out now for most currently supported devices. What's new in 3.2.1-0: * minui fixes (cryptomilk) *...
forum.xda-developers.com