yashsingh1/xdaforums huggingface dataset:
[LineageOS Questions & Answers] marcinguy:
I just flashed my mobile with LineageOS 14.1

To my surprise I see the crashes that they dont show full stack trace.

Only this:

01-03 22:44:01.189 12773 12807 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x42424242 in tid 12807 (hci_thread)

Do I have to enable it somehow?

I would expect to see something like this (this I remember from Cyanogenmod and Stock Android)

02-05 16:45:13.279 307 1231 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x1 in tid 1231 (netmgrd)

02-05 16:45:13.351 6570 6570 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

02-05 16:45:13.352 6570 6570 F DEBUG : CM Version: '14.1-20170131-NIGHTLY-osprey'

02-05 16:45:13.352 6570 6570 F DEBUG : Build fingerprint: 'motorola/osprey_retus_2gb/osprey_u2:6.0.1/MPI24.107-55/33:user/release-keys'

02-05 16:45:13.352 6570 6570 F DEBUG : Revision: '0'

02-05 16:45:13.352 6570 6570 F DEBUG : ABI: 'arm'

02-05 16:45:13.352 6570 6570 F DEBUG : pid: 307, tid: 1231, name: netmgrd >>> /system/bin/netmgrd <<<

02-05 16:45:13.352 6570 6570 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x1

02-05 16:45:13.352 6570 6570 F DEBUG : r0 b6b01f10 r1 00000001 r2 b6b06560 r3 00000040

02-05 16:45:13.352 6570 6570 F DEBUG : r4 b647f3fc r5 b6b06eac r6 b6b01f10 r7 b6b02d07

02-05 16:45:13.352 6570 6570 F DEBUG : r8 b5f07520 r9 b5f07500 sl 00000001 fp b6f7ea49

02-05 16:45:13.352 6570 6570 F DEBUG : ip 00000000 sp b647f000 lr b6af9ba5 pc b6af9bce cpsr 20070030

02-05 16:45:13.363 6570 6570 F DEBUG :

02-05 16:45:13.363 6570 6570 F DEBUG : backtrace:

02-05 16:45:13.363 6570 6570 F DEBUG : #00 pc 00007bce /system/vendor/lib/libnetmgr.so (netmgr_nl_decode_nlmsg+269)

02-05 16:45:13.363 6570 6570 F DEBUG : #01 pc 00020f7d /system/bin/netmgrd

02-05 16:45:13.363 6570 6570 F DEBUG : #02 pc 00033893 /system/bin/netmgrd

02-05 16:45:13.364 6570 6570 F DEBUG : #03 pc 00041b09 /system/bin/netmgrd

02-05 16:45:13.364 6570 6570 F DEBUG : #04 pc 0000bef9 /system/vendor/lib/libdsutils.so (stm2_process_input+632)

02-05 16:45:13.364 6570 6570 F DEBUG : #05 pc 0000c7dd /system/vendor/lib/libdsutils.so (stm2_instance_process_input+204)

02-05 16:45:13.364 6570 6570 F DEBUG : #06 pc 0001213d /system/bin/netmgrd

02-05 16:45:13.364 6570 6570 F DEBUG : #07 pc 00003f9f /system/vendor/lib/libdsutils.so

02-05 16:45:13.364 6570 6570 F DEBUG : #08 pc 000477d3 /system/lib/libc.so (_ZL15__pthread_startPv+22)

02-05 16:45:13.364 6570 6570 F DEBUG : #09 pc 00019b7d /system/lib/libc.so (__start_thread+6)

Thanks,
[LineageOS Questions & Answers] Ibuprophen:
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread for your device.

https://xdaforums.com/showthread.php?t=3466246

Good Luck!

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[LineageOS Questions & Answers] marcinguy:
Thanks!

Actually it is a general Question in regards to LineageOS 14.1.

The device I use is S3 Neo+ GT-9301I

I pasted sample output as I it remember from Motorola device.

So on my device, as stated I just get:

12-31 13:11:00.180 8059 8096 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 8096 (bt_workqueue)
12-31 13:11:00.181 209 209 W : debuggerd: handling request: pid=8059 uid=1002 gid=1002 tid=8096
12-31 13:11:00.220 8059 8096 F libc : failed to resend signal during crash: Operation not permitted
12-31 13:11:00.229 8335 8335 E DEBUG : unexpected waitpid response: n=8096, status=00000000
12-31 13:11:00.229 8335 8335 E : debuggerd: timed out waiting for signal
12-31 13:11:00.231 8335 8335 E : debuggerd: ptrace detach from 8096 failed: No such process
12-31 13:11:00.233 8335 8335 E : debuggerd: failed to kill process 8059: No such process
12-31 13:11:00.236 778 810 I BootReceiver: Copying /data/tombstones/tombstone_09 to DropBox (SYSTEM_TOMBSTONE)

