Database Users

[Q] Wifi Won't Turn On, System Files Won't Open, Root Access Gone? Send Help.

Just today, my rooted Galaxy S4 was working perfectly. At about 9 AM I downloaded Liveboot (same person who made SuperSU) After downloading and configuring it, I restarted my phone and it worked. Until... after I tried to turn my wifi on. This is where my problems started. I can't start my wifi... it just turns light yellow forever with the menu forever saying "Wifi turning on." I tried to reopen liveboot, to it forever displaying a "loading screen" for which I soon figured out why. In my root explorer, MANY system files are unopenable, stating they were last modified in 1970, some in 1969. This has caused it so all of my root access is gone. It's on the phone but the apps can't access it because the files can't be opened. They display no error message, when I try to open them nothing happens.
I have tried:
Taking battery out
Hard reboot
Restart
Deleting a wifi file in the data folder but I can't open the data folders
Reinstalling root
I do not want to do a factory reset as I believe it will not fix it as others with the wifi problem have said.
TL;DR I downloaded a boot app, wifi is broken and files are too.
I have never flashed and I'm unsure how to do it, I'm quite tech savvy but I'm afraid to ruin my phone.

Update, I factory reset my phone.
Didn't do anything other than clear my root so I could "possibly" get a new phone from the warranty that expires in 2 and a half months. Does anyone know how to fix the wifi issue?

Anyone have a fix? I'm probably going to use my warranty but It would be great to fix it to saver time
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app

Are you just rooted or do you have safestrap or a custom recovery installed?
You might have to odin back to stock to get everything working again.

I would say Odin to stock and start from scratch. If your safe strapped or a m variant you get slightly different issues or problems.
If you warranty it you'll probably be safe strapped.

TrawL said:
Just today, my rooted Galaxy S4 was working perfectly. At about 9 AM I downloaded Liveboot (same person who made SuperSU) After downloading and configuring it, I restarted my phone and it worked. Until... after I tried to turn my wifi on. This is where my problems started. I can't start my wifi... it just turns light yellow forever with the menu forever saying "Wifi turning on." I tried to reopen liveboot, to it forever displaying a "loading screen" for which I soon figured out why. In my root explorer, MANY system files are unopenable, stating they were last modified in 1970, some in 1969. This has caused it so all of my root access is gone. It's on the phone but the apps can't access it because the files can't be opened. They display no error message, when I try to open them nothing happens.
I have tried:
Taking battery out
Hard reboot
Restart
Deleting a wifi file in the data folder but I can't open the data folders
Reinstalling root
I do not want to do a factory reset as I believe it will not fix it as others with the wifi problem have said.
TL;DR I downloaded a boot app, wifi is broken and files are too.
I have never flashed and I'm unsure how to do it, I'm quite tech savvy but I'm afraid to ruin my phone.
Click to expand...
Click to collapse
If you were running a Google Edition ROM, you need to do a soft reboot or hot reboot to get WiFi working. I know sometimes I have issues with the flashable SuperSU, so if you're not getting root prompts, try just reinstalling it from the market. And check your time and date settings to make sure they're set to network or at least manually set them. I've had all those happen after my phone does a hard shutdown, but if none of those work then flashing stock and reinstalling is your best bet.

Could you send me a tutorial to flash with Odin? I've never done it before. If it requires root I literally can't root my phone because the root "files" are in the corrupted folders that can't be opened, which is what's happening with the wifi.
Edit: never mind I found a good tutorial. I'll do it when I get home.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app

