Database Info

[Q] Fresh ROM for Evo Shift 4G: Keeps Resetting

I've installed Fresh ROM on my Evo Shift 4G. It worked for about a week, then the GPS stopped working (a known bug with this device and Gingerbread). I restarted the device as normal, and when it came back up all my downloaded apps and the Market were gone, and the device was in that strange indeterminate state where I'm both synced to a Gmail account and not at the same time (the Setup app appears in the Apps folder). Signing in doesn't help.
I rebooted into Clockwork Recovery (3.2.0.1), wiped data/factory reset, wiped the cache, wiped dalvik, and installed Fresh ROM again.
Once that was complete and booted, I signed in, attempted to install an app and the phone reset. There's no file manager installed nor terminal app so I can't delete things by bash. I connected over USB and tried to adb shell in, but that caused the phone to reset.
I'm stuck. Clearly something has not been properly wiped prior to installing Fresh ROM.
What do I need to do to get out of this loop?

SoopahMan said:
I've installed Fresh ROM on my Evo Shift 4G. It worked for about a week, then the GPS stopped working (a known bug with this device and Gingerbread). I restarted the device as normal, and when it came back up all my downloaded apps and the Market were gone, and the device was in that strange indeterminate state where I'm both synced to a Gmail account and not at the same time (the Setup app appears in the Apps folder). Signing in doesn't help.
I rebooted into Clockwork Recovery (3.2.0.1), wiped data/factory reset, wiped the cache, wiped dalvik, and installed Fresh ROM again.
Once that was complete and booted, I signed in, attempted to install an app and the phone reset. There's no file manager installed nor terminal app so I can't delete things by bash. I connected over USB and tried to adb shell in, but that caused the phone to reset.
I'm stuck. Clearly something has not been properly wiped prior to installing Fresh ROM.
What do I need to do to get out of this loop?
Click to expand...
Click to collapse
Sounds like you either had a bad Flash, a bad Download, or both. So redownload the Rom you choose, then Clear and Flash your device according to THESE INSTRUCTIONS .

Thanks for the response. I downloaded the ROM again and ran a check - identical to the file I downloaded previously. So, if the ROM is the culprit, then the latest version of Fresh ROM for Evo Shift does not work (4.1.1).
I followed the instructions linked, wiping the cache and dalvik-cache twice (why?), and wiping system etc prior to installing the ROM.
I'm running into the exact same issues as before - I can't install anything from the Market, and the phone resets if I connect it to a computer over USB. When it resets, it resets multiple times and when it comes back up the 4G no longer works.
If I rerun the above instructions, the 4G works again, but I'm stuck back in this loop - can't use the Market or connect it over USB or it will reset, so forth.
Could Fresh ROM 4.1.1 for Evo Shift be bad? I still suspect the real problem is something is not sufficiently wiped or setup prior to install.
In case it might help, here's an ls -al after installing Fresh Rom 4.1.1 on my phone (an HTC Evo Shift 4G after following the above install instructions).
/
drwxr-xr-x 2 root root 0 Jan 17 07:39 boot
drwxr-xr-x 4 root root 1024 Jan 17 07:41 cache
drwxrwx--x 2 root root 0 Jan 1 1970 data
drwxr-xr-x 2 root root 0 Jan 17 07:39 datadata
-rw-r--r-- 1 root root 3462 Jan 1 1970 default.prop
drwxr-xr-x 12 root root 3060 Jan 17 07:39 dev
drwxr-xr-x 2 root root 0 Jan 17 07:39 emmc
drwxr-xr-x 2 root root 0 Jan 17 07:39 etc
-rwxr-x--- 1 root root 94372 Jan 1 1970 init
-rwxr-x--- 1 root root 899 Jan 1 1970 init.rc
dr-xr-xr-x 79 root root 0 Jan 1 1970 proc
drwxr-xr-x 4 root root 0 Jan 1 1970 res
drwx------ 2 root root 0 May 15 2011 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 Jan 17 07:39 sd-ext
drwxrwxrwx 78 root root 32768 Jan 1 1970 sdcard
drwxr-xr-x 18 root root 0 Jan 17 07:39 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxr-xr-x 2 root root 0 Jan 17 07:45 tmp
-rw-r--r-- 1 root root 0 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 4027 Jan 1 1970 ueventd.rc
-rw-r--r-- 1 root root 987 Jan 1 1970 ueventd.speedy.rc
/data
(empty)
/system
drwxr-xr-x 2 root root 0 Jan 1 1970 bin
/system/bin
(empty)
/sys
drwxr-xr-x 2 root root 0 Jan 17 07:53 android_camera
drwxr-xr-x 2 root root 0 Jan 17 07:53 android_camera_awb_cal
drwxr-xr-x 2 root root 0 Jan 17 07:53 android_touch
drwxr-xr-x 2 root root 0 Jan 17 07:53 block
drwxr-xr-x 2 root root 0 Jan 17 07:39 board_properties
drwxr-xr-x 9 root root 0 Jan 17 07:53 bus
drwxr-xr-x 2 root root 0 Jan 17 07:53 camera_led_status
drwxr-xr-x 47 root root 0 Jan 17 07:53 class
drwxr-xr-x 4 root root 0 Jan 17 07:53 dev
drwxr-xr-x 10 root root 0 Jan 17 07:39 devices
drwxr-xr-x 2 root root 0 Jan 17 07:53 firmware
drwxr-xr-x 3 root root 0 Jan 17 07:53 fs
drwxr-xr-x 6 root root 0 Jan 17 07:53 kernel
drwxr-xr-x 62 root root 0 Jan 17 07:53 module
drwxr-xr-x 2 root root 0 Jan 17 07:53 power
drwxr-xr-x 2 root root 0 Jan 17 07:53 systemlog
I can post more or other diagnostics if others have something to recommend. Really stuck here.