Any ideas?

Where there is "Operation not permitted"?
[LineageOS Questions & Answers] marcinguy:
Narrowed it down to this:

int rc = syscall(SYS_rt_tgsigqueueinfo, getpid(), gettid(), signal_number, info);

if (rc != 0) {

__libc_format_log(ANDROID_LOG_FATAL, "libc", "failed to resend signal during crash: %s",

strerror(errno));

_exit(0);

}

12-31 14:35:20.070 14851 14881 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 14881 (bt_workqueue)

12-31 14:35:20.070 16288 16288 W : debuggerd: handling request: pid=14851 uid=1002 gid=1002 tid=14881

12-31 14:35:20.100 14851 14881 F libc : failed to resend signal during crash: Operation not permitted

Wondering why it gets Operation not permitted?
[LineageOS Questions & Answers] marcinguy:
Figured it out.

Had to modify debbugerd (bionic) and adjust selinux.

Now debuggerd can attach to the process and show the debug info and backtrace.
[General Questions and Answers] simonsez9:
Hi,

How can I create my own RUU file? I have a completely untouched stock HTC M9+ and I'd like to create an RUU of the phone before I start customizing it so I can always return to stock if needed. I think the way to do this is create an RUU from the phone ,but I can't find any instructions online for doing so.

Thanks,

simon
[General Questions and Answers] Ibuprophen:
I don't have this device but, the following threads may be helpful for what you are looking to do and don't be afraid to ask for some member guidance within one of them.

https://xdaforums.com/showthread.php?t=3754079

https://xdaforums.com/showthread.php?t=3547166

https://xdaforums.com/showthread.php?t=3690966

https://xdaforums.com/showthread.php?t=3152206

Good Luck!

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[General Questions and Answers] simonsez9:
Hi,

Thanks for answering my post. Unfortunately the links you provided are =archives of RUU images. I was actually trying to find out how one creates an RUU so I could create one of my stock HTC M9+ international edition. If it's possible I would like to create my own RUU to have a master copy of my own stock phone that I could use to return to stock before I started modding. I know I could use the links in those posts for this purpose, but I'd like to learn how to make these RUU images.

simon
[Windows Mobile Development and Hacking General] selvagan:
Hi,

Would like to know how to flash HTC Kaiser TYTN II ROM on HTC TILT 8925 and where can we download original TYTN II ROM. Is there any blog which talks about it.
[Windows Mobile Development and Hacking General] taiseer999:
1 Yes but be careful with radio versions.

2 http://xdaforums.com/showthread.php?t=369282
[Honor 8 Questions & Answers] Alex070609:
Hi World,

So, i've tried to go back into a stock rom after dealing with serious problems with a bad flash on TWRP, i've gone from EMUI to LineageOS then tried to go back into stock.

i flashed :

System.img

Cust.img

Boot.img

and Recovery.img

from the Duke-L09I_C675B130.rar i saw on XDA.

problem is i can't perform a factory reset neither wipe the cache partition and every time i try to do the Dload method it stops and doesn't move at 5% the there is a "!" in the middle of the circle.

my phone is an FRD-L09 and im in france so if somebody can help me, your welcome.

Have a nice day !
[Moto Z Force Questions & Answers] Rtuz2th:
Hi,

first of all I know this is a well discussed topic, I know there are already threads and I know the verizon unlocking policy. I bought a used Z Force via Ebay, got it shipped to my home in Germany. When it arrived, it suffered from the Wifi and Bluetooth issue, but it worked with my sim card. I shipped it back to America because a phone without bluetooth and wifi is useless for me. Motorola replaced it with a new phone (I'm sure about this, the new phone Motorola sent me has a different IMEI.) Bluetooth and Wifi work now - but it won't read my Simcard. It recognizes my PIN and accepts it, but it wont connect to the german GSM network, although bands are compatible, I've checked that before. It does not even read the number from the Sim, and I've got a notification that the inserted Sim is not a Verizon Sim. How do I get this phone working with my german carrier? Is this one really locked? I've called Verizon, they sent me to motorola. Motorola wants to send an unlock code to my german carrier. But as far as I know all verizon phones are unlocked from the start, so I do not really get the problem? Does anyone have an idea or could explain me whats going on here? Thank you very much,

rtuz2th
[Moto Z Force Questions & Answers] kkhadr:
Strange, because I bought three Verizon Moto Z Force from eBay shipped to Egypt and all 3 are working fine for more than year now.
[Moto Z Force Questions & Answers] Rtuz2th:
Okay, just in case anyone faces the same problems - the Simcard I used was defective, although it was a new one from my german carrier. Got a new simcard and everything works fine.
[Galaxy S3 Neo General] spirit_of_the_ocean:
The S3 neo comes in two variants:

a) two samsung cameras