TrawL said:
Could you send me a tutorial to flash with Odin? I've never done it before. If it requires root I literally can't root my phone because the root "files" are in the corrupted folders that can't be opened, which is what's happening with the wifi.
Edit: never mind I found a good tutorial. I'll do it when I get home.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
Update. I had time to flash my phone and completely reinstall my OS. My binary is completely reset now, and my boot screen no longer says "Custom" anymore. Completely stock. No root. I can return it for a warrenty.
http://www.androidrootz.com/2014/03/how-to-unrootunbrick-at-galaxy-s4-sgh.html
(Just in case anyone needed it, I haven't seen many people with this problem and would hopefully like to help anyone who does to get a new phone)
After all this hassle...
My wifi still doesn't work. The only upside is I can return my phone without worry.
Doing this has set me phone to version 4.3 instead of 4.4.2, but now when I try to turn my phones wifi on, it says this:
Security information
The device has detected an application attempting to perform actions that are not permitted. These actions have been blocked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Upon clicking this, it opens a small window displaying the following
Security information
The device has detected an application attempting to perform actions that are not permitted. These actions have been blocked. It is recommended that you restart your device.
Reboot now, Reboot Later
After this, I went into my settings and screwed around with the "Security" settings for a tiny bit before giving up, then going into recovery mode and clearing the cache, just in case.
I think it's time for a warrenty if nobody can help.

I don't really know if I'm much help, but I can confirm that I was on hyperdrive rom rl20 and so far I've run into a whack of issues... let me explain.
First off I'm a Koodo client, and I have the sgh-i337m Rooted with cf-autoroot and twrp installed because bootload is unlocked.
I was running hyperdrive rl20, and my wifi wouldn't work and neither would my service, after extensive reading I concluded the only way to make this rom work was to download the modules package for at&t listed in one of the hyperdrive forums, now I've done so and everything ran great except the missing features that the rom offered but not available on the device itself because hardware didn't permit it. So my wifi and network issues were solved.
Since then the L update for Koodo had been released, and i flashed back to stock to my dismay, my wifi didn't work back with the stock rom now, I'm convinced the module flash had something to do with it. I'm not that savvy when it comes to figuring out what modules are, I've tried to unzip the modules package I've downloaded and since I'm unaware of what blocks are mounted where I don't know what part of the packages need to be flashed separately. I've wipe the device 3x in one recovery session, I mean everything besides the OTG (nothing connected) and the external SD. I then rebooted and wiped everything rebooted wiped everything and rebooted and wiped everything and rebooted and then installed the update with Samsung Switch because Kies and Kies3 wouldn't work for device recovery. I fist went to 4.4.2 released the same day as the L update, and then flashed again just to make sure, then I did the update not OTA but I put the device back in recovery mode and flashed again with Samsung Switch to the 5.x.x update, now I have service but the wifi still no working. I'm starting to lose my mind. All was well before I flashed the modules for AT&T in that thread. If I somehow new how to extract the modules or what modules were needed maybe I could be more of assistance.
But right now I'm up that creek, resembles brown stuff that comes when your stomach doesn't feel to well, and with out a paddle.
I can't return mine for warranty I don't think because my knox bit is triggered. I don't know what I'm going to do. But there has to be a fix. I refuse to believe that a module flash screwed my phone up and I can't flash back to whatever the issues was or flash over to fix it. I just refuse, so help me Odin and Thor I will summon the furry of so many Norse gods, the grounds will shake and unleash a force like no other. lol ... Sorry it's like 5am where I am and I'm watching the last episode of Vikings

The wifi on my s4 kept dieing I fixed it by reflashing the kernel and the radio modules. What kernel are you on? (under settings->about)

autonomousperson said:
The wifi on my s4 kept dieing I fixed it by reflashing the kernel and the radio modules. What kernel are you on? (under settings->about)
Click to expand...
Click to collapse
I fixed it with the help of another gentlemen that posted the oc3 modules stripped from the new L rom. He explained to me how to rip the modules out of a rom and I did out of the rom I was running before HyperDrive RL20 and I just flashed those modules back and viola .... I was able to flash right up to 5.0.1 ... thats what I'm running now with out any issues accept obviously I lost root, so thats what I'm in the process of doing now probably just CF-AutoRoot because I could careless about knox trigger at this point the phones out of warranty anyway, I usually wait until about 9 to 10 months in to purchase of the phone and then kind of stop caring about it and get a new one while warranty still applicable. So I'm on my new one. Thanks for the help anyway.
crocowboy.
"there are two types of bikers, those that have crashed, and those that will crash."

S4 Carrier Reset (Stock ROM not working)

Hello. There have been a lot of problems with my S4 and it looks like now it might be useless. I need to try a carrier reset, but I can't get a sense rom to work.
I'm using Freedompop (which is horrible, but I can't find a permanent job). It uses Sprint's network. When I got the phone, it was "refurbished" with a burned-in screen. Other than that, it worked. After three or so days, it downloaded an update that was supposed to fix Stagefright vulnerability. I checked it out and it looked legitimate, but I still didn't install it. Two or three days later, I saw that it was installing itself. When it rebooted, it got screen hang. It wouldn't do anything. I rebooted it a few more times, but it was still not working. The phone had TeamWin Recovery Project installed, so I selected the options to try to repair it and I ended up wiping the OS and installing OctOS. The phone worked after that. OctOS had some issues with crashing Trebuchet, but it worked.
Freedompop claims to give 500 MB of data free and claims that their messaging app does not count against it. Well, they don't and it does. I got to 422 MB and they cut me off because I made it past 422 MB. I checked my phone data usage and it added up including the Messaging app data usage. I called Freedompop and the representative told me right away that the data had an early cap and he was going to restore my service. All I had to do is not use the "browser" (data). I never got that data back. The billing cycle passed and I didn't get my service reset. I called again and the rep was messing with me until I finally got her to stop. When she did, she said that the service was fine on their end and it's probably my phone. I didn't believe her because she was messing with me and I called again. The next rep told me that he reset the service too and that because it didn't work when the first one did it, I should try a carrier reset from the phone. I didn't see the option so I called another day and I eventually got an MSL code. The problem with that is that it doesn't work without a sense rom.
I decided to install a sense rom to use the MSL code, but they wouldn't install. When I finally got one to install, the screen was hanging again. I think somehow the part of the sense rom bootloader got damaged and I don't know what it is or how to fix it. I reinstalled OctOS again and I've just been using it through Wi-Fi for now, but I need to be able to fix carrier reset problems so I can switch carriers and keep the phone once I get a job.
The short story:
I need to do a carrier reset through custom OS or install a sense rom that doesn't hang but the Samsung Galaxy S4 has sense rom hanging issues. I have TeamWin Recovery Project installed on the phone. It came in that way.
Please help. Thank you.

newmask said:
Hello. There have been a lot of problems with my S4 and it looks like now it might be useless. I need to try a carrier reset, but I can't get a sense rom to work.
I'm using Freedompop (which is horrible, but I can't find a permanent job). It uses Sprint's network. When I got the phone, it was "refurbished" with a burned-in screen. Other than that, it worked. After three or so days, it downloaded an update that was supposed to fix Stagefright vulnerability. I checked it out and it looked legitimate, but I still didn't install it. Two or three days later, I saw that it was installing itself. When it rebooted, it got screen hang. It wouldn't do anything. I rebooted it a few more times, but it was still not working. The phone had TeamWin Recovery Project installed, so I selected the options to try to repair it and I ended up wiping the OS and installing OctOS. The phone worked after that. OctOS had some issues with crashing Trebuchet, but it worked.
Freedompop claims to give 500 MB of data free and claims that their messaging app does not count against it. Well, they don't and it does. I got to 422 MB and they cut me off because I made it past 422 MB. I checked my phone data usage and it added up including the Messaging app data usage. I called Freedompop and the representative told me right away that the data had an early cap and he was going to restore my service. All I had to do is not use the "browser" (data). I never got that data back. The billing cycle passed and I didn't get my service reset. I called again and the rep was messing with me until I finally got her to stop. When she did, she said that the service was fine on their end and it's probably my phone. I didn't believe her because she was messing with me and I called again. The next rep told me that he reset the service too and that because it didn't work when the first one did it, I should try a carrier reset from the phone. I didn't see the option so I called another day and I eventually got an MSL code. The problem with that is that it doesn't work without a sense rom.
I decided to install a sense rom to use the MSL code, but they wouldn't install. When I finally got one to install, the screen was hanging again. I think somehow the part of the sense rom bootloader got damaged and I don't know what it is or how to fix it. I reinstalled OctOS again and I've just been using it through Wi-Fi for now, but I need to be able to fix carrier reset problems so I can switch carriers and keep the phone once I get a job.
The short story:
I need to do a carrier reset through custom OS or install a sense rom that doesn't hang but the Samsung Galaxy S4 has sense rom hanging issues. I have TeamWin Recovery Project installed on the phone. It came in that way.
Please help. Thank you.
Click to expand...
Click to collapse
1. Touchwiz ROM is what you need, Sense is on HTC phones.
2. Have you tried wiping the internal SD? Using Odin to install a stock ROM from www.sammobile.com?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bilgerryan said:
1. Touchwiz ROM is what you need, Sense is on HTC phones.
2. Have you tried wiping the internal SD? Using Odin to install a stock ROM from
Click to expand...
Click to collapse
Ah, OK. I've wiped the internal SD and, after that, some of the roms had trouble installing. I had to wipe the phone a few times just to get one installation. I tried to use Odin the first time I got the screen hang and it read the phone. After the carrier problem, I tried it again and it wouldn't read it anymore. I've tried it with the stock OS, OctOS, and cyanogenmod and also no OS and it didn't read it at any time after my data got cut off. I only got one of the stock OS that I downloaded to actually install. I made sure they were all the Sprint ones, but just that one worked.

