Develop Bugs

[Q] How to re-enable the stock launcher (or any disabled app)???

i am still trying to figure out how to re-enable com.lge.launcher2 as it was disabled and i have no idea how to get it back as primary launcher via command line in ADB.
I can't install it from the SDcard or as an attachment as it says "Application Not Installed" (maybe protected????).
tried "pm install -r com.lge.launcher2 -f" and get:
pkg: com.lge.launcher2 - Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]
anyone have any ideas??

Did you just switch launchers or did you freeze it with nobloat/titanium backup? If you are trying to do it with abd are you doing it from a shell terminal or just adb from a command prompt? Did you issue the su command to give yourself superuser priveledges?

I downloaded Go Launcher and switched launchers then did a backup with titanium backup, but when i rebooted after a hard reset (trying things on your phone and screwing up can make that happen sometimes LOL!!) it showed up in TB with a line through it and i cannot restore it, as when i hit restore in TB it hangs at the restore screen.
i am using ADB shell from a PC with XP home.
and yes, after 26 years using computers (and loving linux since 13!!) i did use SU to elevate me to SuperUser.

Settings -> Applications -> Manage Applications
Go to the launcher that you made default and click the 'Clear defaults' button.
---------- Post added at 09:24 AM ---------- Previous post was at 09:23 AM ----------
But you may be looking for something more advanced as it sounds like you may have deleted/removed the application?

clear defaults for the current launcher is not available, greyed out. I wonder if the LGhome2.apk and obex need to be signed or something. i am stumped.
Here's what i have done so far:
copied the LGHome2.apk and LGHome2.obex to the /system/apps/ directory
changed permissions and ownership to the same as other files in the directory
tried renaming them to com.lge.launcher2.apk and com.lge.launcher2.obex, no change.
pm enable lghome2 -f
and
pm install lghome2 -f
pm enable com.lge.launcher2 -f
and
pm install com.lge.launcher2 -f
I went as far as setting the /system and /system/app to Read/Write for the install.
All i get is:
pm install LGHome2
pkg: LGHome2
Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]
i'm outta my scope now, HELP!?!

[Q] Copying files to /system | S-ON | HTC One X

I have rooted my HTC One X and want to copy files in /system/xbin folder. My phone shows S-ON. And Eclipse is not able to copy files to /system and adb push from shell is also not working. Is there a way I can copy files to /system/xbin?
I am running stock ROM.
My phone is NOT associated with any vendor.

adb remount
adb push filename /system/xbin
Sent from my HTC One X

You can also use es file explorer and go into the options tick up to root and the request root and then tick mount as r/w.
Then just move files as you will.
Sent from my HTC One X using XDA Premium HD app

realunited123 said:
adb remount
adb push filename /system/xbin
Sent from my HTC One X
Click to expand...
Click to collapse
The above way does not seem to work. Whenever I use adb remount(or adb mount) it says operation not permitted and I am trying to this from root privileges
My OS is :- Ubuntu 12.04
ADB(platform-tools) -> Rev 20
If you need anything more please ask me .

Additional Question
treebill said:
You can also use es file explorer and go into the options tick up to root and the request root and then tick mount as r/w.
Then just move files as you will.
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
First of all thanx it worked. I think I will have to live with this way A ADB/Eclipse based would have been cool
Will the files moved from SDcard to phones root in anyway lose and privileges(like losing executable)? If yes, please suggest a way to restore it.

KillerTheLord said:
The above way does not seem to work. Whenever I use adb remount(or adb mount) it says operation not permitted and I am trying to this from root privileges
My OS is :- Ubuntu 12.04
ADB(platform-tools) -> Rev 20
If you need anything more please ask me .
Click to expand...
Click to collapse
When doing adb shell su do you get any toast notification on your phone? Or does it just say denied ?
Strange it works perfectly here Also are you using SuperSU or any other superuser app?
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
KillerTheLord said:
First of all thanx it worked. I think I will have to live with this way A ADB/Eclipse based would have been cool
Will the files moved from SDcard to phones root in anyway lose and privileges(like losing executable)? If yes, please suggest a way to restore it.
Click to expand...
Click to collapse
Yes you need to change the permissions after moving from sdcard. Use Root Explorer(Long press on the file--> Change permissions)