Is it odd that /sd-ext is at root and not located on the SD card, and a directory not a symlink?

Now that you have 10 posts you should try posting your questions in the thread for flipz's rom.So the dev can help and maybe anyone else that is running this rom. Also have you tried the a2sd remove command adb shell or from terminal emulator? See if that helps.
Sent from my PG06100 using Tapatalk

A bit more to isolate the problem:
If the phone resets (due to attempting an install from the Market or plug in from USB), 4G fails - but if I restart the phone at that point, when it reboots 4G works again. So 4G appears to be fine, it's the resets that are at the core of the issue.
I shutdown, removed the SD card, booted, and attempted to install an app and got the same reset, so it's not the SD card - it's definitely a problem somewhere on internal storage.
What else do I need to clear to clear this up?
Fresh ROM's pages say to look in /data/app and /system/app for a place where an app already exists that would cause a conflict.
Here's /data after booting the ROM and setting up a Gmail account:
lrwxrwxrwx 1 root root 14 Jan 17 07:54 app -> /system/sd/app
lrwxrwxrwx 1 root root 22 Jan 17 07:54 app-private -> /system/sd/app-private
drwx------ 5 system system 1024 Jan 6 1980 backup
drwxrwx--x 2 system system 14336 Jan 17 16:25 dalvik-cache
drwxrwx--x 161 system system 9216 Jan 17 07:57 data
drwxr-x--- 2 root log 1024 Jan 17 07:54 dontpanic
lrwxrwxrwx 1 root root 11 Jan 17 07:54 drm -> /data/local
-rw-r--r-- 1 root root 6134 Jan 6 1980 dta2sd.lg1
-rw-r--r-- 1 root root 6266 Jan 6 1980 dta2sd.lg2
-rw-r--r-- 1 root root 6266 Jan 6 1980 dta2sd.log
drwxrwxrwx 2 root root 1024 Jan 17 07:54 htcfs
drwxr-xr-x 4 root root 1024 Jan 17 07:42 jit
drwxrwx--x 4 shell shell 1024 Jan 17 07:54 local
drwxrwx--- 2 root root 12288 Jan 17 07:41 lost+found
drwxrwx--t 10 system misc 1024 Jan 17 07:55 misc
drwx------ 2 root root 1024 Jan 6 1980 property
drwx------ 3 system system 1024 Jan 17 07:55 secure
drwxrwxr-x 9 system system 1024 Jan 17 17:48 system
drwxrwx--- 3 system system 1024 Jan 17 17:14 wimax
I'd like to know if app and app-private are as expected (they appear to be the result of the ROM install, since they were completely wiped prior to installing it). The app symlink is a strange one. It points to /system/sd/app, which I can't cd to. /system/sd I can cd to, and this is all it contains:
-rw-r--r-- 1 root root 17 Aug 1 2008 placeholder
A file named placeholder. What?
I'm starting to suspect apps2sd. None of the relevant partitioning steps are in those install instructions, and they appear to be specific to the apps2sd of CyanogenMod. Google's appears to support a DOS partition, while CyanogenMod's appears to only support an ext3 partition, which I do not have.
At the same time, removing the SD card didn't change things, so color me confused.

As suggested by FdxRider you should definately post up in the Rom thread. That way you can get help resolving the issue from others running the same Rom.

It was apps2sd.
To resolve this problem, I had to:
Reboot into ClockwordModRecovery
Connect the phone to a computer over USB
In Clockwork, choose Mount Storage and choose the last option, Mount USB.
Dump anything I wanted to keep off of the SD card (most importantly, the FreshRom zip file).
Then, back in Clockwork, Advanced>Partition SD
Choose a size (they recommend 1024M)
This wipes out everything on the SD card, creates a Linux partition for apps2sd to use, marks the rest as a Windows partition.
Wait till it's done, then, still from ClockworkModRecovery:
Wipe cache, dalvik cache, system, data
Factory reset
Now Mount USB again so you can copy the FreshRom zip back onto the Windows partition (the only part that will come up on a Windows machine).
Eject on the Windows machine to ensure the copy completes, Unmount in Clockwork.
Install the ROM again
Let it boot, restart
Setup my Google Account/Gmail user
And one final thing:
As it turns out ES File Explorer is pre-installed on this ROM. That means installing it from the Market will make the phone go crazy regardless of proper setup. But I am now able to install other apps just fine from the Market (at last).

reset loop NO clockwork until factory reset
I installed Fresh 4.1.1 on my shift 4g
I went to install ROM Manager got it downloaded and it reset the phone at install.
I even tried going to the website and installing it that way. Same results.
I can't get clockwork to work, when i hold the volume down and then press power nothing happens until i release the power button then it goes directly to the Fresh install.
PLEASE HELP!!!!
---------- Post added at 05:30 AM ---------- Previous post was at 05:09 AM ----------
I got the problem solved. I used the RRU and it walked me through a recovery, part of it was yanking the battery. DUH!

Gear2 Root

{
"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"
}
Root for Gear2 R380
Packed rootfs.img
NE5
R380XXU0BNE5rootfs_root.tar (Needs Gear 2 R380XXU0BNE5 installed)
NDD
R380XXU0BNDDrootfs_root.tar (Needs Gear 2 R380XXU0BNDD installed)
ND8
R380XXU0BND8rootfs_root.tar (Needs Gear 2 R380XXU0BND8 installed)
Gear2 NEO:
NE5
R381XXU0BNE5rootfs_root.tar (Needs Gear 2 NEO R381XXU0BNE5 installed)
Load into Odin and flash.
Done
Need sdb.exe from Tizen-SDK?
sdb.exe
What is this good for?
Disable camera sounds:
sdb root on
sdb shell mount -o remount,rw /
sdb shell mv /usr/share/sounds/mm-camcorder/ /usr/share/sounds/mm-camcorder_bak/
sdb shell mv /usr/apps/com.samsung.w-camera-app/res/sounds /usr/apps/com.samsung.w-camera-app/res/sounds_bak
sdb shell mount -o remount,ro /
Custom ringtones:
sdb root on
sdb push your_ringtone.ogg /opt/share/settings/Ringtones/
reboot watch
Keep in mind free diskspace is 80MB for /opt/ don't fill it up!