newmask said:
Ah, OK. I've wiped the internal SD and, after that, some of the roms had trouble installing. I had to wipe the phone a few times just to get one installation. I tried to use Odin the first time I got the screen hang and it read the phone. After the carrier problem, I tried it again and it wouldn't read it anymore. I've tried it with the stock OS, OctOS, and cyanogenmod and also no OS and it didn't read it at any time after my data got cut off. I only got one of the stock OS that I downloaded to actually install. I made sure they were all the Sprint ones, but just that one worked.
Click to expand...
Click to collapse
At that point you dial ##72786# in the Phone app and that does the carrier reset, but that's only on the stock ROM.

bilgerryan said:
At that point you dial ##72786# in the Phone app and that does the carrier reset, but that's only on the stock ROM.
Click to expand...
Click to collapse
That's the problem. The phone doesn't seem to get stock ROMs to work anymore. I've gotten one to install, but it hangs which was the initial phone problem and why I switched to OctOS. I need to either be able to get a ROM that will get past the bootloading screen or a way to do carrier resets with custom ROMS.

newmask said:
That's the problem. The phone doesn't seem to get stock ROMs to work anymore. I've gotten one to install, but it hangs which was the initial phone problem and why I switched to OctOS. I need to either be able to get a ROM that will get past the bootloading screen or a way to do carrier resets with custom ROMS.
Click to expand...
Click to collapse
When you say it hangs, how long to you wait? It can take up to 20 minutes for the initial boot
Sent from my SPH-A120

bilgerryan said:
At that point you dial ##72786# in the Phone app and that does the carrier reset, but that's only on the stock ROM.
Click to expand...
Click to collapse
mattzeller said:
When you say it hangs, how long to you wait? It can take up to 20 minutes for the initial boot
Sent from my SPH-A120
Click to expand...
Click to collapse
I've left it running for a few hours a few times mostly because I was waiting for about an hour and I just got tired and forgot.

What is your baseband in settings/about device? Make sure you aren't trying to Odin am older version than the last one you were on.

bilgerryan said:
What is your baseband in settings/about device? Make sure you aren't trying to Odin am older version than the last one you were on.
Click to expand...
Click to collapse
L720VPUGOD2. The version should be the same. I didn't update anything on top of installing the ROMs. It worked when I when I ran Odin after the first OctOS 5.1.1 installation.

newmask said:
L720VPUGOD2. The version should be the same. I didn't update anything on top of installing the ROMs. It worked when I when I ran Odin after the first OctOS 5.1.1 installation.
Click to expand...
Click to collapse
just trying to eliminate any possibilities for what's causing the problem.

I know. I think the screen hang problem is connected to the main cause of everything, but I have no idea what it is. I could try out some more ROMs for Lollipop. Where can I find some that can use codes like factory stock ROMs?

newmask said:
I know. I think the screen hang problem is connected to the main cause of everything, but I have no idea what it is. I could try out some more ROMs for Lollipop. Where can I find some that can use codes like factory stock ROMs?
Click to expand...
Click to collapse
Android Development section

I tried to install Triforce ROM and I stumbled across this when it didn't work: http://forum.xda-developers.com/showpost.php?p=43683835&postcount=1204
Apparently, that could have fixed the screen hang problem back when my phone was being read by Odin. This stings. If I can get the phone to be read, I could check this out, but I'm stuck again.

newmask said:
I tried to install Triforce ROM and I stumbled across this when it didn't work: http://forum.xda-developers.com/showpost.php?p=43683835&postcount=1204
Apparently, that could have fixed the screen hang problem back when my phone was being read by Odin. This stings. If I can get the phone to be read, I could check this out, but I'm stuck again.
Click to expand...
Click to collapse
That is a very old ROM and the fix most likely won't work either. Try flashing something more recent like Wicked X.

bilgerryan said:
That is a very old ROM and the fix most likely won't work either. Try flashing something more recent like Wicked X.
Click to expand...
Click to collapse
TriForce worked for the carrier reset. It just looks tacky and Wi-Fi doesn't work on it. I want to fix the bootloader issue so I can get to a stock ROM.
Wicked X didn't do the carrier reset. It reset itself instead and booted to TWRP.
I installed Wicked X after TriForce, so I'm going to re-install TriForce, do the carrier reset, and see if it carries over to OctOS.

[DISCUSSION] Is unencrypted really faster in real-world usage?

UPDATE:
I was able to get 2 units side-by-side again. This time both of them were encrypted. The difference was one was running the original MDA89E OS and the other was running the latest MTC19V OS.
I just did 1 simple test, I created a 238.5MB zip file of my Titanium backup directory.
On MDA89E (user partition encrypted) it took 6:39
On MTC19V (user partition encrypted) it took 1:01
This result along with the previous results that found virtually no difference between decrypted and encrypted on MHC19Q leads me to the conclusion that decrypting probably did see a performance boost on the original MDA89E software all the way up to probably MMB29V but from MHC19J onwards, up to at least MTC19V, there is virtually no real-world (rather than benchmark) difference between decrypted and encrypted.
I didn't have time to do more detailed testing on this phone as it needed to be returned.
----
So I have 2 5x's side-by-side running MHC19Q. Exact same software loaded, exact same system settings.
One has encrypted userdata. The other has decrypted userdata. Both have dm-verity (integrity checking for /system and /vendor) disabled.
I compare boot times and they are the same.
Then I compare taking 3 HDR+ camera shots and the speed is the same and the processing of HDR completes at the same time.
I start browsers on both and they come back the same time.
I tried starting Riptide GP2, Cut The Rope, and a offline GPS program I use. The games started maybe 0.25 seconds faster on the unencrypted phone. The GPS started the same.
I was surprised at how little difference, so I rebooted to make sure nothing was cached, and retried. Same results.
As an aside, I also compared boot times with bootloader locked stock encrypted with dm-verity enabled to decrypted with dm-verity disabled. Decrypted with dm-verity disabled might be 1 or 2 seconds faster for start up, but you get a 5 second delay with the Orange bootloader warning screen.
So I'm wondering what else to test to show off how fast decrypted userdata is? If there is a noticeable benefit on something I use often I'd probably end up keeping the userdata unencrypted.
I'm not interested in artificial benchmarks showing throughput.
For the record, I haven't experienced any lagginess on any of the configurations, encrypted or not, for my own usage patterns, even on the original MDA89E.
The camera is definitely faster to start up on MHC19Q over the one in MDA89E but only by about 0.5 second.
Standby battery time is the same whether encrypted or not. That is really dominated by whether you have wifi turned on all time (either on purpose or through android bug) or going to sleep and whether you have strong or weak cell signal.

