Howdy,
I got my s23 plus and I would like to unlock the native call recorder. How can I do it? and is it even possible at this moment?
you need to change CSC to THL
i use automatic call recorder and it works
qwerty1q said:
you need to change CSC to THL
Click to expand...
Click to collapse
Hi,
Can you help me pls?
My model name: SM-916W
Baseband version:
S916WVLU1AWBE
1. Got the latest PS driver from here (developer.samsung.com/android-usb-driver)
2. Got the latest Odin tool
3. Visit SAMMOBILE and downloaded S916BXXS1AWBM for SM-S916B THL
But, Odin gives the error "Fail Auth"
And phone showed me the following error:
Secure check fail: ab1(1)
image extract failed
do you know what should I do?
Karfagen said:
Hi,
Can you help me pls?
My model name: SM-916W
Baseband version:
S916WVLU1AWBE
1. Got the latest PS driver from here (developer.samsung.com/android-usb-driver)
2. Got the latest Odin tool
3. Visit SAMMOBILE and downloaded S916BXXS1AWBM for SM-S916B THL
But, Odin gives the error "Fail Auth"
And phone showed me the following error:
Secure check fail: ab1(1)
image extract failed
do you know what should I do?
Click to expand...
Click to collapse
Have you put the phone in download mode, or in recovery mode?
Pupet_Master said:
Have you put the phone in download mode, or in recovery mode?
Click to expand...
Click to collapse
download mode
Karfagen said:
download mode
Click to expand...
Click to collapse
Well try another USB port or cable.
Check if in OS, adb commands work
If not, it's the PC. If it work then i have no idea actually
Related
Hello, i just got my GS7 as an upgrade from rogers a few days ago. I flashed TWRP and rooted with CF auto root. I made a huge mistake by disabling developer options after rooting, and then rebooted my phone. When i disabled developer options, it also disabled OEM unlock. When my phone rebooted it said in red letters above the samsung logo: Custom binary blocked by FRP lock. It would then turn off and only show that screen. I could not boot into recovery, i could only go to download mode. So using odin i attempted to flash the stock firmware and stock recovery. Now when i try to turn on my phone it is stuck in a boot loop but i can get into the stock recovery. In recovery i did a factory reset, but it was still in a boot loop. At the bottom of the recovery page it says:
No Support SINGLE-SKU
Supported API: 3
dm-verity error . . .
In download mode it says: ODIN MODE
DOWNLOAD SPEED: FAST
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON
Secure Download : Enabled
WARRANTY VOID: 1 (0X0500)
RP SWREV: B:2 K:0 S:1
I have tried using kies 3 emergency firmware recovery, but my device does not show up on the list. I tried firmware upgrade and initialization by entering model number and serial number, but it says SM-G930W8 does not support initialization.
MODEL: SM-G930W8
SM-G930WZKAXAC
Im stuck and dont know what else to try. Any advice?
mrkole said:
Hello, i just got my GS7 as an upgrade from rogers a few days ago. I flashed TWRP and rooted with CF auto root. I made a huge mistake by disabling developer options after rooting, and then rebooted my phone. When i disabled developer options, it also disabled OEM unlock. When my phone rebooted it said in red letters above the samsung logo: Custom binary blocked by FRP lock. It would then turn off and only show that screen. I could not boot into recovery, i could only go to download mode. So using odin i attempted to flash the stock firmware and stock recovery. Now when i try to turn on my phone it is stuck in a boot loop but i can get into the stock recovery. In recovery i did a factory reset, but it was still in a boot loop. At the bottom of the recovery page it says:
No Support SINGLE-SKU
Supported API: 3
dm-verity error . . .
In download mode it says: ODIN MODE
DOWNLOAD SPEED: FAST
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON
Secure Download : Enabled
WARRANTY VOID: 1 (0X0500)
RP SWREV: B:2 K:0 S:1
I have tried using kies 3 emergency firmware recovery, but my device does not show up on the list. I tried firmware upgrade and initialization by entering model number and serial number, but it says SM-G930W8 does not support initialization.
s/n: r58jc1a22hr
MODEL: SM-G930W8
SM-G930WZKAXAC
Im stuck and dont know what else to try. Any advice?
Click to expand...
Click to collapse
When flashing with Odin, what files did you use? (Did you use all 4: BL, AP, CP, and CSC?)
Craz Basics said:
When flashing with Odin, what files did you use? (Did you use all 4: BL, AP, CP, and CSC?)
Click to expand...
Click to collapse
i only used AP. I was following a youtube video where he only selected AP
mrkole said:
i only used AP. I was following a youtube video where he only selected AP
Click to expand...
Click to collapse
Ah. You need to use atleast ap AND csc. Dont use home csc if its there.
Down the stock ROM from sammobile.com. It will be in a zip format. Unzip once it using 7zip to yield a tar.md5 file. Just flash this entire file in the appropriate Odin slot.
I have always flash Samsung stock firmware without splitting the firmware into 4 files.
I would not use kies anymore.
audit13 said:
Down the stock ROM from sammobile.com. It will be in a zip format. Unzip once it using 7zip to yield a tar.md5 file. Just flash this entire file in the appropriate Odin slot.
I have always flash Samsung stock firmware without splitting the firmware into 4 files.
I would not use kies anymore.
Click to expand...
Click to collapse
Update: I flashed "combination files" which was supposed to disable FRP lock. After flashing I seem to have gotten an entirely new 'recovery?' I'm really not sure what this is or where to go from here. This is what it looks like: Combination Files https://imgur.com/gallery/jsJIJ
Any ideas on what this is?
Craz Basics said:
Ah. You need to use atleast ap AND csc. Dont use home csc if its there.
Click to expand...
Click to collapse
Update: I flashed "combination files" which was supposed to disable FRP lock. After flashing I seem to have gotten an entirely new 'recovery?' I'm really not sure what this is or where to go from here. This is what it looks like: Combination Files https://imgur.com/gallery/jsJIJ
Any ideas on what this is?
mrkole said:
Update: I flashed "combination files" which was supposed to disable FRP lock. After flashing I seem to have gotten an entirely new 'recovery?' I'm really not sure what this is or where to go from here. This is what it looks like: Combination Files https://imgur.com/gallery/jsJIJ
Any ideas on what this is?
Click to expand...
Click to collapse
Thats the recovery or android?
Download this: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/XAC/download/G930W8VLU2BQK4/198012/
And flash all 4 files in Odin. Not sure what firmware you flashed lol. This should fix up everything, you'll have to unlock the bootloader again if you had to unlock it yourself.
Here is the latest Rogers rom I found: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/RWC/download/G930W8VLU2BQK4/197399/
I have never flashed 4 files to a Samsung phone when restoring to stock. I download the file, zip once to get a single tar.md5 for, and flash the single file in Odin.
Craz Basics said:
Thats the recovery or android?
Download this: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/XAC/download/G930W8VLU2BQK4/198012/
And flash all 4 files in Odin. Not sure what firmware you flashed lol. This should fix up everything, you'll have to unlock the bootloader again if you had to unlock it yourself.
Click to expand...
Click to collapse
Solved!!! after flashing combination files found here: https://www.androidfilehost.com/?fid=529152257862696216
on the left panel i could enable developer options in the settings app: https://imgur.com/gallery/jsJIJ
Then using the free trial of the chimera tool for windows i downloaded and flashed the stock firmware. Phone booted up and i just had to enter my google account info and i was good to go!
audit13 said:
Here is the latest Rogers rom I found: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/RWC/download/G930W8VLU2BQK4/197399/
I have never flashed 4 files to a Samsung phone when restoring to stock. I download the file, zip once to get a single tar.md5 for, and flash the single file in Odin.
Click to expand...
Click to collapse
Solved!!! after flashing combination files found here: https://www.androidfilehost.com/?fid=529152257862696216
on the left panel i could enable developer options in the settings app: https://imgur.com/gallery/jsJIJ
Then using the free trial of the chimera tool for windows i downloaded and flashed the stock firmware. Phone booted up and i just had to enter my google account info and i was good to go!
After flash 7.0 rom via SPflashtool, my phone fust virable.
After format with flag Format whole flash except Bootloader, my Phone is dead. The PC just detect it like a Port Com (COM4). Using SPflashtool again, with hold key, It say ERROR : S_BROM_CMD_STARTCMD_FAIL (2005). Without hold key, It say ERROR: S_AUTH_HANDLE_IS_NOT_READY (5000)
What I can do to repair my Phone?
I know I was did a terrible work with Fortmat flag
I need your help
Don't use sptool... Use ost 6.0.4
Elvaa said:
After flash 7.0 rom via SPflashtool, my phone fust virable.
After format with flag Format whole flash except Bootloader, my Phone is dead. The PC just detect it like a Port Com (COM4). Using SPflashtool again, with hold key, It say ERROR : S_BROM_CMD_STARTCMD_FAIL (2005). Without hold key, It say ERROR: S_AUTH_HANDLE_IS_NOT_READY (5000)
What I can do to repair my Phone?
I know I was did a terrible work with Fortmat flag
I need your help
Click to expand...
Click to collapse
Download this file and flash it using OST tool
(https))(//mega).(nz)/#!M4AT0QbK!KvwxJbBRN0M42Tgo_HX3axBpVt5qTMI5TirnlP3xmWk
davidson7279 said:
Download this file and flash it using OST tool
(https))(//mega).(nz)/#!M4AT0QbK!KvwxJbBRN0M42Tgo_HX3axBpVt5qTMI5TirnlP3xmWk
Click to expand...
Click to collapse
Tried, and it's not working
Did you try OST version6.1.2 or Version 6.0.4?
Elvaa said:
Tried, and it's not working
Click to expand...
Click to collapse
Try it with Version 6.0.4... It worked for me..
6.1.2 doesnt work
davidson7279 said:
Try it with Version 6.0.4... It worked for me..
6.1.2 doesnt work
Click to expand...
Click to collapse
Tried both Version, but failed, too. My Phone go to Dead Mode, It can be flash by 6.0.2. The 6.1.2 supported Dead Mode but It show an error
Hello guys. I was too confident and bought Poco F2 Pro that is bricked - it keeps rebooting and never reaches the system. Now I am in trouble. So I would like to fix it, but it has locked bootloader. What are my options? I can get into fastbood mode and recovery mode, I tried the "wipe all data" option in recovery mode - to no effect. Thanks beforehand for any answers!
EDIT: PC Suite will not connect, eventhough there is such option in the recovery mode. There are only 3 options in the recovery - PC suite, wipe all data and reboot.
chnapo said:
Hello guys. I was too confident and bought Poco F2 Pro that is bricked - it keeps rebooting and never reaches the system. Now I am in trouble. So I would like to fix it, but it has locked bootloader. What are my options? I can get into fastbood mode and recovery mode, I tried the "wipe all data" option in recovery mode - to no effect. Thanks beforehand for any answers!
EDIT: PC Suite will not connect, eventhough there is such option in the recovery mode. There are only 3 options in the recovery - PC suite, wipe all data and reboot.
Click to expand...
Click to collapse
whitch version of Pc suite?
Try this:
https://c.mi.com/thread-2504118-1-0.html
or
https://forum.xda-developers.com/t/failed-to-mount-invalid-argument.4199945/page-2
NOSS8 said:
whitch version of Pc suite?
Try this:
https://c.mi.com/thread-2504118-1-0.html
or
https://forum.xda-developers.com/t/failed-to-mount-invalid-argument.4199945/page-2
Click to expand...
Click to collapse
Thank you, now I struggle with finding out if that is a global or EU version. Could you please help me out with that? Can it be found out with IMEI or SN or something?
PC suite is 2.2.0_7032_2717 - seems like there isn´t a newer one
chnapo said:
Thank you, now I struggle with finding out if that is a global or EU version. Could you please help me out with that? Can it be found out with IMEI or SN or something?
Click to expand...
Click to collapse
https://www.imei.info/
NOSS8 said:
https://www.imei.info/
Click to expand...
Click to collapse
That I checked first but I don´t see the information there.
chnapo said:
That I checked first but I don´t see the information there.
Click to expand...
Click to collapse
IMEI.info: Poco F2 Pro (M2004J11G)
Just 128 or 256 wait!!!
NOSS8 said:
IMEI.info: Poco F2 Pro (M2004J11G)
Click to expand...
Click to collapse
So I went for global as it seems to be the one, I get: ERROR: Sideload error -> adb: failed to read command: No error. Phone reboots and goes again to the recovery mode.
EDIT: that is using the first link
chnapo said:
So I went for global as it seems to be the one, I get: ERROR: Sideload error -> adb: failed to read command: No error. Phone reboots and goes again to the recovery mode.
EDIT: that is using the first link
Click to expand...
Click to collapse
Which method did you use?
Which command?(cmd or power shell)
Which rom?
Check drivers.
Your pc suite is outdate(Wait I'm looking for the link)
https://c.mi.com/thread-2656146-1-0.html
Pc suite
and try with this method
https://forum.xda-developers.com/t/failed-to-mount-invalid-argument.4199945/page-2
I downloaded both files from this link:
https://c.mi.com/thread-2504118-1-0.html
Ran the first file, y - enter, y - enter, then it writes this:
After next Y, it will write a lot of things for a split second and then close.
Then I run the second program according to the instructions - drag and drop the zip rom into xiaomiadb.exe
Which gives me this message
and immediately restarts the phone, that will afterwards go to recovery mode again.
chnapo said:
I downloaded both files from this link:
https://c.mi.com/thread-2504118-1-0.html
Ran the first file, y - enter, y - enter, then it writes this:
After next Y, it will write a lot of things for a split second and then close.
Then I run the second program according to the instructions - drag and drop the zip rom into xiaomiadb.exe
Which gives me this message
and immediately restarts the phone, that will afterwards go to recovery mode again.
Click to expand...
Click to collapse
Where and which rom have you downloaded?
NOSS8 said:
Where and which rom have you downloaded?
Click to expand...
Click to collapse
Hold on, I am finally able to connect my phone to the PC suite, so I may follow that first, or what do you suggest? It offers me an update, so I like that better. Right now downloading the update via PC suite.
This is the ROM I downloaded: https://xiaomifirmwareupdater.com/miui/lmi/stable/V12.2.4.0.RJKMIXM/
https://forum.xda-developers.com/t/failed-to-mount-invalid-argument.4199945/post-84274979
Choose restore not update and use the latest version of Pc suite
Clicking restore does nothing. I am using the version 4.0.529 now.
chnapo said:
Clicking restore does nothing. I am using the version 4.0.529 now.
Click to expand...
Click to collapse
Did you the last version of miflash?
NOSS8 said:
Did you the last version of miflash?
Click to expand...
Click to collapse
Sorry, do you mean Mi PC Suite? Mi Flash is supposed to work only with unlocked bootloaders, isn´t it? Latest version of PC suite I could find was 4.0.529 and that is the first one I tried that managed to recognize my phone.
What about the select file option and flashing the rom I downloaded previously?
chnapo said:
What about the select file option and flashing the rom I downloaded previously?
Click to expand...
Click to collapse
Oups yes mi pc suite
chnapo said:
What about the select file option and flashing the rom I downloaded previously?
Click to expand...
Click to collapse
Also u need to flash stock recovery.img,
extract recovery.img from stock rom and flash it using adb fastboot method. Reboot to stock recovery and navigate to mi-asisstant. Now connect your phone with mi pc suite. there will be listed rom version of your device. Download exactly same rom (full recovery rom) and flash on pc suite
NOSS8 said:
Also u need to flash stock recovery.img,
extract recovery.img from stock rom and flash it using adb fastboot method. Reboot to stock recovery and navigate to mi-asisstant. Now connect your phone with mi pc suite. there will be listed rom version of your device. Download exactly same rom (full recovery rom) and flash on pc suite
Click to expand...
Click to collapse
Why do you think I am not using stock recovery right now? It doesn´t seem to have been overwritten..
Requirements:
-Tested working on firmware A125USQS3BVA2
-A MTK bootloader unlocking tool, tested working with UnlockTool
-This is for A125U on binary 3 ONLY
Special thanks to @Boster27 for translate guide and test method
Steps:
1- Boot into Download Mode (vol+ & vol- & pwr) and flash this custom BL file BL_A125.tar with ODIN patched using the BL button. The device will reboot to an error screen, this is normal.
2- Boot into BROM mode using Test Points (picture attached, needs light dissasembly). Using UnlockTool or your MTK tool of choice, head to the Samsung section and select A125, then on the BROM tab, choose Unlock Bootloader.
After this the device should reboot into recovery and perform a factory reset automatically. In case it doesn't, go into recovery manually (vol+ & pwr) and perform a factory reset. After this the device should boot normally.
3- Once the setup process is complete, connect to Wifi and enable Developer Options to confirm that OEM Unlock is enabled and unlocked. Install the latest version of Magisk Manager and use it to patch the AP file for the corresponding firmware.
4- Boot into Download Mode, make sure the AutoReboot option is unchecked in ODIN, and flash the magisk_patched.tar AP file, and the stock CP, CSC and USERDATA files. Then manually boot into recovery and perform a factory reset. After this the device should boot normally.
5- Once the setup process is complete again, connect to Wifi and enable Developer Options to confirm that OEM Unlock is still enabled and unlocked. Install the latest Magisk app and launch the app.
It should show a dialog asking for additional setup. Let it do its job and the app will automatically reboot your device.
And done! Phone is rooted on binary 3!
Hello
Thanks for the input.
I have a problem when I write the BL_A125.tar it bricks and I can't get into recovery mode to do a wipe.
Attached image of the error.
Thank you
I was able to do it, thanks.
I wrote full firmware, wiped and started from scratch, everything went ok, thanks
marioz17 said:
magisk_patched.tar AP file, and the stock CP, CSC and USERDATA files.
Click to expand...
Click to collapse
link to these files please
mfeliu07 said:
I was able to do it, thanks.
I wrote full firmware, wiped and started from scratch, everything went ok, thanks
Click to expand...
Click to collapse
magisk_patched.tar AP file, and the stock CP, CSC and USERDATA files.
do you have the link for the full firmware
unruly1981 said:
magisk_patched.tar AP file, and the stock CP, CSC and USERDATA files.
do you have the link for the full firmware
Click to expand...
Click to collapse
Yes here is https://samfw.com/firmware/SM-A125U/AIO/A125USQS3BVA2
marioz17 said:
Yes here is https://samfw.com/firmware/SM-A125U/AIO/A125USQS3BVA2
Click to expand...
Click to collapse
thank u
marioz17 said:
Yes here is https://samfw.com/firmware/SM-A125U/AIO/A125USQS3BVA2
Click to expand...
Click to collapse
does it have the magisk_patched.tar ?
unruly1981 said:
does it have the magisk_patched.tar ?
Click to expand...
Click to collapse
You need to patch the AP from firmware with magisk app
Did you have to take the phone apart. or can you just use the software.
timandolly said:
Did you have to take the phone apart. or can you just use the software.
Click to expand...
Click to collapse
Need to take apart, but this phone is so easy to open
Would this work on the S127DL? The Tracfone Galaxy A12.
Wish39 said:
Would this work on the S127DL? The Tracfone Galaxy A12.
Click to expand...
Click to collapse
i need the phone to test but you can try if the phone can enter BROM mode with testpoint
marioz17 said:
i need the phone to test but you can try if the phone can enter BROM mode with testpoint
Click to expand...
Click to collapse
Ok when I get one then I will try. Do you also have a unlockable BL for the Galaxy A21 (A215U, A215W, A215U1, S215DL)? I have a S215DL that I can test for that, but it is on binary 6.
Wish39 said:
Ok when I get one then I will try. Do you also have a unlockable BL for the Galaxy A21 (A215U, A215W, A215U1, S215DL)? I have a S215DL that I can test for that, but it is on binary 6.
Click to expand...
Click to collapse
I want this phone to be my next project
mfeliu07 said:
Hello
Thanks for the input.
I have a problem when I write the BL_A125.tar it bricks and I can't get into recovery mode to do a wipe.
Attached image of the error.
Thank you
View attachment 5591207
Click to expand...
Click to collapse
Did you add the ap ,modem and csc when you used the modded bootloader.
mfeliu07 said:
Hello
Thanks for the input.
I have a problem when I write the BL_A125.tar it bricks and I can't get into recovery mode to do a wipe.
Attached image of the error.
Thank you
View attachment 5591207
Click to expand...
Click to collapse
I got the same how did you fix?
timandolly said:
I got the same how did you fix?
Click to expand...
Click to collapse
You write the BL_A125.tar, disconnect the battery and unlock the booloader, after this it enters without problems and is deleted.
If it doesn't, disconnect battery and force enter recovery with volume up and power, do a factory reset
timandolly said:
Did you add the ap ,modem and csc when you used the modded bootloader.
Click to expand...
Click to collapse
This after unlocking booloader
mfeliu07 said:
You write the BL_A125.tar, disconnect the battery and unlock the booloader, after this it enters without problems and is deleted.
If it doesn't, disconnect battery and force enter recovery with volume up and power, do a factory reset
Click to expand...
Click to collapse
Thanks for helping. I rooted 4 note 4s and they all finally give out so I am going to try a newer phone
I was flashing my phone with a stock sm-n960f firmware and was having some error "secure check failed bootloader "
I checked my about phone and the model number is showing sm-n960f but when I am in download mode it shows sm-n960n
Can someone please help me out
The problem is you tried to flash a ROM what is not matching.
Watch this video:
jwoegerbauer said:
The problem is you tried to flash a ROM what is not matching.
Watch this video:
Click to expand...
Click to collapse
Ok