fibs said:
Root for Gear2 R380 (fw: R380XXU0BNDD)
Packed rootfs.img: http://www.mediafire.com/download/2wxvnezieg7025x/r380rootfs_root.tar
Load into Odin and flash.
Done
Click to expand...
Click to collapse
thx!
are the terminal commands needed after the flash?
would this also be ok for the new E5 release?

TML1504 said:
thx!
are the terminal commands needed after the flash?
would this also be ok for the new E5 release?
Click to expand...
Click to collapse
No, commands are not needed. It's just to show the version and howto check if it worked.
This will not work if E5 is installed since you will flash the whole root filesystem.

I can build for E5 if needed. Did not upgrade my watch yet..

fibs said:
I can build for E5 if needed. Did not upgrade my watch yet..
Click to expand...
Click to collapse
I appreciate your good work on this. Unfortunately I'm in the US and still stuck on ND8. As a suggestion, since you're going to build this for new ROMs as they come out, could you start adding the last three letters/numbers of the ROM to your tar files?

JimSmith94 said:
I appreciate your good work on this. Unfortunately I'm in the US and still stuck on ND8. As a suggestion, since you're going to build this for new ROMs as they come out, could you start adding the last three letters/numbers of the ROM to your tar files?
Click to expand...
Click to collapse
Thx, already included version build for the E5 .tar uploading right now. The sad part is that the only "useful" way to use the root access right now is to get rid of the camera sounds
But if you need root access to your ND8 I can upload.

fibs said:
Thx, already included version build for the E5 .tar uploading right now. The sad part is that the only "useful" way to use the root access right now is to get rid of the camera sounds
But if you need root access to your ND8 I can upload.
Click to expand...
Click to collapse
If you have easy access to ND8, that would be great. Otherwise I can wait for the newer builds to hit. I'll be upgrading as soon as I can anyway.

fibs said:
I can build for E5 if needed. Did not upgrade my watch yet..
Click to expand...
Click to collapse
Please, thx!

TML1504 said:
Please, thx!
Click to expand...
Click to collapse
I kept my first post updated. E5 added.

Can this be used with NEO as well?

mpogr said:
Can this be used with NEO as well?
Click to expand...
Click to collapse
i guess not, due to different hardware. although: perhaps it would work, because the hardware is very similar except the cam. depends on the partition layout, and that could be the same...
this is the partition layout of the gear one (with tizen), i guess "our" layout will be very similar...
lrwxrwxrwx 1 root root 15 Jun 3 07:32 boot -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Jun 3 07:32 bota0 -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jun 3 07:32 bota1 -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 15 Jun 3 07:32 csa -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Jun 3 07:32 csc -> ../../mmcblk0p13
lrwxrwxrwx 1 root root 16 Jun 3 07:32 fota -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Jun 3 07:32 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Jun 3 07:32 param -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Jun 3 07:32 ramdisk1 -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Jun 3 07:32 ramdisk2 -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 15 Jun 3 07:32 recovery -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Jun 3 07:32 reserved -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 16 Jun 3 07:32 rootfs -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 16 Jun 3 07:32 system -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 16 Jun 3 07:32 system-data -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Jun 3 07:32 user -> ../../mmcblk0p15
fibs said:
I kept my first post updated. E5 added.
Click to expand...
Click to collapse
thx again very much! worked flawlessly!
can you please provide the "sdb.exe" from the tizen-sdk as well?

TML1504 said:
this is the partition layout of the gear one (with tizen), i guess "our" layout will be very similar...
lrwxrwxrwx 1 root root 15 Jun 3 07:32 boot -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Jun 3 07:32 bota0 -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jun 3 07:32 bota1 -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 15 Jun 3 07:32 csa -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Jun 3 07:32 csc -> ../../mmcblk0p13
lrwxrwxrwx 1 root root 16 Jun 3 07:32 fota -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Jun 3 07:32 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Jun 3 07:32 param -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Jun 3 07:32 ramdisk1 -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Jun 3 07:32 ramdisk2 -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 15 Jun 3 07:32 recovery -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Jun 3 07:32 reserved -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 16 Jun 3 07:32 rootfs -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 16 Jun 3 07:32 system -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 16 Jun 3 07:32 system-data -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Jun 3 07:32 user -> ../../mmcblk0p15
Click to expand...
Click to collapse
Partition layout of Gear 2 is like this:
lrwxrwxrwx 1 root root 15 Jun 4 00:27 boot -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Jun 4 00:27 bota0 -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jun 4 00:27 bota1 -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 15 Jun 4 00:27 csa -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 16 Jun 4 00:27 csc -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 16 Jun 4 00:27 fota -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Jun 4 00:27 module -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 15 Jun 4 01:13 param -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 15 Jun 4 00:27 ramdisk1 -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Jun 4 00:27 ramdisk2 -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Jun 4 00:27 recovery -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 16 Jun 4 00:27 rootfs -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Jun 4 00:27 system -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Jun 4 00:27 system-data -> ../../mmcblk0p13
lrwxrwxrwx 1 root root 16 Jun 4 00:27 user -> ../../mmcblk0p14
It is different, but I have no idea how layout of gear neo looks like.
TML1504 said:
thx again very much! worked flawlessly!
can you please provide the "sdb.exe" from the tizen-sdk as well?
Click to expand...
Click to collapse
Sure, link will be added to main post.