From my personal experience.
I ran my N5X unencrypted for couple of months and then decided to encrypt to see if I experience a noticeable difference.
I didn't experience any noticeable difference so I decided to keep it encrypted and still have it this way. I think it's not worth it to bother with disabling forced encryption during every firmware update, especially when running stock kernel.

Pretty much same as everyone else i have talked to and my personal experience isn't any different.
One other test I am interested in, restoring a back up of stock rom. My 5X seems way slower restoring a back up in twrp latest than my n6 or 6P, anyone else have the same experience resorting back ups.
Or do sfhub can you run the test?
Thanks for the post!
Sent from my Nexus 5X using XDA-Developers mobile app

razrlover said:
One other test I am interested in, restoring a back up of stock rom. My 5X seems way slower restoring a back up in twrp latest than my n6 or 6P, anyone else have the same experience resorting back ups.
Or do sfhub can you run the test?
Click to expand...
Click to collapse
I don't have the side-by-side units anymore, but I'm guessing at the linux level if I did copied the system partition image to the data partition using dd I would notice a difference.
At the Android level I'm thinking the "extra" stuff Android is doing causes it to not be able to reach the full potential of the storage (even at the half speed the encryption has supposedly limited the storage to)
Kind of like putting a 550MB/sec SSD on an old computer with SATA2. It can probably only do 150MB/sec over the SATA2 (vs SATA3) interface, so even if you drop the SSD rate in half to 225MB/sec, while that looks bad on benchmarks, your old PC doesn't care because it can barely handle 150MB/sec.
I didn't do tests to prove this, so it is just a theory, but I did do some side-by-side comparisons listed above and I really can't effectively tell any difference between encrypted and decrypted userdata (for my usage)
I'm guessing the nandroid backups from TWRP would see some difference, but I don't do those often as the images are just getting larger and larger these days.

As an update, I left the unit unencrypted for about a month, but recently I discovered 2 downsides, which while minor, pushed me over the edge to re-encrypt the user partition.
With user partition un-encrypted (only tested MHC19J through MTC19T)
1) visual voice mail tab disappears from phone application if you reboot in airplane mode (this is on Project Fi)
2) USB OTG flash drive reader takes 2 inserts to recognize micro-sd card
These both have to do with delayed recognition of attached devices when user partition is decrypted. In the first case, upon reboot while in Airplane mode the SIM card is not detected, instead it says "No SIM card". When you have encrypted user, it detects the SIM card and says "No service"
For the second case, it detects the USB flash card reader, but not the microsd card in the reader. Upon second insert, it detects both. When user partition is encrypted, it detects both immediately.
These are detailed here:
http://forum.xda-developers.com/nexus-5x/general/resolved-visual-voice-mail-disappearing-t3391434
Also in re-encrypting the user partition I found it didn't work through Android "Settings" for my setup.
I have systemless root and TWRP 3.0.2-0. When you choose to Encrypt phone using Settings, it proceeds to reboot, but then gets stuck at the animation forever. I left it like that overnight.
I then held the Power button to reboot, expecting everything to be corrupted with a half way encryption, but to my surprise, the phone booted with no issues and the Settings still said it was un-encrypted.
I then went back and flashed stock boot and recovery, and rebooted the phone, allowing the standard "first boot" encryption to run. It took around 10 minutes, but everything encrypted fine with no data loss (I had around 15GB on the phone at the time, all backed up of course)

sfhub said:
I'm not interested in artificial benchmarks showing throughput.
Click to expand...
Click to collapse
When the difference is small you won't notice in daily activities, unless in a particular condition, one day, on one app that requires to process lot of data (reading/writing from disk) you will notice that it take some time if you have encryption. That's why the use of benchamark, they give you an indication of who is definetely faster (in many conditions faster just for 1 millisecond, sometimes faster than some seconds/minutes)!
You should test apps that write read / write lot of data, maybe like measure a heavy game start up, or measure an app that write for example mp3 tags in bulk mode to all mp3 of a huge album, etc.

sfhub said:
So I have 2 5x's side-by-side running MHC19Q. Exact same software loaded, exact same system settings.
One has encrypted userdata. The other has decrypted userdata. Both have dm-verity (integrity checking for /system and /vendor) disabled.
I compare boot times and they are the same.
Then I compare taking 3 HDR+ camera shots and the speed is the same and the processing of HDR completes at the same time.
I start browsers on both and they come back the same time.
I tried starting Riptide GP2, Cut The Rope, and a offline GPS program I use. The games started maybe 0.25 seconds faster on the unencrypted phone. The GPS started the same.
I was surprised at how little difference, so I rebooted to make sure nothing was cached, and retried. Same results.
As an aside, I also compared boot times with bootloader locked stock encrypted with dm-verity enabled to decrypted with dm-verity disabled. Decrypted with dm-verity disabled might be 1 or 2 seconds faster for start up, but you get a 5 second delay with the Orange bootloader warning screen.
So I'm wondering what else to test to show off how fast decrypted userdata is? If there is a noticeable benefit on something I use often I'd probably end up keeping the userdata unencrypted.
I'm not interested in artificial benchmarks showing throughput.
For the record, I haven't experienced any lagginess on any of the configurations, encrypted or not, for my own usage patterns, even on the original MDA89E.
The camera is definitely faster to start up on MHC19Q over the one in MDA89E but only by about 0.5 second.
Standby battery time is the same whether encrypted or not. That is really dominated by whether you have wifi turned on all time (either on purpose or through android bug) or going to sleep and whether you have strong or weak cell signal.
Click to expand...
Click to collapse
Right on, it has no real-world difference similar to modifying the kernel, just a PITA to go back and forth every time there is a new release.