b) non-selfie-camera from sony(imx 175) and samsung selfie-camera.

At this point we have 2 working los 14.1 and it is good to know which one you need.

METHOD: Hidden Menu

Now I have an update to figure out which sensor you have. This I have from Thargorsson.

THIS WILL ONLY WORK ON YOUR (MEANS WITH WORKING CAMERA) STOCK ROM!

It should be E08QT or B08QT.

E08QT = SAMSUNG

B08QT = SONY

Thanks to kickivivi :good:

He collected lots of information.

Methods who will work 100%:

Method 1:

In neo Homies group Kickyvivi added:

So it depends on which build of Leos you installed.

Method 2:

Install Los 14.1 for Samsung:

LOS with working Samsung cams:

https://androidfilehost.com/?fid=673956719939827464

If both cam work you have samsung else sony.

Method 3:

Take a logcat on stock rom. Open camera and close it. Search in logcat for imx175. If it is in there you have sony cam if not samsung.

These have unfortunately proven to be not 100% reliable:

Method 4:

You can use those apps like:

- Device Info HW

- Phone INFO ★Samsung★

But they only work on stock because the read whats in roms data.

BEWARE:

On Neo Homies some people reported to get false results. So the results are not always reliable.

Method 5:

Also there are stocks roms which contain both files. So this is also not reliable.

Special thanks go to:

- Kickyvivi

- Neo Homies Telegram group
[Galaxy S3 Neo General] spirit_of_the_ocean:
UPDATE

Hello,