This is to make a change in ringtone sound?

dansafe said:
This is to make a change in ringtone sound?
Click to expand...
Click to collapse
Is possible.
push your ringtones to: /opt/share/settings/Ringtones/
When in .ogg only filename will be displayed. When in .mp3 it will show up like ring.mp3
I think a reboot is needed to find your new ringtones in the list.
But keep in mind free diskspace is 80MB for /opt/ don't fill it up!

Super good work ! THX.

Ok, im a noob at watch rooting. Is there a special version of odin for the watch or a special way to do this? Does it wipe everything? All I wish to do is wipe the camera sounds.
Sent from my SM-N900T using Tapatalk

Safe to assume this won't work with the Neo? If it does awesome work. If not still awesome work lol.

Compusmurf said:
Ok, im a noob at watch rooting. Is there a special version of odin for the watch or a special way to do this? Does it wipe everything? All I wish to do is wipe the camera sounds.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
no special odin needed! i used 3.07
to enter download mode: press and hold the watch-button, when the watch reboots quickly press the button a few times, select download, then flash.
it does no wipe.
important: first flash the official rom, then the according rootfs from the first post.
enable usb debugging in watch settings
afterwards you need the sdb.exe, open a command prompt where the exe is located and enter the following commands:
sdb root on
sdb shell mount -o remount,rw /
sdb shell mv /usr/share/sounds/mm-camcorder/ /usr/share/sounds/mm-camcorder_bak/
sdb shell mv /usr/apps/com.samsung.w-camera-app/res/sounds /usr/apps/com.samsung.w-camera-app/res/sounds_bak
it worked perfectly for me!
---------- Post added at 05:53 PM ---------- Previous post was at 05:52 PM ----------
fogame said:
Safe to assume this won't work with the Neo? If it does awesome work. If not still awesome work lol.
Click to expand...
Click to collapse
neo would need a specific rootfs, otherwise the procedure is the same!

TML1504 said:
neo would need a specific rootfs, otherwise the procedure is the same!
Click to expand...
Click to collapse
Fantastic! Now I just need to find the rootfs lol. Someone will probably beat me to it.

This is to make a change in alerts sound?
btw. silent camera and change ringtones works verry good ! THX

[Q] TWRP Folder Permission Denied

Update: Fixed by
command !
Guys,
I am currently Running STOCK LRX21O.Rooted using Chainfire's AutoRoot and TWRP -2.8.1.0. I made backup but I am unable to access it using ES file explorer(with root option enabled). Also tried Root explorer but It just doesnt show the Folder itself.
When I boot into TWRP it shows the Backup folder there. So I tried to check it with adb to do a ls and it shows its there. I need to copy that folder to cloud just incase. I dont see permission issues. Plese suggest how to fix this ?
Code:
C:\Users\Zaibrockstar>adb shell ls -l /sdcard/
drwxrwx--- root sdcard_r 1971-01-05 22:48 Alarms
drwxrwx--x root sdcard_r 2014-11-12 21:00 Android
drwxrwx--- root sdcard_r 2014-11-12 23:29 DCIM
drwxrwx--- root sdcard_r 2014-11-13 08:44 Download
drwxrwx--- root sdcard_r 1971-01-05 22:48 Music
drwxrwx--- root sdcard_r 2014-11-12 21:34 Notifications
drwxrwx--- root sdcard_r 2014-11-12 23:26 Pictures
drwxrwx--- root sdcard_r 1971-01-05 22:48 Podcasts
drwxrwx--- root sdcard_r 1971-01-05 22:48 Ringtones
[B][U]lstat '/sdcard//TWRP' failed: Permission denied[/U][/B]
drwxrwx--- root sdcard_r 2014-11-13 09:27 backups
drwxrwx--- root sdcard_r 2014-11-12 21:32 baidu
drwxrwx--- root sdcard_r 2014-11-12 23:13 media
Code:
C:\Users\Zaibrockstar>adb shell ls -R /sdcard/
/sdcard/:
Alarms
Android
DCIM
Download
Music
Notifications
Pictures
Podcasts
Ringtones
[COLOR="Red"]TWRP[/COLOR]
backups
baidu
media
[B][COLOR="Red"]/sdcard//TWRP: Permission denied[/COLOR]
[/B]
Thanks
Zaib

http://forum.xda-developers.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749

Redmi Note 7 Pro with MIUI 11 in bootloop, as I chanded the dpi in developer option

I've increased the dpi in developer option and once I changed the dpi the phone screen turned black and the phone started to reboot, after each reboot it lands in recovery mode. Is there any way to take my phone out of this while preserving my data.
Is there any way to back up the data using adb sideload (MiPCSuite), or fastboot commands (or reinstall the MIUI 11.0.5.0 zip file if it helps).
My Phone runs latest MIUI 11 and usb debugging is enabled, (unfortunately oem unlocking is disabled)
Thankyou!
P.S: Changing dpi was perfectly fine in MIUI 10.

[email protected] said:
I've increased the dpi in developer option and once I changed the dpi the phone screen turned black and the phone started to reboot, after each reboot it lands in recovery mode. Is there any way to take my phone out of this while preserving my data.
Is there any way to back up the data using adb sideload (MiPCSuite), or fastboot commands (or reinstall the MIUI 11.0.5.0 zip file if it helps).
My Phone runs latest MIUI 11 and usb debugging is enabled, (unfortunately oem unlocking is disabled)
Thankyou!
P.S: Changing dpi was perfectly fine in MIUI 10.
Click to expand...
Click to collapse
Bl is locked??
Sent from my Redmi Note 7 Pro using XDA Labs

