Related
Hello,
I've spent the better part of 2 days trying to figure this out. First, I attempted to use ThePagel's ODIN guide to root without tripping the KNOX counter. That wouldn't work, as I constantly received NAND write start/fail messages. Ultimately, I followed the CF Auto Root guide at tomsguide-dot-com/us/samsung-galaxy-s6-guide,review-2856-3.html. I located my device (SM-G920T), and downloaded the appropriate auto root files which included ODIN 3.10.6. I previously downloaded and attempted to use ODIN 3.10.6 and ODIN 3.10.7. The ODIN version that came with the auto-root program had differences in the ODIN.ini file, but when I followed the instructions it flashed a CACHE.img and RECOVERY.img file, showed a green "PASS" sign, and attempted to reboot.
When my phone automatically attempted to reboot, the top of the GS6 logo screen has red letters stating "Recovery is not SEAndroid Enforcing." When I return to the download/ODIN screen I see the following in formation now:
Product Name: SM-G920T
Current Binary: Custom
System Status: Official
FRP Lock: Off
Secure Download: Enabled
KNOX Warrant Void: 1 (it tripped)
RP SWRev: B:3, K:2, S:2
After this failure, I realized my phone was previously Android 5.1.1, and the CF Auto Root files I used are for 5.0.2. Now I'm attempting to use ODIN to restore a stock 5.0.2 as well as a 5.1.1 build, but keep receiving the NAND Write Start/Fail message. After a NAND failure going to Android 5.0.2, I notice my device has a black and red message reading, "SW Rev. Check Fail. Device: 3, Binary: 1." Attempting to go back to Android 5.1.1 (where I started), the error message states "Device 3, Binary 2."
I've attempted to alter the .tar.md5 file and include ONLY the CACHE.img and RECOVERY.img, but when I do, the MD5 value doesn't match, and I am unable to proceed.
I'll continue to read threads and try to figure out how to fix this, but any help would be appreciated. Thank you.
I've tried to create my own tar.md5 files including only the CACHE.img and RECOVERY.img and naming them after the CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t filename, but the MD5 hash/checksum doesn't match. I can't find anywhere to change it, and can't figure out how to make the MD5 check pass. WTF. I don't remember being this stupid the last few times I rooted phones.
**SOLVED**
MBuckley81 said:
I've tried to create my own tar.md5 files including only the CACHE.img and RECOVERY.img and naming them after the CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t filename, but the MD5 hash/checksum doesn't match. I can't find anywhere to change it, and can't figure out how to make the MD5 check pass. WTF. I don't remember being this stupid the last few times I rooted phones.
Click to expand...
Click to collapse
Not sure what exactly changed, but maybe the fact I read this:
forum.xda-developers.com/tmobile-galaxy-s6/help/tried-to-root-5-0-2-5-1-1-guide-t3191903/
I tried doing the same stuff, but it wasn't until I used PeaZip instead of WinRAR or 7Zip. I put the stock 5.1.1 Cache.img and Recovery.img files in my own .tar file (not tar.md5), and was able to use ODIN to push them to the phone. It rebooted, then did the dancing android monkey loading screen. All my other stuff is still on the phone.
MBuckley81 said:
I've tried to create my own tar.md5 files including only the CACHE.img and RECOVERY.img and naming them after the CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t filename, but the MD5 hash/checksum doesn't match. I can't find anywhere to change it, and can't figure out how to make the MD5 check pass. WTF. I don't remember being this stupid the last few times I rooted phones.
Click to expand...
Click to collapse
You don't need to add the .MD5 to the file name..
Stick with .TAR, that will bypass the MD5 Check..
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
.
.
Hi guys the recent Australian firmwares N920IDVU3BPL2 of N920I has restriction which forces to stay on latest firmware. My LTE is not working on N920IDVU3BPL2 and it is not allowing me to install any old firmware to me.
If I still try to install any old firmware which was working and had good LTE on same phone then I get
"SYSTEM REV CHECK FAIL DEVICE 1 BINARY 0" error"
I think if I can flash my old firmware modem through twrp then I may fix LTE signal issue. Can anyone provide any assistance on how to create TWRP flashable modem and bootloader zip file because ODIN does not allow me to flash old firmware now.
Did you found it? I need the modem too. Question, is it necessary to flash bootloader too in order to flash modem?
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
Here you will find the boot.img.tar to root the above mentioned device. I am not responsible for any damage to your device.
Bootloader should be unlocked [emoji356]. Ensure you are on the correct firmware that is listed above. I have extracted and compressed the file that is needed. It has been tested and working. This should be installed using Odin 3.14.4 and flashed in AP slot. Once you have correct firmware flashed on device, turn off device, open Odin, put device in download mode, add boot.img.tar to AP click start. After flash completes device will be rooted. Setup device install Magisk Manger and follow prompts.
WARNING...THIS PROCESS WILL REQUIRE A FACTORY DATA RESET ONCE COMPLETE. MAKE SURE TO SAVE OR BACKUP ALL IMPORTANT FILES.
OP SHOULD READ
Android 10/2.1
Sent from my SM-N975U using Tapatalk
Boot.img.tar
https://mega.nz/file/fhQVxKoY#BOcM_dSRG0URBjIS51L6olCUchCzDc0G_3fGAbjcWxI
Sent from my SM-N975U using Tapatalk
N770FXXU3BTF1(Spain)
BOOT.TAR (ROOT)
https://mega.nz/file/D8ARBSpS#Iuq0O9RdBZbZypQjMHCeQ4oeSukzmr43m8pxsgNTnUk
Sent from my SM-N770F using Tapatalk
New update upgrades bootloader to S4
Sent from my SM-N975U using Tapatalk
I went ahead and flashed the new firmware with odin.
N770FXXU4BTG7. This will update your bootloader to revision 4(U4). If you flash this with odin as I did instead of waiting for the OTA, once flashed oem unlock will not be present. What you need to do if this happens is go to Auto update date and turn it off. Then set date 8 days ahead. Then click Software update in settings. Let device check and it will probably say current firmware is up to date. After that reboot device and oem unlock should be present. I am also including the patched boot.img for this firmware. I used Spain(PHE) all of the new firmware version should be able to be rooted...but proceed with caution as I have not tested any other version. I can confirm this root works. If i have time I will create a patched img for different versions just shoot me a PM. Again I will if I have time. But for now I am posting the boot.img to root the firmware listed above.
Boot.img.tar (Spain..PHE)
https://mega.nz/file/P15BxKDT#UGMUuUfgalr4GsKVMlSn2ng4_61Mi3nXrdcsRG4sy9I
Sent from my SM-N975U using Tapatalk
N770FXXS5BTG9 Spain(PHE)
Boot.img (Root)
https://mega.nz/file/f1AzVSzZ#XVp2E1w_eJqHFMQy5TlV58OklsbQI0b4zS-K1ELs9AY
Once you update to S5 bootloader there is no going back to any bootloader lower than S5 or U5. Remember to rename to boot.img.tar
Sent from my SM-N770F using Tapatalk
XXU5CTH4 ONE UI 2.5
https://mega.nz/file/voxECChD#jqbikCg5pwVifI_wzOLyeP6iI5u93nF435WoOTLBDXM
boot.img.tar(Root)
https://mega.nz/file/iw5miaaJ#-jNdBboodADL8-IK1TFkHagUucmn2SsMOirkCyVfwXA
Sent from my SM-N960U using Tapatalk
The new U6 firmware can be rooted, I tested it today. But to make sure, I flashed the U5 bootloader in Odin along with U6 Ap..Cp..Csc to make sure I could flash back to U5. All worked fine..root worked even with having U5 bootloader combined with U6 firmware.
Sent from my SM-N986U using Tapatalk