Galaxy A14 (SM-A145 and SM-A146) Custom Kernels and TWRPs

[Graeme354]

I sent you a bit of feed back but probably in the wrong place. I have flashed the four TWRP recoveries on my A145R/DNS and no damage done. Nothing has taken either. I tried adb side load and Odin but when I reboot to recovery, it comes up as normal.

 

[demlasjr]

Still no feedback?
There are a lot of of downloads and I still don't know if the TWRPs work!

Hi mate. I tested your last version of twrp on A145R and doesn't works, it's like nothing's happening. I still having the same original recovery.

 

[physwizz]

Hi mate. I tested your last version of twrp on A145R and doesn't works, it's like nothing's happening. I still having the same original recovery.

So the first one works but only with usb mouse.
I'll send you some more on pm.

 

[MR.EXPLAINT]

JUST BE ASK ANYONE KNOW WHERE I CAN FIND ABOUT " HOW TO ROOT SAMSUNG SM-A145F (MTK)
THANKS ALOT

 

[physwizz]

JUST BE ASK ANYONE KNOW WHERE I CAN FIND ABOUT " HOW TO ROOT SAMSUNG SM-A145F (MTK)
THANKS ALOT

Exynos 850 Resources ]TWRPs] [Kernels]

Devices post#1 Root method post#2 TWRP post#3 Kernels post#4 Debloaters post #5 wizzROM creators post #6 More Resources https://t.me/a127f_res Exynos 850 Devices 1. A12s A127f & A127m 2. M12 M127f & M127g 3. A21s A217f & A217m 4...

forum.xda-developers.com

 

[physwizz]

A145P A145R twrp build4
Extra partitions added

Unzip to find the tar file

Touch not working.
Use usb mouse.

Do not format data

 

[exnfox]

well ive done it and damn near bricked this phone using mtkutility (well now its called android utility)

all i know is that it still shows ub in the device maanger... its weird though trying to flasxh firmware i download stock rom from samsung and extract the firmware using the mtkutility and the scatter file it generates says its for mt6853 however the phone im trying to fix registers / says online that its mt6833 so inevitably sp flash tool fails....

any suggesations would be great... im able to use mtk auth bypass and even begin to flash with sp tools but there scren has only remained black no matter what... cant get to odin or recovery or anything ...

 

[physwizz]

A146B A146M twrp build 2
Exynos 1330

See post #82

 

[physwizz]

well ive done it and damn near bricked this phone using mtkutility (well now its called android utility)

all i know is that it still shows ub in the device maanger... its weird though trying to flasxh firmware i download stock rom from samsung and extract the firmware using the mtkutility and the scatter file it generates says its for mt6853 however the phone im trying to fix registers / says online that its mt6833 so inevitably sp flash tool fails....

any suggesations would be great... im able to use mtk auth bypass and even begin to flash with sp tools but there scren has only remained black no matter what... cant get to odin or recovery or anything ...

It looks like you've messed up your device with mktutility.

Back to Stock ROM after hard crash
@physwizz
A. On your PC
- Firmware: download from one of these sites
https://samfrew.com or https://www.samfirmware.net


Fastest

Samsung Firmware Download - Lastest official firmware update

Samsung Firmware Download ⭐ Official and fast update ⭐ Lastest and old version ⭐ Max speed and free download ⭐ Best Samsung Galaxy website

samfw.com

1. Connect phone cord to PC
2. Reboot into download mode

Normal method
1. Turn off phone
2. Hold down both volume keys
3. Plug in computer

Bootlooping
1. Plug in to computer
2. Hold down both volume keys

For a difficult phone
1. Connect usb to computer but not to phone
2. Hold down all 3 keys
3. When it buzzes release power and quickly plug in usb to phone.
It might take a few times to get it right.

If it's REALLY BAD
Wait for the battery to completely run down and use normal method.

Escaping the Black screen of Death.

Method 1 - to reboot to TWRP recovery
1. Plug in USB cable to PC
2. Hold down all 3 buttons on phone.
3. When it buzzes release volume down and plug in USB cable to phone.
4. Restore a backup

Method 2 - to reboot to download
1. Plug in USB cable to PC
2. Hold down all 3 buttons on phone.
3. When it buzzes release power button and plug in USB cable to phone.

3. Flash each part of the firmware into its slot.
BL_xxxxxxx.tar.md5 goes into the BL slot
AP_xxxxxxx.tar.md5 goes into the AP slot
CP_xxxxxxx.tar.md5 goes into the CP slot
CSC_xxxxxx.tar.md5 goes into the CSC slot.
Note: if you want to revert to a version with a lower binary, just flash AP and CSC.