same problem with my mix mix2. accidentally changed dpi 600 to 6000. now phone stucked on bootloop, any way to revert back, somebody help me
thanks

Unlock bootloader using mi unlock tool. then flash the latest fastboot rom. Unlocking bootloader wipes internal storage also.

Vishal P said:
Unlock bootloader using mi unlock tool. then flash the latest fastboot rom. Unlocking bootloader wipes internal storage also.
Click to expand...
Click to collapse
i want my personal files too

iMesutOzil said:
i want my personal files too
Click to expand...
Click to collapse
No u cant. If bl is locked then use a deep flash cable to flash in edl mode using mi flash tool. Downlaod lattest fastboot rom from mi website and then flash it in edl mode.
Sent from my Redmi Note 7 Pro using XDA Labs

Same thing happened to my mi mix 3... big ****ing bug

If you set up ADB on your PC before the bootloop happened, you might still be able to enter adb shell when the phone is in the boot animation phase. Try that and if so, reset the DPI from ADB.
adb shell wm density reset
That should work.

I changed my dpi from default (392) to 411 on my POCO F1, MIUI 11, nothing happened.

Do NOT change the Smallest width / DPI to an absurd number. If you do, and if you don't have ADB enabled or you don't have an unlocked bootloader, there's no way to restore the default DPI nor is there a way to reset your phone to factory defaults (unless the built-in MIUI recovery has the option to wipe data).

hackermssharma said:
Bl is locked??
Sent from my Redmi Note 7 Pro using XDA Labs
Click to expand...
Click to collapse
Yupp

[email protected] said:
Yupp
Click to expand...
Click to collapse
So u have to now flash miui lattest fastboot rom using deep flash cable in edl mode.
Sent from my Redmi Note 7 Pro using XDA Labs

Bug
did anyone find w solutions except erase all data
for me i have adb but #wm density reset throw Permission error :crying::crying:
i really need to copy my files before wipe but can't find solution
going to /storage/emulated/0/ seems to have encrypted folders/files
HTML:
$adb shell ls -halt /storage/emulated/0/
total 39K
-rw-rw---- 1 root sdcard_rw 72 2020-02-03 00:35 FgiQtKyeKzw6kG+F1MzmSA
drwxrwx--x 22 root sdcard_rw 3.4K 2020-02-02 18:17 .
drwxrwx--x 2 root sdcard_rw 3.4K 2020-02-02 18:17 dKMxDxL7j7oMuXS0dTZLvD
drwxrwx--x 2 root sdcard_rw 3.4K 2020-01-31 12:06 wgQKDk,UYBX5+QCmtp3TgA
drwxrwx--x 5 root sdcard_rw 3.4K 2020-01-30 20:48 DWB,QUyj4QsWQDdjnD2TmC
-rw-rw---- 1 root sdcard_rw 74 2020-01-29 19:20 +Sa1tuwh8qDNX70,cXkG8A
drwxrwx--x 2 root sdcard_rw 3.4K 2020-01-29 19:20 ae60B1sKAy7DVYxwogwqSC
-rw-rw---- 1 root sdcard_rw 2 2020-01-29 19:20 r5PwopcfV04Svv5nJlDgDC
drwxrwx--x 3 root sdcard_rw 3.4K 2020-01-27 12:18 m,vKs+YZOwVf727Hnr5ENA
drwxrwx--x 5 root sdcard_rw 3.4K 2020-01-22 21:48 T0oYyqREd0bnaJ0UUPpXqC
drwxrwx--x 7 root sdcard_rw 3.4K 2020-01-18 22:24 Ru8BfHo31O0e5zQU1P9BYC
drwxrwx--x 9 root sdcard_rw 3.4K 2020-01-17 02:00 28oc9z9OmfErUWpCmQCKgB
drwxrwx--x 3 root sdcard_rw 3.4K 2020-01-16 23:00 D,hr3l9Fb6Yr2KCMjYMxeC
drwxrwx--x 3 root sdcard_rw 3.4K 2020-01-16 07:57 cRMXNSqqlqXji2+RIz1UfA
drwxrwx--x 2 root sdcard_rw 3.4K 2020-01-16 07:43 6YeHUpP585MuMASMaPH6KA
drwxrwx--x 3 root sdcard_rw 3.4K 2020-01-13 22:29 0cjhLjEMgL5o2Vubeumb3B
drwxrwx--x 3 root sdcard_rw 3.4K 2019-12-31 17:05 RqW9BJOAk6,u,RFRhe95PA
drwxrwx--x 2 root sdcard_rw 3.4K 2019-12-26 01:39 KMnWNXgD46Ld4wq+NNt0iA
drwxrwx--x 2 root sdcard_rw 3.4K 2019-12-16 03:26 E,cwkt4ZnQv4TKNdDoDwaA
drwxrwx--x 5 root sdcard_rw 3.4K 2019-12-15 17:33 wgsU61k+WwJUAOSkx6us3C
drwxrwx--x 3 root sdcard_rw 3.4K 2019-12-15 11:36 9LFK1i4G+RHy8asXFe7XpA
drwxrwx--x 3 root sdcard_rw 3.4K 2019-12-15 10:54 ,JRes9ZrBhL,YHcMCdFbVIlpkdN
drwxrwx--x 7 root sdcard_rw 3.4K 2019-12-15 10:43 MKbC4maFyMRpw7A4o1nH5D
drwxrwx--x 3 root sdcard_rw 3.4K 2019-12-13 17:17 1,lyeBF4+FXLquN8Bti5zC
drwx--x--x 4 root sdcard_rw 3.4K 2008-12-31 17:01 ..
HTML Code:
$adb shell du -sh 'storage/emulated/0/*'
4.0K storage/emulated/0/+Sa1tuwh8qDNX70,cXkG8A
7.0K storage/emulated/0/,JRes9ZrBhL,YHcMCdFbVIlpkdN
23K storage/emulated/0/0cjhLjEMgL5o2Vubeumb3B
3.9M storage/emulated/0/1,lyeBF4+FXLquN8Bti5zC
4.1M storage/emulated/0/28oc9z9OmfErUWpCmQCKgB
3.5K storage/emulated/0/6YeHUpP585MuMASMaPH6KA
22K storage/emulated/0/9LFK1i4G+RHy8asXFe7XpA
11K storage/emulated/0/D,hr3l9Fb6Yr2KCMjYMxeC
3.0M storage/emulated/0/DWB,QUyj4QsWQDdjnD2TmC
3.5K storage/emulated/0/E,cwkt4ZnQv4TKNdDoDwaA
4.0K storage/emulated/0/FgiQtKyeKzw6kG+F1MzmSA
3.5K storage/emulated/0/KMnWNXgD46Ld4wq+NNt0iA
2.6G storage/emulated/0/MKbC4maFyMRpw7A4o1nH5D
2.9M storage/emulated/0/RqW9BJOAk6,u,RFRhe95PA
10G storage/emulated/0/Ru8BfHo31O0e5zQU1P9BYC
8.2M storage/emulated/0/T0oYyqREd0bnaJ0UUPpXqC
3.5K storage/emulated/0/ae60B1sKAy7DVYxwogwqSC
27K storage/emulated/0/cRMXNSqqlqXji2+RIz1UfA
3.5K storage/emulated/0/dKMxDxL7j7oMuXS0dTZLvD
47M storage/emulated/0/m,vKs+YZOwVf727Hnr5ENA
4.0K storage/emulated/0/r5PwopcfV04Svv5nJlDgDC
465M storage/emulated/0/wgQKDk,UYBX5+QCmtp3TgA
645M storage/emulated/0/wgsU61k+WwJUAOSkx6us3C
i can read my density but not write i think USB debug (secure Security) is not enable .. is there a way to enable via adb in this stat !!!