realunited123 said:
When doing adb shell su do you get any toast notification on your phone? Or does it just say denied ?
Strange it works perfectly here Also are you using SuperSU or any other superuser app?
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
Yes you need to change the permissions after moving from sdcard. Use Root Explorer(Long press on the file--> Change permissions)
Click to expand...
Click to collapse
I am using SuperSU as Super User App. And I think I am doing something wrong here. You mentioned about adb shell su. I think I might be wrong here. Here is how I tried to execute the command.
[email protected]: <path to platformtools> ./adb remount
remount failed: Operation not permitted
do I have to raise ADB shell to SU level. If yes, how?

KillerTheLord said:
I am using SuperSU as Super User App. And I think I am doing something wrong here. You mentioned about adb shell su. I think I might be wrong here. Here is how I tried to execute the command.
[email protected]: <path to platformtools> ./adb remount
remount failed: Operation not permitted
do I have to raise ADB shell to SU level. If yes, how?
Click to expand...
Click to collapse
Strange. Are you using the stock kernel ? If that is the case then it does not have insecure adbd (ro.secure=0) so remount will not work. Try a custom kernel.
Does adb has SU permissions from recovery ? Try booting into recovery, mounting the system partitions and try to push something from adb. Check the SuperSU app to update binary but that should not be a problem.

realunited123 said:
Strange. Are you using the stock kernel ? If that is the case then it does not have insecure adbd (ro.secure=0) so remount will not work. Try a custom kernel.
Does adb has SU permissions from recovery ? Try booting into recovery, mounting the system partitions and try to push something from adb. Check the SuperSU app to update binary but that should not be a problem.
Click to expand...
Click to collapse
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.

KillerTheLord said:
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
Click to expand...
Click to collapse
I guess you are using stock kernel then. Try franco's or faux's kernel.
adb remount wont work from os on stock boot.img.
After rebooting into recovery go to mounts and storage-->mount /system and then push something from adb. See if that works.

KillerTheLord said:
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
Click to expand...
Click to collapse
I think this app does exactly what you want :
http://forum.xda-developers.com/showthread.php?t=1687590

realunited123 said:
I guess you are using stock kernel then. Try franco's or faux's kernel.
adb remount wont work from os on stock boot.img.
After rebooting into recovery go to mounts and storage-->mount /system and then push something from adb. See if that works.
Click to expand...
Click to collapse
Well this didn't work either. I hope to switch to some other ROM in future(I hate HTC Sense ). But as of now Root Explorer did the job. I mounted my sdcard and copied files to it and used Root Explorer to move files to /system and then changed permissions.
Thanks for help it really made it easy .

make sure your path devs are oke for su.
in terminal run:
sudo su
adb kill-server
adb devices
you should see your HOX HTxxxxx nr.
and here you should be able to connect eclipse to HOX by adb.

NikMel said:
make sure your path devs are oke for su.
in terminal run:
sudo su
adb kill-server
adb devices
you should see your HOX HTxxxxx nr.
and here you should be able to connect eclipse to HOX by adb.
Click to expand...
Click to collapse
The problem was not accessing the device using ADB. The problem was I was not able to write to root system. ES Explorer and Root Explorer both did the job for me. I will be putting the final instructions for the process(detailed ones) soon.

Instructions onw how to copy files to root file system on HTC One X with S-ON
1) Unlock and Root your phone. Follow instructions below
http://www.youtube.com/watch?v=gIeq8Jx28cs
and then
http://www.youtube.com/watch?v=80lMHUgxwww
2) Install ES Explorer(File Manager) Link :- https://play.google.com/store/apps/details?id=com.estrongs.android.pop&hl=en
3) Connect device to computer(even if it is not recognized by ADB/Computer)
4) In Phone select Disk drive option. Now the phone's storage will be mounted on your computer as removable device.
5) Copy the files you want to send to phone's root system to any folder here.
6) Change phone's mode to charge only and wait for 2-3 secs(let phone remount sdcard)
7) Open ES Explorer and open menu(those 3 dots at bottom and select Settings)
8) Tick the following options
Up to Root
Root Explorer
Mount File System
9) A dialog box for permission will open Grant it.
10) Now copy files from /sdcard/<Folder where u put files> to where ever you want o copy files to.
11) Long press on file to change permissions and stuff.
Post here if you are stuck someone will surely help you.

