Related
If you have rooted using SuperSU then even after using SuperSU to unroot you will running into a couple of errors. Here is how you fix them.
Error #1:
install-recovery.sh can not be copped
[Fix]
Restore your phone using the image found in the MOTO X 2014 Pure Multi Tool found:
https://www.androidfilehost.com/?fid=95784891001604540
Then flash the ATT modem found :
http://cl.ly/1l0x3y0e0L3s
Then reflash the OTA zip
---------------------------------------------------------------------------------------------------------
Error #2
Extra content found in modem
Flash the ATT modem found:
http://cl.ly/1l0x3y0e0L3s
Flash the OTA zip.
Some people have reported having to do a factory restore or re-flash the ATT modem again after the OTA finished installing in order to get LTE.
This worked perfectly, thanks!
What was y'all command line for flashing modem???
fastboot flash modem (file name)
And flashing the AT&T modem will still allow us to use the device on TMobile?
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.
Hi all,
I have a SM-T810 with TGY CSC (Hong Kong) and with Android 5.0.2.
My initial plan was to a) root it, b) to change CSC to UK and c) to install 6.x.x.; in order to do it I followed these steps:
- downloaded and installed Odin 3.10.7
- downloaded and installed twrp_3.0.2-1_sm-t810.tar (note: I rebooted the tablet in recovery mode and I saw the new recovery SW installed)
- downloaded and successfully installed smt810_cf_autoroot.tar
but after booting the tablet I have noticed the following:
- a message "recovery is not seandroid enforcing" appears the first time
- after it, the tablet is now stuck flashing in cycle the Samsung startup page
- I am not anymore able to get in the recovery menu (the screen stop blinking the Samsung start page and it shows it statically this time) to perform a hard reset.
I have understood from the message above that i have flashed the wrong files, but they seem ok.
How can I get out from this impasse?
Thanks in advance.
Fabz
Don't flash CFautoroot root. Flash supersu v2.76 with twrp.
CFautoroot replaces your recovery.
You will need to flash stock firmware first to recover. Also not sure why you are doing the previous steps. Just flash the MM firmware.
Thanks ashyx for your quick reply.
I am not an expert on Android rooting, so just to check if I have understood correctly, your are suggesting the following:
a) flash stock firmware first to have the tablet back.
You seems to advice to flash directly Marshmallow (MM) but since it looks like there isn't any official MM
stock release for the TGY CSC, would the flashing of the MM stock firmware for, for instance, the UK CSC work?
b) download supersu and copy in the tablet storage
c) after it, I should install TWRP
d) boot in recovery mode and install supersu from the menu.
Is it correct?
Thanks again
Fabz
ashyx said:
Don't flash CFautoroot root. Flash supersu v2.76 with twrp.
CFautoroot replaces your recovery.
You will need to flash stock firmware first to recover. Also not sure why you are doing the previous steps. Just flash the MM firmware.
Click to expand...
Click to collapse
effevi1 said:
Thanks ashyx for your quick reply.
I am not an expert on Android rooting, so just to check if I have understood correctly, your are suggesting the following:
a) flash stock firmware first to have the tablet back.
You seems to advice to flash directly Marshmallow (MM) but since it looks like there isn't any official MM
stock release for the TGY CSC, would the flashing of the MM stock firmware for, for instance, the UK CSC work?
b) download supersu and copy in the tablet storage
c) after it, I should install TWRP
d) boot in recovery mode and install supersu from the menu.
Is it correct?
Thanks again
Fabz
Click to expand...
Click to collapse
Just try flashing the MM rom as it is. There is only one MM rom at the moment for the T805 and it's German region.
I have flashed this no probs on my international T805 which is originally from Hong Kong.
These are multi csc devices so should install fine. The only partition likely to fail if any will be hidden.img which can be omitted anyway.
effevi1 said:
Thanks ashyx for your quick reply.
I am not an expert on Android rooting, so just to check if I have understood correctly, your are suggesting the following:
a) flash stock firmware first to have the tablet back.
You seems to advice to flash directly Marshmallow (MM) but since it looks like there isn't any official MM
stock release for the TGY CSC, would the flashing of the MM stock firmware for, for instance, the UK CSC work?
b) download supersu and copy in the tablet storage
c) after it, I should install TWRP
d) boot in recovery mode and install supersu from the menu.
Is it correct?
Thanks again
Fabz
Click to expand...
Click to collapse
Check this page it has some MM stock firmware tars as well as LP for the t810. Maybe you'll find something you can use.
http://www.mrcrab.net/view-stockrom/sm-t810.html
jhill110 said:
Check this page it has some MM stock firmware tars as well as LP for the t810. Maybe you'll find something you can use.
Thanks all,
I managed to flash easily the MM UK version without any problem and without loosing any data.
Best regards
Fabz
Click to expand...
Click to collapse
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
I recently got SM-N960N note 9 it has SKC carrier firmware. It is unlocked already. I wanted to flash Non-carrier firmware pda: N960NKSU3CSJ1 csc: N960NOKR3CSJ1 .
Download mode:
SM-N960N
Current binary : samsung official
Oem lock: OFF
FRP lock : OFF
KG State : checking
warranty void 0x1
.
.
Here is the problem: After i flash that firmware, ODIN says pass (finished 1min28secs) then reset and phone restarts. But it is constantly waiting at "Installing system update" stuck here for too long time it is just stuck never continue. What should i do ? Also what is unlocked phone means ?
xx98burak98xx said:
I recently got SM-N960N note 9 it has SKC carrier firmware. It is unlocked already. I wanted to flash Non-carrier firmware pda: N960NKSU3CSJ1 csc: N960NOKR3CSJ1 .
Download mode:
SM-N960N
Current binary : samsung official
Oem lock: OFF
FRP lock : OFF
KG State : checking
warranty void 0x1
.
.
Here is the problem: After i flash that firmware, ODIN says pass (finished 1min28secs) then reset and phone restarts. But it is constantly waiting at "Installing system update" stuck here for too long time it is just stuck never continue. What should i do ? Also what is unlocked phone means ?
Click to expand...
Click to collapse
Since your download mode shows FRP OFF & OEM LOCK OFF nothing to worry it's fully unlocked.
It just looks to me that some partitions might got corrupted during flashing process.
I suggest you flash twrp recovery first via odin
Then boot into twrp recovery manually
go to wipe section in twrp and format data.
Then reboot twrp recovery again and go to wipe and wipe dalvic cache+data+system+cache+internal storage
Your all partitions are clean now and decrypted.
Then flash stock firmware again
Reboot phone and be patient for few minutes.
Hopefully this should work without issues.
Trex888 said:
Since your download mode shows FRP OFF & OEM LOCK OFF nothing to worry it's fully unlocked.
It just looks to me that some partitions might got corrupted during flashing process.
I suggest you flash twrp recovery first via odin
Then boot into twrp recovery manually
go to wipe section in twrp and format data.
Then reboot twrp recovery again and go to wipe and wipe dalvic cache+data+system+cache+internal storage
Your all partitions are clean now and decrypted.
Then flash stock firmware again
Reboot phone and be patient for few minutes.
Hopefully this should work without issues.
Click to expand...
Click to collapse
I flashed TWRP and it is stuck too
TWRP screen is just waiting constantly now. Seems I cant go recovery... I think maybe firmware was broken.
Model: SM-N960N
Version: N960NKSU3CSJ1/N960NOKR3CSJ1/N960NKOU3CSJ1/N960NKSU3CSJ1
OS: Pie(Android 9)
Filename: SM-N960N_1_20191014163901_mqqoydk22i_fac.zip.enc4
Size: 4298148096 bytes
LogicValue: h7d2bh2hwlojzdq8
i am downlading this. I could not find any link of this build. Have anyone has link for that firmware ?
Why i cant flash stock n960f firmwares ? it has same hardware... anyway to flash stock n960f to n960n ?
okay i flash that firmware and it is again CARRIER VERSION ... When booting i dont want to see SKC telecom and i dont want my phone has carrier functions such as T1Phone etc. What should i do ?
I flashed
PDA N960NKSU3CSG3
CSC N960NOKR3CSG3
firmware. I got "installing system update" stuck again... What the heck ?
Also i say flashes takes 1min28secs. It is too less to me i think. AP file at least 3600mb and i connected usb 2.0 port to odin. 3600mb/88secs=40.9mb/s , is this normal ?
Okay now i understand whats happening. I flash too many roms. I tried dm verity twrp or other version of PIE's . Every flashing rom nothing change my current rom. Odin says PASS no error but its still same. No change. What is happening someone help please ??
xx98burak98xx said:
Okay now i understand whats happening. I flash too many roms. I tried dm verity twrp or other version of PIE's . Every flashing rom nothing change my current rom. Odin says PASS no error but its still same. No change. What is happening someone help please ??
Click to expand...
Click to collapse
I also have the n960n, tried to flash it to a non carrier and failed every time. I tried using the KOO version, I think that's the non carrier Korean version that didn't work.
I was told from few XDA forum's members that is not possible to flash an n960n to a n960f with official firmware unless you use custom firmware.
trannote9 said:
I also have the n960n, tried to flash it to a non carrier and failed every time. I tried using the KOO version, I think that's the non carrier Korean version that didn't work.
I was told from few XDA forum's members that is not possible to flash an n960n to a n960f with official firmware unless you use custom firmware.
Click to expand...
Click to collapse
You have exact same problem with me comrade! I cant change my carrier flash. Everytime it is opening with SK telecom and i am very tired of this ****. That's my fifth day of effort. But still i cant change carrier flash with i found KOO firmwares. So i decided to flash modified stock rom from alenxdre(?) devb 6.0
1) Be sure KG state is checking
2) Flash TWRP via ODIN
3) format data (be careful) and reboot to recovery again
4) wipe all partitions except extsdcard and usb otg
5) Download DM-verity file and flash it with ur extsdcard in TWRP install option. (I dont know why i did this but it worked atleast so i dont know its necessary or not...)
6) Flash Devb 6.0 modified stock rom for n960n
7) Flash magisk root zip file
8) Wıpe factory data if it is required
9) If it is works (at least worked for me) you wont see boot animation of carrier(finally!)
10) But it is still says YOU ARE SKC service provider (What da heck man ??)
After this you have functionable TWRP and MagısK root so you can do anything you want. Go play store and download Phone INFO *SAM* program. That program needs root and it has tool "CSC CHANGER (ROOT)". Since we have only 4 option: SKC, KTC, LUC, and finally KOO !! , Opening tool will redirect you to rom's preconfig CSC change menu and you can select KOO from there. I selected it. Rebooted. TWRP did some update to system and HOLA! My phone is KOO after these all instructions. Good to go. Or not ? Phone info program still says your phone's ORIGINAL FIRMWARE SERVICE PROVIDER IS SKC!!?? Yes we change it to KOO but truth is i could not find any KOO firmware even i flashed modified stock firmware...
Yes i succeeded with this way but thats modified stock rom. It has same appearence with stock rom and good for me. No problem imo. But the real problem: WHY ALL FIRMWARES SAYS SKC? I tried at least 10 different same firmware pda csc cp or different with same modem number, i could not succeeded...
SOMEONE SHOULD HELP US!
xx98burak98xx said:
You have exact same problem with me comrade! I cant change my carrier flash. Everytime it is opening with SK telecom and i am very tired of this ****. That's my fifth day of effort. But still i cant change carrier flash with i found KOO firmwares. So i decided to flash modified stock rom from alenxdre(?) devb 6.0
1) Be sure KG state is checking
2) Flash TWRP via ODIN
3) format data (be careful) and reboot to recovery again
4) wipe all partitions except extsdcard and usb otg
5) Download DM-verity file and flash it with ur extsdcard in TWRP install option. (I dont know why i did this but it worked atleast so i dont know its necessary or not...)
6) Flash Devb 6.0 modified stock rom for n960n
7) Flash magisk root zip file
8) Wıpe factory data if it is required
9) If it is works (at least worked for me) you wont see boot animation of carrier(finally!)
10) But it is still says YOU ARE SKC service provider (What da heck man ??)
After this you have functionable TWRP and MagısK root so you can do anything you want. Go play store and download Phone INFO *SAM* program. That program needs root and it has tool "CSC CHANGER (ROOT)". Since we have only 4 option: SKC, KTC, LUC, and finally KOO !! , Opening tool will redirect you to rom's preconfig CSC change menu and you can select KOO from there. I selected it. Rebooted. TWRP did some update to system and HOLA! My phone is KOO after these all instructions. Good to go. Or not ? Phone info program still says your phone's ORIGINAL FIRMWARE SERVICE PROVIDER IS SKC!!?? Yes we change it to KOO but truth is i could not find any KOO firmware even i flashed modified stock firmware...
Yes i succeeded with this way but thats modified stock rom. It has same appearence with stock rom and good for me. No problem imo. But the real problem: WHY ALL FIRMWARES SAYS SKC? I tried at least 10 different same firmware pda csc cp or different with same modem number, i could not succeeded...
SOMEONE SHOULD HELP US!
Click to expand...
Click to collapse
I gave up at end. You can find the KOO version at sammobile. Thanks for the instruction, did you manage to get rid of the carrier apps?
---------- Post added at 12:20 PM ---------- Previous post was at 12:16 PM ----------
SOMEONE SHOULD HELP US![/QUOTE]
I gave up at end. You can find the KOO version at sammobile. Thanks for the instruction, did you manage to get rid of the carrier apps?
trannote9 said:
I gave up at end. You can find the KOO version at sammobile. Thanks for the instruction, did you manage to get rid of the carrier apps?
---------- Post added at 12:20 PM ---------- Previous post was at 12:16 PM ----------
SOMEONE SHOULD HELP US!
Click to expand...
Click to collapse
I gave up at end. You can find the KOO version at sammobile. Thanks for the instruction, did you manage to get rid of the carrier apps?[/QUOTE]
Modified stock rom has no carrier apps u can guess
trannote9 said:
I gave up at end. You can find the KOO version at sammobile. Thanks for the instruction, did you manage to get rid of the carrier apps?
---------- Post added at 12:20 PM ---------- Previous post was at 12:16 PM ----------
SOMEONE SHOULD HELP US!
Click to expand...
Click to collapse
I gave up at end. You can find the KOO version at sammobile. Thanks for the instruction, did you manage to get rid of the carrier apps?[/QUOTE]
Nope like i said: I tried at least 10 firmware from different sites different sources. Every firmware = carrier version
xx98burak98xx said:
I gave up at end. You can find the KOO version at sammobile. Thanks for the instruction, did you manage to get rid of the carrier apps?
Click to expand...
Click to collapse
Nope like i said: I tried at least 10 firmware from different sites different sources. Every firmware = carrier version[/QUOTE]
Are you installing the Stock Samsung N960N OS? If you are make sure that you have all the correct files including the correct USM file loaded before you start the process.
iceepyon said:
Nope like i said: I tried at least 10 firmware from different sites different sources. Every firmware = carrier version
Click to expand...
Click to collapse
Are you installing the Stock Samsung N960N OS? If you are make sure that you have all the correct files including the correct USM file loaded before you start the process.[/QUOTE]
what is USM file ? Yea i tried n960n stock firmwares but i solved the problem and boot animation has been gone. i told what did i do in last posts