killuadk said:
did anyone find w solutions except erase all data
for me i have adb but #wm density reset throw Permission error :crying::crying:
i really need to copy my files before wipe but can't find solution
going to /storage/emulated/0/ seems to have encrypted folders/files
$adb shell ls -halt /storage/emulated/0/total 39K-rw-rw---- 1 root sdcard_rw 72 2020-02-03 00:35 FgiQtKyeKzw6kG+F1MzmSAdrwxrwx--x 22 root sdcard_rw 3.4K 2020-02-02 18:17 .drwxrwx--x 2 root sdcard_rw 3.4K 2020-02-02 18:17 dKMxDxL7j7oMuXS0dTZLvDdrwxrwx--x 2 root sdcard_rw 3.4K 2020-01-31 12:06 wgQKDk,UYBX5+QCmtp3TgAdrwxrwx--x 5 root sdcard_rw 3.4K 2020-01-30 20:48 DWB,QUyj4QsWQDdjnD2TmC-rw-rw---- 1 root sdcard_rw 74 2020-01-29 19:20 +Sa1tuwh8qDNX70,cXkG8Adrwxrwx--x 2 root sdcard_rw 3.4K 2020-01-29 19:20 ae60B1sKAy7DVYxwogwqSC-rw-rw---- 1 root sdcard_rw 2 2020-01-29 19:20 r5PwopcfV04Svv5nJlDgDCdrwxrwx--x 3 root sdcard_rw 3.4K 2020-01-27 12:18 m,vKs+YZOwVf727Hnr5ENAdrwxrwx--x 5 root sdcard_rw 3.4K 2020-01-22 21:48 T0oYyqREd0bnaJ0UUPpXqCdrwxrwx--x 7 root sdcard_rw 3.4K 2020-01-18 22:24 Ru8BfHo31O0e5zQU1P9BYCdrwxrwx--x 9 root sdcard_rw 3.4K 2020-01-17 02:00 28oc9z9OmfErUWpCmQCKgBdrwxrwx--x 3 root sdcard_rw 3.4K 2020-01-16 23:00 D,hr3l9Fb6Yr2KCMjYMxeCdrwxrwx--x 3 root sdcard_rw 3.4K 2020-01-16 07:57 cRMXNSqqlqXji2+RIz1UfAdrwxrwx--x 2 root sdcard_rw 3.4K 2020-01-16 07:43 6YeHUpP585MuMASMaPH6KAdrwxrwx--x 3 root sdcard_rw 3.4K 2020-01-13 22:29 0cjhLjEMgL5o2Vubeumb3Bdrwxrwx--x 3 root sdcard_rw 3.4K 2019-12-31 17:05 RqW9BJOAk6,u,RFRhe95PAdrwxrwx--x 2 root sdcard_rw 3.4K 2019-12-26 01:39 KMnWNXgD46Ld4wq+NNt0iAdrwxrwx--x 2 root sdcard_rw 3.4K 2019-12-16 03:26 E,cwkt4ZnQv4TKNdDoDwaAdrwxrwx--x 5 root sdcard_rw 3.4K 2019-12-15 17:33 wgsU61k+WwJUAOSkx6us3Cdrwxrwx--x 3 root sdcard_rw 3.4K 2019-12-15 11:36 9LFK1i4G+RHy8asXFe7XpAdrwxrwx--x 3 root sdcard_rw 3.4K 2019-12-15 10:54 ,JRes9ZrBhL,YHcMCdFbVIlpkdNdrwxrwx--x 7 root sdcard_rw 3.4K 2019-12-15 10:43 MKbC4maFyMRpw7A4o1nH5Ddrwxrwx--x 3 root sdcard_rw 3.4K 2019-12-13 17:17 1,lyeBF4+FXLquN8Bti5zCdrwx--x--x 4 root sdcard_rw 3.4K 2008-12-31 17:01 ..HTML Code:$adb shell du -sh 'storage/emulated/0/*'4.0K storage/emulated/0/+Sa1tuwh8qDNX70,cXkG8A7.0K storage/emulated/0/,JRes9ZrBhL,YHcMCdFbVIlpkdN23K storage/emulated/0/0cjhLjEMgL5o2Vubeumb3B3.9M storage/emulated/0/1,lyeBF4+FXLquN8Bti5zC4.1M storage/emulated/0/28oc9z9OmfErUWpCmQCKgB3.5K storage/emulated/0/6YeHUpP585MuMASMaPH6KA22K storage/emulated/0/9LFK1i4G+RHy8asXFe7XpA11K storage/emulated/0/D,hr3l9Fb6Yr2KCMjYMxeC3.0M storage/emulated/0/DWB,QUyj4QsWQDdjnD2TmC3.5K storage/emulated/0/E,cwkt4ZnQv4TKNdDoDwaA4.0K storage/emulated/0/FgiQtKyeKzw6kG+F1MzmSA3.5K storage/emulated/0/KMnWNXgD46Ld4wq+NNt0iA2.6G storage/emulated/0/MKbC4maFyMRpw7A4o1nH5D2.9M storage/emulated/0/RqW9BJOAk6,u,RFRhe95PA10G storage/emulated/0/Ru8BfHo31O0e5zQU1P9BYC8.2M storage/emulated/0/T0oYyqREd0bnaJ0UUPpXqC3.5K storage/emulated/0/ae60B1sKAy7DVYxwogwqSC27K storage/emulated/0/cRMXNSqqlqXji2+RIz1UfA3.5K storage/emulated/0/dKMxDxL7j7oMuXS0dTZLvD47M storage/emulated/0/m,vKs+YZOwVf727Hnr5ENA4.0K storage/emulated/0/r5PwopcfV04Svv5nJlDgDC465M storage/emulated/0/wgQKDk,UYBX5+QCmtp3TgA645M storage/emulated/0/wgsU61k+WwJUAOSkx6us3C
i can read my density but not write i think USB debug (secure Security) is not enable .. is there a way to enable via adb in this stat !!!
Click to expand...
Click to collapse
Well it looks encrypted, You can't copy your files this way...You would have to unlock the BL and reset it...