this discussion is making me consider encrypting my data partition again via the security->encrypt phone menu.
if i backed up my current system via TWRP to external storage prior to encryption, would i be able to restore it on top of the encryption?

Damn it! I decrypted but today I flashed PA rom and it got encrypted again
Do I need to format data always when flashing??
When I had decrypted, I didn't notice better battery. But maybe a slightly fastness improvement. Or maybe placebo. But I don't mind losing encryption
Sent from my Nexus 5X using Tapatalk

andQlimax said:
When the difference is small you won't notice in daily activities, unless in a particular condition, one day, on one app that requires to process lot of data (reading/writing from disk) you will notice that it take some time if you have encryption. That's why the use of benchamark, they give you an indication of who is definetely faster (in many conditions faster just for 1 millisecond, sometimes faster than some seconds/minutes)!
You should test apps that write read / write lot of data, maybe like measure a heavy game start up, or measure an app that write for example mp3 tags in bulk mode to all mp3 of a huge album, etc.
Click to expand...
Click to collapse
As I mentioned, I understand benchmark differences. I only care about differences I will notice in everyday use. I don't really care about running un-encrypted so that a benchmark runs fast or something somebody else uses, but I never, or almost never, use will run slightly faster.
For what I do use, I tested offline GPS apps which load lots of data. I tested Riptide GP2 which loads a decent amount of data. Basically everything I tested from within Android had so little difference (if any) that it wasn't noticeable. I am talking .25 second at most.
You probably will notice if you write to a file directly using dd, for example if you are doing image backup of system, but I really don't do this stuff daily. I might do it only once when I first get the phone to preserve the factory images.
Anyway, since the difference was so tiny and I noticed a separate problem of my visual voicemail tab disappearing on reboot related to encrypted user partition, I re-encrypted. The test I care about is if I am grumbling everyday about how slow things are and really I noticed zero difference.
I don't have anything against un-encrypted user as I ran that way for a month. I just really saw no benefit.
As a bonus my USB OTG flash reader gets recognized right away instead of requiring 2 inserts.
There is no way this encrypted vs un-encrypted setup is causing the huge slowdowns some people are experiencing. That is caused by something different, probably EMMC getting close to full or some Android bug.

2x4 said:
this discussion is making me consider encrypting my data partition again via the security->encrypt phone menu.
if i backed up my current system via TWRP to external storage prior to encryption, would i be able to restore it on top of the encryption?
Click to expand...
Click to collapse
Encrypt from Settings->Security won't work with TWRP and rooted boot.img. At least it didn't with MTC19T. I don't know if the problem is TWRP or boot.img but on the reboot after the Encryption plugin your phone warning/prompt the thing just hangs on the boot animation forever (I left it all night).
I ended up flashing stock boot.img and recovery.img, then letting the encrypt on first use routine go through. It took around 10-15 minutes. Then I flashed TWRP and supersu again. This is the only way I was able to re-encrypt and preserve my data.

sfhub said:
Encrypt from Settings->Security won't work with TWRP and rooted boot.img. At least it didn't with MTC19T. I don't know if the problem is TWRP or boot.img but on the reboot after the Encryption plugin your phone warning/prompt the thing just hangs on the boot animation forever (I left it all night).
I ended up flashing stock boot.img and recovery.img, then letting the encrypt on first use routine go through. It took around 10-15 minutes. Then I flashed TWRP and supersu again. This is the only way I was able to re-encrypt and preserve my data.
Click to expand...
Click to collapse
hmm wait, so there's no way to re-encrypt if you've already decrypted and you're using a custom rom?

Javi22 said:
Damn it! I decrypted but today I flashed PA rom and it got encrypted again
Do I need to format data always when flashing??
When I had decrypted, I didn't notice better battery. But maybe a slightly fastness improvement. Or maybe placebo. But I don't mind losing encryption
Click to expand...
Click to collapse
If the kernel you flashed has forceencrypt in the mount tables, it will encrypt upon first boot.
I was able to preserve unencrypted through various flashes by following this routine.
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery twrp.img
[(re)boot into recovery from bootloader]
install SuperSU.zip
The key is never let an unknown status boot.img, where you aren't sure of the encryption status, boot on your phone.
If you always install SuperSU (even if not necessary) after flashing unknown status boot.img, then it will always patch the boot.img to remove forceencrypt and you'll never get re-encrypted.
You could replace any of the steps above with equivalent pre-patched kernels, etc.

sfhub said:
If the kernel you flashed has forceencrypt in the mount tables, it will encrypt upon first boot.
I was able to preserve unencrypted through various flashes by following this routine.
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery twrp.img
[(re)boot into recovery from bootloader]
install SuperSU.zip
The key is never let an unknown status boot.img, where you aren't sure of the encryption status, boot on your phone.
If you always install SuperSU (even if not necessary) after flashing unknown status boot.img, then it will always patch the boot.img to remove forceencrypt and you'll never get re-encrypted.
You could replace any of the steps above with equivalent pre-patched kernels, etc.
Click to expand...
Click to collapse
Thank you! I will consider this next time

2x4 said:
hmm wait, so there's no way to re-encrypt if you've already decrypted and you're using a custom rom?
Click to expand...
Click to collapse
I don't know if it works with custom roms, I can only tell you what I experienced with the setup I described, originally stock MTC19T boot.img that went through systemless root setup via SuperSU and TWRP recovery.
I didn't experiment further to see if the problem was with TWRP recovery or with the systemless root boot.img so I can't tell you which one (or both) was causing the issue.
I imagine if your custom ROM is based on a stock kernel, you could LEAVE the custom rom system image in place, JUST flash stock boot.img and stock recovery.img, let the first boot encryption do its thing, then reflash your custom boot.img and twrp recovery.
That is what I did to get things re-encrypted and it was relatively painless after I figured out what to do.
Even if your custom ROM is not based on stock kernel, the same technique might work, because the encryption is done by the kernel prior to Android booting. Your custom ROM in this case, depending on why it is using a modified kernel, might not boot properly until after you replace the kernel it expects.
So in short, I think you should be able the encrypt, but probably not with Settings->Security