4. Factory data reset
5. Wait for the restart
6. Skip through a minimal setup
7. Activate developer mode
8. Allow usb debugging
9. Reboot into download mode
10. Flash recovery.tar in the AP slot
11. Reboot into TWRP and mount everything that you can.
12. Format Data (not just wipe) - don't restart
13. Flash multidisabler or Disable_Dm-Verity_ForceEncrypt if needed by your device.
14. Wipe both caches then go back and Reboot into Recovery.
15. Restore your data backup.
16. Reboot

 

[exnfox]

It looks like you've messed up your device with mktutility.

Back to Stock ROM after hard crash
@physwizz
A. On your PC
- Firmware: download from one of these sites
https://samfrew.com or https://www.samfirmware.net


Fastest

Samsung Firmware Download - Lastest official firmware update

Samsung Firmware Download ⭐ Official and fast update ⭐ Lastest and old version ⭐ Max speed and free download ⭐ Best Samsung Galaxy website

samfw.com

1. Connect phone cord to PC
2. Reboot into download mode

Normal method
1. Turn off phone
2. Hold down both volume keys
3. Plug in computer

Bootlooping
1. Plug in to computer
2. Hold down both volume keys

For a difficult phone
1. Connect usb to computer but not to phone
2. Hold down all 3 keys
3. When it buzzes release power and quickly plug in usb to phone.
It might take a few times to get it right.

If it's REALLY BAD
Wait for the battery to completely run down and use normal method.

Escaping the Black screen of Death.

Method 1 - to reboot to TWRP recovery
1. Plug in USB cable to PC
2. Hold down all 3 buttons on phone.
3. When it buzzes release volume down and plug in USB cable to phone.
4. Restore a backup

Method 2 - to reboot to download
1. Plug in USB cable to PC
2. Hold down all 3 buttons on phone.
3. When it buzzes release power button and plug in USB cable to phone.

3. Flash each part of the firmware into its slot.
BL_xxxxxxx.tar.md5 goes into the BL slot
AP_xxxxxxx.tar.md5 goes into the AP slot
CP_xxxxxxx.tar.md5 goes into the CP slot
CSC_xxxxxx.tar.md5 goes into the CSC slot.
Note: if you want to revert to a version with a lower binary, just flash AP and CSC.

4. Factory data reset
5. Wait for the restart
6. Skip through a minimal setup
7. Activate developer mode
8. Allow usb debugging
9. Reboot into download mode
10. Flash recovery.tar in the AP slot
11. Reboot into TWRP and mount everything that you can.
12. Format Data (not just wipe) - don't restart
13. Flash multidisabler or Disable_Dm-Verity_ForceEncrypt if needed by your device.
14. Wipe both caches then go back and Reboot into Recovery.
15. Restore your data backup.
16. Reboot

download mode is gone as well as TWRP was never there i dont think.... i am able to see it all in MTK client idk if i can find the issue with these logs here:'

[02:11:25]: Status: Waiting for PreLoader VCOM, please connect mobile
[02:12:07]: CPU: MT6833(Dimensity 700 5G k6833)
[02:12:07]: HW version: 0x0
[02:12:07]: WDT: 0x10007000
[02:12:07]: Uart: 0x11002000
[02:12:07]: Brom payload addr: 0x100a00
[02:12:07]: DA payload addr: 0x201000
[02:12:07]: CQ_DMA addr: 0x10212000
[02:12:07]: Var1: 0x73
[02:12:07]: Disabling Watchdog...
[02:12:07]: HW code: 0x989
[02:12:07]: Target config: 0xe5
[02:12:07]: SBC enabled: True
[02:12:07]: SLA enabled: False
[02:12:07]: DAA enabled: True
[02:12:07]: SWJTAG enabled: True
[02:12:07]: EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
[02:12:07]: Root cert required: False
[02:12:07]: Mem read auth: True
[02:12:07]: Mem write auth: True
[02:12:07]: Cmd 0xC8 blocked: True
[02:12:07]: Get Target info
[02:12:07]: BROM mode detected.
[02:12:07]: HW subcode: 0x8a00
[02:12:07]: HW Ver: 0xca00
[02:12:07]: SW Ver: 0x0
[02:12:07]: ME_ID: 097333218F96773457F401D891C12042
[02:12:07]: SOC_ID: 82AE35D282D70380568C082849AD3CF0DE6EED7C2BF0BB6C95E458B9213CDEB8
[02:12:10]: Loading payload from mt6833_payload.bin, 0x264 bytes
[02:12:10]: Kamakiri / DA Run
[02:12:10]: Trying kamakiri2..
[02:12:10]: Done sending payload...
[02:12:10]: Successfully sent payload: C:\Users\exn\Desktop\mtkclient-main\MTKClient GUI 2.0\mtkclient\mtkclient\payloads\mt6833_payload.bin
[02:12:10]: Device is protected.
[02:12:10]: Device is in BROM mode. Trying to dump preloader.
[02:12:11]: Jumping to 0x200000
[02:12:11]: Jumping to 0x200000: ok.