Naveenthemi said:
Well it looks encrypted, You can't copy your files this way...You would have to unlock the BL and reset it...
Click to expand...
Click to collapse
unlock BT without erase DATA !! can you guild me !!

killuadk said:
unlock BT without erase DATA !! can you guild me !!
Click to expand...
Click to collapse
I'm sorry....... Xiaomi currently offers no method to unlock the bootloader without formatting the internal storage. There are NO third party tools either. You would have to undergo formatting to unlock the BT. Even the service centre can't avoid that.

Naveenthemi said:
I'm sorry....... Xiaomi currently offers no method to unlock the bootloader without formatting the internal storage. There are NO third party tools either. You would have to undergo formatting to unlock the BT. Even the service centre can't avoid that.
Click to expand...
Click to collapse
is it possible to recover photo after wipe data !! if yes suggest any software !!

killuadk said:
is it possible to recover photo after wipe data !! if yes suggest any software !!
Click to expand...
Click to collapse
It usually isn't possible to recover photos in this case, but it wouldn't kill to try.
Use (https://play.google.com/store/apps/details?id=com.defianttech.diskdigger)
It's the only free, working app I've come across for photo recovery. Even then it's only a chance you would get the photos back in the original quality or fully.

Naveenthemi said:
It usually isn't possible to recover photos in this case, but it wouldn't kill to try.
Use (https://play.google.com/store/apps/details?id=com.defianttech.diskdigger)
It's the only free, working app I've come across for photo recovery. Even then it's only a chance you would get the photos back in the original quality or fully.
Click to expand...
Click to collapse
I did try it but he found nothing (encryption ) know i will try to pull all the hard into my pc and use another soft

Help! I have the same problem on my Redmi Note 8. BT is locked, too

sd-card file-systems keeps breaking when I write to it

EvolutionX_4.6_ginkgo-10.0-20200819-0341-OFFICIAL
(same problems with crDroid; stock ROM (Pie) works fine)
Redmi Note 8
Clean install: Format & wipe
After adopting SD and migrating data I'm having some problems. Tested with 2x 128GB cards and 1x 64GB cards, same problems every time. Also tried fresh re-installs with format & wipe, same problems.
When copying files to "/sdcard" (aka "/mnt/runtime/full/emulated", aka "/storage/emulated/0/") I keep getting corrupted directories; directories that I can't write to, I can't delete, I can't move/rename, I can't change permissions, I can't change owner/group. Every time this happens, "df" shows more space being used, but files can't be found.
Problem happens when copying files to adopted storage via "adb push", tar, zip, cpio, and MTP.
I've also tried extracting from a zip file using a GUI app, and also deleting borked directories with a GUI app: No joy.
This is a major problem. This is making it impossible to load up the SD card with the files I need.
Just trying to "adb push" a TitaniumBackup directory to the new phone, and it gets to about 70-80% and then dies with this error:
Code:
adb: error: failed to copy 'TitaniumBackup/com.android.theme.font.xxxx-xxxxxx.apk.gz' to '/sdcard/test/com.android.theme.font.xxxx-xxxxxx.apk.gz': remote couldn't create file: Invalid argument
It keeps dying at slightly different points, but every time it dies it corrupts the directory that I'm copying into; I can't delete it, I can't move/rename it, I can't add anything to it, etc. "df" shows that space is being consumed, but there's no files. The sdcard just keeps getting corrupted, every time.
Code:
rm -rfv test*
rm: test: Directory not empty
rm: test2: Directory not empty
rm: test3: Directory not empty
Code:
find test*
test
test2
test3
Code:
mv test xxx
mv: bad 'test': No such file or directory
Code:
stat test
File: test
Size: 516096 Blocks: 864 IO Blocks: 512 directory
Device: 1fh/31d Inode: 11108 Links: 2
Access: (0771/drwxrwx--x) Uid: ( 0/ root) Gid: ( 1015/sdcard_rw)
Access: 2020-09-03 20:45:01.248588627 +1200
Modify: 2020-09-03 20:50:58.918624257 +1200
Change: 2020-09-03 20:50:58.918624257 +1200
This does nothing:
Code:
find . -inum 11108 -delete
Any ideas?
Linux localhost 4.14.193-QuicksilveR™ #1 SMP PREEMPT Wed Aug 19 05:58:46 CEST 2020 aarch64

Screenshots, error messages while trying to use a GUI tool to extract a zip file.

This is the only type of log entry that I'm seeing consistently when there's a failure (via "adb push"), but I'm also seeing a lot of them when there's no failure:
Code:
[ 09-04 12:27:30.567 891: 891 W//system/bin/adbd ]
type=1400 audit(0.0:26467): avc: denied { search } for comm=73796E6320737663203139 name="oem" dev="mmcblk0p86" ino=45 scontext=u:r:adbd:s0 tcontext=u:object_r:oemfs:s0 tclass=dir permissive=0
And after some testing, it's really trashing the file-system.
Code:
$ du -hcs .
487M .
487M total
df -h .
Filesystem Size Used Avail Use% Mounted on
/mnt/expand/b780ec4a-2dac-4b9e-bf9e-a044afdcad6b/media 118G 61G 57G 52% /storage/emulated

Just me? Any ideas? This is a new phone, and it's really not usable until I get this sorted out.
Code:
pwd
/sdcard
find . \! -type d
<no output>
du -hcs .
4.7M .
4.7M total
df -h .
Filesystem Size Used Avail Use% Mounted on
/mnt/expand/b7cc023f-4716-4010-8078-6a44f560a496/media 118G 82G 36G 70% /storage/emulated
rm -rfv *
rm: test1: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: test2: Directory not empty
rm: test3: Directory not empty
rm: test4: Directory not empty
rm: test5: Directory not empty
rm: test6: Directory not empty
rm: test7: Directory not empty
rm: TitaniumBackup: Directory not empty
rm: TitaniumBackup: Directory not empty
find . -exec ls -lhd {} +
drwxrwx--x 20 root sdcard_rw 3.4K 2020-09-04 13:31 .
drwxrwx--x 2 root sdcard_rw 24K 2020-09-04 10:12 ./test1
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 11:34 ./test10
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 11:40 ./test10/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 11:45 ./test11
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 11:51 ./test11/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 11:57 ./test12
drwxrwx--x 2 root sdcard_rw 504K 2020-09-04 12:02 ./test12/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 12:09 ./test13
drwxrwx--x 2 root sdcard_rw 504K 2020-09-04 12:15 ./test13/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 12:19 ./test14
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 12:25 ./test14/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 12:30 ./test15
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 12:36 ./test15/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 12:40 ./test16
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 12:47 ./test16/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 13:01 ./test17
drwxrwx--x 2 root sdcard_rw 420K 2020-09-04 13:04 ./test17/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 13:18 ./test19
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 13:22 ./test19/TitaniumBackup
drwxrwx--x 2 root sdcard_rw 56K 2020-09-04 10:21 ./test2
drwxrwx--x 2 root sdcard_rw 56K 2020-09-04 10:26 ./test3
drwxrwx--x 2 root sdcard_rw 20K 2020-09-04 10:57 ./test4
drwxrwx--x 2 root sdcard_rw 20K 2020-09-04 10:57 ./test5
drwxrwx--x 2 root sdcard_rw 92K 2020-09-04 11:07 ./test6
drwxrwx--x 3 root sdcard_rw 116K 2020-09-04 11:12 ./test7
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 11:20 ./test8
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 11:26 ./test8/TitaniumBackup
drwxrwx--x 3 root sdcard_rw 3.4K 2020-09-04 11:27 ./test9
drwxrwx--x 2 root sdcard_rw 500K 2020-09-04 11:33 ./test9/TitaniumBackup

Code:
logcat '*:V'
I'm watching the logs in one window, while I get failures in another window. I'm not seeing anything in the logs that corresponds to the failures.
And the sd-card has passed "badblocks" with zero errors.

Nevermind… The problem is being reproduced with stock firmware.
After following these instructions to Enable Adoptable Storage On Mi Phone, I can very consistently reproduce the problem with a stock ROM.
Seems like a hardware fault.

Update: Just got a brand new Redmi Note 8. Out of the box, everything is stock. Same problem with Adata 128GB cards.
I'm trying to get these cards to puke in another machine, but they're testing perfectly.
In the phone, I'm testing with a Lexar 64GB card, and I can't find any problems with it.
Is it possible that these particular Adata cards (brand new!) just aren't compatible with this phone? Is anyone else using 128GB Adata cards with this phone?
I guess I'll have to get a different brand 128GB (or maybe 256GB?) card and do more testing.

And… I got the same error while un-taring 8GB of podcasts. This is with the 64GB Lexar card.
Now what???