we found out that some stock roms have files for both cameras. So method number 4 is not reliable :(.

We found out that on the same country there are samsung and sony neos. We did not find a system yet.
[Galaxy S3 Neo General] spirit_of_the_ocean:
Update: Easiest method

The neo homies user EdgyIsHere made this thread:

https://xdaforums.com/showthread.php?t=3311213

That means if your stock rom has "NI" and "NJ" in the PDA and/or CSC it is Samsung If not it IS Sony.
[Galaxy S3 Neo General] hidden_root:
well seems indeed i have sony sensors, thats wired thats dont show in hw app

CyanogenMod 12 by Rox works fine without the need to Camera Fix

can i just replace camera sensor and get it to work with the roms?

[IMG="screenshot"]https://i.imgur.com/pWi7ko4.png[/IMG][
[Galaxy S3 Neo General] spirit_of_the_ocean:
Updated information

I updated the first post. Unfortunatly not every posted method was reliable. :(
[Galaxy S3 Neo General] spirit_of_the_ocean:
UPDATE:

Added the method with hidden menu in stock rom (see OP)

Yes, Leo did it by himself. It is possible just to change the camera hardware. Technically the samsung camera will work with the motherboard of sony edition and the other way round.
[Galaxy S3 Neo General] Ciccio_22:
which rom I have to choose on sammobile for sensory sony ?? thank you so much
[Galaxy S3 Neo General] andy_s2018:
Hello

I downloaded the app aida64 ...... but the voice devices I can not find ..... I find devices ....

and anyway tells me camera not aviable ....

I have lianeage 14.1 .....

how do I do it because the camera does not work ...... :( :( :(

Hello and thanks
[Galaxy S3 Neo General] shhnedo:
Guys, need some clarification here.

Here's the phone: GT-i9301I

Baseband: I9301I

XX

UAPG1

Build number: KOT49H.I9301I

XC

SAQA2

Service menu: E08QLHI01CI

As far as I know, E08 is supposed to be the Samsung camera, which is supposedly common on stock firmware with a PDA

XC

. My question is if the mismatch between baseband and build number (XX and XC respectively) is important? If yes, then PDA refers to the build number, right?
[Galaxy S3 Neo General] maiwufsiorn:
I installed LineageOS 16 on my Samsung Galaxy SIII Neo a year ago and now I want to update to LineageOS 17, but I can't remember anything about my camera.

However when I browse the contents of the filesystem (with FX on the rooted phone) I see a lot of E08QL_* files in SYSTEM/VENDOR/LIB (and no B08QL_* files). Does that mean that I have a Samsung rear camera? Or isn't that a safe bet?

Cheers,

mai
[Galaxy S3 Neo General] andy_s2018:
i have installed INFO DEVICE HV but it does not put me the brand or vendor

I have lineage 16 .....
[Galaxy S3 Neo General] themercenary333:
I have Samsung Galaxy S III Neo with LineageOS 17.1. I have a similar problem with the camera. Both rear and front are not worked on LineageOS 17.1. Even the camera app does not appear in the app list. When I open the "Open Camera" or another camera app, it gets stuck on the black screen. In fact, both rear and front cameras did not work on stock ROMs. Actually, I couldn't find which stock ROM suited my device before installing LineageOS. I tried lots of stock ROMs but only the rear camera work on Romania and Open Australia stock ROMs. When I checked with AIDA64 and codes in the stock ROMs where the rear camera was running, I saw that the model of the device was "s3ve3gxx". Therefore, I flashed lineage-17.1-20210809-nightly-s3ve3gxx (Samsung Galaxy S III Neo / Sony Camera). I installed LineageOS 17.1 hoping it would fix my camera and battery draining problem. However, I experience many problems, including not working of camera and flashlight, overheating, battery draining. How can I solve this issue do you have any idea?

*** On the other hand, the battery was running out very quickly in the stock ROM (with DBT code) where the two cameras were not working. The app that consumes the most battery is called "mm-qcamera-daemon".
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] SK00RUPA:
TWRP 3.2.1-0 For A5 2017​

​

Disclaimer​

/*
* Your warranty will be VOID after installing a custom recovery.
*
* Get notified yourself that I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it!
* YOU are choosing to make these modifications,
* and if you point the finger at me for messing up your device,
* I will laugh at you.
*

This is for A5 2017 only​

Download​

TWRP SM-A520F FOR FLASHING IN TWRP:

https://basketbuild.com/filedl/devs?dev=androidlover5842&dl=androidlover5842/a5y17lte/recovery_a5y17lte-080318.img

TWRP SM-A520F FOR FLASHING IN ODIN:

https://www.androidfilehost.com/?fid=890129502657588962

Instructions​

With Twrp : download the .img file on your phone and flash it throw the older twrp by the image installation menu

With Odin : download the .tar file and flash on AP case of Odin

Credits​

[MENTION=8910950]TwrpBuilder[/MENTION] for his tool/trees

[MENTION=7552758]PMFRTT[/MENTION] for testing

source: https://github.com/TwrpBuilder/android_devivce_a5y17lte
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] PMFRTT:
Working flawless on my device! Good Job DEV
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] SK00RUPA:
Keep in mind that is mainly work of TwrpBuilder: https://xdaforums.com/member.php?u=8910950

But good to know that is working perfectly!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] PMFRTT:
Reserved
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] SK00RUPA:
The TWRP is repaired now and everything is working as expected, download and enjoy! :)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] KaiKellner:
It is working perfectly.

Thanks
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] AndreCalado:
Any issue for now or it still works perfectly?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] KaiKellner:
Still working flawlessly. Am using it on the latest Stock Rom February Patch DBT. The ONLY disadvantage is the missing language support. It is English available only.

Cheers
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] mcvisster:
Do we need to flash "no-verity-no-encrypt_ashyx.zip" also? Because i don't see it in instructions.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ChARCOOL:
If you use stock Samsung ROM with Magisk it will lag your phone!

check my thread and you don't need to flash no-verity-no-encrypt_ashyx.zip
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] mcvisster:
No. Im not planing to use samsung stock. Im waiting official LOS for our device. So i need it to flash rom and after to use it on LOS. So there should be no lag or problems with this TWRP on LOS?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] moozer:
Works flawlessly

---------- Post added at 12:26 AM ---------- Previous post was at 12:24 AM ----------

Disagree - It does NOT lag the phone. Never has done with mine...not with stock firmware or LOS and it's variants.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] LuandersonGama:
error

only official release binaries are to be flashed(recovery)

all versions twrp give me error
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] SK00RUPA:
https://xdaforums.com/samsung-a-series-2017/how-to/guide-root-install-twrp-samsung-t3747535 :)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] mcvisster:
Your TWRP is not working without "no-verity-no-encrypt_ashyx.zip". Iflashed it through odin. Made backup and now im stuck with samsung logo. Just so i can use Lineage OS. Thank you.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] neon28:
TWRP is not working

are you going to fix it?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] SK00RUPA:
Whats is not working for you?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] neon28:
I do not know why TWRP is not working on my device,

i use fw oreo russia and odin 3.13.1
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] moozer:
Is your device OEM locked?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] neon28:
I've read it

got in TWRP once but did not work properly

then I restarted the device and TRWP disappeared
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] moozer:
What do you get instead of TWRP? Anything different?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] neon28:
I entered TRWP with orange color theme

but I can not delete data and the other,

can not install ROM,

can not see the ZIP file in SD CARD

etc

---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------

I reentered the standard recovery
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] moozer:
And you can enter download mode to use in Odin?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] neon28:
yes
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] moozer:
Really strange. How many times have you tried to flash via Odin
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] neon28:
4x

now i am using FW oreo russia

and odin v3.13.1

Can you help me?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] moozer:
I'll try to help bro.

Did TWRP work on Nougat?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] neon28:
i have never tried in nougat
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] moozer:
I've had it in Nougat and flashed stock SER Oreo without affecting TWRP.

Not sure what I can do really but I'll get back to you with suggestions. In the meantime, make sure you have a brand new copy of the latest TWRP (delete what you already have and redownload to ensure you're working with absolutely clean files).
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] neon28:
ok, i'm downloading a new TWRP file

and if you can, you use ODIN VERSI how much?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] moozer:
Use latest ODIN

---------- Post added at 11:09 AM ---------- Previous post was at 11:07 AM ----------

Just checking...is this the TWRP you are downloading?

https://www.androidfilehost.com/?fid=890129502657588962
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] moozer:
Hi. Been a little busy with family, sorry I've not been in touch.

Okay. You have fresh files all ready.

Open up Odin.

Connect phone via USB. Reboot into download mode.

Before you flash the recovery, untick the Auto Reboot option

Tap AF and load up the new TWRP file

Flash the recovery and when complete, unplug USB and reboot into recovery by pressing Home+Volume Up+Power[/QUOTE]
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Andriano24:
If you don't see any zip or .img file, the problem is that your device is encrypted. To remove that go to Twrp Recovery > Wipe > Format Data and type "yes". Your data should be now decrypted but if you boot into ROM it will automatically encrypt your files (Samsung security logic). So make sure to have this; https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip already downloaded to your SD Card. (Make sure to flash this file INSIDE Twrp only after formating your data. IT'S NOT AN ODIN FLASHABLE FILE! And I say only after formating your data because you can't just flash it, Twrp only has access to mount the data after a format). This will decrypt for sure your phone and then you will have the ability to flash anything via Twrp! But keep in mind that if you reflash the firmware via Odin and install again any Twrp you have to to the steps again, ah, what a pain! I hope I helped you out :D.

---------- Post added at 04:01 PM ---------- Previous post was at 03:58 PM ----------

You may mean AP, not AF :P.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] moozer:
Thank you - simple typo
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Andriano24:
You have to flash that file inside Twrp, not Odin :laugh:. But first so you will be able to flash that you have to follow this post; https://xdaforums.com/samsung-a-series-2017/development/recovery-sm-a520f-2017-t3759214/post76299176 :D.

---------- Post added at 04:09 PM ---------- Previous post was at 04:05 PM ----------

Oh... So you flashed a new bootloader. That's not good. You got RMM Stage:Prenormal.

Take a look at this thread; https://xdaforums.com/samsung-a-series-2017/how-to/guide-root-install-twrp-samsung-t3747535

---------- Post added at 04:16 PM ---------- Previous post was at 04:09 PM ----------

For those who already read it, I have added some extra lines so you understand everything.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] moozer:
He said he had TWRP but it vanished. I assumed wiped by error somehow.

We'll await his reply.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Andriano24:
Yeah ;):good:.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] neon28:
[/QUOTE]

thanks for your support

before I often make modifications ROM from the era of S3 mini until J5 2016 and all goes as I let

end of december 2017 i changed my device from j5 2016 to A5 2017 and until yesterday i have never modified my 2015 A5 device

until finally I replace NOUGAT region indonesia (ori) to OREO region SER

all the suggestions from you and what I have learned I have tried but nothing works

and that confuses me why can not I delete data through TRWP?

even i can not see the file in SD CARD

but I can see the external SD CARD file as usual

and strangely the TRWP I installed will be lost when my device is rebooted or restarted

I feel very stupid

Please help me

I have to learn a lot from you guys

:crying: :crying: :crying: