Database Develop

sd-card blues...

Hey guys I have a question for you all about sd-cards
I sbf'd
Installed ota 5.7.894 (because of no true .906 sbf I won't flash it)
Regained root
Installed busybox 1.20 (figured newer might be better)
Installed safestrap (tweaked of course 1.08f)
Now
My phone see's the internal/external sd-cards fine and mounts/formats/explores just fine
My laptop also see's internal/external sd-cards just fine
However
Rootbrowser cannot see the sd-card
Safestrap cannot find /sdcard
But
Root explorer can see the internal and external just fine
I have tried sbfing several times to see if it will fix it
I have tried not installing the ota,changing versions of busybox ect..
Why can my phone see and work with the sd-cards just fine but programs cannot?
Because safestrap cannot see the sd-card I cannot create backups..
Any help is greatly appreciated

I think Rick#2 acknowledged this in the safestrap 1.08f thread and had this advice for those experiencing the error:
(For the record, this change almost worked for me - safestrap would now access my external sdcard (/sdcard), but when I would select a zip to flash, it would just take me back to the menu. I dropped a reply with my results in that thread.)
Rick#2 said:
While you're in Safestrap, either go into the console or "adb shell" into your phone. (Remember that for adb to work properly in the recovery your phone has to boot up with the USB cable already connected).
If you type:
Code:
ls -l /dev/block | grep mmcblk0
what output does it provide? For me, it spits out "mmcblk0" but... I'm pretty sure that for those that aren't able to mount their external sdcards it will say mmcblk0p1. In which case, the fix is easy; I'll be sure to update my package, obviously, but for those of you who want to try a little DIY, copy the file /systemorig/etc/safestrap/recovery.zip onto your computer and unzip it. Inside, there's be a file called /etc/recovery.fstab; edit this and change the line corresponding to /sdcard (It ought to be on line 3, or the second line of actual text) to the following:
Code:
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
Click to expand...
Click to collapse
At this point, after copying the recovery.fstab back to my phone, I assumed I had to correct the permissions of the file, so I did. If I am wrong, someone please let me know!
continuing his reply...
Doesn't really matter how many spaces you have between; ideally you'll just need to hit tab each time.
Hopefully this is what the issue was. I remembered changing that line because I was getting random error messages about my external /sdcard and since I didn't see /dev/block/mmcblk0p1 in my /dev/block directory I assumed I must have made a typo and changed it... here's one tiny example of how easy it is to completely bork these things. Multiply it by a million and you have kernel development...
Click to expand...
Click to collapse

That might work if it was just safestrap having the issue..but its not
Even cwm cannot backup the apps on the sd-card as it cannot see it as well..
But root explorer and the stock file browser can see the internal/external sd-cards
And write on them just fine..and even mount/unmount and format...arrrggggg
This is killin me

[Q] Unlocking / Rooting Nexus 7 without having to Wipe it

Hello Everyone,
So I have had a Nexus 7 for about a few months now and I love it! I have done some research and I am getting mixed answers.
My question is: Is it possible to Unlock a Nexus 7 without having to wipe the data.
Thanks so much in advance.

No.
The tablet can now be rooted without unlocking the boot loader, however.
There is a third method for re-locking & unlocking without touching the data - but it requires at least one prior unlock which does destroy all data.

bftb0 said:
No.
The tablet can now be rooted without unlocking the boot loader, however.
There is a third method for re-locking & unlocking without touching the data - but it requires at least one prior unlock which does destroy all data.
Click to expand...
Click to collapse
I am checking this out now.
Just wanted to say thanks ahead of time

@handy
If you were asking about this because you were contemplating rooting, please be advised about the importance of making full nandroid backups. Perversely, the rooting guides fail to mention how important this is... especially if you are averse to wiping the tablet.
The reason? If you are rooted and you wedge your O/S somehow with a "mod gone bad", the only means of rescue will be unlocking the boot loader (to be able to use the advanced capabilities of fastboot), which wipes the tablet.
The way to do this with a locked bootloader is to flash a custom recovery to the recovery partition (from a root shell command line) after you have rooted.
That way if something goes wrong with booting the regular OS, you have a custom recovery to fall back on - and hopefully you used it to create a Nandroid backup before modding your lightly rooted stock ROM.
good luck

I agree with @bftb0
Just make it clear, I't possible to root without wipping. But you are still locked. Not possible to Unlock without wipping yet. If your data and OS is important for you (not for me) you must keep a backup first. Don't rely on the words I'll be successfully rooted with my OS and data anything can go wrong at any moment.

I just want to thank you all very very much!
I was successful using the method linked in the original post: http://forum.xda-developers.com/showthread.php?t=2233852
I have been researching for ways to root my Nexus 7 without having to unlock it since unlocking would mean losing all my data and the sole purpose of wanting to root my nexus 7 was to gain access to good backup programs and methods like titanium backup and full bit by bit NAND backups. Which I am still not sure I can use full bit by bit nand yet but hey this is a start in the right direction. And I didn't lose any data doing this.
Thanks so much and I will keep in touch with how it goes.

HandyAndyXDA said:
I just want to thank you all very very much!
I was successful using the method linked in the original post: http://forum.xda-developers.com/showthread.php?t=2233852
I have been researching for ways to root my Nexus 7 without having to unlock it since unlocking would mean losing all my data and the sole purpose of wanting to root my nexus 7 was to gain access to good backup programs and methods like titanium backup and full bit by bit NAND backups. Which I am still not sure I can use full bit by bit nand yet but hey this is a start in the right direction. And I didn't lose any data doing this.
Thanks so much and I will keep in touch with how it goes.
Click to expand...
Click to collapse
Get started on installing a custom recovery (either CWM or TWRP) immediately so that you can make a Nandroid backup.
And then get a copy of that off the tablet for safe keeping.
Note (here I am reading between the lines of your post) that on the N7, Nandroid backups exclude /data/media !! - Basically, everything that you see in "/sdcard" is NOT BACKED UP by Nandroid.
You need a full Nandroid backup in the event of some kind of disaster (rooting experiment or mod gone wrong), but you also do need to backup stuff you feel is worth keeping from your /sdcard. You can use MTP for that if you want.
good luck and be careful.

Thanks for the backup tips! I was not aware that it won't backup sdcard directory.
Not to get off the thread topic because the whole purpose of rooting for me was to gain the best backup possible and being able to use USB flash drives now is nice too.
Anyway, I would like to know what you recommend for backup and how it works / how to use it. I would love to have something that works like acronis. I am really interested in making a bit by bit image that I can store on my desktop or flash drive that I can recover from.
I am researching on my own but I'd love to get input from you guys if you don't mind.
PS: Thanks again! You have been great help!
And now that I see the thanks button, everyone of you is getting a thanks!:good:

Forget my last question asking about backup. That would go in another thread anyway and besides I ventured into using TWRP that I installed using GooManager and its just awesome. Thanks again everyone and be well.

HandyAndyXDA said:
Forget my last question asking about backup. That would go in another thread anyway and besides I ventured into using TWRP that I installed using GooManager and its just awesome. Thanks again everyone and be well.
Click to expand...
Click to collapse
TWRP does exactly what you want with backups

Unfortunately TWRP does not backup everything! Luckily I didn't do a hard factory reset when I was testing it out so I didn't lose any data.
It seems to me that TWRP does not backup internal storage. On another note these android directory names and aliases are really making me crazy lol.
I would really like to be able to recover from a hard factory reset including all data on the nexus 7. Is there any way possible to do this with TWRP or anything else?
Thanks so much.

HandyAndyXDA said:
Unfortunately TWRP does not backup everything! Luckily I didn't do a hard factory reset when I was testing it out so I didn't lose any data.
It seems to me that TWRP does not backup internal storage. On another note these android directory names and aliases are really making me crazy lol.
I would really like to be able to recover from a hard factory reset including all data on the nexus 7. Is there any way possible to do this with TWRP or anything else?
Thanks so much.
Click to expand...
Click to collapse
so, if TWRP were to back up the internal storage, where would it store that backup? It wouldnt be able to store a backup of itself ON itself...
if you want a backup of the internal storage, just copy it to a usb thumb drive over OTG or to your computer, nandroids are not meant to back up 'sdcard' storage and never have been
want to recover from a complete loss of everything?
make TWRP backup
copy /sdcard contents to USB OTG or computer, your TWRP is on that directory so you would be copying EVERYTHING

Pirateghost said:
so, if TWRP were to back up the internal storage, where would it store that backup? It wouldnt be able to store a backup of itself ON itself...
if you want a backup of the internal storage, just copy it to a usb thumb drive over OTG or to your computer, nandroids are not meant to back up 'sdcard' storage and never have been
want to recover from a complete loss of everything?
make TWRP backup
copy /sdcard contents to USB OTG or computer, your TWRP is on that directory so you would be copying EVERYTHING
Click to expand...
Click to collapse
Thanks and sorry I didn't mention that I was backing up using TWRP to a usb flash drive all along. I am having trouble copying /sdcard now for 2 reasons:
1) Sometimes its called "Storage", sometimes its a directory within others, sometimes its called "internal".......I am just not sure what the actual directory is anymore.
2) I have tried copying as much as i could manually to my desktop via usb. but does windows see all that i need to copy and each time i select all and copy it, windows explorer lags and eventually crashes lol.
As of now I am trying to copy one fold at a time to windows. .....no I don't know what I am doing. Just getting frustrated so I am trying to copy it all on my own as well as useing TWRP lol