UPDATE:
I was able to get 2 units side-by-side again. This time both of them were encrypted. The difference was one was running the original MDA89E OS and the other was running the latest MTC19V OS.
I just did 1 simple test, I created a 238.5MB zip file of my Titanium backup directory.
On MDA89E (user partition encrypted) it took 6:39
On MTC19V (user partition encrypted) it took 1:01
This result along with the previous results that found virtually no difference between decrypted and encrypted on MHC19Q leads me to the conclusion that decrypting probably did see a performance boost on the original MDA89E software all the way up to probably MMB29V but from MHC19J onwards, up to at least MTC19V, there is virtually no real-world (rather than benchmark) difference between decrypted and encrypted.
I didn't have time to do more detailed testing on this phone as it needed to be returned.

For me, unencrypted is the way to go. I use my phone as my main music player, and audio tends to skip when I'm using my phone while listening to music on an encrypted setup. It's kind of a deal breaker for me tbh.

hmghmg said:
For me, unencrypted is the way to go. I use my phone as my main music player, and audio tends to skip when I'm using my phone while listening to music on an encrypted setup. It's kind of a deal breaker for me tbh.
Click to expand...
Click to collapse
Did you try that only on early OS releases?
I record and playback 1080p video with no skipping. 1080p video is much higher bitrate than audio so it would be surprising if encryption on the latest releases would cause skipping for audio.

sfhub said:
Did you try that only on early OS releases?
I record and playback 1080p video with no skipping. 1080p video is much higher bitrate than audio so it would be surprising if encryption on the latest releases would cause skipping for audio.
Click to expand...
Click to collapse
Yes, I have! I tried it on the latest marshmallow build. (Sorry, I forgot the build number)
If it works for you, I wonder what's wrong with mine...

hmghmg said:
Yes, I have! I tried it on the latest marshmallow build. (Sorry, I forgot the build number)
If it works for you, I wonder what's wrong with mine...
Click to expand...
Click to collapse
1) When you say "using your phone" what else are you doing when it starts skipping?
2) Which music app are you using
I'm pretty sure decryption of an encrypted user partition can easily handle the bit rate needed for audio playback if everything is being done in isolation, so there must be some interaction going on that causes what you are seeing.

VZW HTC 10 - ExtSD as Internal & Bootloops

Hello fellow HTC 10 friends,
Mods, please move this thread to the appropriate subforum if I have posted this question in the wrong place. I have read these forums for years but am a new poster here.
EDIT: It turns out Xposed has nothing to do with these issues, the memory card is what is causing the boot loops. The card is formatted for use as internal storage so I'm trying to figure the best way to back up my data before formatting it, or trying to locate a repair utility that can just find and eliminate the bad file. I found a utility that made a direct image of the disk and seemed to skip the bad data but I'm hesitant to restore that back to the card, let alone format the card with that as my only backup. The phone boots perfectly fine without the card, and so far it appears as though if I give it a few minutes to finish the full boot process I can sneak the card in and the phone wont crash until I say run a heuristic malware scan on all files or something that loads the bad file. It is possible that a file that is only loaded when a given Xposed module is activated is stored on the external card causing boot loops only while Xposed is installed.
/EDIT
Anyhow, I am hoping someone can point me in the right direction with regard to troubleshooting an issue. I have a VZW 10, S-Off/Locked, and am having a peculiar issue with intermittent boot loops. Occasionally, upon running out of battery or performing a full Power Off/Boot cycle, my phone will get stuck in an infinite boot loop triggered during the "Starting apps..." screen immediately following the Verizon boot animation. Once this happens, the looping is infinite, and the only way to recover is to run the Xposed Uninstaller zip from recovery and wipe dalvik/cache. The phone then takes an extremely long time to rebuild the wiped file system and functions normally. Wiping D/C alone does not resolve the issue, and the boot loops resume once it reaches a certain app during the "optimization" process.
I presume there must be some sort of logging tools that can assist me with finding out what is causing this. Currently, Xposed-enabled apps greatly shape the user experience on my 10, and to simply ditch the framework is not really a viable option. I wouldn't mind having to deal with these loops once in a while but today I was nowhere near home and very much in need of a phone when the loops struck again. Today the phone simply crashed leading into the loops, which is the first system instability I've encountered outside of the boot process.
If anyone has experienced this same issue or can direct me to logging/troubleshooting software that would help identify the culprit I would be very appreciative! Thanks in advance for any help you guys may be able to provide!

Are you running a deodexed or odex rom?
Sent from my HTC6545LVW using Tapatalk

Curious as to which type of xposed you are using? Magisk? , romracer, or rovos

REtails said:
Hello fellow HTC 10 friends,
Mods, please move this thread to the appropriate subforum if I have posted this question in the wrong place. I have read these forums for years but am a new poster here.
Anyhow, I am hoping someone can point me in the right direction with regard to troubleshooting an issue. I have a VZW 10, S-Off/Locked, and am having a peculiar issue with intermittent boot loops. Occasionally, upon running out of battery or performing a full Power Off/Boot cycle, my phone will get stuck in an infinite boot loop triggered during the "Starting apps..." screen immediately following the Verizon boot animation. Once this happens, the looping is infinite, and the only way to recover is to run the Xposed Uninstaller zip from recovery and wipe dalvik/cache. The phone then takes an extremely long time to rebuild the wiped file system and functions normally. Wiping D/C alone does not resolve the issue, and the boot loops resume once it reaches a certain app during the "optimization" process.
I presume there must be some sort of logging tools that can assist me with finding out what is causing this. Currently, Xposed-enabled apps greatly shape the user experience on my 10, and to simply ditch the framework is not really a viable option. I wouldn't mind having to deal with these loops once in a while but today I was nowhere near home and very much in need of a phone when the loops struck again. Today the phone simply crashed leading into the loops, which is the first system instability I've encountered outside of the boot process.
If anyone has experienced this same issue or can direct me to logging/troubleshooting software that would help identify the culprit I would be very appreciative! Thanks in advance for any help you guys may be able to provide!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3441976
Sent from my Andromax AD683J using XDA-Developers mobile app
---------- Post added at 11:04 PM ---------- Previous post was at 10:49 PM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
REtails said:
Hello fellow HTC 10 friends,
Mods, please move this thread to the appropriate subforum if I have posted this question in the wrong place. I have read these forums for years but am a new poster here.
Anyhow, I am hoping someone can point me in the right direction with regard to troubleshooting an issue. I have a VZW 10, S-Off/Locked, and am having a peculiar issue with intermittent boot loops. Occasionally, upon running out of battery or performing a full Power Off/Boot cycle, my phone will get stuck in an infinite boot loop triggered during the "Starting apps..." screen immediately following the Verizon boot animation. Once this happens, the looping is infinite, and the only way to recover is to run the Xposed Uninstaller zip from recovery and wipe dalvik/cache. The phone then takes an extremely long time to rebuild the wiped file system and functions normally. Wiping D/C alone does not resolve the issue, and the boot loops resume once it reaches a certain app during the "optimization" process.
I presume there must be some sort of logging tools that can assist me with finding out what is causing this. Currently, Xposed-enabled apps greatly shape the user experience on my 10, and to simply ditch the framework is not really a viable option. I wouldn't mind having to deal with these loops once in a while but today I was nowhere near home and very much in need of a phone when the loops struck again. Today the phone simply crashed leading into the loops, which is the first system instability I've encountered outside of the boot process.
If anyone has experienced this same issue or can direct me to logging/troubleshooting software that would help identify the culprit I would be very appreciative! Thanks in advance for any help you guys may be able to provide!
Click to expand...
Click to collapse
ganyong said:
http://forum.xda-developers.com/showthread.php?t=3441976
Sent from my Andromax AD683J using XDA-Developers mobile app
Click to expand...
Click to collapse
Sent from my Andromax AD683J using XDA-Developers mobile app