Boot Animation Help

Could anyone help me out? I wanted to use this bootanimation i edited from a cm10 rom. Using the CM10 file manager, when I attempt to move the file it tells me "the operation is not permitted in current folder." When I use ES File manager it tells me that the move failed. Ive tried changing permissions on the file but it tells me permission change failed. I am rooted and have enabled root access on the file managers. I've also tried to preview the bootanimation using Rom Toolbox Pro but it says "failed loading the animation."
I have also attempted to use adb to push the file. I go into adb and first thing I do is make sure my device is found with "adb devices" then I do
adb shell
su
adb push bootanimation.zip /system/media/bootanimation.zip <--- at this step it tells me there are no devices even though doing "adb devices" shows my device.
Is this a problem with my bootanimation or something else entirely? Not sure what it could be with my phone, Im currently on CM10.0. Can anyone please help?

anyone??

Have you tried moving it using root explorer app?
Sent from my SGH-T999 using xda app-developers app

Does adb shell, su give adb root access?
Try
Abd root is a command and will restart adb in root. Try that instead
Sent from my SGH-T999 using xda premium
---------- Post added at 04:10 PM ---------- Previous post was at 04:02 PM ----------
Oh, it's because adb shell runs adb inside ur phone, so you can't push the file from your computer. Don't so adb shell. Just so
Adb devices #check ur device is there
Adb root
Adb push bootanimation.zip /system/media
Sent from my SGH-T999 using xda premium

dudds4 said:
Does adb shell, su give adb root access?
Try
Abd root is a command and will restart adb in root. Try that instead
Sent from my SGH-T999 using xda premium
---------- Post added at 04:10 PM ---------- Previous post was at 04:02 PM ----------
Oh, it's because adb shell runs adb inside ur phone, so you can't push the file from your computer. Don't so adb shell. Just so
Adb devices #check ur device is there
Adb root
Adb push bootanimation.zip /system/media
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
thanks I will try this when I get home. I am still wondering why I cant change permissions or move files using es file manager or the CM file manager? They both have SU access

Best method is root explorer
Zephyron said:
thanks I will try this when I get home. I am still wondering why I cant change permissions or move files using es file manager or the CM file manager? They both have SU access
Click to expand...
Click to collapse

I believe those other file managers, even with SU, still won't let you write to the system folder. Root Explorer has an option to use it as read only or read write.

dudds4 said:
Does adb shell, su give adb root access?
Try
Abd root is a command and will restart adb in root. Try that instead
Sent from my SGH-T999 using xda premium
---------- Post added at 04:10 PM ---------- Previous post was at 04:02 PM ----------
Oh, it's because adb shell runs adb inside ur phone, so you can't push the file from your computer. Don't so adb shell. Just so
Adb devices #check ur device is there
Adb root
Adb push bootanimation.zip /system/media
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Just tried this and it says "failed to copy 'bootanimation.zip' to '/system/media/bootanimation.zip' : read-only file system.
Romcrazguy said:
Best method is root explorer
Click to expand...
Click to collapse
CrazyCharlie said:
I believe those other file managers, even with SU, still won't let you write to the system folder. Root Explorer has an option to use it as read only or read write.
Click to expand...
Click to collapse
Just tried Root Explorer and it still gives me the same error message when I try to move it "cannot move because file-system is read-only" and when I attempt to change permissions it gives me this error "permission change was not successful, please note that some file systems (e.g. sd card) do not allow permission changes"
I am at a complete loss as to why I cannot change the permissions for my files even though I was able to do it before in the past (same sd card). Anyone know a solution to this problem?