since MTP came about copying using windows explorer or any file browser, just plain sucks.
you have a couple of options here,
1. Use AIRDroid and copy it over your wifi
2. Use ADB and simply do 'adb pull /data/media C:\path\to\your\backup\folder
personally i prefer adb, i make regular backups of my phone and tablet and keep them on USB thumbdrive or sdcard on my laptop

Pirateghost said:
since MTP came about copying using windows explorer or any file browser, just plain sucks.
you have a couple of options here,
1. Use AIRDroid and copy it over your wifi
2. Use ADB and simply do 'adb pull /data/media C:\path\to\your\backup\folder
personally i prefer adb, i make regular backups of my phone and tablet and keep them on USB thumbdrive or sdcard on my laptop
Click to expand...
Click to collapse
Already tried Airdroid which was working great until about 20 minutes later when it just stopped. Guess its just too much for airdroid too.
Yeah MTP isnt great lol.
And thanks again, I will give the adb method a try.

HandyAndyXDA said:
Already tried Airdroid which was working great until about 20 minutes later when it just stopped. Guess its just too much for airdroid too.
Yeah MTP isnt great lol.
And thanks again, I will give the adb method a try.
Click to expand...
Click to collapse
Oh, one more thing:
Am I correct in saying that all that Windows sees is the total internal storage? In other words every file that I can explore using Windows is what TWRP doesn't backup?