also this log ?


.....Port - Device detected
Port - Device detected
DAXFlash - Uploading xflash stage 1 from MTK_AllInOne_DA_5.2152.bin
xflashext - Patching da1 ...
xflashext - Patching da2 ...
DAXFlash - Successfully uploaded stage 1, jumping ..
DAXFlash - Successfully received DA sync
DAXFlash - UFS FWVer: 0x34
DAXFlash - UFS Blocksize:0x1000
DAXFlash - UFS ID: KM5P9001DM-B42
DAXFlash - UFS CID: ce014b4d355039303031444d2d423432
DAXFlash - UFS LU0 Size: 0xee5800000
DAXFlash - UFS LU1 Size: 0x400000
DAXFlash - UFS LU2 Size: 0x400000
DAXFlash - DRAM config needed for : ce014b4d355039303031444d2d423432
DAXFlash - No preloader given. Searching for preloader
DAXFlash - Sending emi data ...
DAXFlash
DAXFlash
DAXFlash - [LIB]: ←[31mError on sending parameter: DA exceed max num (0xc0070005)←[0m
DAXFlash
DAXFlash - [LIB]: ←[31mError on sending parameter: DA exceed max num (0xc0070005)←[0m
DAXFlash
DAXFlash - [LIB]: ←[31mError on sending parameter: DA exceed max num (0xc0070005)←[0m
DAXFlash
DAXFlash - [LIB]: ←[33mNo preloader given. Operation may fail due to missing dram setup.←[0m
DAXFlash - Uploading stage 2...
DAXFlash
DAXFlash - [LIB]: ←[31mError on sending data: DA hash mismatch (0xc0070004)←[0m
DAXFlash
DAXFlash - [LIB]: ←[31mError on booting to da (xflash)←[0m
None

any help would be greatly appreciated... still trying to figure out how come when i download firmware from those sites and try to extract a scatter file from it it comes up as mt6853 when almost positive this phone is mt6833

 

[physwizz]

download mode is gone as well as TWRP was never there i dont think.... i am able to see it all in MTK client idk if i can find the issue with these logs here:'






any help would be greatly appreciated... still trying to figure out how come when i download firmware from those sites and try to extract a scatter file from it it comes up as mt6853 when almost positive this phone is mt6833

A146p 5g Mediatek MT6833 (a14xm)

 

[exnfox]

A146p 5g Mediatek MT6833 (a14xm)

Yeah then why does it say mt6855 when I extract Samsung rom for a146p firmware idk

 

[physwizz]

Yeah then why does it say mt6855 when I extract Samsung rom for a146p firmware idk

That's nothing.
The A145f is listed as MT6769 but when I started to build the twrp I discovered it was actually Exynos850

 

[physwizz]

A146P recovery.img shows mt6833

 

[exnfox]

so how can i go about getting this device operational? pretty sure the partition table is gone off phone any time i try to flash in spft after bytpasasing auth i get a invalid partition error xc000400008

 

[physwizz]

so how can i go about getting this device operational? pretty sure the partition table is gone off phone any time i try to flash in spft after bytpasasing auth i get a invalid partition error xc000400008

Reinstall firmware using Odin

 

[exnfox]

Reinstall firmware using Odin

no download mode

 

[physwizz]

no download mode

Lost Download Mode?

If your phone boots into recovery mode instead of download mode, this is how I solved it.

1. Let the battery drain down until the phone turns off.
2. Try to turn the phone back on a few times by holding power key.
3. Hold both volume keys and then plug in cable to pc.

This gave me my download back again.

@physwizz

 

[exnfox]

Sadly no recovery or download mode phone stays black however shows up in device manager as mtk preloaded or mtk usb or mtk da agent or vcom

 

[Graeme354]

Any more info on a TWRP recovery for the A145R/DNS ?? Am having no success whatsoever but my phone is fine regardless. I just want Google off it completely.