To make it easier for you just go to YouTube and click on change boot animation root explorer you will see detailed instructions
Hit thanks if this helps
My ParanoidKang Android Tmo S3

Okay.. so I figured out why I couldnt replace the boot animation. I used ES File manager to mount the sdcard as r/w and it worked after. Now Im faced with the problem of getting a blank boot animation. When I restart my phone it just shows a blackscreen as my boot animation until it loads into the OS. Could someone mind checking my bootanimation zip and let me know if I have done anything wrong?

[GUIDE][ROOT] Blu Dash 3.5 d170 - Help with recovery and root

Update: New guide is in post # 122
http://forum.xda-developers.com/showthread.php?p=40433602#post40433602
The guide is in post # 98
http://forum.xda-developers.com/showthread.php?p=39362805#post39362805
Hello,
I have a Blu Dash 3.5 and would like to install clockworkmod recovery and enable root access, but so far have not found anything. Could you help me?
thank you

I tried using SuperOneClick, Gingerbreak, zroot but all without success.
Anyone have any other option?

_ _

I managed to set up the android SDK on ubuntu but I get permission denied message when trying to copy the files to the /system
I suppose I have to remount the partition in RW to be able to put the files but no idea how to do this.

_ _

fenrixarena said:
Well you can't without it being rooted, right now I just don't care about it anymore it's just a phone, & $30 isn't worth just freeing up some space. No guarantee that will make it run smoother without crashes either, that could just be a result of interface, so a bit of speed don't seem worth it to me, I have my own ringtones with ringdroid so I'm happy.
Everything having to do with extracting the boot.img requires it to be rooted otherwise I know enough about enough crapola already I could make that all spiffy and zabam if I wanted. I would just literally edit all the img files and provide a simple update.zip given I could get signing to work!
unfortunately I get nothing from fastboot at all, not sure it would help though. oem unlock stuff is all I recall about that besides it being a great wau to flash images to the phone
let me know if you make any progress, I'll put in my effort if you do anything at all that intices me to find a path to progress
Click to expand...
Click to collapse
fenrixarena, hope you get to find any progress on rooting this phone. I also agree with you that it is no worth the time or effort with this kind of phone but I think that the challenge is interesting . In my case I have no idea on how you may root it but I am sure it is possible i guess it all in find another compatible boot.img that can be rooted, right?
Regards,

- -

_ _

What is the address of the site that charges $ 30? We can verify that other users would like to do and split the cost ...

I managed to make root ...
I found the CWM recovery and stock recovery for Qsmart.
I was very curious if it would work in BLU and ended up installing the CWM with fastboot. It did not work, the screen just stays with the BLU and not access the recovery.
Then I installed stock recovery and did not work ...
But I realized that Windows recognized the device connected and I recognized two units with unsupported format.
then returned to the prompt and saw that the ADB was working. I used the command 'adb shell' and to my surprise was how the cursor #
So without wasting time already put su and busybox in /system/ bin and superuser.apk in /system/app, I changed the permissions and restarted the phone. And the root was working perfectly. :victory:
Only one problem, I do not have the recovery installed.
I wonder how I can help you to make root without losing recovery

>>

I use Windowns 7 Pro x64 bits.
I installed the drivers in the SuperOneClick version 2.3.3.
With the drivers installed could use fastboot and adb command.
Turning on the phone + vol - access mode fastboot / bootloader
It would be good to get root without losing the recovery. Because we need him to compile a clockworkmod recovery.
I used the romdump and got the following files:
https://docs.google.com/file/d/0B5rQL4bfhfPRZXhhZkg1Mkx5SHc/edit?usp=sharing
I used the mkfs.yaffs2 to convert the file system.tar for system.img
https://docs.google.com/file/d/0B5rQL4bfhfPRMGdaNnQ4b1RwclU/edit?usp=sharing
This system.img would function on another device?