I got the adb command line tool. I have it running, but how do i direct it to the nexus? I mean there is no drive letter for the tablet.
Sorry to be a pest.

HandyAndyXDA said:
Oh, one more thing:
Am I correct in saying that all that Windows sees is the total internal storage? In other words every file that I can explore using Windows is what TWRP doesn't backup?
Click to expand...
Click to collapse
Yeah. Pretty sure.
HandyAndyXDA said:
I got the adb command line tool. I have it running, but how do i direct it to the nexus? I mean there is no drive letter for the tablet.
Sorry to be a pest.
Click to expand...
Click to collapse
Look at the command that i posted. You don't use a drive letter.
Sent from my Galaxy Nexus

Pirateghost said:
Yeah. Pretty sure.
Look at the command that i posted. You don't use a drive letter.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Tried that exact command aside from changing the save destination and no luck.
I don't know what I am doing wrong lol

HandyAndyXDA said:
Oh, one more thing:
Am I correct in saying that all that Windows sees is the total internal storage? In other words every file that I can explore using Windows is what TWRP doesn't backup?
Click to expand...
Click to collapse
I have not been able to convince myself that the MTP implementation is deterministic, although in theory it is impossible for it not to be. (Translation: I don't trust it at all)
"adb pull" will work best when the remote shell automatically acquires root privileges, but that requires a modified boot image (the /default.prop file in the boot ramdisk) for rooted-stock ROMs, but this shouldn't be needed for "adb pull /sdcard/" - it is needed for pulling files from other areas of /data, or /system, etc though.
You previously mentioned "bit for bit", and that won't happen for adb or MTP as all timestamps, ownership, and file mode info will be lost when files are transferred to a Windows filesystem. The latter two are not particularly important for /sdcard, and I suppose that a lot of people won't care too much about timestamps either. You might feel differently though.
Actually attempting to do something closer to "bit-for-bit" brings it's own set of problems. You could use a (busybox version of) "tar" program in either the recovery or the OS, but you probably need to write the output to a mounted NTFS filesystem because of large-file ( > 2Gb) limitations of FAT filesystems. That's a non-starter with a stock kernel (for the regular OS, anyway) and it is my impression that TWRP's kernel isn't mounting NTFS in rw mode yet (I don't know about CWM)
To date when I've needed to wipe the tablet and restore it I've just used Nandroid backup/restore plus adb pull/push for /sdcard. (I wish adb was faster - it seems to be 3x-5x slower than MTP)
I suppose there are other alternatives (network mounting of CIFS shares using compatible kernels, etc) but I haven't tried them so far.
good luck

/sdcard problems after upgrading Android

I'm seeing a few posts and qquestions about this with the latest Lollipop release being upon us.
There are several issues here and I wanted to write a quick note aboyut them both for you
1) You cannot SEE your /sdcard data after updating to lollipop
Cause:
Some strange difference between L and KK, where /storage/emulated and /data/media are not "alligned"
Fix:
Open a terminal emulator application and enter the following 2 line command (Press enter after each line)
Code:
su
restorecon -FR /data/media/0
Reboot
2) You have lost permissions to /sdcard
Cause:
You restored all your sdcard data using adb push or MTP whilst booted into recovery. IT screws up your permissions. These methods are fine for single files or backups that you waant to flash or restore, but as soon as you start pushing folders, this issue will be seen
Fix:
In a root explorer app, browse to /data/media/0 and locate your Download folder. Set the permissions for all on Download to read / write (Long press the Download folder > permissions)
Download and flash THIS ZIP from the thread below.
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms] (by @osm0sis)
You can also download the zip to a computer and adb push it / MTP via recovery
3) 32 GB device shows the storage of 16 GB version
Cause:
Unknown. This has actually been happening since the Nexus 5 was released
Fix:
Wipe cache and data
4) TWRP backups are missing
Cause:
This is really unknown. We're not even sure that this can be fixed. Some say its a TWRP bug but that cannot be proven.
Sometimes backup folder is empty....
Fix:
Multiple things you can try. Some have to use restorecon command but usually that has to be done after every backup.
Others have just flashed the factory images
Some of us have never had issues so its hard to call it a bug, but there is definitely something funky going on here.
Other times, backups shows as an unknown file type, 0bytes in size. I haven't a specific fix as I have had no feedback from anyone who has fixed it. You could try deleting that unknown file then running the fix above.
Also, please update to TWRP 2.8.3.0
5) All I see in /sdcard is 0 folder
Cause:
Well known issue on /data/media/0 devices - which is the location of the /sdcard. Unsure of the cause on Nexus 5 though
Fix:
/sdcard is in /data/media/0. If you see a 0 folder in /sdcard, you're actually seeing /data/media/0/0.
To fix, just move /data/media/0/0/* to /data/media/0

I updated without a problem. Be sure to update to latest SDK and to wipe sdcard, eg. clean install.
Sent from Pure Nexus 5

alen1901 said:
I updated without a problem. Be sure to update to latest SDK and to wipe sdcard, eg. clean install.
Sent from Pure Nexus 5
Click to expand...
Click to collapse
Yep, the first issue is fine if you wipe your /sdcard.
The second one is caused by restoring your sdcard afterwards

I have used always Mixplorer and now after flashing 5.0 I cant see nothing under /root. Why so? Something with root permissions? everything else is ok. ( I want to modify build.prop a little )
do I need use some other file explorer?

restorecon -FR /data/media/0 fixed a problem I had with a bad TWRP folder on my Nexus 10 - many thanks!

rootSU said:
Yep, the first issue is fine if you wipe your /sdcard.
The second one is caused by restoring your sdcard afterwards
Click to expand...
Click to collapse
I restored everything except data and android folders back to sdcard, i even restored obb files and no problems at all. It is the best practice for users to restore only their data, not the ones android creates itself. Im sure most people just selects everything and transfer to pc/stick, then copy everything back.
Sent from Pure Nexus 5

Thanks dude. I wish I had this information this morning - would've saved me a lot of sweat.

I'm facing some serious issues today with this.
At first I encountered the issue when installing the flashable update. The OP suggested to execute few command lines in a terminal emulator, but it would only have worked if you rooted your device with cfroot. So I tried to re-root with cfroot with no luck: it kept saying already unlocked. At this point in the settings said I had 3/3 free gigs of storage. Out of desperation I tried to flash every single part of the stock image via fastboot, and re-do the procedure with cfroot and all. However after doing all of that I ended up with 12/12 free gigs, which is what I'm left with right now. I also tried to fix the permissions either with the root explorer app and by flashing the the provided fix, but nothing has happened. No traces of either Titanium backups or whatever files I had before on my storage, it's basically like a new phone with a blank 12 gb storage (keep in mind I have the 32 gb version). I really don't know what to do at this point anymore. Have I by any mean flashed the partitions of a 16 gb variant or something? Will I ever be able to get my storage back? Any help wuld be much appreciated.
Update: apparently I also flashed userdata so my phone believed to be a 16 gb unit. A data wipe fixed it. Obviously my storage is gone but that's my bad, I'll be more careful before udating next time.

vnvman said:
I'm facing some serious issues today with this.
At first I encountered the issue when installing the flashable update. The OP suggested to execute few command lines in a terminal emulator, but it would only have worked if you rooted your device with cfroot. So I tried to re-root with cfroot with no luck: it kept saying already unlocked. At this point in the settings said I had 3/3 free gigs of storage. Out of desperation I tried to flash every single part of the stock image via fastboot, and re-do the procedure with cfroot and all. However after doing all of that I ended up with 12/12 free gigs, which is what I'm left with right now. I also tried to fix the permissions either with the root explorer app and by flashing the the provided fix, but nothing has happened. No traces of either Titanium backups or whatever files I had before on my storage, it's basically like a new phone with a blank 12 gb storage (keep in mind I have the 32 gb version). I really don't know what to do at this point anymore. Have I by any mean flashed the partitions of a 16 gb variant or something? Will I ever be able to get my storage back? Any help wuld be much appreciated.
Update: apparently I also flashed userdata so my phone believed to be a 16 gb unit. A data wipe fixed it. Obviously my storage is gone but that's my bad, I'll be more careful before udating next time.
Click to expand...
Click to collapse
Yeah that's a different but common issue.

Thank you, rootSU. This fixed my issue.

So I have tried the fixes and all of my files are still in sdcard/0 and not just sdcard... Any help I can't figure this out?

rizhqrd said:
So I have tried the fixes and all of my files are still in sdcard/0 and not just sdcard... Any help I can't figure this out?
Click to expand...
Click to collapse
Move them manually.

Tried the first solution as it seems to be my issue, but it doesn't seem to work. Any ideas?

tomp100 said:
Tried the first solution as it seems to be my issue, but it doesn't seem to work. Any ideas?
Click to expand...
Click to collapse
Please explain your issue.

Hey thanks for this post. I've been through this issue like 3 times and keep forgetting about restorecon.
On that note, I was getting the following output:
~ # restorecon -FR /data/media/0/
restorecon: invalid option -- F
Click to expand...
Click to collapse
The fix appears to work without the "F" flag. Do you know why this is not a valid flag?
According to a general rundown of restorecon, the "F" flag does the following:
-F
Force reset of context to match file_context for customizable files, and the default file context, changing the user, role, range portion as well as the type.
Click to expand...
Click to collapse

RVDigital said:
Hey thanks for this post. I've been through this issue like 3 times and keep forgetting about restorecon.
On that note, I was getting the following output:
The fix appears to work without the "F" flag. Do you know why this is not a valid flag?
According to a general rundown of restorecon, the "F" flag does the following:
Click to expand...
Click to collapse
Not sure but glancing at the Dev preview thread, some had success with this:
restorecon -r /data/media/0/*

Tried both, all that happened is that /sdcard is now blank. /data/media/0 still lists all of the files, but /sdcard itself is empty or unlinked or something. I unfortunately don't know which of the two steps did it.

Quick question, I'm currently on slimkat and plan on clean flashing tonight via bigxies ROM. With this method of fixing the SD card, I won't lose all my data as far as downloads, pictures, etc.?

rootSU said:
Please explain your issue.
Click to expand...
Click to collapse
Essentially, the phone doesn't think it has an SD card. When i click on SD card in root browser, it is empty. Items that were on the SD card in 4.4.4 are now located in data/media/0/0 , and I am unable to move these items to SD. Also, if I try to dowload sonething off the internet, I get a "no SD card" message.

I can confirm that my issues were caused by importing my backed up /SDCard/ data via an "adb push" while in recovery.
If doing the same while the phone is booted into system, permissions are set appropriately and no further action is required.
Thanks again for this post!

Encryption lollipop?

Hi there! I was wondering if anyone has been able to get encryption to work on lollipop? I'm running stock rooted lollipop on my purse edition and when I go to encrypt it shows the android/gear then screen goes black and stays that way.
Thanks in advance!
PS. not a noob with android adb/fastboot or root

Yeah I've got the same issue. I have no clue what's causing it. A few people on the Moto X subreddit mentioned that a factory reset made it possible, but that's not really a step I want to take just to gain encryption.

Not sure you may want it - big problems on the nexus 6,its bogging down the phone to the point of embarrassment. I know this isn't a nexus 6, but it's damn close! So be careful what you may want to enable!

npompei said:
Not sure you may want it - big problems on the nexus 6,its bogging down the phone to the point of embarrassment. I know this isn't a nexus 6, but it's damn close! So be careful what you may want to enable!
Click to expand...
Click to collapse
ive heard that b4 and i would like to see some actual proof, maybe run a week with the encryption and a week without.

SurlyDuff said:
Yeah I've got the same issue. I have no clue what's causing it. A few people on the Moto X subreddit mentioned that a factory reset made it possible, but that's not really a step I want to take just to gain encryption.
Click to expand...
Click to collapse
okays ill make a backup and attempt tonight. will let know if fixed it. if not im going to downgrade to 4.4.4 and then upgrade to 5.0 and do a factory wipe to see if being rooted was the problem

Sigh, I realized after writing all this that I'm talking about kit kat, not lollipop. I'd assume that much is the same safe mode thing should still work, but not sure about the various directories I refer to when undoing encryption or app compatibilities.
--
I encountered this problem. There are multiple potential roadblocks. Mostly related to uncooperative background programs. The easiest thing to do is to boot into safe mode and then encrypt. That's what worked for me. If you still have a problem, have supersu remove the su binary and then try again in safe mode.
Just Google how to boot into safe mode.
---------- Post added at 02:50 AM ---------- Previous post was at 02:03 AM ----------
Note that TWRP does not decrypt encrypted data partitions for our device. Also, you can't simply unencrypt.
I ended up undoing encryption because the phone was noticeably laggier. Thus process was not well documented anywhere and was painful.
How to undo encryption (need root, obviously. From my recollection, so there may be errors):
1) Make an onandroid. Since you're doing this after you've booted, the nandroid will have images of the unencrypted partitions. https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup
2) copy this to the appropriate place in the twrp folder, to prepare for your eventual nandroid restore. Example: /data/media/0/TWRP/BACKUPS/TA44904H9S/2014-10-31--01-05-42/
3) copy the entire contents of your sdcard, including the nandroid you just made, to a computer or USB OTG (usb otg drive is easier). Twrp directory ownership and permission are screwed up, so make sure the nandroid copied over. You may have to explicitly navigate to /data/media/0 to make it copy (as opposed to /storage/emulated/0)
4) Use the following program to copy and eventually restore the timestamps: https://play.google.com/store/apps/details?id=br.com.pogsoftwares.filetimestamp . If you don't do this, the grouping of your photos and videos in gallery will be messed up. There may be other files for which this is important, I'm not sure.
5) go to twrp, and at least do a factory reset and format/wipe sdcard (not 100% sure, I may have just wiped everything)
6) copy the saved contents of your SD card to /data/media/0. I don't recall if I used twrp file manager or qtadb for this.
7) the directory and file permission on sdcard will be ****ed. Run this script to fix that: https://www.dropbox.com/s/ur596dpgzw478qm/perm.sh?dl=0 . Google to figure out how to run scripts from twrp terminal. Don't try to do this later. When I tried to do it from within android it didn't work because the version of chown I had didn't support one of the switches in the script
8) reboot into android
9) use the timestamp program to fix the file timestamps on your sdcard. I never saved the timestamps ahead of time. The program can fix the photo timestamps based on exif and the video timestamps based on filenames. But it's just easier if you saved the timestamps ahead of time.
10) immediately reboot to twrp and restore just the data partition. If you don't do this, Gallery will never fix itself based on the fixed timestamps.
11) some app data on sdcard may still be screwed up. If a program is not working right, go the the relevant directory in /sdcard/android/data and delete it.
I'm sure there are errors somewhere in the guide, just pm me if there is a problem and I'll figure it out and fix this guide

i ended up downgrading to 4.4.4 then updated to 5.0 factory reset (from inside os), encrypted i see not decrease in speed, benchmarks are same as before, will keep updated. i am rooted again and have no warning boot loader image.

So after using it for about a week. It seems the more you use the device the more lag it produces. I like the security from it.. But its not worth this insane decrease in performance.

eavandy0797 said:
So after using it for about a week. It seems the more you use the device the more lag it produces. I like the security from it.. But its not worth this insane decrease in performance.
Click to expand...
Click to collapse
How did you downgrade to 4.4?
Thanks.

swears11 said:
How did you downgrade to 4.4?
Thanks.
Click to expand...
Click to collapse
i followed the directions from Motorola. https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
i used the Moto X(2nd Gen) Pure Edition:
KK-4.4.4-KXE21.187-42-41 TMO image

Sort of a bootloop after Android 11 update

Hello guys,
I hope someone can help me with this problem...
So the thing is - yesterday I finally got OneUI 3 and Android 11 update (yay?). But ofcourse as soon as the phone rebooted and optimised all the apps and came back to main screen it rebooted after a minute or so...everytime. As soon as I enter my pin and unlock the phone it reboots after a short period.
The same problem happened when I de-bloated the phone a while ago via ADB - but I then enabled back all the apps except facebook and some "safe to debloat apps" which were not even system apps and it has since worked for almost a year. But here we go again....
I even "re enabled/installed" all the apps I could list in ADB ( so basically all the apps on the phone) and then went to wipe cache - but still no go.
I am also wondering if there is a posibility to somehow mount storage just to copy some files to my computer (which are important, and my latest backup is around a month old) and then I'll gladly do a a factory reset - no problem.
Any help would be appreciated, thanks!

If you're able to use ADB to enable/install apps, then you should be able to use "adb pull path/to/files" to copy the files to your computer. You could reboot into recovery mode and see if your computer pulls up the storage that way too. Also, if you have TWRP, you can use the file system to copy files to an external SD card. So you have a few options to get your files.
You can also create a back-up of specific apps (and their data) using "adb backup -f MyBackUpName.ab com.corp.AppName".

TacoDeMuerte said:
If you're able to use ADB to enable/install apps, then you should be able to use "adb pull path/to/files" to copy the files to your computer. You could reboot into recovery mode and see if your computer pulls up the storage that way too. Also, if you have TWRP, you can use the file system to copy files to an external SD card. So you have a few options to get your files.
You can also create a back-up of specific apps (and their data) using "adb backup -f MyBackUpName.ab com.corp.AppName".
Click to expand...
Click to collapse
Hello, thanks for the reply and helping out.
But all the commands and stuff is kinda useless because the phone reboots sooner than in 30 seconds after getting to the main screen. When I boot to recovery the storage doesn't get mounted.......
And I would've had TWRP but the phone is still under warranty so that's a shame, because on my backup phone I have it (and so did on all the previous ones) and it would be great. But IIRC if I install TWRP now, the phone needs to be wiped.
FFS samsung, what is this....because I now read a couple threads and posts on social media people having exactly same problem, and some didn't do anything with ADB prior to update. shame...