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
Related
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 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
I'm having the the problem after try to flash (N920LKLU2DQC7_N920LLUC2DQC7_N920LKLU2DQC4_HOME.ta r). Odin3 v3.12 stuck at initialization step as image attached. Also try with Odin3 v3.07 and Odin3 v3.10.6 with the same problem. Maybe because FRP lock in ON status or anything else? Need help ASAP
Screen info on Download Mode
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-N920L
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
Secure Download: Enable
KNOX WARRANTY VOID: 0 (0х0000)
RP SWREV: B:2 K:0 S:0
Try again after enabling 'OEM Unlock' in the Developer Options. By doing so FRP lock will be off.
And what exactly are you trying to do...?
Shiv Parmar said:
Try again after enabling 'OEM Unlock' in the Developer Options. By doing so FRP lock will be off.
And what exactly are you trying to do...?
Click to expand...
Click to collapse
Actually, this is phone come from stock official rom, which is received OTA update from samsung then try to download the updates but it's stuck during updating. Now this phone, can boot into download mode only.
I can't boot into system anymore and turn the on the OEM unlock function in developer mode.
Is there solution to resolve this. TIA
Im just guessing; since the OP doesn't flash a custom stuff like twrp recovery, OEM unlocking is not necessary. And the knox is hasn't tripped yet as i see. I would try another usb port, different version of odin(run as administrator) and be sure usb drivers are correctly installed on the PC. If all is OK; just try flashing the fw version which came installed on the device. If it success, enable oem unlock then try flashing latest fw and keep the OEM unlock enabled for future plans like rooting etc.
Mi MIX
7.5.4 Épic
Konsstantine34 said:
Im just guessing; since the OP doesn't flash a custom stuff like twrp recovery, OEM unlocking is not necessary. And the knox is hasn't tripped yet as i see. I would try another usb port, different version of odin(run as administrator) and be sure usb drivers are correctly installed on the PC. If all is OK; just try flashing the fw version which came installed on the device. If it success, enable oem unlock then try flashing latest fw and keep the OEM unlock enabled for future plans like rooting etc.
Mi MIX
7.5.4 Épic
Click to expand...
Click to collapse
FYI, I already try to flash with different Odin like v3.12, v3.07 and v3.10.6 but still same stuck at initialization step but I'm not flash the fw which is came at first because I dont know what the previous fw. The fw that I try to flash is original samsung fw from sammobile which is the latest ones (Nougat 7.0), actually this device is not mine, its my friend device that need my help to resolve it.
Maybe this device is from 5.0 and received OTA update for 6.0, maybe I should try to flash with 5.0 version first the try 6.0 later. Anyway thanks for advice @Konsstantine34
Do refer attachment, which version should I flash it?
antuketot76 said:
FYI, I already try to flash with different Odin like v3.12, v3.07 and v3.10.6 but still same stuck at initialization step but I'm not flash the fw which is came at first because I dont know what the previous fw. The fw that I try to flash is original samsung fw from sammobile which is the latest ones (Nougat 7.0), actually this device is not mine, its my friend device that need my help to resolve it.
Maybe this device is from 5.0 and received OTA update for 6.0, maybe I should try to flash with 5.0 version first the try 6.0 later. Anyway thanks for advice @Konsstantine34
Do refer attachment, which version should I flash it?
Click to expand...
Click to collapse
Upgrading from X to latest fw; shouldn't be a problem, downgrade could. In my opinion it's about the usb port/cable. Try different ones of them. Side note: If odin fails/freezes once; you have to reboot into download mode again to start a new session.
Also can you please post the screenshot of Options tab in Odin? Perhaps partition stuff or others are checked which supposed to be not.
Konsstantine34 said:
Upgrading from X to latest fw; shouldn't be a problem, downgrade could. In my opinion it's about the usb port/cable. Try different ones of them. Side note: If odin fails/freezes once; you have to reboot into download mode again to start a new session.
Also can you please post the screenshot of Options tab in Odin? Perhaps partition stuff or others are checked which supposed to be not.
Click to expand...
Click to collapse
See the screenshot attached for option tab, its stuck at initialization inside log
antuketot76 said:
See the screenshot attached for option tab, its stuck at initialization inside log
Click to expand...
Click to collapse
Well, i have no idea more than that. Perhaps another pc or Kies way(never used). What's the P7500 though?
Konsstantine34 said:
Well, i have no idea more than that. Perhaps another pc or Kies way(never used). What's the P7500 though?
Click to expand...
Click to collapse
opps, wrong photo. P7500 is for my galaxy tab 10.1... actually now Im flash a galaxy tab.
Its should be N920LKLU2DQC7_N920LLUC2DQC7_N920LKLU2DQC4_HOME.tar.md5
Guys, really need your help on this problem, do you have any ideas on this.
Sorry for disturbing you guys, so sorry.
@CodeNameRedNeck
@LiL_Assassin
@Art Vanderlay
antuketot76 said:
Guys, really need your help on this problem, do you have any ideas on this.
Sorry for disturbing you guys, so sorry.
@CodeNameRedNeck
@LiL_Assassin
@Art Vanderlay
Click to expand...
Click to collapse
If Odin is seeing the phone in download mode my guess would be that your drivers are fine (I could be wrong) so I can't help but wonder why it sticks on initialization. I flash firmware on my device with FRP on all the time. I can only suggest using smart switch. When you connect your phone with smart switch running it will tell you that your device is not supported. It will still work. You will need the serial number and you must use capital letters and the dash in the model number.
CodeNameRedNeck said:
If Odin is seeing the phone in download mode my guess would be that your drivers are fine (I could be wrong) so I can't help but wonder why it sticks on initialization. I flash firmware on my device with FRP on all the time. I can only suggest using smart switch. When you connect your phone with smart switch running it will tell you that your device is not supported. It will still work. You will need the serial number and you must use capital letters and the dash in the model number.
Click to expand...
Click to collapse
Im try with Samsung Kies but not try yet with Smart Switch.
Maybe I can try it with Smart Switch, look if this successful.
Anyway thanks
Try to download latest stock firmware update N920CXXU3CQE1 from samupdate or Samsung mobile and install it via odin that should work .....
mala96 said:
Try to download latest stock firmware update N920CXXU3CQE1 from samupdate or Samsung mobile and install it via odin that should work .....
Click to expand...
Click to collapse
As u mention above is fw for model N920C not same as model inside this thread.
Refer photo attached, my model is N920L korean version LG U+
antuketot76 said:
As u mention above is fw for model N920C not same as model inside this thread.
Refer photo attached, my model is N920L korean version LG U+
Click to expand...
Click to collapse
But did you tried to download the latest version N920LKLU2DQE1 and install it .....
antuketot76 said:
As u mention above is fw for model N920C not same as model inside this thread.
Refer photo attached, my model is N920L korean version LG U+
Click to expand...
Click to collapse
If you have adb installed on your pc you don't even need odin.. Just go into recovery mode and select flash from adb then open a command prompt and (first make sure your firmware is in the SAME exact folder as adb is) then type adb sideload firmwarename.md5
Try that.
mala96 said:
But did you tried to download the latest version N920LKLU2DQE1 and install it .....
Click to expand...
Click to collapse
Yes, I already try flash both latest fw as below but failed.
7.0 version - N920LKLU2DQC7_N920LLUC2DQC7_N920LKLU2DQC4_HOME.tar.md5
GALAXY Note 5 SM-N920L 15.01.2017 6.0.1 Korea (LG Uplus) (LUC) N920LKLU2CPL5
--------------------------------------------------------------------------------------------------------------------
6.0.1 version - N920LKLU2CPL5_N920LLUC2CPL5_N920LKLU2CPL5_HOME.tar.md5
GALAXY Note 5 SM-N920L 15.01.2017 6.0.1 Korea (LG Uplus) (LUC) N920LKLU2CPL5
As I mention below that this device only can boot into Download Mode only, can't boot into system or recovery screen at all even use the combination button.
MrMike2182 said:
If you have adb installed on your pc you don't even need odin.. Just go into recovery mode and select flash from adb then open a command prompt and (first make sure your firmware is in the SAME exact folder as adb is) then type adb sideload firmwarename.md5
Try that.
Click to expand...
Click to collapse
Fyi, this device can boot into download mode ONLY even I try several times with button combination.
My pc already have ADB install on it. Is it using adb method gonna work in download mode or just in recovery mode only? I also dont know what fw is it in this device due to I can view download mode only.
antuketot76 said:
Fyi, this device can boot into download mode ONLY even I try several times with button combination.
My pc already have ADB install on it. Is it using adb method gonna work in download mode or just in recovery mode only?
Click to expand...
Click to collapse
Sorry adb sideload only works in recovery.. Try using my version of odin.. Sometimes odin will freeze and say Not Responding when it's first checking the MD5 file but if you leave it alone for 5 minutes I'll respond again.. Don't connect the phone until after odin finishes checking the md5 file..
My odin version is here you just need to unzip it..
odin-here
MrMike2182 said:
Sorry adb sideload only works in recovery.. Try using my version of odin.. Sometimes odin will freeze and say Not Responding when it's first checking the MD5 file but if you leave it alone for 5 minutes I'll respond again.. Don't connect the phone until after odin finishes checking the md5 file..
My odin version is here you just need to unzip it..
odin-here
Click to expand...
Click to collapse
Thanks for your advice, will try it now and will let u know after this...
PLEASE HELP Note8 hang the logo
The problem is as follows:
When I make a software update for the SM-950f / DS, the phone hangs on the samsung logo
I searched and flashed again with Odin but the result was an error
At startup the error message: kernel rev check fail device 2 binary 1
I flash twrp-3.1.1-0-greatlte_V3 the error: flash fail
Flashing TWRP-3.2.3-TwrpBuilder-greatlte-2018-08-21_17-30 similar results
Now I do not know how to start
I think you use the wrong Odin Version. You need Odin v3.13.1.
You used twrp already before your Software Update? Or why you want to flash TWRP?
Normally it's enough to flash a 4 part stock firmware to get your device working again. Use the "home CSC" file to don't lose your own files.
Edit:
on your first try it looks like you tried to flash an older firmware version. You can't downgrade the bootloader. Flash the same or a newer firmware.
Don't be afraid to hit the "Thanks" button if someone helped you. It don't hurts
m4gicvn said:
PLEASE HELP Note8 hang the logo
The problem is as follows:
When I make a software update for the SM-950f / DS, the phone hangs on the samsung logo
I searched and flashed again with Odin but the result was an error
At startup the error message: kernel rev check fail device 2 binary 1
I flash twrp-3.1.1-0-greatlte_V3 the error: flash fail
Flashing TWRP-3.2.3-TwrpBuilder-greatlte-2018-08-21_17-30 similar results
Now I do not know how to start
Click to expand...
Click to collapse
For the TWRP error, are you wiping data (where you have to type yes) first? If you do not do that TWRP won't work. There is also newer versions of TWRP available.
Logel said:
I think you use the wrong Odin Version. You need Odin v3.13.1.
You used twrp already before your Software Update? Or why you want to flash TWRP?
Normally it's enough to flash a 4 part stock firmware to get your device working again. Use the "home CSC" file to don't lose your own files.
Edit:
on your first try it looks like you tried to flash an older firmware version. You can't downgrade the bootloader. Flash the same or a newer firmware.
Don't be afraid to hit the "Thanks" button if someone helped you. It don't hurts
Click to expand...
Click to collapse
Previously my phone was not rooted or installed TWRP, everything original.
The phone announces a new software update, I make updates and the result is a phone hang on the samsung logo
I downloaded a stock rom, I made Flash with Odin 3.13.1 but the result was a bug, now I do not have a Bootloader. I found out that I was flashing an old version.
So I need Flash recovery, I was trying to find a new version but as a result I could not successfully flash.
I have been trying to find a newer Fimware (such as Android 8) but now I'm still not successful
Logel said:
Edit:
on your first try it looks like you tried to flash an older firmware version. You can't downgrade the bootloader. Flash the same or a newer firmware.
Don't be afraid to hit the "Thanks" button if someone helped you. It don't hurts
Click to expand...
Click to collapse
m4gicvn said:
Previously my phone was not rooted or installed TWRP, everything original.
The phone announces a new software update, I make updates and the result is a phone hang on the samsung logo
I downloaded a stock rom, I made Flash with Odin 3.13.1 but the result was a bug, now I do not have a Bootloader. I found out that I was flashing an old version.
So I need Flash recovery, I was trying to find a new version but as a result I could not successfully flash.
I have been trying to find a newer Fimware (such as Android 8) but now I'm still not successful
Click to expand...
Click to collapse
What do you mean you cannot flash and you don't have a bootloader?
"kernel rev check fail device 2 binary 1" means your device is binary 2 and you're trying to flash binary 1 onto your device.
e.g the latest version firmware for note 8 is N950FXXU4CRGA - U4 shows this firmware is binary 4. On the bootloader - SWREV B:1 - this should show if your device is binary 1.
You will need to first oem unlock the device to flash TWRP/custom img. Warning- flashing TWRP will result in KNOX 1.
Note - bootloader should still be there (you might just have drained all your battery) unless the flash failed during flashing bootloader (bootloader is download mode).
Download firmware here (same firmware for n950fd and n950f) - use samfirm program for faster download (only latest ver).
bluecub1st said:
What do you mean you cannot flash and you don't have a bootloader?
"kernel rev check fail device 2 binary 1" means your device is binary 2 and you're trying to flash binary 1 onto your device.
e.g the latest version firmware for note 8 is N950FXXU4CRGA - U4 shows this firmware is binary 4. On the bootloader - SWREV B:1 - this should show if your device is binary 1.
You will need to first oem unlock the device to flash TWRP/custom img. Warning- flashing TWRP will result in KNOX 1.
Note - bootloader should still be there (you might just have drained all your battery) unless the flash failed during flashing bootloader (bootloader is download mode).
Download firmware .
Click to expand...
Click to collapse
Very thank you
I downloaded the android version 8, I successfully flashed. But this time it was like the beginning. the phone is moving, into the upgrade and error, android child back
Then the phone automatically enters recovery mode
I implemented the wipe cache and wipe data but could not change the result
bluecub1st said:
What do you mean you cannot flash and you don't have a bootloader?
"kernel rev check fail device 2 binary 1" means your device is binary 2 and you're trying to flash binary 1 onto your device.
e.g the latest version firmware for note 8 is N950FXXU4CRGA - U4 shows this firmware is binary 4. On the bootloader - SWREV B:1 - this should show if your device is binary 1.
You will need to first oem unlock the device to flash TWRP/custom img. Warning- flashing TWRP will result in KNOX 1.
Note - bootloader should still be there (you might just have drained all your battery) unless the flash failed during flashing bootloader (bootloader is download mode).
Download firmware
Click to expand...
Click to collapse
How to oem unlock the device?
To oem unlock (like all the new samsung devices) you must enable it in the developer options in settings.
As your phone would not boot oem unlock is not available. you must first ensure the phone can boot to stock firmware
So i tried to root my phone and it happend. After i flashed A10 to phone (again) because my system stuck on bootloop after trying to again flash root. I booted to the system. The normal welcome screen appear, instead of complete it, i decided to go to the recovery and wipe phone again. I dont know why i did it, but i did and now the phone is stuck on bootloop. I tried many things but when i try to even flash system again without root, it stucks on logo. One boot takes time about 2,3 minutes, at the end almost black screen appears (almost because its little shining, it looks like LCD black) for 3sec then everything goes again until battery drain out. From this i can normally boot to any custom or stock recovery. It happend like 3weeks ago and phone is still on bootloop. Please help. Im on TWRP 3.2.3-1_ashyx and i cant find any newer for this phone model, there isnt any orangefox recovery too. I dont know what to do, i tried everything i can like ADB, no success, odin, no success, apps that repair system, also no success. I dont know Im a moron or something but if you can help, tell me everything step by step. Im on bootloader 8.
here is the TWRP i use
Download and flash latest stock firmware for your country via Odin:
Download Samsung Galaxy A6+ SM-A605F firmware
Download the latest Samsung firmware for Galaxy A6+ with model code SM-A605F. Check out our free download or super fast premium options.
www.sammobile.com
Then use this TWRP version for easy flashing custom roms or Magisk (root):
[RECOVERY][UNOFFICAL][LINK FIXED] TWRP 3.5.0 for Samsung Galaxy A6+ 2018
Team Win Recovery Project 3.5.0 Special Notes: 1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options). 2. KNOX will be tripped once you flashed custom binaries to your phone. (Your warranty may be voided. However this may not...
forum.xda-developers.com
However you don't need TWRP if you need only root. Instructions here:
Installation
The Magic Mask for Android
topjohnwu.github.io
When i flash latest stock rom im still in bootloop, I also have problem with flashing that TWRP because odin just errors with Complete (write) operation Failed. Re-flashing system doesnt work. I tried everything, even re-partition. I cant use ADB, also I cant do TOTAL re-install of system because my TWRP is too old and i cant delete Vendor partition, only from TWRP 3.4.0 or higher i can do that, also that old TWRP is buggy,
MDN2137 said:
When i flash latest stock rom im still in bootloop
Click to expand...
Click to collapse
How did you do that? Just putted AP, BL, CP and CSC (not HOME_CSC) in Odin and flashed?
nqnxev said:
How did you do that? Just putted AP, BL, CP and CSC (not HOME_CSC) in Odin and flashed?
Click to expand...
Click to collapse
Im not that stupid . I putted AP fle in AP slot like everything else, i also used CSC not Home CSC.
nqnxev said:
How did you do that? Just putted AP, BL, CP and CSC (not HOME_CSC) in Odin and flashed?
Click to expand...
Click to collapse
Im 100% sure i putted everything in right slot
If you have working properly TWRP at the moment, then just flash newer version TWRP from current TWRP (get IMG file and flash as "Recovery" (choose "Recovery" partition for flashing) and reboot).
MDN2137 said:
and i cant delete Vendor partition
Click to expand...
Click to collapse
Why would you do that? Don't mess with partitions ifself without reason. Just try to update TWRP and then wipe partitions: cache, dalvik, data. You can then try also flashing GSI. Follow instructions from this thread. Maybe it will help.
well... the phone is still stuck on bootloop, but i updated the TWRP thanks to you, but before i had to wipe several partitions to do that, because without that i had error with that SEANDROID bla bla bla, it just means i propably installed wrong recovery or system. I dont know what to do i tried everything i know and Im out of ideas. Please help, this phone is trying to kill me, i want to throw this phone from scycraper and i think this is the best idea.
I think that phone is bricked really hard, like a real brick, but maybe there is still some chance.
The same situation after flashing GSI? Also bootloop?
I dont know how to flash GSI on latest Android10 update
MDN2137 said:
I dont know how to flash GSI on latest Android10 update
Click to expand...
Click to collapse
Instructions here.
Well...... it worked! Thanks.