Database Develop

TWRP asking for password

Hello, when I TWRP it asks for a password to decrypt data and if I don't input the password it won't let me access the emulated sdcard. I've never put any password though =/
Is there any way to restore twrp without flashing the stock image/wiping data?

Please search next time...
The password is as follows: (type or exactly as written below)
default_password

Pilz said:
Please search next time...
The password is as follows: (type or exactly as written below)
default_password
Click to expand...
Click to collapse
I typed it as you wrote it with the underscore and no uppercase letters but it gives me Password Failed, Please Try Again
I actually made a quick search before posting and I tried this password before.. Another solution is to wipe data/factory reset but if possible I'd like just to re-install TWRP or remove the password somehow

you missed a step initially. after unlocking the bootloader, you MUST reboot first before flashing TWRP.
to fix this, you'll need to hit cancel at the password screen, then go into wipe and do a factory reset. next, go back into wipe and press the format data button. you have to type yes to continue.
this isnt a fun process, as you have to re-setup your device again, but you've just learned something.

xBeerdroiDx said:
you missed a step initially. after unlocking the bootloader, you MUST reboot first before flashing TWRP.
to fix this, you'll need to hit cancel at the password screen, then go into wipe and do a factory reset. next, go back into wipe and press the format data button. you have to type yes to continue.
this isnt a fun process, as you have to re-setup your device again, but you've just learned something.
Click to expand...
Click to collapse
I assumed he already did this, but in which case we have all been here at one point. I learned the hard way twice now...

kal eh said:
Hello, when I TWRP it asks for a password to decrypt data and if I don't input the password it won't let me access the emulated sdcard. I've never put any password though =/
Is there any way to restore twrp without flashing the stock image/wiping data?
Click to expand...
Click to collapse
No need to fear, Theskillfultroll is here! :good:
To fix your issue, download NEXUS ROOT TOOLKIT by WugFresh, after doing so, you need to open it up and choose your correct device (DO NOT MAKE A MISTAKE HERE OR ELSE YOU CAN BE HARD BRICKED) if you have already unlocked the OEM, then good for you, but what i wanna focus here is on the main window, right hand side* there is a button labeled 'FLASH STOCK + UNROOT' depending on your situation , if you are soft bricked select so, if not click device on. if soft bricked it will tell you what to do, and vice versa on other option, AFTERWARDS, attempt to stock flash and unroot, now if it fails godforbid, you have to go to options and ENABLE FORCE FLASH *WARNING IF YOU DID NOT CHOOSE CORRECT DEVICE AND YOU PICK THIS, YOU WILL BE HARD BRICKED* and go through with that. and bam done. i got in a soft loop when i accidentally flashed a boot.img over a rom which made my phone unusable . i had to go through with the soft bricked option AND force flash, it was scary but dont worry man! any more questions ? feel free to PM me

TheSkillfulTroll said:
No need to fear, Theskillfultroll is here! :good:
To fix your issue, download NEXUS ROOT TOOLKIT by WugFresh, after doing so, you need to open it up and choose your correct device (DO NOT MAKE A MISTAKE HERE OR ELSE YOU CAN BE HARD BRICKED) if you have already unlocked the OEM, then good for you, but what i wanna focus here is on the main window, right hand side* there is a button labeled 'FLASH STOCK + UNROOT' depending on your situation , if you are soft bricked select so, if not click device on. if soft bricked it will tell you what to do, and vice versa on other option, AFTERWARDS, attempt to stock flash and unroot, now if it fails godforbid, you have to go to options and ENABLE FORCE FLASH *WARNING IF YOU DID NOT CHOOSE CORRECT DEVICE AND YOU PICK THIS, YOU WILL BE HARD BRICKED* and go through with that. and bam done. i got in a soft loop when i accidentally flashed a boot.img over a rom which made my phone unusable . i had to go through with the soft bricked option AND force flash, it was scary but dont worry man! any more questions ? feel free to PM me
Click to expand...
Click to collapse
wow. seems like a whole lot of work and worry, especially when compared to simply performing 2 wipes in recovery to solve this problem. no extra software required.
OP, stay away from toolkits.