I appreciate all of the replies! It appears simple coincidence was responsible for making it seem as though Xposed was the culprit, I have traced the issue back to my external sd card, which appears to have a few corrupted files on it. I haven't found a tool to repair the card yet so I am working on imaging the card minus the bad files so I can format it and replace the files. I updated the original post to reflect these findings.
Any recommendations for the best way to accomplish this task?
Edit: To answer other questions, I'm using stock VZW rom, latest SuperSU and Xposed releases installed.

What files are you trying to replace?
If just personal files, Why not hook to PC backup the personal files music/pictures by just moving them over (drag and drop).
Then format to portable
Go into twrp do a full format not just wipe/factory reset and start over with a fresh rom install
Wiping dalvik and cache does nothing to fix your sort of problem

afuller42 said:
What files are you trying to replace?
If just personal files, Why not hook to PC backup the personal files music/pictures by just moving them over (drag and drop).
Then format to portable
Go into twrp do a full format not just wipe/factory reset and start over with a fresh rom install
Wiping dalvik and cache does nothing to fix your sort of problem
Click to expand...
Click to collapse
I honestly just don't feel like going through the hassle of setting up the phone with a fresh flash, that's kind of my goal in all of this, I prefer the challenge of figuring out how to fix the issue I guess lol.
That being said, I noticed that a batch of apps, including system apps, had lost many vital permissions for some unknown reason (yay HTC devices) and I restored those as necessary. I then also decided to try and perform an integrity check interally, went into recovery and unmounted all partitions, ran adb shell, cat /etc/fstab to find blocks, and ran e2fsck on the ext sdcard. Lastly I made sure my SD card was fully inserted now, because you never know with that stuff lol. Power cycled the phone successfully 3 times now with no issues or abnormalities...I guess I'll have to see what happens.
Edit: apparently my old laptop was still logged in to my ancient lurker account from many phones and skill levels ago, oops.

Samsung Galaxy Tab A- Need to backup but stuck in boot loop after update

