Related
Verizon Galaxy Nexus.
I was running 4.0.4 IMM30B leak. The new leak/possible update came out, I decided to flash it. Saw that it was only good for updating from 4.0.2 (ICL53F), so I wiped, formatted, and reinstalled it. Re set up my phone (titanium backup, homescreens, android market updates for a few apps, the basics). Everything seemed fine, though I didn't try saving anything. Ran the update to the new 4.0.4, and everything seemed fine and dandy.
The next day, titanium backup runs (scheduled) and fails. Says not enough storage or something despite the fact that it also shows ~14GB free space...
Tried to take a screenshot of the issue, and I get a notification that it "Couldn't capture screenshot." "Couldn't save screenshot. Storage may be in use."
Curious, I tried to take a picture with the system camera app, and it doesn't seem to save pictures either. Though no error messages tell me such things.
Caching seems to work, updating apps seems to work, using 'most' apps seems to work, but saving data to the virtual SDcard has no such luck.
Assuming that it's a permissions issue, I went into CWM Recovery and did a 'fix permissions.' Though that has not fixed anything.
Various searches have shown me that others have experienced this problem, but I haven't seen anyone with a solution. Also, they seem to be experiencing it in various AOKP roms (specifically for the Transformer tablet).
Question: Anyone know what I can do to fix it?
Haha this happened to me and no1 could answer it happened when i went from aokp m4 to m5.. Was odd, but what i did to fix was relock and unlock the bootloader and then get all my stuff back with titanium.. At least that worked fine for me
Edit: well i relocked restarted system and boot android, then reboot into bootloader and unlocked again, then boot into android (fresh new system) and im writing this from my fixed phone 1 week ago.. No problems so far
Sent from my Galaxy Nexus using xda premium
msedek said:
Haha this happened to me and no1 could answer it happened when i went from aokp m4 to m5.. Was odd, but what i did to fix was relock and unlock the bootloader and then get all my stuff back with titanium.. At least that worked fine for me
Edit: well i relocked restarted system and boot android, then reboot into bootloader and unlocked again, then boot into android (fresh new system) and im writing this from my fixed phone 1 week ago.. No problems so far
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Glad to hear that there is a fix. I may end up doing this tonight... I'm hoping that a quicker, simpler fix is available (something like boot an insecure.img and change permissions of these folders via adb, or something).
Thanks for that though, as I now know that it should work.
Happening on GSM Galaxy Nexus as well. I tried a rom over milestone 5, then reinstalled milestone 5 and restored my backup, and then got this problem. Seems sdcard is not writable to at all. Gonna try out the bootloader locking stuff i guess.
I ended up using the Galaxy Nexus Toolkit (for time and automated simplicity) to wipe the device, reflash 4.0.2 (signed by Google), reroot, CWM reccovery, and restore the virtual sdcard backup saved with the toolkit.
Once the virtual sd was restored, I restored my apps (but no system apps) with titanium backup. Haven't had the time since to reupgrade to 4.0.4, but 4.0.2 seems to be working for me nicely.
I am able to screenshot, and nice things like that, but sometimes titanium backup is giving me errors about not being able to save due to insufficient space (still 14GB free). Gonna dive into that issue today.
4.0.2 works good.. What its bad about it its the lag, the ROM its laggy and also the battery life and the photo quality.. ICS now its much better than 4.0.2
Sent from my Galaxy Nexus using xda premium
No fix?
I'm also getting this problem and only since installing android 4.3 from CM 10.2
I have also noticed that when I connect by USB to my PC I can't see anything but the external sd card whereas in the past I've been able to see 3 devices - ext sd, int sd and system. This makes me think it's permissions but I'm not sure what to change and where.
I need a screenshot to send a picture of an mms issue I'm having and can't re-install/restore whatever as this deletes the mms with the problem so I need a fix that leaves the phone as it is except for this repair.
Any help appreciated.
Redscorpian said:
I'm also getting this problem and only since installing android 4.3 from CM 10.2
I have also noticed that when I connect by USB to my PC I can't see anything but the external sd card whereas in the past I've been able to see 3 devices - ext sd, int sd and system. This makes me think it's permissions but I'm not sure what to change and where.
I need a screenshot to send a picture of an mms issue I'm having and can't re-install/restore whatever as this deletes the mms with the problem so I need a fix that leaves the phone as it is except for this repair.
Any help appreciated.
Click to expand...
Click to collapse
Dat gravedig.
Just try reflashing your device from a stock image.
Beauenheim said:
Dat gravedig.
Just try reflashing your device from a stock image.
Click to expand...
Click to collapse
And do you think that'll be leaving it as it is?
I fixed this deleting the "pictures" folder with RootExplorer.
jwiegand said:
I fixed this deleting the "pictures" folder with RootExplorer.
Click to expand...
Click to collapse
Tried booting in t recovery fixing permissions, tried delete the screenshot folder and tried wiping the dalvik... Never thought of deleting the Pictures folder. Solved it for me to! (This problem just occurred without me flashing a new rom or anything. A ~9 month old AOKP and the error just came up after a reboot)
Thanks jwiegand!
bergmanman said:
Tried booting in t recovery fixing permissions, tried delete the screenshot folder and tried wiping the dalvik... Never thought of deleting the Pictures folder. Solved it for me to! (This problem just occurred without me flashing a new rom or anything. A ~9 month old AOKP and the error just came up after a reboot)
Thanks jwiegand!
Click to expand...
Click to collapse
I'm on a different phone, but I fixed this issue by clearing the defaults for the program that launched pictures. In my case, I use Gallery, so in Program Info under Settings, I reset defaults and everything worked fine. I guess this is the same thing as deleting the Pictures folder since I believe it is an issue of 'releasing' the memory that remains in use by your respective program. For all future requests as to which program should be used to launch a file (or picture in this case), I never select the option that binds future requests to one specific program. Hope that helps .
My fix: re enable the media scanner!
Like many others, I have disabled the DRM and media scanner services because of the bug that caused ridiculous cpu usage (particularly on boot). Re enabling the media scanner fixed this problem right up. If you want a free and easy utility to do this, check out: "Rescan Media ROOT"
https://play.google.com/store/apps/details?id=com.addz.mediascannerroot
Disclaimer: I am not associated with the author of that app.
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
I tried all the previous solutions without success, but manually creating the Pictures/Screenshots folder worked flawlessly on my LG 4X.
Thanks TulsaDavid!
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
Thanks alot! Worked for me!!
Thanks, TulsaDavid!
Making screenshots folder solved it for me aswell.
Unable to take Screenshot, USB storage maybe in use
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
I have tried using home+power button, turned on swipe and had difficulty in using the S PEN to make the screenshot - still doesnt work.
I also tried making a new folder but still doesnt work.
My unit is Samsung Note 8.0
/sdcard permissions broken
Just had this happen on my Nexus 5.
The cause was using adb push to copy files to /sdcard when I was booted into recovery. All the files and folders were owned by root:root. I had to reboot to recovery, adb shell, and then
Code:
chown -R media_rw:media_rw /data/media/0
It might be possible to do this while booted in android with Connectbot or something, but I didn't try that.
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
Thank you TulsaDavid. This helped me tremendously. You're a deity!
Sent from my SGH-T989 using Tapatalk
I just came from the LG G2X that I had CWM and switch Roms almost weekly and never had the problem that I'm having now but I feel that CWM may be (at least) partially at fault (although there may be a problem somewhere between the keyboard and chair as well). The problem is now I only have 198MB left on the "Phone" that as of two days ago was just about 9.1GB. In those two days I have installed the OUDHS CWM , made a backup with CWM, installed SuperSU v1.25 , installed the Stock Deodexed/Zipaligned JDQ39.M919UVUAMDB 5/3 , made another backup with CWM and now I'm out of space. With CWM on my G2X I was use to it putting the backups on the external SD card. I take it with the OUDHS version it puts it on the phone somewhere. But I can't find out where. I've looked using ES File Explorer to search root and everywhere else but I can't seem to locate where all the backups are being cached. I'm also concerned that it may be that when roms get installed they don't just lay down on top of the the old rom's space. But I can't find anything in the forum that neither supports nor disproves that concern.
Thanks,
twitch
I found mine under /data/media/clockworkmod/backup ... check there
laparka said:
I found mine under /data/media/clockworkmod/backup ... check there
Click to expand...
Click to collapse
That's were they were. Thanks! Now if I can figure out how to get CWM to work off of the external SD card it will save me some cut and paste time.
Hello,
I have had my HTC One M8 for a while now but I wasn't really happy with the soundquality while playing through my headphones, so I looked for ways to improve it. I found a few methods and finally decided to give it a try. These methods require a root so yesterday I have rooted my phone for the first time. Unfortunately I am experiencing some problems now.
The rooting process went without too much trouble. I used hasoon2000's toolkit and have TWRP version 2.7.0.2 installed as recovery and used it to install the provided SuperSU, which didn't work at first. On the forums I found a newer version and installed that one, updated it and got it to work.
Now this is where I think I messed up: I read somewhere that when rooted, you are able to delete pre-installed apps from the phone. I downloaded SD maid and deleted Kid Mode, Zoe and 7digital. When I deleted Kid Mode I got an error saying it has crashed. I tapped away the error but from this point I couldn't go back to my homescreen anymore because my launcher kept crashing (com.htc.launcher crashed). I rebooted the phone and the launcher worked again, but the phone still seemed to be buggy.
After this I tried to install the snapdragon audio+ (this was my first choice for an equalizer). I downloaded the apk and moved it to the system folder using ES file manager. I installed but when I tried to use it (through settings in google play music app) my phone would crash. I uninstalled it and tried again, but when I tried to move the apk to the system map like before, my phone would crash everytime. I then found out the file I used doesn't work for lollipop so I figured that's what caused the crashes.
My next move was to try and install viper4android. I downloaded it from the Play Store and opened it. It told me it needed an installation of BusyBox so I downloaded that too. But when I opened the BusyBox app and clicked install my phone would crash again. After some searching I found that the HTC One M8 requires BusyBox to be flashed manually so I downloaded the file but when I tried to load it onto my phone I noticed this wasn't possible anymore.
Now when I connect my phone to my PC the PC recognizes it, but when I open the map in Windows Explorer it only shows three maps; .showme, _nero_sync and Ringtones. I know there should be more as they were there before. It also shows my phone's capacity as a total of 10GB (shouldn't this be 16GB?). Also when I try to connect it with Sync Manager it gives me an error everytime I reconnect the phone; Device unavailable. Please reconnect your device [4].
I have tried to reset the phone through settings, wipe with TWRP and fix permissions with TWRP. I also tried reinstalling Sync Manager and the drivers on my PC. What I'm thinking now is I maybe have done something wrong in the ES file explorer that would make the folders unaccessible.
My phone is running stock android 5.0.1 and my PC Windows 7 64-bit.
I hope someone can help me, Thanks.
P.S: Sorry for the long post, I figured I'd give as much info as possible.
@Steef076 First update recovery to the latest one (2.8.6.0)
Second if you go and delete vital or integrated parts of the stock rom you will get a lot of bugs. Third, viper4android requires to write system and you can't write system with the stock kernel, you need an unsecured kernel or unsecure it yourself.
10GB is right since 6 is eaten by android. At this point I would just revert to a backup or install any custom rom around here. Most are close to stock and with no bloatware and come with root. You can even clean them further using a tool called ROM Cleaner. It will most likely solve all your problems
Did the deleted system apps reappear after reboot, or do they remain "uninstalled"? If the system is write protected like TempestZ states, any deleted system apps should reappear after a reboot.
Revert your nandroid to restore the system apps. And you didn't make a nandroid, you really should before making any system modifications for the very reason that it allows you to revert if you run into problems.
Another good practice, is if you don't know what effect deleting a system app will have (such as "safe to delete" lists that can sometimes be found on XDA) you should first freeze the app with Titanium Backup. If freezing doesn't cause any issues, then go ahead and delete. If you do have issues, just unfreeze the app.
Steef076 said:
Now when I connect my phone to my PC the PC recognizes it, but when I open the map in Windows Explorer it only shows three maps; .showme, _nero_sync and Ringtones. I know there should be more as they were there before. It also shows my phone's capacity as a total of 10GB (shouldn't this be 16GB?). Also when I try to connect it with Sync Manager it gives me an error everytime I reconnect the phone; Device unavailable. Please reconnect your device [4].
Click to expand...
Click to collapse
No, Windows will never show 16 GB. It only shows "internal storage" partition, or the user accessible portion of the storage. A good chunk is reserved for the OS.
Does what is shown in Windows differ from what is shown in ES if you browse to internal storage?
Thanks for the replies. @TempestZ @redpoint73
First of all I managed to update twrp to 2.8.6.0 using adb/fastboot.
To answer your question @redpoint73 the system apps I had deleted indeed reappeared after reboot. Also I didn't make a nandroid before I deleted the files, as I did not even know this was possible. Now I have made a nandroid of my stock ROM that is working decently, except for the TV app keeps crashing (I'm not opening it) and the connection to the PC is not working properly (not sure if this is ROM based?). I have noticed when the phone is in recovery I CAN see the folders through windows explorer. HTC sync manager still doesn't find it though. I am working on finding a proper stock ROM or maybe flash a custom one to see if that will fix it.
I understand now that the OS is taking up the storage space. The space windows is showing is the same as ES file manager so I guess this is fine.
HTC Sync is a hot mess. It often causes more troubles than it solves.
One thing you can try (to see if it fixes the USB connectivity) is uninstall HTC Sync and all HTC drivers. Than connect the phone. Don't let it install HTC Sync. Go to Windows Device Manager, find the device. Then pick the option to manually select the drivers, and pick the generic "Android MTP device" (or something to that effect) drivers.
This doesn't work for everyone. But it worked for me to be able to "see" the internal storage of my M8 on my home PC (Win 7). Annoyingly, it seems to vary from one PC to another. My work laptop (also Win 7) works fine with HTC Sync.
Steef076 said:
So if I understand correctly, 'version-main' is the same as 'firmware' and 'software number' (found in settings)? If so, my current firmware seems to be 4.19.114.2.
Now, what you're saying is I should do an OTA but this isn't possible because I have a custom recovery right?
Also, when I want to flash stock rom and stock recovery or do a nand don't I need the files that fit my cidnum? How would your file work for me?
Click to expand...
Click to collapse
If yours already on 4.19.114.2 then no need to do OTA as that the latest.
and my backup will bring back your device back to stock as you first bought it when restore with a full wipe.
Try to solve your problem first, only when you really need the backup then only I will upload ... let me know
ckpv5 said:
If yours already on 4.19.114.2 then no need to do OTA as that the latest.
and my backup will bring back your device back to stock as you first bought it when restore with a full wipe.
Try to solve your problem first, only when you really need the backup then only I will upload ... let me know
Click to expand...
Click to collapse
Hello, sorry for the late reply.
I have decided to give a custom ROM a try. I now have ARHD 41.0 installed and it seems this took care of my problems. All the maps are showing in windows explorer and HTC sync manager is connecting properly with my phone again. Also no more crashing apps. Your backup would still be of much use for me as I am not sure I want to stick with a custom ROM and therefore would like to have a stock ROM backup.
Thanks in advance.
A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
I then went onto Google Chrome and tried to save a random image and was prompted to overwrite *completely random image name* in documents. No matter which option I hit (overwrite or create new file) I am given the notification it has downloaded but if I tap it then I'm just taken to a black screen with a triangle and an exclamation mark. When I go into the file manager and go to internal storage there is absolutely nothing in there.
I thought this might have something to do with the SD card so I put it back in but was again prompted to format it, so this time I did it as removable storage and it hasn't made a difference. Any ideas?
Android Version 6.0
Software Number 6.13.206.5
If you need any more info let me know.
Thanks!
dezzybird said:
A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
I then went onto Google Chrome and tried to save a random image and was prompted to overwrite *completely random image name* in documents. No matter which option I hit (overwrite or create new file) I am given the notification it has downloaded but if I tap it then I'm just taken to a black screen with a triangle and an exclamation mark. When I go into the file manager and go to internal storage there is absolutely nothing in there.
I thought this might have something to do with the SD card so I put it back in but was again prompted to format it, so this time I did it as removable storage and it hasn't made a difference. Any ideas?
Android Version 6.0
Software Number 6.13.206.5
If you need any more info let me know.
Thanks!
Click to expand...
Click to collapse
Did you update the binaries?
xunholyx said:
Did you update the binaries?
Click to expand...
Click to collapse
I was never given an option, it said they couldn't be installed by the app. I was going to try the fix where you install them directly by saving a zip to your phone's internal storage and then installing it but then I noticed the problem with my internal storage.
dezzybird said:
A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone
Click to expand...
Click to collapse
When you chose to make the SD a part of internal storage (known as the new "adoptable storage" option in Marshmallow), you merged it (with the phone's internal storage) as part of the data partition. Then you yanked out a part of that partition, by removing the SD (and why you did that in order to root, I don't know).
I'm not too familiar with what happens (or is supposed to happen, anyway) when you choose adoptable storage, then remove the SD. But I think its safe to say, that resulting storage issues is not a surprise.
dezzybird said:
I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
Click to expand...
Click to collapse
The toolkit hasn't been updated in over a year, and causes many issues for that reason. It hasn't been updated for Marshmallow (Android 6) and therefore can't root MM. Toolkit also contains an obsolete version of TWRP which will also cause some issues.
Good rule of thumb: whenever rooting an Android device, you should be sure to use updated methods; and verify the method works with your Android version.
Since you have TWRP installed, try going to the Wipe section in TWRP. Then select the button that says "Format Data" and see if that helps your issue with writing to internal storage. Do not select to wipe any other things in the Advanced section of Wipe (another rule of thumb - if you don't know what it is don't wipe it. For instance wiping "System" will delete the OS entirely).
Of course, formatting data will cause any data to be lost. So backup accordingly (if there is anything left) before you format data.
Once you have the storage issue sorted out (hopefully the above helps), ditch the toolkit, and do the following steps manually:
1) Unlock bootloader (should already be done)
2) Flash TWRP 3.0 with fastboot
3) Flash SuperSU 2.65 in TWRP, to properly root
Aye, I couldn't find an alternative to the toolkit so I just ran with it but I guess I've learned that lesson.
I've managed to sort the issue now so I'll post what I did here for any people who may happen upon the thread in future. I'm still not sure what caused the issue in the first place; maybe it was the memory card, maybe I selected the wrong thing to wipe in TWRP, maybe it was the toolkit or maybe a bit of everything because I'm stupid.
Before I discovered the issue I was going to install the SuperSU binaries manually (since they didn't install for some reason) and install a custom ROM, so I decided to just go ahead with it. After flashing the ROM and then SuperSU.zip everything worked fine and I had a fully rooted phone running Cyanogenmod. According to the guide I was reading I had to wipe a number of things (the Dalvik Cache, System, Cache, and Data) anyway so I don't think it mattered that I had somehow erased the internal memory as it seemed to be reinstalled with the ROM. This is just a guess though, all I know for sure is it's fine now (fingers crossed).
So next time I'd just use the toolkit to help unlock the bootloader and maybe flash a recovery as that seemed to work fine, but manually flash SuperSU.zip to root yourself in case the toolkit is what broke it.
Thanks for your help!
dezzybird said:
Aye, I couldn't find an alternative to the toolkit so I just ran with it but I guess I've learned that lesson.
Click to expand...
Click to collapse
The best way to achieve bootloader unlock and root is to just do the steps manually.
You don't need a toolkit to do these things. Anyone that can follow instructions and type a few fastboot commands can do it.
All that folks need to do it manually is here. Everything in Section 1 is valid, with the exception that the TWRP version number in the command needs to (obviously) match the number you are trying to install (the example given in the guide is an older version). Some things in Section 2 and 3 are obsolete (s-off method, firmware version) but that's irrelevant in this case (and for most folks) since those things aren't necessary to unlock the bootloader, root, or flash custom ROMs.
dezzybird said:
Before I discovered the issue I was going to install the SuperSU binaries manually (since they didn't install for some reason)
Click to expand...
Click to collapse
What do you mean "for some reason"? I told you the reason. The toolkit uses an old, long obsolete version of SuperSU that existed before MM. It therefore can't root MM, and there is no reason to believe it would. New Android builds often (almost always) require new root methods, and old versions of SuperSU are usually going to cause you trouble. That is why you should always research the current root methods, when trying to root.
dezzybird said:
After flashing the ROM and then SuperSU.zip everything worked fine and I had a fully rooted phone running Cyanogenmod.
Click to expand...
Click to collapse
You don't need to root after flashing a custom ROM, they are already rooted.
You also don't need to root in order to flash a custom ROM. Unlocked bootloader and custom recovery is all you need to flash custom ROMs.
dezzybird said:
According to the guide I was reading I had to wipe a number of things (the Dalvik Cache, System, Cache, and Data) anyway so I don't think it mattered that I had somehow erased the internal memory as it seemed to be reinstalled with the ROM. This is just a guess though, all I know for sure is it's fine now (fingers crossed).
Click to expand...
Click to collapse
These are not correct assertions. Doing the default wipe in TWRP (it says most of the time, this is all that is needed, and it means it!) doesn't touch internal storage.
On a similar note, flashing a ROM doesn't touch internal storage, either. It just flashes system partition and boot.img partition.
dezzybird said:
So next time I'd just use the toolkit to help unlock the bootloader and maybe flash a recovery as that seemed to work fine, but manually flash SuperSU.zip to root yourself in case the toolkit is what broke it.
Click to expand...
Click to collapse
I'd strongly advise against using the toolkit at this point, or suggesting to others to use it. As I've already tried to explain (but you seem to be ignoring) the components of the toolkit are woefully obsolete. By the time you flash recovery manually (with fastboot) and manually flash the proper version SuperSU, there isn't much of value that the toolkit does. The bootloader unlock procedure via HTCDev.com is pretty self-explanatory (and the guide I've posted explains whatever isn't already obvious). And is justifiable to say that if you can't handle doing these things manually, you probably shouldn't have root.
I was just stating what I did to fix the issue and what I would have done instead with the same amount of knowledge I had when I started. I did search for stuff like "how to root HTC One M8 2016" and whatnot and the toolkit showed up in like the first 4 results, plus it was linked in the sidebar of the Android subreddit as the go-to option so I assumed I'd be good to go but apparently not.
After I flashed the ROM I didn't see SuperSU which I had been led to believe was what signified if the phone was rooted (if you had SuperSU > Rooted. If not > Not rooted) but apparently not. Like I mentioned, this was my first time rooting a device and I was kinda winging it as a learning experience, hence not doing things optimally (or particularly right)
Thanks for the info, that'll definitely make things easier next time!
dezzybird said:
I was just stating what I did to fix the issue and what I would have done instead with the same amount of knowledge I had when I started.
Click to expand...
Click to collapse
And what I am saying is: what you stated you "would have done instead" (or do "next time") is in fact not the correct thing to do.
Also, when you say "this is what I would have done" it read strongly like a suggestion to others what "they should do".
Just trying to prevent obvious pitfalls for both you and others in the future.
dezzybird said:
I did search for stuff like "how to root HTC One M8 2016" and whatnot and the toolkit showed up in like the first 4 results, plus it was linked in the sidebar of the Android subreddit as the go-to option so I assumed I'd be good to go but apparently not.
Click to expand...
Click to collapse
My advice would be to stick to XDA, and just use the search function here; or simply browse the forums. Reason being, randomly Googling for root methods will often yield random "root" websites with poorly organized, outdated information; which is often just stolen from XDA in the first place.
The question (and answer) of rooting this device pops up pretty frequently; as well as common pitfalls, solutions, etc. While the forums may be a bit intimidating to work through, the answers are all here; and not hard to find, once you become accustomed to how the forum is organized.
dezzybird said:
After I flashed the ROM I didn't see SuperSU which I had been led to believe was what signified if the phone was rooted (if you had SuperSU > Rooted. If not > Not rooted) but apparently not.
Click to expand...
Click to collapse
The knowledge in the following 2 paragraphs are fairly esoteric, but proboably could have been found in the CM thread or other threads:
CM has a slight oddity to it (and I'm sure its devs have there reasons) versus many other ROMs (but you may find a similar thing in other AOSP based ROMS) in that the ROM is pre-rooted, but root access is toggled "off" by default. To turn it on, do to phone's Settings>Developers Options, and there you find the option to toggle root on or off (default is off).
If you don't see Developer Options in Settings, its a bit of a quirky Android trick to make it appear. Go to Settings>About>Software information>More, then tap the "Build number" 7 times, and you will see a toast message that "You are now a developer" (yeah, that is what it really says!) and the option is now available in Settings.
i wanted to install new stock rom from here but fastboot wont install it so i went to twrp and tried to flash it from there but during flashing twrp just rebooted itself and saying installation wasnt sucessful, i figured this is due to S-On but prior to flashing it i did possibly the stupidest thing, i went to ADVANCED WIPE and wiped every option on the list(dalvik,system,data,internal storage,cache) except for micro sdcard ofcourse. i then went to FIX PERMISSIONS and stupidly select the ALSO FIX SELINUX CONTEXTS. when those done i then went and install another image which is on the sdcard that i downloaded from here E9pw_Android5.0_Sense70_E1.zip . the installation went well and rebooted itself and got to the homescreen and whatnot. but the troubles came when i tried to install apps from playstore and it gave me all kind of errors known to man, even going into file manager to access the internal storage gave me problem it says something along ACCESS IS DENIED or CANT ACESSS EMULATED OR SOMETHING LIKE THAT. when i opened chrome to download something the browser just crashed because apparently it wont able to access the emulated storage. yeah i fcked up badly here. dont know whatelse to do.
see below of the files that i currently have in my external microsd card:
E9pw_Android5.0_Sense70_E1.zip -WORKS
open gapps arm64 android 5.0 stock
RUU 0PJXIMG_A55ML_DTUL_L50_SENSE70_hTC_Asia_WWE_1.35.7 07.2 - DONT WORK
0PJXIMG_A55ML_DTUL_L50_SENSE70_hTC_Asia_WWE_1.35.7 07.2 - DONT WORK
Thanks!
Got it fixed! by going to TWRP-->WIPE-->FORMAT DATA and reinstall the ROM. if anybody experiencing the same problem please do the same.
Zorg The Great said:
Got it fixed! by going to TWRP-->WIPE-->FORMAT DATA and reinstall the ROM. if anybody experiencing the same problem please do the same.
Click to expand...
Click to collapse
hy i am in exactly same situataion. S ON with twrp installed i accidentaly formatted all and it showd no storage later on i formatted system too and now device has no os. I can still boot in to recovery. DOnt kow what to do now