xBeerdroiDx said:
wow. seems like a whole lot of work and worry, especially when compared to simply performing 2 wipes in recovery to solve this problem. no extra software required.
OP, stay away from toolkits.
Click to expand...
Click to collapse
Op said he doesn't want to wipe data and he doesn't have access to recovery (I think) saw your post about manual flashing though, pretty good
Sent from my Nexus 6 using XDA Free mobile app

ok, so i have this same problem. i have tried the "default_password" thing and the steps in post #4. after performing steps in post #4 everything worked great. but for some reason weeks later the problem has returned. is it possible i'm tripping or could the problem have returned? i know it seems highly unlikely but...
i have also been advised to redo the entire root process, is that a viable option as well?

sinceg1 said:
ok, so i have this same problem. i have tried the "default_password" thing and the steps in post #4. after performing steps in post #4 everything worked great. but for some reason weeks later the problem has returned. is it possible i'm tripping or could the problem have returned? i know it seems highly unlikely but...
i have also been advised to redo the entire root process, is that a viable option as well?
Click to expand...
Click to collapse
could be a twrp bug? are you on the latest version? you can try just updating the recovery, via fastboot or app(like flashify). if that doesnt work you can try wiping out the recovery partition(via fastboot) then reflashing the recovery.

yes i am on the current version via rashr app. i'm not sure how to wipe the recovery partition in fastboot....but it seems time i learn.
again, any thoughts to repeating the root process?

sinceg1 said:
yes i am on the current version via rashr app. i'm not sure how to wipe the recovery partition in fastboot....but it seems time i learn.
again, any thoughts to repeating the root process?
Click to expand...
Click to collapse
why? all that is is flashing supersu or removing it? that had nothing to do with your recovery. you dont need root to have a custom recovery.

ok, so it seems the next thing to try is wipe recovery partition then reflash recovery. i'll begin looking into how to do that. thank you again.

Had this problem last night, if you have a pattern password try using this:
1 2 3
4 5 6
7 8 9
I had an upper case L and it translated to 2589 and that's what unlocked it for me. Hope this helps someone

Ok, I was also asked for a password a couple of days ago for the first time ever, even though I had accessed TWRP several times before to flash roms, kernels etc so I don't think the reason was that I had forgotten to reboot after bootloader. In my case, I didn't even think of trying to enter any PWD so I selected "cancel" and from what I saw I thought my SD was wiped so I re-flashed stock from Bootloader and re-set the device, rather painfull (now I keep a nandroid backup). The thing is though, before I decided to flash stock I just tried exiting recovery and restarting the system and it wouldn't boot by any means. Just sat on the Google logo for ages heating up. And all this happened after a normal shutdown of the device, not after some fancy flashing/modding...

mclisme said:
Ok, I was also asked for a password a couple of days ago for the first time ever, even though I had accessed TWRP several times before to flash roms, kernels etc so I don't think the reason was that I had forgotten to reboot after bootloader. In my case, I didn't even think of trying to enter any PWD so I selected "cancel" and from what I saw I thought my SD was wiped so I re-flashed stock from Bootloader and re-set the device, rather painfull (now I keep a nandroid backup). The thing is though, before I decided to flash stock I just tried exiting recovery and restarting the system and it wouldn't boot by any means. Just sat on the Google logo for ages heating up. And all this happened after a normal shutdown of the device, not after some fancy flashing/modding...
Click to expand...
Click to collapse
Are you encrypted?

i was wondering if that made a matter. i didn't want to sound crazy mentioning it....yes, i am encrypted. do we believe that will make a matter?

sinceg1 said:
i was wondering if that made a matter. i didn't want to sound crazy mentioning it....yes, i am encrypted. do we believe that will make a matter?
Click to expand...
Click to collapse
Absolutely. If your storage is encrypted, TWRP cannot access it without you entering a password. If you don't enter the password, your storage would appear to be blank to recovery.
I personally prefer to wipe my entire device and keep a kernel that does not enforce encryption. Encryption (in my opinion) makes life difficult for rooted users.

seems to be the answer here. i have seen "how to's" on decrypting.... i will decrypt the device, will i have to do anything additional from that point? reflash recovery perhaps? sounds like it would be a good step, but i guess we won't know until i decrypt.

