I have a Samsung S4 9505 mobile which is stuck in a bootloop.
In order to fix it I have installed a new firmware (Android 5 and 4.4) via ODIN but that does not change the boot loop.
USB debugging is not active on the device. I have wiped the cache several times. I do not want to make a factory reset because there is still some important data on it.
Is there a way to fix this or to rescue the data?
Thanks
Dusi
If the data is in the internal storage, install TWRP and use its file manager and try to recover it that way. It's odd that reinstalling the ROM via Odin didn't help, but regardless of that, a factory reset is likely in your future. If the data cannot be retrieved using the TWRP file manager, it's lost.
Many corporate IT security policies including mine at work are requiring that all devices used for work, i.e. BYOD, must be encrypted. I prefer my device to be rooted…and control my device to my liking. There’s a problem though… it’s not easy encrypting with root present. I set out on a mission to get it working.
There is very little information about encrypting Galaxy S6 devices (or any Galaxy for that matter) with root. I've tried numerous methods around the web and here on XDA but none worked with any of the current ROMs. I spent several days researching, investigating, and testing various methods before finding a solution that works.
Although not required, I started a fresh start—flashed the official Marshmallow stock ROM for my device (SM-G920i) and in the process wipe my device completely, including formatting the data partition and wiping the internal SD.
I previously had Lollipop installed with custom ROM. A nandroid was performed, ran TiBu then copied all the contents of the internal memory on my laptop prior to going to official stock. Can never be too careful.
The steps outlined below was tested on both ALEXIS ROM 5.0 and XtreStoLite 3.3.1 ROMs using the G920i unlocked variant. It may work on other international variants.
Flash stock Marshmallow ROM through Odin in ‘AP’ with AutoReboot and NAND Erase checked (from Odin v3.11.1 options)
Flash CF-AutoRoot via ODIN [let it auto-reboot when complete]
Flash TWRP 3.0.2-1 via ODIN [disable auto-reboot in ODIN options]
Reboot into TWRP recovery
Perform factory reset then format Data partition
Reboot TWRP recovery so that the Data partition is refreshed
Copy custom ROM and other flash files you’ll be using to /sdcard/ using ADB Push command. For example o adb push Rom.zip /sdcard/tools.
Flash custom ROM then reboot
Be patient—reboot will take about 5 minutes
Power off then boot into TWRP again to perform a factory reset and wipe Delvic cache
Reboot - wait patiently as boot will take several minutes
When the system finally boots up go through the first start wizard then go into setting to set up pin and fingerprints you wish to use
Encrypt phone -- this will take a while before it's complete. Be patient; the device will reboot several times, ask for password at boot-up then boot into the finally into the system.
The phone is now encrypted. Because we performed a factory reset, root and TWRP recovery were removed. We now have to flash CF-autoroot and TWRP recovery via Odin. Again, patience is required--it'll take about 5-10 minutes for the boot to complete.
Note that TWRP does not know how to decrypt Samsung encryption and therefore it can't read the /data/ partition. That partition will either have to be formatted before flashing a new ROM or removing encryption. Now I did not test removing the encryption, but I’d suggest that you have current backups of your device prior to performing that task.
I hope this helps anyone experiencing this issue.
Seems to me, that if they want the device encrypted, they would also prohibit root, it is a security risk.
So is there any chance to update an encrypted Rom via TWRP?
Good walkthrough.
I did also some research and i found on some other forums the opinion, that a full-disk-encryption on a rooted phone make not much sense,
where you can replace/install the custom recovery and decrpt the data with some adb commands? Is that true?
Confusing.
tefole said:
Good walkthrough.
I did also some research and i found on some other forums the opinion, that a full-disk-encryption on a rooted phone make not much sense,
where you can replace/install the custom recovery and decrpt the data with some adb commands? Is that true?
Confusing.
Click to expand...
Click to collapse
twrp do don't support samsung decryption, so encrypted data can be only deleted. but, if you enable reactivation lock, then, you can't flash in recovery, so stolen phone is like brick
BUT with custom rom (TyrannusRom and note 7 port) encrypted phone do not boot (boot loop), so there I finished my work with encryption
paulyz said:
twrp do don't support samsung decryption, so encrypted data can be only deleted. but, if you enable reactivation lock, then, you can't flash in recovery, so stolen phone is like brick
Click to expand...
Click to collapse
I see.
I believe, that i can live without the ability that TWRP doenst decrypt the /data and the /sdcard partition,
if I can run with a CFW, and if the phone is rooted and encrypted.
After i put the CFW on the phone, even I need TWRP anymore. Usually i try to dont change the CFW so frequently.
With reactivation look you mention the "OEM unlock" in the Android\developer settings I guess?
Is the flashing really locked, like brick, really? If you can't flash in recovery, but how to restore a stock firmware with odin? Isnt it the same?
I didnt get that
tefole said:
I see.
I believe, that i can live without the ability that TWRP doenst decrypt the /data and the /sdcard partition,
if I can run with a CFW, and if the phone is rooted and encrypted.
After i put the CFW on the phone, even I need TWRP anymore. Usually i try to dont change the CFW so frequently.
With reactivation look you mention the "OEM unlock" in the Android\developer settings I guess?
Is the flashing really locked, like brick, really? If you can't flash in recovery, but how to restore a stock firmware with odin? Isnt it the same?
I didnt get that
Click to expand...
Click to collapse
"Reactivation lock lets you use your Samsung account to prevent others from activating your device if it's ever lost or stolen. With Reactivation lock turned on, you will be required to enter your Samsung account credentials prior to performing a factory reset on the device. Your Samsung account login should be something you can easily remember."
when RL activated, you can't flash, you always get error.
One big problem, what after encryption you can't update ROM, change or update kernel and etc.
I see., thx for the infos.
I did some research as well. With activated RL you can go only in download mode and install stock with Odin.
But the phone is going to ask you for your samsung account credentials - anyway.
tefole said:
I see., thx for the infos.
I did some research as well. With activated RL you can go only in download mode and install stock with Odin.
But the phone is going to ask you for your samsung account credentials - anyway.
Click to expand...
Click to collapse
if you will find useful information, post, because, I very interested too, just do not have a lot time to play with this.
So the little idiot of me tried changing the build.prop file which is only editable with root. My device is ofcourse, rooted. So after editing only the model number and restarting the phone, it's stuck on device name logo. Anyone know how to revert this? How can I fix this if I can't even boot into the phone.
Just flash the stock ROM via Odin.
Stock ROM at SamMobile and Odin at this post
I just did that. At first I was afraid of losing all my data on sdcard, but after reflashing the stock rom all my data was intact, including my apps. Thanks for the help!
Your data was intact because you didn't make wipe
Hey y'all.
Long story short on points:
More than a year ago I bought the SM-N935F on Android 7 and rooted it with this guide
After that, I transferred all my applications with Titanium backup to it, which I have already done two times (Note 1->3->4->FE)
... everything was fine ...
Two weeks ago, after pressing the 'Reboot' in *#0808#-menu, I received the message 'Custom binary blocked by FRP Lock' without the ability to log into TWRP
I flashed the stock firmware of the same version that I had (N935FXXS2ARA1) using Odin to fix it (AP + BL + CP + HOME_CSC)
... after that I did not lose any application data or settings, but lost root ...
After 7 days of waiting for RMM, I reflashed TWRP and received the message 'Failed to mount /data', because I did not want to format /data partition
Questions:
Why after rebooting from *#8080#-menu has FRP-lock turned on?
Why the unencrypted /data partition after installing the stock firmware has become encrypted without losing any data - does the stock firmware encrypt the partition after flashing?
If the answer to the previous question is 'yes', was there any way to prevent this (another way to bypass the FRP-lock)?
And the most important question: Is there any way now for me to get root without losing application data (or save this data before formatting /data partition and then recover it)?
Thank you very much for help!
flash moded twrp with encryption support and you'll be able to restore your data.
I use this for S7 Edge. Not sure if it's compatible for FE or not.
As I understand, it's not about encryption, it's about "quota support in oreo update for the /data partition". And I'm on nougat.
Why the unencrypted /data partition after installing the stock firmware has become encrypted without losing any data - does the stock firmware encrypt the partition after flashing?
Click to expand...
Click to collapse
Could you answer this question please.
Sprint Note 4, completely unmodified, stock everything. 4.4.4 I'm pretty sure.
I've been out of the loop for a long time, is it at all possible to install TWRP or use AROMA file manager without wiping any of the data from my phone? I've forgotten my password and the main goal of unlocking the phone is to back up the data so a factory reset or anything that deletes data is completely out of the question.
flashing twrp will not delete anything
do your homework and READ about twrp and related stuff - there's a lot of info on the sprint forum, very helpful
you will be ultimately more aware and responsible about what you can do with your phone
https://forum.xda-developers.com/note-4-sprint/help/installing-twrp-t3381073