okay, I am having one problem, what did you type for the permissions?
I've got superuser.apk pushed and the su in the /system/bin but when i try to chmod 777 it returns to -r- after I reboot!
Here's howto manually back up now that I have recovery adb root:
cat /proc/mtd
Then just cat (mtd#) > /sdcard/(image.img)
You can restore via fastboot flash

fenrixarena said:
okay, I am having one problem, what did you type for the permissions?
I've got superuser.apk pushed and the su in the /system/bin but when i try to chmod 777 it returns to -r- after I reboot!
Here's howto manually back up now that I have recovery adb root:
cat /proc/mtd
Then just cat (mtd#) > /sdcard/(image.img)
You can restore via fastboot flash
Click to expand...
Click to collapse
you get root access in adb shell?
send su to /system/bin with permission 6755.
busybox to /system/bin with permission 755.
and superuser.apk to /system/app with 644.
reboot your phone
then download terminal emulator on your phone and enter the command su
if the cursor change to # worked

erickreisbr said:
you get root access in adb shell?
send su to /system/bin with permission 6755.
busybox to /system/bin with permission 755.
and superuser.apk to /system/app with 644.
reboot your phone
then download terminal emulator on your phone and enter the command su
if the cursor change to # worked
Click to expand...
Click to collapse
These are actually good news... Right on!!! Cheers if you manage to root Blu Dash 3.5 :victory:
Can someone guide me on how I can Root my phone? What adb tools do i need?
Regards

az0ik said:
These are actually good news... Right on!!! Cheers if you manage to root Blu Dash 3.5 :victory:
Can someone guide me on how I can Root my phone? What adb tools do i need?
Regards
Click to expand...
Click to collapse
I can upload the cwm.img & adb I used + fastboot. Not all adb.exe will recognize the phone. Also drivers from qsmart for adb bridge.
1 boot holding vol down + power (about 15 sec.)
Fastboot flash recovery cwm.img
Then turn phone off.
Boot holding vol UP + Power (about 15 sec)
Adb push su /system/bin
Adb push busybox /system/bin
Adb push superuser.apk /system/app
adb shell
~# chmod 6755 /system/bin/su
~# chmod 755 /system/bin/busybox
~# chmod 644 /system/app/superuser.apk
reboot your phone
terminal emulator - su
permission granted
IT WORKED!
---------- Post added at 02:21 AM ---------- Previous post was at 02:00 AM ----------
sorry, tomorrow I will upload a zip with the img i used and so forth all in one zip so you can root with that, unless it's here by someone else by then I gotta work!

fenrixarena said:
I can upload the cwm.img & adb I used + fastboot. Not all adb.exe will recognize the phone. Also drivers from qsmart for adb bridge.
1 boot holding vol down + power (about 15 sec.)
Fastboot flash recovery cwm.img
Then turn phone off.
Boot holding vol UP + Power (about 15 sec)
Adb push su /system/bin
Adb push busybox /system/bin
Adb push superuser.apk /system/app
adb shell
~# chmod 6755 /system/bin/su
~# chmod 755 /system/bin/busybox
~# chmod 644 /system/app/superuser.apk
reboot your phone
terminal emulator - su
permission granted
IT WORKED!
---------- Post added at 02:21 AM ---------- Previous post was at 02:00 AM ----------
sorry, tomorrow I will upload a zip with the img i used and so forth all in one zip so you can root with that, unless it's here by someone else by then I gotta work!
Click to expand...
Click to collapse
Thank you so much Fenrixarena!! You are awesome :good::good::good:. I still can believe it, i thought it was a lost hope... I really appreciate for uploading the files I am patient enough to wait another day

Follow the ADB and the recovery I've used.
The drivers installed by SuperOneClick, but have these here:
32 bits - http://www.mediafire.com/?21na032gnzbfza2
64 bits - http://www.mediafire.com/?1hrwo325cb1ej2w

Fx

fenrixarena said:
interesting, I got a cwm4s12.img that's larger(4.51) and because of having a 64bit laptop without 32bit support I had to use a smaller ADB (158kb) to be able to recognize the phone and only on regular usb debugging does superoneclick install drivers which was useless since I needed the drivers to work in recovery.
If those files don't work for you I will upload mine
I got my files from foreign thread, and since I download so many versions and custom versions of programs like adb I'm not sure where it came from !!
oh, and he rooted the phone first, I only did it on a more bothersome platform.
Click to expand...
Click to collapse
the root worked on your phone?
Now we need a recovery. I'm trying to learn how to compile cwm, but it is very complicated.

Solved - TWRP Error "failed to mount system"

I have tried installing TWRP on my Pixel XL. I have tried the newest version 3.3.1.0 img and older ones. I boot twrp and then try to install the zip file of which I've tried newer and older versions. And get the following error.
This happens even if I try to install magisk zip.

After this error, I rebooted into recovery by accident with adb. And it booted into TWRP! Apparently the installation of TWRP worked. I then reinstalled TWRP and did not receive the error anymore. And was able to install Magisk.

Got this on and off too. Eventually became permanent. Have to open an ADB shell and umount /v and umount /s every time I twrp now. I think it's an incompatibility between recent OTA image and twrp.

jeffcookio said:
Got this on and off too. Eventually became permanent. Have to open an ADB shell and umount /v and umount /s every time I twrp now. I think it's an incompatibility between recent OTA image and twrp.
Click to expand...
Click to collapse
Can you expand on the open ADB shell? I can't seem to get it working.

IlyaKol said:
Can you expand on the open ADB shell? I can't seem to get it working.
Click to expand...
Click to collapse
Sure. Once you have recovery up and the phone plugged in via USB, run
Code:
adb shell
. Then, execute
Code:
umount -v /v; umount -v /s;
from the shell that opens up. Do this before doing anything else and TWRP will remount the vendor and system partitions when needed without issue. If you run some commands prior to this, they may fail completely or partially due to inability to mount the vendor or system partitions. It's pretty annoying.
In some cases, you may need to correct the system mount by doing a bind mount as described at GitHub wuxianlin/android_device_oneplus_enchilada issues #2 (not allowed to post a link as I don't yet have 10 posts), but I've found I usually don't have to do this if I unmount the partitions right away before doing anything else.

That code doesn't work for me. I get a error saying no such file or directory
---------- Post added at 02:52 PM ---------- Previous post was at 02:52 PM ----------
jeffcookio said:
Sure. Once you have recovery up and the phone plugged in via USB, run
Code:
adb shell
. Then, execute
Code:
umount -v /v; umount -v /s;
from the shell that opens up. Do this before doing anything else and TWRP will remount the vendor and system partitions when needed without issue. If you run some commands prior to this, they may fail completely or partially due to inability to mount the vendor or system partitions. It's pretty annoying.
In some cases, you may need to correct the system mount by doing a bind mount as described at GitHub wuxianlin/android_device_oneplus_enchilada issues #2 (not allowed to post a link as I don't yet have 10 posts), but I've found I usually don't have to do this if I unmount the partitions right away before doing anything else.
Click to expand...
Click to collapse
That code doesn't work for me. I get a error saying no such file or directory

TheSayaMan said:
That code doesn't work for me. I get a error saying no such file or directory
---------- Post added at 02:52 PM ---------- Previous post was at 02:52 PM ----------
That code doesn't work for me. I get a error saying no such file or directory
Click to expand...
Click to collapse
I got it to work. The correct code is umount -a /v; umount -b /s;

TheSayaMan said:
That code doesn't work for me. I get a error saying no such file or directory
---------- Post added at 02:52 PM ---------- Previous post was at 02:52 PM ----------
That code doesn't work for me. I get a error saying no such file or directory
Click to expand...
Click to collapse
?* Most likely you don't have anything mounted at those locations then and your error is something else.
This has become less of an issue as Magisk has been updated to understand the system-as-root mountpoints that are now required in Android 10. TWRP itself hasn't yet been updated but the Magisk install script seems to manage OK now.
I'd advise against `umount -a` that another poster shared since that's liable to unmount everything. Rather, check your mountpoints with mount -v and unmount the system and vendor partitions at whatever their respective mountpoints end up being.

Has anyone had any luck booting twrp onto their Pixel 3 XL my sd wont mount or it cant decrypt