I'm having some lingering issues with my EVO even after running OTA updates. I am running a rooted stock ROM, currently software version 1.32.651.6 (I have not attempted the latest OTA update yet).
In particular are two problems - SD card issues have remained even after the OTA update. This was present even before rooting but after installing the first update (I went to a "full-service" store on opening day and they set it up themselves, assuming everyone would want it - luckily I could still get root). Issues include the Camera application reporting permissions problems randomly when trying to save pictures to the SD card, HTC's music application freaking out and coming to a near freeze trying to crawl the SD card during one of its troublesome spurts, and files disappearing from file explorers. So basically run of the mill, pre-first-OTA sd card problems. But occurring after the update and both before/after rooting.
Second is a problem with the camera itself. When first booting, HTC's included photo/video application will instantly crash after showing the camera icon on the black background. Google Goggles freezes for about 10 seconds then reports it was unable to connect to the camera. After the phone being on for about half an hour, these issues (seemingly) go away until the next reboot.
Last, and least frequent but still troubling, is a problem with the device powering on. At least twice I have been unable to get the device to turn on after powering it off, forcing a pull and replace of the battery to get it working again.
As far as I know, all of these issues could be either hardware or software. Even the power problem - my best guess is that the phone never powers off fully, but is instead locked inside of a deep sleep state and thus can not turn on until a battery pull forces the entire system off.
The questions being - first, are there any known solutions to the above problems? I have found many threads in particular regarding SD card issues, but none that seem to report these problems post-update. The others I have seen little to nothing about.
Second - if there are not known solutions, would it be prudent to return the phone as it may likely be a hardware problem?
Since it seems I'm forced to take the last update if I get a replacement, I may likely have problems getting a full root back. I'd like to avoid that if possible - having root works wonders for doing application development using non-native (unexposed) API's (Which - side note - since I'm developing for 2.1 at the moment, other than hacking for direct access to a Surface, does anyone know of a _fast_ way to do direct blits from native code? glTexImage2d is insanely slow).
Thanks all any help. Again, apologize if any of these are solved and gone problems, but I wasn't able to procure anything myself.
I'd go for the replacement, sounds like a defective unit..
Be sure that the folks here at xda will get root working regardless of OTA.
replace the unit, i'm very particular about my phones, if there is anything wrong with it I replace it.
I too have the SD card issue, I have updated, i have rooted, re-rooted, flashed new rom, different roms (fresh and sd) and it has always given me the sd card issue. Sometimes it wants to be a pain and not work at all, sometimes its good for at least a week or two. I am waiting for a little longer to make sure when I get a replacement its a newer version.
SD card permission errors --- POSSIBLE FIX
I hope/think/believe I fixed this error for those interested, I use my EVO for work and need it to work without a hitch....
Here goes (**Note i am a noob with smartphones with a dangerous amount of IT knowledge - disclaimer for those brave enough to browse around the root files and SD card files; I am not responsible for you bricking your phone, I am only trying to help those in need and putting in my 2 cents_)
Download and open the app ---> Root Explorer (or any other root explorer for that matter) from Android market.
Once Root Explorer is open (look up top/left it will say) Mounted as r/o (means read only) - press the white button to mount it as r/w (read & write)
Press and long hold on the SD card directory (folder) - you will get another window from which you must select the permissions option.
Under top option USER - check all marks -- READ WRITE AND EXECUTE & click OK.
VERY IMPORTANT - Click on the (white button) Mount as r/o to write protect your root files on your phone again.
I just applied this fix about 45 mins ago and seems to be working......updates to come if issues persist or re-surface. (**Note I could not see photos or play music and some apps were also giving me FCs (intermittently) due to permission or write errors to SD card; and now it seems to be working like nothing ever happened.)
What I have ::: stock ROM on EVO supersonic with recent HTC updates applied - standard 8Gig SD card provided with phone / had rooted but put back stock ROM for preference issues.
Hope this info helps some folks...very frustrating issue.
Cheers
SD card permission errors --- POSSIBLE FIX
ONE LAST SIDENOTE COMMENT -
I transfer data to my PC often (running Win 7 32bit_)
It is crucial that you right click on "safely remove hardware" icon on the lower right side (next to date and time) and WAIT until windows tells you
..."It is now safe to remove your hardware" --- I was just taking the plug out when done and it appears as if that could have started or compounded these issues with the SD card.
I too get the could not connect problems at times. And I have lost access to the SD card a few times. Some say its Fring that causes the problem. But after removing it I still have camera issues. I noticed that having the LED Light on while trying to open the camera will cause this problem.
I am running CM6 RC1 so this is to be expected from Release Candidates. Sit tight. It will get fixed.
Well after a full 24 hrs...no issues with the read write error on my EVO SD card, I think that when the phone is removed from PC incorrectly (i.e. pulling USB cable out in mode other than "Charge only" i.e. HTC sync, Disk Drive, Internet sharing - it causes it to "corrupt" the permissions on the SD card - It is still working like a champ and i am waiting impatiently for my EVO Froyo update ... feedback appreciated for those whom tried this fix and had it work....txs
@LF142
Hi there. So I followed all of your instructions above and downloaded Root Explorer. However, every time I change the permissions, they don't save. User, Group and Other is always switched off at root level. Do you think this may mean my SD card is corrupted?
I rooted it with BakedSnack.
I now want to un-root it as I miss taking shots, looking at my shots, listening to my tunes etc.
But I want to keep all my apps. All my texts and everything else. Whats the best way to go about this? I am also a bit of a n00b and I apologize if this is in the wrong forum, but when Froyo releases tomorrow (apparently) do I have to unroot to receive the update?
Thanks
Hi guys,
I really need your help on this one.
I have searched the forums and the web for a full day now and it seems that I am not alone with my problem here:
Last night I used Solid Explorer to create a subfolder with pictures within the Camera folder. I then tried to move that folder somewhere else on the "SD Card".
But when the process was finished, the subfolder was empty and all the pictures were gone. I could still see the thumbnails in the Camera folder, but when I tried to open one of them, they also all just disappeared!
Now I have read several threads here on xda about the problems of file recovery on a MTP device... Seems like normal file recovery programs will not be of any help in this case.
However I was hoping, that by now someone came up with a solution to this problem, since it affects all users of the GNex.
Some more infos on my side:
The phone runs 4.0.4, is not rooted and not unlocked - everything is stock.
Data back up via Google Plus and Dropbox was not possible, since I am on holidays in Asia with no data plan or WiFi available.
I have switched the phone to flight mode and (hopefully) not written any new data on the storage.
So my questions would be the following:
1) Has anybody yet found a way to asign a physical drive letter to the GNex, making it possible to be recognized by regular file recovery software?
Or is anybody currrently looking into that matter, trying to find a solution?
2) In case that I will not be able to recover the pictures myself through some pc software off the net, will I be able to let some professional have my files restored for me? If I understand correctly, all it takes is a software, that is able to recognize a ext3 or ext4 storage system???
I would really appreciate any help on this matter, because these pictures mean a lot to me and I really hope that I will be able to get them back somehow.
Thanks in advance,
Patrick.
Edit: Argh! First post and I got it wrong already! Sorry, I meant to post this in the Q/A section but ended up posting it in General :-/
I had to format my sd card losing 13GB of information yesterday. This was also due to stupid mtp. Sorry i doubt you can recover.
Sorry to hear that! Until now I could never understand the objections many people seemed to have concerning MTP, as it handled pretty much the same as an USB device when using a Windows PC. But now that I gained some insight in the matter, it's probably the ONE thing I don't like about this phone.
It just sucks to find that out the hard way...
But maybe somebody else still has an idea and can point me in the right direction?
I've had the same problem, and I'm blaming MTP as well. I finally gave up, formatted my drive and replaced MTP with cloud services or transferring files via adb.
While updating to lollipop i accidentally relocked and unlocked the bootloader resulting in a full memory wipe but i had my college work on there so i really need to recover the data lost but upon connecting the phone to the pc it appears as "portable device" which is not detected by recovery tools as well as the android apps as the undeleter root couldn't recover the data i need so is there a way to
1- connect htc one m8 to the pc as usb storage (aka removable disk)
2- another way to recover files
Thanks in advance
The issue is that Android now mounts internal storage by MTP, as opposed to the old Mass USB storage format. So computer's can no longer read the memory like its a USB drive. I think at some point (probably not even for this phone) I saw a method to dump the files in order to perform a file recovery, but it was pretty complicated and looked like a PITA.
You can try some apps on the Play Store that claim to recover files (using the phone itself, not a computer). But I've never used any, can't vouch for them, and don't know if they really work. Also keep in mind, the more you use the phone, the higher the likelihood that the files you want will be overwritten by other data.
Good luck. But in the future you have to remember to backup important personal data before making any major changes or mods to the device. I never fail to be disappointed at how many folks never bother to backup their important data; than freak out about it once its lost. Most of the time, at that point its too late. You should have been backing it up all along. If its important to you, back it up.
Well sir thank ypu for your help i don't think ill be able not to use the phone all that long as well as im now facing that the wifi wont open which is really annoying
Hello!
This is my first post in this forum, please be indulgent if I don't understand some stuff or abbreviations immediately.
I recently bought a Galaxy A3 2017 (SM-A320FL) to replace my old one with shattered screen and back cover. I tried the new Poco X3 for two weeks, but I wasn't satisfied with it since it was just wayyy too large for me, and also the phone speaker was unbearably loud (all people around me could follow the conversation on phone, even on lowest volume), which then led to the decision of sending it back and buying another used A3 2017 in good condition, as I was very satisfied with it, except of limited internal storage which continued to be an issue over months and years. And since the spare parts would have cost the same as the smartphone costs used at the moment, the decision was easy.
To avoid the single problem I had with the old phone, I wanted to root the phone right from the start so I could adopt the SD card as internal storage and/or change the folder some apps (especially WhatsApp) are storing their data and media in. Since the phone is factory reset and I have the other one which is still functioning, I don't have to take much care while trying things, which is great. I took yesterday evening until late night for that plan, and although a lot of threads and posts I read said that rooting the stock OS with latest update of Android 8 is not possible, I did it after some trial and error with flashing the custom recovery TWRP through Odin and then flashing SuperSU through TWRP. If a tutorial is needed, I'd happily write down how I did it, just ask.
But I still have a problem with adopting the storage. And as far as I understood, this is related to the storage encryption of Android/Samsung. Please explain if someone knows, I'd really like to understand the mechanisms that make all of this so laborious. I tried to mount the storage in TWRP when I started it first after flashing (it persists btw, as some people said it is gone and no recovery system can be found after the phone booted normally once, why?), but ran into the problem of "internal storage (0MB)". This was solved by wiping it, then I was able to mount the SD card as internal storage and the internal storage also was shown with a reasonable size in MB. I then started the phone which was obviously factory reset by the wiping. Unfortunately I couldn't see any results in the OS (does stock Android or file manager even show these changes in some way?) and also noticed the adopted storage was not anymore adopted when inspecting it in the TWRP recovery and again the internal storage was at 0MB. I then stumbled upon the app "Root Essentials" which is said to be able to adopt the storage, but needs a zip file which must be flashed by the recovery for that process. I tried it, but the flashing process does not work, as it can't find an installation of the app - my guess is, that this also is related to encrypted storage and the 0MB problem, how should the flash be able to look for something in encrypted space?
Soo, my problem now is, that I want to adopt the storage and don't know how to continue & where to begin. I also don't know if that app "Root Essentials" is any good, just read it at several places while googling so gave it a try. The phone is rooted with TWRP (0MB problem persisting) and stock OS now, and the adoptable storage per se is no must-have for me - if there is any other solution to migrate apps and more importantly their data to the SD card, please let me know, I'd be perfectly fine with that also.
Thank you!
Flo
Hey there Flo,
I am facing the same issues like you, always having to clear up space (e.g. Chrome cache) because the internal storage is not enough for the apps. And you cannot move many of the apps to the SD card, only their data. Last time I had to rermove Teams altogether because it was eating up 500+MB, and I couldn't afford it anymore as the free space dropped below 600MB.
Sooo, here are some basics I have learnt while looking for solutions.
Current custom ROMs are not an option for me as I use this phone for banking and production tasks, and I could not find any of them stable and issue-free enough to switch from the stock one.
The stock ROM is full of bloatware, especially Samsung stuff I do not need, and some others, like the Facebook app. However, you cannot extend internal storage with your SD card as Samsung does not allow this, and this is impossible with the stock ROM.
So I am stuck here, as I cannot leave the stock ROM, but I am constantly running out of space. Currently, I have rooted my device and installed TWRP, too, and I am planning to try one of the debloated stock ROMs to see if they can solve at least my problem with running out of free space on the internal storage.
In any case, what I can confirm is that you either have the stock ROM, and then you can only install apps on the internal storage, or if you want to extend your internal storage with the SD card, you'll have to choose one of the custom ROMs that allow this and wave goodbye to Knox and some other features.
I hope the above helps.
Hi!
Thanks for your detailed answer!
I didn't find a way to adopt the storage persistently, and I think at this point I'll just take your word that it won't be possible with the stock ROM. I knew that the stock ROM adopt storage option isn't able to be brought back by some adb shell commands as it was possible earlier (until 6.0 Marshmallow I think), but I thought that it maybe is possible by tricking the storage the OS sees with the mount in TWRP before the first start. Doesn't seem to work at all (for mostly unknown reasons, at least for me ).
And same for me, I don't know if the custom ROMs nowadays are better a lot, but doesn't sound like that as you described it. I flashed Resurrection Remix on my Galaxy S4 a few years ago, and although I liked the customizability and slimness, I too often ran into bugs and errors with it, which is why I abandoned the phone in the end.
However, I kind of found a fix I can live with on the SM-A320FL: I downloaded Link2SD from Playstore and also upgraded to the plus version, which is reasonably priced. This enables to also store app data on the SD card. I tried it with the 64GB SD card I had rolling around, partitioned it with MiniTool Partition Wizard following this guide to conform Link2SD requirements, and it worked perfectly. I also uninstalled all sorts of bloatware, and as far as i saw the shift to external storage of the apps I tried works fine. All data, including app, cache and app data is moved (and/or linked, not sure) to the ext2 partition on the SD card (which is shown to be a broken partition in Android storage settings btw, but that's fine). If any, only <1KB of file size per app remains in internal storage, which seems great!
I am currently waiting for my ordered 256GB SD card (U3, A2) to arrive next week, then I will do the full port from the old to the new A3 and I'll see how WhatsApp and Spotify behave being stored in external storage. Hopefully Link2SD is able to shift them, especially WhatsApp, since that was the main factor in cluttering the internal storage very fast and efficient.
If the Link2SD doesn't work for WhatsApp media, I'll give FolderMount a try, the direct mount then seems to work for many.
Since you mentioned it: What are the great features of Knox? The secure folder? Data encryption by screen lock? I can't remember using Knox features knowingly in the past three years. Is Knox not already blown by flashing a custom recovery?
Thanks for your help!
Flo
The internal storage data partition not mounting in TWRP is due to the partition being encypted when Android is booted, but also due to quota being enabled and latest version of TWRP for this phone (3.2.3-0 AFAIK) being unable to mount this. Fix for this is to flash a zip from Zackptg5 which disables both these options. See https://forum.xda-developers.com/t/...y-a3-sm-a320f-fl-y-2017.3562302/post-79260952 for full details
I see that OrangeFox is available now (https://orangefox.download/device/a3y17lte), so maybe this is able to mount without these problems, I am going to flash this soon so I will let you know!
FYI I am using H-ROM by Astrako. Very close to stock (it is a port from the A7) and seems to work well. VoWiFI is working in this ROM which was essential for me.
lastsaskatchewanpirate said:
The internal storage data partition not mounting in TWRP is due to the partition being encypted when Android is booted, but also due to quota being enabled and latest version of TWRP for this phone (3.2.3-0 AFAIK) being unable to mount this. Fix for this is to flash a zip from Zackptg5 which disables both these options. See https://forum.xda-developers.com/t/...y-a3-sm-a320f-fl-y-2017.3562302/post-79260952 for full details
I see that OrangeFox is available now (https://orangefox.download/device/a3y17lte), so maybe this is able to mount without these problems, I am going to flash this soon so I will let you know!
FYI I am using H-ROM by Astrako. Very close to stock (it is a port from the A7) and seems to work well. VoWiFI is working in this ROM which was essential for me.
Click to expand...
Click to collapse
Did “orange fox” work?
King p1n said:
Did “orange fox” work?
Click to expand...
Click to collapse
Yes, with OrangeFox I didn't need to flash the zip file from Zackptg5 which removes quota. I didn't get on with the latest H-ROM 6.0 (too many niggles, particularly ambient light sensor doesn't work so no adaptive brightness; fingerprint scanner doesn't work in apps; video call doesn't work in WhatsApp), but OrangeFox worked really well, definitely recommend it. Sorry for not remembering to come back and update sooner!
lastsaskatchewanpirate said:
Yes, with OrangeFox I didn't need to flash the zip file from Zackptg5 which removes quota. I didn't get on with the latest H-ROM 6.0 (too many niggles, particularly ambient light sensor doesn't work so no adaptive brightness; fingerprint scanner doesn't work in apps; video call doesn't work in WhatsApp), but OrangeFox worked really well, definitely recommend it. Sorry for not remembering to come back and update sooner!
Click to expand...
Click to collapse
Thank you
Which rom do you use and recommend?
Or can orange fox be used with the stock rom?
Doing this on behalf on a friend who is struggling with storage issues, been years since I’ve touched android
King p1n said:
Thank you
Which rom do you use and recommend?
Or can orange fox be used with the stock rom?
Doing this on behalf on a friend who is struggling with storage issues, been years since I’ve touched android
Click to expand...
Click to collapse
Currently I use H-ROM 2.0 (https://forum.xda-developers.com/t/...7-port-v2-0-pie-oneui-64-bits-treble.3940532/) which works well. Only two main niggles that I might change back to stock - video doesn't work in WhatsApp (but is OK in WhatsApp Business) and some VoWiFi calls have echo, but this might just be normal for VoWiFi, not had echo on normal cell network calls. Stock ROM is now available with Android 8 (Oreo) so when I have time I was intending to try that again, maybe with debloat to remove some of the stock apps.
I would recommend OrangeFox, and although I started with TWRP and flashed this over the top, I think you should be OK to just flash this straight from Odin. TWRP would only flash in old version of Odin, I would guess OrangeFox maybe would be the same. Flash in AP using older version Odin3 v3.12.10. Untick auto reboot, when complete power off with vol down + power, then force to recovery using volume up, home and power
lastsaskatchewanpirate said:
Currently I use H-ROM 2.0 (https://forum.xda-developers.com/t/...7-port-v2-0-pie-oneui-64-bits-treble.3940532/) which works well. Only two main niggles that I might change back to stock - video doesn't work in WhatsApp (but is OK in WhatsApp Business) and some VoWiFi calls have echo, but this might just be normal for VoWiFi, not had echo on normal cell network calls. Stock ROM is now available with Android 8 (Oreo) so when I have time I was intending to try that again, maybe with debloat to remove some of the stock apps.
I would recommend OrangeFox, and although I started with TWRP and flashed this over the top, I think you should be OK to just flash this straight from Odin. TWRP would only flash in old version of Odin, I would guess OrangeFox maybe would be the same. Flash in AP using older version Odin3 v3.12.10. Untick auto reboot, when complete power off with vol down + power, then force to recovery using volume up, home and power
Click to expand...
Click to collapse
just to clarify I could use Orange fox with stock rom and enable adopted storage? So I can use SD for apps when necessary.
I did get adopted storage working of sorts, but certain screens were missing from storage in the setting menu (I think Samsung didn't include or removed these as the phone was not intended to work with Adopted Storage), so it would crash when trying to perform certain actions. I can't actually remember now if you could move apps to the Adopted Storage using the standard system menus, it was so flakey that I stopped using that and switched to using Link2SD (which I had already used before so had a Plus license for) and this does exactly what I needed. These are the steps I used to get Link2SD working: https://forum.xda-developers.com/t/app-1-6-link2sd.919326/post-82757807. I don't think you need the Plus version, but it doesn't cost much, removes the ads and lets you move a few more files. Hope that helps