Hello all,
Hopefully I'm posting this in the correct section and someone can help me with my dilemma..
I have a Samsung Galaxy Tab A, Model #T510, running stock Android 9 Pie (I believe).
I was trying to clear up space in the file system yesterday when a system update window came up. I tried to schedule for later and it started the install anyways. Shortly after it started the update, it stopped because of "low storage" and got stuck in a Boot Loop of the Samsung logo screen.
It then goes to the Android Recovery with the following error:
"Perform Lacking Storage Booting"
*(See image 1 for actual screen)
It gives me the following options:
"-Reboot to bootloader
-Apply update from ADB
-Apply update from SD card
-Wipe data/factory reset
-Wipe cache partition
-Mount /system
-View recovery logs
-Run graphics test
-Run locale test
-Power off"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried Powering Off, Checking the Rescue Logs, and Rebooting. All result in a continuous boot loop, until it eventually kicks me back to the Recovery Page. I've wiped the cache partition, and it didn't make a difference. Still stuck in boot loop before being kicked back to Recovery.
However, when I try "Reboot to bootloader", it gives me a different screen (See image 2) with the following four options:
"Android Recovery
samsung/gtalxlwifixx/gtalxlwifi 10/0P1A. 190711.020/TS10XXU3BTFH
user/release-keys
Android Recovery 10/0P1A. 190711.020/TS10XXU3BTPN
user/release-keys
Use volume up/down and power. Your phone couldn't start normally. Some configuration data may be corrupt. Follow the instructions:
1. Try again
Restart your phone. If your phone continues to be unable to start, go to the next step.
2. Erase app data
Deleting app configuration data may allow your phone to start in Safe mode. Safe mode allows access to basic functions, so you can back up any important data stored on your phone. After backing up your data, a factory reset may be needed to get your phone to start normally.
3. Visit a service center
If you don't want to erase your app data or your phone still doesn't start, visit a service center for assistance.
-Try again
-Erase app data
-Power off
-View rescue log
#Reboot Recovery Cause is [system server:10028 RecoverySystemRescueParty] E: [libfs ngr]Unable to disable quotas on /dev/block/platform/13500000.dmmce/by-name/userdata becaus /system/bin/tune2fs is missing #Reason is [RescueParty] Supported API: 3"
So, here is my dilemma...
I have already backed up the SD card that I was using in the tablet, as I was able to extract it's contents onto my PC without issue, (after taking it out of the tablet).
BUT I can't find a way to access the internal storage!! I need to get in to backup my files because my daughter uses it for homeschooling and she's done a ton of work since my last full backup (roughly a month ago).
I've tried connecting the tablet via USB data to my laptop, to see if I could open it from there, as a storage device...
No-go. PC doesn't recognize it at all.
I've tried backing it up through my Samsung Account, and Find My Mobile and can't because the tablet can't connect to my network... (Because I can't get it to boot into Android)
I've accepted the fact that I will most likely have to do a factory reset, but I need to get my data off first.
Does anyone know of a way I can back up the internal storage outside of Android?
Or how to get into this magical Safe Mode?
I've been trying different things since yesterday and can't find a solution. I've thought about trying the "Erase App Data" option in the Recovery page, as it talks about the ability to load into Safe Mode.
But if I do that, will I actually lose everything? Has anyone used this function before?
I would greatly appreciate any help I can get. I'm a certified tech with Dell (albeit years ago now), so I've tried a few tricks of the trade, but as everyone knows... Because I didn't root it in the beginning, I can't use the exploit commands without tripping Knox. So I can't even back it up via TWRP.
And as usual, Samsung has been no help. They won't say whether or not the data can be backed up or recovered, they are defaulting to sending it out for repair.
All I'm looking for is to find out IF it's possible. If it is, then there is a solution.
I'm so frustrated with it, that I've considered using it for target practice But because my daughter's schoolwork is on it, and she's quite the little novelist (she's only 10 haha)... She is a puddle of emotion at the moment because she thinks everything has been erased.
So, if anyone knows more info on this.. I beg for your assistance! I'm always trying to gain more knowledge and stay current, so I'm open to suggestions!!
Thank you in advance, let me know if further details are needed.

BBCro said:
Hello all,
Hopefully I'm posting this in the correct section and someone can help me with my dilemma..
I have a Samsung Galaxy Tab A, Model #T510, running stock Android 9 Pie (I believe).
I was trying to clear up space in the file system yesterday when a system update window came up. I tried to schedule for later and it started the install anyways. Shortly after it started the update, it stopped because of "low storage" and got stuck in a Boot Loop of the Samsung logo screen.
It then goes to the Android Recovery with the following error:
"Perform Lacking Storage Booting"
*(See image 1 for actual screen)
It gives me the following options:
"-Reboot to bootloader
-Apply update from ADB
-Apply update from SD card
-Wipe data/factory reset
-Wipe cache partition
-Mount /system
-View recovery logs
-Run graphics test
-Run locale test
-Power off"
View attachment 5596551
I have tried Powering Off, Checking the Rescue Logs, and Rebooting. All result in a continuous boot loop, until it eventually kicks me back to the Recovery Page. I've wiped the cache partition, and it didn't make a difference. Still stuck in boot loop before being kicked back to Recovery.
However, when I try "Reboot to bootloader", it gives me a different screen (See image 2) with the following four options:
"Android Recovery
samsung/gtalxlwifixx/gtalxlwifi 10/0P1A. 190711.020/TS10XXU3BTFH
user/release-keys
Android Recovery 10/0P1A. 190711.020/TS10XXU3BTPN
user/release-keys
Use volume up/down and power. Your phone couldn't start normally. Some configuration data may be corrupt. Follow the instructions:
1. Try again
Restart your phone. If your phone continues to be unable to start, go to the next step.
2. Erase app data
Deleting app configuration data may allow your phone to start in Safe mode. Safe mode allows access to basic functions, so you can back up any important data stored on your phone. After backing up your data, a factory reset may be needed to get your phone to start normally.
3. Visit a service center
If you don't want to erase your app data or your phone still doesn't start, visit a service center for assistance.
-Try again
-Erase app data
-Power off
-View rescue log
#Reboot Recovery Cause is [system server:10028 RecoverySystemRescueParty] E: [libfs ngr]Unable to disable quotas on /dev/block/platform/13500000.dmmce/by-name/userdata becaus /system/bin/tune2fs is missing #Reason is [RescueParty] Supported API: 3"
View attachment 5596553
So, here is my dilemma...
I have already backed up the SD card that I was using in the tablet, as I was able to extract it's contents onto my PC without issue, (after taking it out of the tablet).
BUT I can't find a way to access the internal storage!! I need to get in to backup my files because my daughter uses it for homeschooling and she's done a ton of work since my last full backup (roughly a month ago).
I've tried connecting the tablet via USB data to my laptop, to see if I could open it from there, as a storage device...
No-go. PC doesn't recognize it at all.
I've tried backing it up through my Samsung Account, and Find My Mobile and can't because the tablet can't connect to my network... (Because I can't get it to boot into Android)
I've accepted the fact that I will most likely have to do a factory reset, but I need to get my data off first.
Does anyone know of a way I can back up the internal storage outside of Android?
Or how to get into this magical Safe Mode?
I've been trying different things since yesterday and can't find a solution. I've thought about trying the "Erase App Data" option in the Recovery page, as it talks about the ability to load into Safe Mode.
But if I do that, will I actually lose everything? Has anyone used this function before?
I would greatly appreciate any help I can get. I'm a certified tech with Dell (albeit years ago now), so I've tried a few tricks of the trade, but as everyone knows... Because I didn't root it in the beginning, I can't use the exploit commands without tripping Knox. So I can't even back it up via TWRP.
And as usual, Samsung has been no help. They won't say whether or not the data can be backed up or recovered, they are defaulting to sending it out for repair.
All I'm looking for is to find out IF it's possible. If it is, then there is a solution.
I'm so frustrated with it, that I've considered using it for target practice But because my daughter's schoolwork is on it, and she's quite the little novelist (she's only 10 haha)... She is a puddle of emotion at the moment because she thinks everything has been erased.
So, if anyone knows more info on this.. I beg for your assistance! I'm always trying to gain more knowledge and stay current, so I'm open to suggestions!!
Thank you in advance, let me know if further details are needed.
Click to expand...
Click to collapse
Welcome to XDA,
This is the correct section for your question, I would ask my good amigo @Oswald Boelcke to kindly help us moving your thread.
Enjoy your stay!

orb_selektor said:
Welcome to XDA,
This is the correct section for your question, I would ask my good amigo @Oswald Boelcke to kindly help us moving your thread.
Enjoy your stay!
Click to expand...
Click to collapse
Thank you so much

orb_selektor said:
Welcome to XDA,
This is the correct section for your question, I would ask my good amigo @Oswald Boelcke to kindly help us moving your thread.
Enjoy your stay!
Click to expand...
Click to collapse
BBCro said:
Thank you so much
Click to expand...
Click to collapse
@BBCro Also a very warm welcome from my side - although you're already a member for two years. I hope you'll always get the support you require.
Thread has been moved to the suggested location.
Regards
Oswald Boelcke

Thanks for your help Oswald, I really appreciate everyone here. Hoping to find a solution, cause I'm just about at my wits end. Yay technology!

I have this problem and I wanted to fix it, my device does not show up the "Lacking storage booting" function in Recovery.