Go to command line in twrp and just enteryes but i get stuck in a bootloop and another i cant wipe the systemthis photo isnt mine because i dont know how to make screenshot while twrp is on but its something like this
View attachment 5849463
Go to command line in twrp and just enteryes but i get stuck in a bootloop and another i cant wipe the systemthis photo isnt mine because i dont know how to make screenshot while twrp is on but its something like this
View attachment 5849463
Could you attach a prebuilt image file?I compiled a WORKING recovery with my friend for samsung a137f ! and its working. I have proof
this recovery was found at https://github.com/edward0181/android_device_samsung_a13ve
but I have encrypted Data partition and I want to decrypt it...
I can't format data through TWRP ;-;
@physwizz could you maybe attach a built version of the a137f twrp tar file cause I can't build it?
@edward0181 is building it@physwizz could you maybe attach a built version of the a137f twrp tar file cause I can't build it?
@wojtekojtek please man
ok lmk when its done building
ok im gonna sound a little dumb,theres older version (not mine, but @edward0181 )
it should work
1. Download samsung's stock firmware hereok im gonna sound a little dumb,
but the phone bootloops!
Ive done everything you've set before
What should I do now?
What magisk should I use? When I tried using Magisk, the phone tried to boot up but after the "Powered by Android" screen it rebooted1. Download samsung's stock firmware here
2. Extract zip file
3. Using 7zip unpack the recovery.img.lz4 file
4. Pack it into tar file,
5. Reboot to download mode
6. Flash the recovery tar file
7. Boot your phone
-------------------
To make TWRP working:
8. Install Magisk on phone
9. Copy AP file to phone
10. Patch it using magisk
11. Move it to pc
12. Flash it (you will lose data)
- in AP slot add your patched file
- in BL add BL file
- in CSC add CSC file
- in CP add CP file
13. Boot your phone
14. Flash TWRP
15. Boot your phone again
Did you flashed all files? (Cp, csc, bl, ap)What magisk should I use? When I tried using Magisk, the phone tried to boot up but after the "Powered by Android" screen it rebooted
update: even when I flash stock firmware it still bootloops(even with factory reset it bootloops, is the bootloader the problem?)
update's update: I bricked the phone? It just bootloops, Re-Partioning doesnt work and it restarts every time, event in recovery, even when "erasing"![]()
(crashes = restarts)Did you flashed all files? (Cp, csc, bl, ap)
If no, then try, maybe it will work...
Edit: also wipe data after flashing stock firmware
Thanks.Thank you very much for your work on 137f.
Will some day a easy-to-handle solution like a lineageOS build result from your valued work?
I recently obtained a 137f, but my S5 is still working, so lazy bone I am I'd rather take an easy path...
Cheers,
Wolf
just use LineageOS TD-based GSIThank you very much for your work on 137f.
Will some day a easy-to-handle solution like a lineageOS build result from your valued work?
I recently obtained a 137f, but my S5 is still working, so lazy bone I am I'd rather take an easy path...
Cheers,
Wolf
Hi, I've build Orangefox TWRP variant for A13 SM-A137F (MTK) phone.
Great workHi, I've build Orangefox TWRP variant for A13 SM-A137F (MTK) phone.
Decryption still not working and disabling FBE break Samsung OS... so take it as it is.
If someone wants to help with correct decyption blobs, then please ;-)
Great work mate!Hi, I've build Orangefox TWRP variant for A13 SM-A137F (MTK) phone.
Decryption still not working and disabling FBE break Samsung OS... so take it as it is.
If someone wants to help with correct decyption blobs, then please ;-)
disabling encryption in vendor breaks oneui?Hi, I've build Orangefox TWRP variant for A13 SM-A137F (MTK) phone.
Decryption still not working and disabling FBE break Samsung OS... so take it as it is.
If someone wants to help with correct decyption blobs, then please ;-)
It does.
nahThank you very much for this hint. It's really confusing, as I could not find a comprehensive instruction for this phone. For an ordinary person it's hard to distinguish what to do. I'll be happy to collect all the data and write an instruction for this phone - promised. But I'd need a little help.
Questions so far:
Sorry for these amateurish questions - but those do occur at amateurs'....
- I found these instructions. But my guess is that it's not necessary to perform all these steps. True? - Should it be possible just to flash the image into the phone, following instructions at the Odin page?
- I found I do need a "arm32-binder64" Type "A" ROM. True? - Or will an "AB" work as well? - More of the latter seem to be around.
- system-td-arm32_binder64-ab-vanilla.img.xz from https://github.com/TrebleDroid/treble_experimentations/releases seems to be a promising candidate. True?
- Images normally come as *.img files, Odin requires *.tar files. Is it good enough to just tar these files for Odin?
Cheers,
Wolf
nahThank you very much for this hint. It's really confusing, as I could not find a comprehensive instruction for this phone. For an ordinary person it's hard to distinguish what to do. I'll be happy to collect all the data and write an instruction for this phone - promised. But I'd need a little help.
Questions so far:
Sorry for these amateurish questions - but those do occur at amateurs'....
- I found these instructions. But my guess is that it's not necessary to perform all these steps. True? - Should it be possible just to flash the image into the phone, following instructions at the Odin page?
- I found I do need a "arm32-binder64" Type "A" ROM. True? - Or will an "AB" work as well? - More of the latter seem to be around.
- system-td-arm32_binder64-ab-vanilla.img.xz from https://github.com/TrebleDroid/treble_experimentations/releases seems to be a promising candidate. True?
- Images normally come as *.img files, Odin requires *.tar files. Is it good enough to just tar these files for Odin?
Cheers,
Wolf
Here it is.yes if you can do the best possible for my equipment, thank you