sinceg1 said:
seems to be the answer here. i have seen "how to's" on decrypting.... i will decrypt the device, will i have to do anything additional from that point? reflash recovery perhaps? sounds like it would be a good step, but i guess we won't know until i decrypt.
Click to expand...
Click to collapse
I'm new to the N6 so I am not sure about decrypting as a process. I just did a full wipe, flashed a kernel that doesnt force encryption .

Unable to mount /data, fastboot doesn't seem to be able to write

Hi everyone, I'm having a lot of problems with my phone: last night, after it dropped to 0% battery life, it wouldn't charge. So i waited a while and ifinally managed to turn it on, but It wouldn't go past the Cyanogenmod logo. So i tried few things,first wiping cache, then factory reset from TWRP and I even tried the "Factory" option in the fastboot screen. Nothing worked, and it even got worse I think, TWRP says it's unable to mount /data partition and /storage partition. I don't know what caused it, and i don't remember the precise moment it became "unmountable" for the first time (since I've been trying to fix this thing for like 24 hours now).
Since i couldn't fix it via recovery, I tried looking for people who had the same problem on the internet, and I tried everything i could find. (like this: http://forum.xda-developers.com/showthread.php?t=2683787).
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068

Are you able to pull logcat?

Logcat command works, i don't get errors in the terminal, but in the text file there's only this line : "/sbin/sh: exec: line 1: logcat: not found"
Dmesg works though, I don't know if it's helpful
"

dagrot said:
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Click to expand...
Click to collapse
I have same phone, you mentioned you also tried to flash stock rom without success, did you flash the partition file aswell before flashing system and the rest of files ? Check the flashfile.xml file into the stock firmware folder to make sure you not missing anything.
Code:
fastboot flash partition gpt.bin
Good luck.

i'm on the same boat. It seems it's a NAND issue, but how come it happens randomly?

It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app

Lynse said:
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Click to expand...
Click to collapse
If it's a bit rare, how come there are a rather interesting quantity of posts regarding that matter? I'd like to know WHY I can't write even with fastboot. There should be a way of unlocking the NAND / partitions. Even if I try to hard brick it, it's impossible.

PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.

jhonnyx said:
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
Click to expand...
Click to collapse
Unfortunately I didn't quite understand what that is about, if you happen to try it out let us know.
Anyway, if we don't manage to fix it, I guess I'm going to try and take it back to the store, since it is a common problem. Only problem is I'm on a custom rom and I can't even go back to stock and relock the bootloader, so I don't think they are going to replace it, but it's worth a try.

You can try by helping me to look for a circuit PDF from the board or trying it yourself.

I could try and disassemble it, but you're gonna have to wait a few days, I'm not at home and I'm gonna be back on the weekend.
As for the circuit pdf, I was only able to find videos and guides on how to disassemble it, unfortunately

Dude, no worries. Ive took the back out with all the screws, but I have nothng to make shorts with.... I'll come up with something. Take your time and keep me posted.

any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?

gbb14 said:
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
Click to expand...
Click to collapse
After that.... well.... after some research, we'll be needing singleimage.bin to use the blankflash utility for lollipop phones (mbm-ci 5.0 lollipop) so somebody can generate the singleimage.bin for us.
Once we have that, we can try to flash the phone at lowlevel to see what happens.

I will search the internets in hoping to find the schematics of this phone.
Keep me informed if you find it faster .
Cheers mate

we can connect through hangouts / etc.
look up for my user at gmail

[PLEASE HELP] Phone stuck on bootloop (tried everything I know)

Hello! My Galaxy note 5 (SM-920G) has been stuck on a boot loop for a week now, I've tried everything. I've used "wipe cache partition", "Wipe data/factory reset", even flashed stock firmware from sammobile using odin. I'm still stuck on a bootloop. I am gonna proceed to explain the events that occurred before and after the bootloop in a level of detail that I'm capable of, also one that I think should be sufficient.
Events before the bootloop:
So here's what happened. I was using my phone as usual when I noticed that I couldn't play any music. Spotify, which I was using at the time, refused to play any song. So, I checked out Phonograph(music app that uses local library) and I couldn't seem to play anything from my local library either. I then proceeded to go ahead and open YouTube only to realize that I couldn't play a video on YouTube either. After much fiddling (I don't remember what exactly I did that caused it) but a YouTube video played, but I heard no sound. From here on out, I could PLAY/VIEW any media related file and such but I heard no sound. I searched it up and apparently a cache partition wipe seemed to do the trick (I should have dug deeper into this but this is what I found). I proceeded to the recovery menu and selected "Wipe Cache Partition" (Forgive me, memories a little fuzzy from here on), If I recall correctly, I got into a bootloop and I wiped the cache partition again and it booted up fine. However, there was still no sound, since it was late at night I decided to give up and go ahead and sleep for now.
The next day, when I woke up, everything was working perfectly. I had no idea why.. but hey, I wasn't about to complain. Fast forward a few days, the sound issue popped up again, so I proceeded to wipe the cache partition again. I repeated this a few times but it didn't work, so I gave up. My phone was booting perfectly fine then. During the course of a week or so (maybe less) I had done quite a few cache partition wipes hoping that it would fix the sound issue. I also tried calling someone, only to figure out that person on the other end couldn't hear me and I couldn't hear them. So, one of these days when I did the whole cache partition wipe, my phone wouldn't boot up. This is where it got stuck in a bootloop.
Events before the bootloop:
So yeah, my phone was stuck in a bootloop. If I remember correctly I used the "cache partition wipe" a lot and even opted for the factory reset option. Which didn't work out either. I finally opted to flash stock rom today but over the course of some days I have been trying a combination of "cache partition" wipe and factory resets. Of course, my attempts were in vain. SO, I decided to flash stock rom today. I found the firmware I needed and used Odin to flash it on my phone and that didn't work either, still stuck on the bootloop. I tried a factory reset and cache wipe after the flash as well.
Relevant images:
1- Screen I'm stuck on
2- When I go to recovery mode, first screen that pops up.
3- The so called update fails, second screen that pops up
4- and finally the recovery menu pops up
So yeah, that's it. I'm currently in the midst of my A level's, so my days are pretty hectic and stressful. I apologize for the long post, first time making a thread on XDA. Please help ;-;

maskimmortalsucks said:
Hello! My Galaxy note 5 (SM-920G) has been stuck on a boot loop for a week now, I've tried everything. I've used "wipe cache partition", "Wipe data/factory reset", even flashed stock firmware from sammobile using odin. I'm still stuck on a bootloop. I am gonna proceed to explain the events that occurred before and after the bootloop in a level of detail that I'm capable of, also one that I think should be sufficient.
Events before the bootloop:
So here's what happened. I was using my phone as usual when I noticed that I couldn't play any music. Spotify, which I was using at the time, refused to play any song. So, I checked out Phonograph(music app that uses local library) and I couldn't seem to play anything from my local library either. I then proceeded to go ahead and open YouTube only to realize that I couldn't play a video on YouTube either. After much fiddling (I don't remember what exactly I did that caused it) but a YouTube video played, but I heard no sound. From here on out, I could PLAY/VIEW any media related file and such but I heard no sound. I searched it up and apparently a cache partition wipe seemed to do the trick (I should have dug deeper into this but this is what I found). I proceeded to the recovery menu and selected "Wipe Cache Partition" (Forgive me, memories a little fuzzy from here on), If I recall correctly, I got into a bootloop and I wiped the cache partition again and it booted up fine. However, there was still no sound, since it was late at night I decided to give up and go ahead and sleep for now.
The next day, when I woke up, everything was working perfectly. I had no idea why.. but hey, I wasn't about to complain. Fast forward a few days, the sound issue popped up again, so I proceeded to wipe the cache partition again. I repeated this a few times but it didn't work, so I gave up. My phone was booting perfectly fine then. During the course of a week or so (maybe less) I had done quite a few cache partition wipes hoping that it would fix the sound issue. I also tried calling someone, only to figure out that person on the other end couldn't hear me and I couldn't hear them. So, one of these days when I did the whole cache partition wipe, my phone wouldn't boot up. This is where it got stuck in a bootloop.
Events before the bootloop:
So yeah, my phone was stuck in a bootloop. If I remember correctly I used the "cache partition wipe" a lot and even opted for the factory reset option. Which didn't work out either. I finally opted to flash stock rom today but over the course of some days I have been trying a combination of "cache partition" wipe and factory resets. Of course, my attempts were in vain. SO, I decided to flash stock rom today. I found the firmware I needed and used Odin to flash it on my phone and that didn't work either, still stuck on the bootloop. I tried a factory reset and cache wipe after the flash as well.
Relevant images:
1- Screen I'm stuck on
2- When I go to recovery mode, first screen that pops up.
3- The so called update fails, second screen that pops up
4- and finally the recovery menu pops up
So yeah, that's it. I'm currently in the midst of my A level's, so my days are pretty hectic and stressful. I apologize for the long post, first time making a thread on XDA. Please help ;-;
Click to expand...
Click to collapse
Was that Lollipop or MM 6 that you were on? In Download mode what does it say on that screen? Is FRP enabled?
P.S what country are you in?

Before flashing in odin do the format in recovery.
Sent from my SM-N9208 using XDA-Developers mobile app

MrMike2182 said:
Was that Lollipop or MM 6 that you were on? In Download mode what does it say on that screen? Is FRP enabled?
P.S what country are you in?
Click to expand...
Click to collapse
I could have sworn I replied to this... I can't seem to post any links here. I pm-ed the images to you! Frp was on, yeah. I was on Marshmallow. I live in the Maldives.

maskimmortalsucks said:
I could have sworn I replied to this... I can't seem to post any links here. I pm-ed the images to you! Frp was on, yeah. I was on Marshmallow. I live in the Maldives.
Click to expand...
Click to collapse
I'm pretty sure I replied to your private message already. On the picture you showed me it said the CSC was SLK and I gave you the link to the correct firmware for the device
You can also download the firmware to flash through odin here too.
https://samsung-firmware.org/download/Galaxy Note 5/9hs6/INS/N920GDDS2BPD2/N920GODD2BPC3/
You can't post any links because you don't have enough "posts" on here yet to prove you're not just coming on here to post some crazy links lol.

MrMike2182 said:
I'm pretty sure I replied to your private message already. On the picture you showed me it said the CSC was SLK and I gave you the link to the correct firmware for the device
You can't post any links because you don't have enough "posts" on here yet to prove you're not just coming on here to post some crazy links lol.
Click to expand...
Click to collapse
Alright so, my cousin somehow managed to get rid of the bootloop with some fiddling and the audio issues still remained. So, he tried to downgrade to 5.1.1 by downloading the firmware for it and the phone got stuck in another bootloop. Tried to flash 6.0.1 again and it didn't work, still stuck on bootloop.
I tried what you have suggested but I can't seem to get into the recovery menu.

maskimmortalsucks said:
Alright so, my cousin somehow managed to get rid of the bootloop with some fiddling and the audio issues still remained. So, he tried to downgrade to 5.1.1 by downloading the firmware for it and the phone got stuck in another bootloop. Tried to flash 6.0.1 again and it didn't work, still stuck on bootloop.
I tried what you have suggested but I can't seem to get into the recovery menu.
Click to expand...
Click to collapse
Already replied to your private message.

Can you not select this directly after odin...

Flush twrp for yours model go to recovery then wape os and every think then flush firmware by odin
Sent from my SM-N920C using XDA-Developers mobile app

Question My Realme x7 max 5G stuck in recovery loop after uninstalling bloatare like glance, finshell pay, hot apps

like the title says I uninstalled the mentioned apps using adb and all of a sudden my camera stopped working so I decided for a simple restart and the device stuck in the loop ever since.
it restarts several times and open realme UI recovery and when I choose language it says " KINDLY REMINDER : system error, after select language, please select Online update(keep data) to recovery system, thanks! " .
So I did what the message said and I connect the wifi but instead of updating it says no updates found.
I also tried to wipe data but I got asked whether to retain contacts/media or format data.
I obviously tried the first one because I need the data but as expected it didn't work.
I am skeptical to clean format because I feel that I can still fix it with retaining the data.
I tried all the key combinations but only the realme UI recovery comes up . Please help me!
thank you

I don't think you'll be able to fix this without a full reflashing of the ROM using SP Tools and a format of the data partition from Recovery. You probably don't have access to full ADB now, if at all, and Fastboot won't help you recover anything. However, you should be able to rescue important files before you do this, as long as you have unlocked your bootloader.
Follow the steps here to install TWRP custom recovery. Once done, you can boot into it from fastboot by running `fastboot reboot recovery`. Once you're in TWRP, you can mount partitions so you can access them over USB from your PC.
Once you've got your important files transferred to your PC, take a full backup to be safe, then flash the stock ROM. This thread can help you do both of those things. Note that flashing the stock ROM using SP Tools will also restore the stock recovery. Once the process is done, boot right into fastboot and use it to reboot back into the stock recovery before letting it actually boot the ROM. Format your data partition (yes the whole thing). Now you can restart, and it should go through first time setup just fine.

I was going to uninstall these apps, but was too lazy. Guess lazyness is not too bad after all.

@Ricodey have you got the solution for this thing beacause i am also experiencing same issue

e_v_i_l_x_ said:
@Ricodey have you got the solution for this thing beacause i am also experiencing same issue
Click to expand...
Click to collapse
Unfortunately I had to go for the latter option of complete reset with the loss of data to get my device boot up . It seems the option to recover the device with data seems too complicated and not to mention the fact that this process is not without it's own risks. If you want an easy out from this issue I suggest that you complete format the device and have your important data backed up from now.
And Obviously I had data not backed up which I wanted on my device during this issue but it wasn't too important and I could let go of it cuz rest of my data was backed up.. but being the nerd I am, I tried to recover that data too.. but as I said it wasn't worth the time and risk for me so I chose the latter option.
Hope this helps! Do reply if you need further assistance !

Ricodey said:
Unfortunately I had to go for the latter option of complete reset with the loss of data to get my device boot up . It seems the option to recover the device with data seems too complicated and not to mention the fact that this process is not without it's own risks. If you want an easy out from this issue I suggest that you complete format the device and have your important data backed up from now.
And Obviously I had data not backed up which I wanted on my device during this issue but it wasn't too important and I could let go of it cuz rest of my data was backed up.. but being the nerd I am, I tried to recover that data too.. but as I said it wasn't worth the time and risk for me so I chose the latter option.
Hope this helps! Do reply if you need further assistance
Click to expand...
Click to collapse
for me the issue was like i just downgraded my device to the a.15 firmware after setting up i uninstalled the bloatware apps and some google apps which were not needed obviously and restarted my device and it got a bootloop, the issue of bootloop wasn't new to me i previoulsy had the same issue when i have downgraded to a.19 firmware. there is a simple fix, if you want to get rid of the bloatware apps now also you can use the disable command like.
(pm uninstall-user --user 0 ----package name---) this will not give any bootloop and can enjoy a part of RAM....
THIS WILL HELP
get in touch if need anything else

A715F stuck in bootloop. Can i fix it without losing data or at least recover it before a reset? (bootloader unlocked)

Hello! I apologize if the terminology won't be correct but i'm not very tech savvy and i'm learning while trying to fix this mess
I have this rooted Samsung A715F (no custom rom) given to me by my cousin some time ago (he can't help me).
The day before yesterday it started boot-looping out the blue and i initially wiped the cache partition without success then i tried to flash the last firmware with Odin after reading some guides here, uploading the HOME_CSC to not lose my data, I've some important pictures i would like not to lose (I know, not making a backup was stupid).
But the problem wasn't solved, the only difference is a new screen during the boot saying: "One ui error" and another "Can't load android system your data may be corrupted[...] where i can select Try again, factory data reset and recovery logs".
Luckily i still can access Download and Recovery mode but i don't really know what to do, i tried to download the firmware flash from other sources but nothing... and i'm pretty sure TWRP isn't installed.
Is there anything i can do before wiping data? Please, please help me

Of course no.
Hard reset and Davlik cache clean is required.

cmfCyangenModteam said:
Of course no.
Hard reset and Davlik cache clean is required.
Click to expand...
Click to collapse
Thank you for your answer! Sigh, i thought as much...
Could you please elaborate? I'm trying to learn

Fuelinme said:
Thank you for your answer! Sigh, i thought as much...
Could you please elaborate? I'm trying to learn
Click to expand...
Click to collapse
To enter recovery press power button and Volume - button, choose Reset function.