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.
Related
Unfortunately today on my display appeared a yellow vertical line from the battery icon up to the very top. This has to be a dead screen.
Since I have bought the device my GPS does not respond at all no-mater what I do...
Therefore I decided it is time to return it to ACER for a warranty repair. Of course I have unlocked my device and installed every possible tweak that exist here in the dev forum. So I want to ask if there is a way to return the device totally stock as it was out of the box or if the unlocking and rooting does void the warranty?
Thank you
HOW TO GUIDE:
1. USB Driver Acer A100 http://global-download.acer.com/GDFiles/Driver/USB/USB_Acer_1.000_A32H_A.zip?acerid=634486286202185014&Step1=Tablet&Step2=ICONIA%20TAB&Step3=A100&OS=a08&LC=en&BC=Acer&SC=PA_6
2. Unlock mode + Recovery required (search for this in dev Forum)
3. Download Official ICS (also in dev forum - use the 300MB version, for me the 250MB didn't work)
4. Copy the file to the Integrated memory of your A100
5. Enter recovery(HOLD power & Vol+ > after vibrate release Power and wait) and install the update.zip by scrolling to it (if you are not sure what to do just read or watch youtube on "how to navigate in recovery")
6.Wait until extracted and then reboot system
7. Wait until everything is brought back to stock
I really need some help because I have to return it soon...I just want to wipe it clean as it came from the factory, without anything on it.
Please help me
SlavPala4a said:
I really need some help because I have to return it soon...I just want to wipe it clean as it came from the factory, without anything on it.
Please help me
Click to expand...
Click to collapse
Supposedly the stock ics official update.zip will relock it and put back to Acer factory status.
Tapatalked from my Galaxy S II.
Could you be a little bit more specific? I mean if you do have a couple of minutes to write a guide for me, I could than structure it, add tags and afterwards it could help a lot of people in my situation...
I would be very pleased to get help from you!
nandroid in the beginning!
I want to add that after I updated to the official ics, as by many guides, I made a nandroid backup. So it was in the very beginning before I began optimizing! Should I just restore this backup?
SlavPala4a said:
I want to add that after I updated to the official ics, as by many guides, I made a nandroid backup. So it was in the very beginning before I began optimizing! Should I just restore this backup?
Click to expand...
Click to collapse
You can but you'll still have an unlocked bootloader and custom recovery. I'll try to find some time but right now I'm short and 13% battery lol
Tapatalked from my Galaxy S II.
SlavPala4a said:
Unfortunately today on my display appeared a yellow vertical line from the battery icon up to the very top. This has to be a dead screen.
Since I have bought the device my GPS does not respond at all no-mater what I do...
Therefore I decided it is time to return it to ACER for a warranty repair. Of course I have unlocked my device and installed every possible tweak that exist here in the dev forum. So I want to ask if there is a way to return the device totally stock as it was out of the box or if the unlocking and rooting does void the warranty?
Thank you
Click to expand...
Click to collapse
I think you can use ad to wipe the recovery and lock the bootloader-
Sent from my A100 using XDA
I truly thank you about trying to help me and giving me suggestions but what is "ad". I am as much of a "hacker" as I could follow the guides in this forum. I am not familiar with the basics and all the hard work behind every new ROM, Kernel, tweak etc... Therefore I really need some kind of a guide or few steps.
For example: if I download the official ics from the dev forum > run the recovery > wipe clean(as by the books) > install the official .zip would that be a true factory reset - locked, no root , no "NASA" stuff
thank you
SlavPala4a said:
I truly thank you about trying to help me and giving me suggestions but what is "ad". I am as much of a "hacker" as I could follow the guides in this forum. I am not familiar with the basics and all the hard work behind every new ROM, Kernel, tweak etc... Therefore I really need some kind of a guide or few steps.
For example: if I download the official ics from the dev forum > run the recovery > wipe clean(as by the books) > install the official .zip would that be a true factory reset - locked, no root , no "NASA" stuff
thank you
Click to expand...
Click to collapse
Sorry, XD. That was spell check in ice cream sandwich. Meant adb.
Sent from my A100 using XDA
Put the update.zip on your SD, hold volume down and power, it restores to stock ics.
The stock official update.zip is around the forum someplace. Maybe in the dev forum.
Tapatalked from my Galaxy S II.
For example: if I download the official ics from the dev forum >copy it to the external sd> run the recovery > wipe clean(as by the books) > install the official .zip would that be a true factory reset?
P.S. I just do NOT want to brick my device, better ask first
Another question/problem: I went to recovery and prepared to run the >>>System Nullify: Nullifies /cache /data /system. THIS DELETES INTERNAL SD!<<<
When I choose to use a zip from SD card it opens the devices integrated memory, BUT when I use a zip from Internal SD it opens the micro SD card. So does that mean it will erase everything from my INTERNAL SD = micro SD(external), dew to recovery internal sd is the external sd....very confusing!
So what happend, I ran the script than I applied the update.zip(from external SD, extracted successfully) from here http://forum.xda-developers.com/showthread.php?t=1307046 FULL PACKAGE
and now I am stuck at ACER logo with bootloader still UNLOCKED!
What are my options?
P.S. I have tried the http://support.acer.com/acerpanam/tablets/2011/Acer/ICONIATab/ICONIATabA100/ICONIATabA100faq9.shtml FACTORY RESET but as soon as it started to "Erasing Userdata..." , reboots and I am again stuck at ACER UNLOCKED MODE logo...
I am now with wiped clean FlexR but I do not know how to install the official ICS?! What should I do?
SlavPala4a said:
Another question/problem: I went to recovery and prepared to run the >>>System Nullify: Nullifies /cache /data /system. THIS DELETES INTERNAL SD!<<<
When I choose to use a zip from SD card it opens the devices integrated memory, BUT when I use a zip from Internal SD it opens the micro SD card. So does that mean it will erase everything from my INTERNAL SD = micro SD(external), dew to recovery internal sd is the external sd....very confusing!
Click to expand...
Click to collapse
My nullifier only does internal no matter what's mounted. Its hard coded to do /data which contains /data/media which is internal. It does not do sdc or external or any other partitions besides /cache /data /system. So basically no, it couldn't unless your recovery mounts external to one of those mount points, which none do unless its been changed.
Tldnr doesn't do external no matter what.
Tapatalked from my Galaxy S II.
Hello,
I installed on my Desire with STOCK HBOOT Sandvold ICS in the Version 0.17.1.1. I choosed stock a2sd in the installation and active in terminal a2sd install. Then I restored my apps by Mybackup Root. I have now the problem if I want to install a app from the market I get the error message "No Disk space available" (or something like that, I'm using German language).
I have a 512mb ext4 partition and activate a2sd in Terminal. I searched the topic for problems like that and found that I have to install mount2sd. I did this, but it didn't help either.
What should I do now? I haven't enough posts to post in the sandvold ics topic.
Greets,
Burak
You should go back to GB...
Sent from my GT-P3100 using Flashes and Thunders
nlooooo said:
You should go back to GB...
Sent from my GT-P3100 using Flashes and Thunders
Click to expand...
Click to collapse
Why? No.
If you can live with slower perfomance, active the stock a2sd again with answers: y, y ,y
vBurak said:
Hello,
I installed on my Desire with STOCK HBOOT Sandvold ICS in the Version 0.17.1.1. I choosed stock a2sd in the installation and active in terminal a2sd install. Then I restored my apps by Mybackup Root. I have now the problem if I want to install a app from the market I get the error message "No Disk space available" (or something like that, I'm using German language).
I have a 512mb ext4 partition and activate a2sd in Terminal. I searched the topic for problems like that and found that I have to install mount2sd. I did this, but it didn't help either.
What should I do now? I haven't enough posts to post in the sandvold ics topic.
Greets,
Burak
Click to expand...
Click to collapse
I had exactly the same problem. At first I chose during flashing the option "Regular a2sdext" as it seems good to me. However, nothing has changed, it was not working for me at all. Then I reflashed again with "Stock a2sd" and after booting I went to terminal and activated it. I tried it with several combinations (in some of them I got the message "Insufficcient storage available" and I only had like 5 apps installed...). At the end I finally made it work with the combination that is recommended by Sandvold - Y N Y. After that I have been installing several apps and my internal memory does not go down almost at all :good:... I will see later, but for now, this is the best set up for me....
I had this problem
I had this problem with one application. When installing from market, there'd be a pop up message saying that there was no more storage space even though there was plenty.
A few hours later, everything went back to normal and I managed to install all the apps I wanted.
(Side question: have you guys updated to Sandvold ICS 0.18 Beta?! I have, but I lost root access, so now I'm trying to regain it. Could someone alert Sandvold? I'm a new member and I can't post to 'Android development forums")
CzarD said:
I had this problem with one application. When installing from market, there'd be a pop up message saying that there was no more storage space even though there was plenty.
A few hours later, everything went back to normal and I managed to install all the apps I wanted.
(Side question: have you guys updated to Sandvold ICS 0.18 Beta?! I have, but I lost root access, so now I'm trying to regain it. Could someone alert Sandvold? I'm a new member and I can't post to 'Android development forums")
Click to expand...
Click to collapse
what do you mean that you lost root access? I was planning to upgrade to 0.18 today (I flashed 0.17.1 yesterday, but I have an issue with my phone - I cannot recevie any phone calls - and I hope another flash might help it...), so I guess I will wait a while....
skubko said:
what do you mean that you lost root access? I was planning to upgrade to 0.18 today (I flashed 0.17.1 yesterday, but I have an issue with my phone - I cannot recevie any phone calls - and I hope another flash might help it...), so I guess I will wait a while....
Click to expand...
Click to collapse
I have been testing 0.18 for a few hours now. Your phone issues should be resolved except you will encounter a new issue. You will lose superuser privilliges, to restore this, you have to install a zip of superuser through recovery.
My comments on Sandvold ICS 0.18
skubko said:
what do you mean that you lost root access? I was planning to upgrade to 0.18 today (I flashed 0.17.1 yesterday, but I have an issue with my phone - I cannot recevie any phone calls - and I hope another flash might help it...), so I guess I will wait a while....
Click to expand...
Click to collapse
I had 0.17.1.1 and all was well, it was tiny bit laggy, but overall it was cool.
i updated to 0.18, and I lost root access: the apps requesting SuperUser premissions were denied. (If you don't know what root access is, please google it)
As iyf said, you can flash the zip provided in Sandvold's official thread to restore root access. Check page 1601 or so for the flashable zip that will restore root access. I did so, and regained root access.
Then I got back all my apps as Sandvold 0.18 is my daily driver. But as I was using it, I noticed that whenever you change something in the system settings, it does not apply immediately. For example, I want my phone to lock immediately when it goes to sleep, well it simply doesn't. The power menu lost a few of the shortcuts it had in 0.17.1.1 (sound profiles...) and even if you restored them in the system settings, it won't change.
All in all, 0.18 is great step in terms of stability and reactiveness. No more scroll lag, apps open seamlessly, and no more 3G signal problems. The camera still isn't working though. Nevertheless, bizarrely the system lost its coherence: the system settings are not immediately applied and used, and the screen just won't lock. Those are the problems I encountered this afternoon.
I hope Sandvold takes a look at this thread as I cannot post on the official ROM thread coz I just registered on XDA.
(My Home button died today, even if I press it really hard, it won't respond, but I think it's a hardware issue)
EDIT: About the no more space issue, I had this today even though there was plenty of space left. I rebooted the phone and the warning disappeared.
CzarD said:
I had 0.17.1.1 and all was well, it was tiny bit laggy, but overall it was cool.
i updated to 0.18, and I lost root access: the apps requesting SuperUser premissions were denied. (If you don't know what root access is, please google it)
As iyf said, you can flash the zip provided in Sandvold's official thread to restore root access. Check page 1601 or so for the flashable zip that will restore root access. I did so, and regained root access.
Then I got back all my apps as Sandvold 0.18 is my daily driver. But as I was using it, I noticed that whenever you change something in the system settings, it does not apply immediately. For example, I want my phone to lock immediately when it goes to sleep, well it simply doesn't. The power menu lost a few of the shortcuts it had in 0.17.1.1 (sound profiles...) and even if you restored them in the system settings, it won't change.
All in all, 0.18 is great step in terms of stability and reactiveness. No more scroll lag, apps open seamlessly, and no more 3G signal problems. The camera still isn't working though. Nevertheless, bizarrely the system lost its coherence: the system settings are not immediately applied and used, and the screen just won't lock. Those are the problems I encountered this afternoon.
I hope Sandvold takes a look at this thread as I cannot post on the official ROM thread coz I just registered on XDA.
(My Home button died today, even if I press it really hard, it won't respond, but I think it's a hardware issue)
EDIT: About the no more space issue, I had this today even though there was plenty of space left. I rebooted the phone and the warning disappeared.
Click to expand...
Click to collapse
of course I know what root is, otherwise I would not be here, right? ... I just did not understand what happened to you when you updated to 0.18.... Now I understand.... and regarding to your issues - in 0.17.1 I had exactly the same problem - my screen did not lock even I set it up correctly and I also had the problem with Home button, it simply did not work + I could not receive any phone calls... all of that was really annoying and I tried to find some help on sandvold's blog, without any success, I also tried their IRC, nobody helped me either. I did not want to do a full wipe again, but at the end I did (and now I have to set up everything as well ) but after full wipe, everything is working correclty... I can receive phone calls, my screen locks and home button is also working ... so I recommend you to do a full wipe, I am sure it will resolve your issues as well...
CzarD said:
I had this problem with one application. When installing from market, there'd be a pop up message saying that there was no more storage space even though there was plenty.
A few hours later, everything went back to normal and I managed to install all the apps I wanted.
(Side question: have you guys updated to Sandvold ICS 0.18 Beta?! I have, but I lost root access, so now I'm trying to regain it. Could someone alert Sandvold? I'm a new member and I can't post to 'Android development forums")
Click to expand...
Click to collapse
I also lost the root access with Beta 0.18(with full wipe),
(Beta 0.17 "root access" is OK!)
Superuser is out of order with this issue so that I can't activate A2SD
btw,
I have once tried the "AD2SDX", but didn't work normally:
I merged 1GB ext4 for it. And every time when I install about 10~15 Apps
A message on the top of the screen would tell me that I almost reached the limit.
(I'm using traditional Chinese, I don't know what it was written in English)
skubko said:
of course I know what root is, otherwise I would not be here, right? ... I just did not understand what happened to you when you updated to 0.18.... Now I understand.... and regarding to your issues - in 0.17.1 I had exactly the same problem - my screen did not lock even I set it up correctly and I also had the problem with Home button, it simply did not work + I could not receive any phone calls... all of that was really annoying and I tried to find some help on sandvold's blog, without any success, I also tried their IRC, nobody helped me either. I did not want to do a full wipe again, but at the end I did (and now I have to set up everything as well ) but after full wipe, everything is working correclty... I can receive phone calls, my screen locks and home button is also working ... so I recommend you to do a full wipe, I am sure it will resolve your issues as well...
Click to expand...
Click to collapse
By full wipe you mean:
1. wipe data/factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
right?
I always do that when I flash a new ROM... Anyway, will try again later and hope that it works.
Caesar
CzarD said:
By full wipe you mean:
1. wipe data/factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
right?
I always do that when I flash a new ROM... Anyway, will try again later and hope that it works.
Caesar
Click to expand...
Click to collapse
yes, it is what I meant... I did full wipe before flashing and then another after it ... I do not wipe battery stats during that process,but it does not matter I hope it will work for you...
UserMatty said:
I also lost the root access with Beta 0.18(with full wipe),
(Beta 0.17 "root access" is OK!)
Superuser is out of order with this issue so that I can't activate A2SD
btw,
I have once tried the "AD2SDX", but didn't work normally:
I merged 1GB ext4 for it. And every time when I install about 10~15 Apps
A message on the top of the screen would tell me that I almost reached the limit.
(I'm using traditional Chinese, I don't know what it was written in English)
Click to expand...
Click to collapse
Whenever I got this message, I'd reboot or hot reboot and it would disappear. I can't remember if I had the same script.
---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------
skubko said:
yes, it is what I meant... I did full wipe before flashing and then another after it ... I do not wipe battery stats during that process,but it does not matter I hope it will work for you...
Click to expand...
Click to collapse
I did a full wipe again, and everything went back to perfect working order. Thanks man
CzarD said:
Whenever I got this message, I'd reboot or hot reboot and it would disappear. I can't remember if I had the same script.
---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------
I did a full wipe again, and everything went back to perfect working order. Thanks man
Click to expand...
Click to collapse
you mean working with AD2SDX ?
Can I ask you how do you merge and format ext4 ?
Actually, I'm using MiniTool Partition Wizard, is it okay ?
cause I did reboot after I saw the message, but didn't work.
But I surely know that I can see "1GB" in "Apps" in "settings"
quite confusing
UserMatty said:
you mean working with AD2SDX ?
Can I ask you how do you merge and format ext4 ?
Actually, I'm using MiniTool Partition Wizard, is it okay ?
cause I did reboot after I saw the message, but didn't work.
But I surely know that I can see "1GB" in "Apps" in "settings"
quite confusing
Click to expand...
Click to collapse
It's not okay, minitool doesn't do that correctly. Use 4ext recovery to partition your sd card.
Sent from my HTC Desire using Flashes and Thunders
UserMatty said:
you mean working with AD2SDX ?
Can I ask you how do you merge and format ext4 ?
Actually, I'm using MiniTool Partition Wizard, is it okay ?
cause I did reboot after I saw the message, but didn't work.
But I surely know that I can see "1GB" in "Apps" in "settings"
quite confusing
Click to expand...
Click to collapse
Quite confusing indeed. I must say I'm no expert developer or programmer, heck I'm an engineering student. i just experiment on my Desire. But my experience in bricking/unbricking/flashing/etc tells me the following:
Minitool wizard apparently is not okay. I used it at first too but my Desire just could not read or detect the EXT3 partition I created. I tried EXT4. I tried different roms and scripts, none worked for me. (To be honest, I only tried 3 roms and a few scripts).
What I used is plain simple: Clockworkmod Recovery partitioning tools. It works for me!
First restore your SD card to full FAT32 configuration (I might suggest changing the basic storage unit from a few bytes to a few kilobytes as it might increase SD card responsiveness).
BACK IT UP, you will lose everything on it when you partition it in CWM.
Boot into recovery and select partition SD card (It is advised that the size of your partition does not exceed 1.5 GB as a few ROM developers have pointed out - not Sandvold though- I use 512 MB, which is more than enough for me). Set SWAP to 0 Bytes. (i have no idea what swap is, should google it, but most threads advise a swap of 0 B).
That's it, you have your partition.
I use CWM and Sandvold 0.18. If you use this setup, everything should be okay, at least it's ok on my phone.
I use stock a2sd when flashing Sandvold ICS ROMs.
I'm on stock HBOOT, S-OFF, and using the regular Kernel that comes with Sandvold 0.18. (I tried tiamat, but the battery dies after half a day of use!)
CzarD said:
Quite confusing indeed. I must say I'm no expert developer or programmer, heck I'm an engineering student. i just experiment on my Desire. But my experience in bricking/unbricking/flashing/etc tells me the following:
Minitool wizard apparently is not okay. I used it at first too but my Desire just could not read or detect the EXT3 partition I created. I tried EXT4. I tried different roms and scripts, none worked for me. (To be honest, I only tried 3 roms and a few scripts).
What I used is plain simple: Clockworkmod Recovery partitioning tools. It works for me!
First restore your SD card to full FAT32 configuration (I might suggest changing the basic storage unit from a few bytes to a few kilobytes as it might increase SD card responsiveness).
BACK IT UP, you will lose everything on it when you partition it in CWM.
Boot into recovery and select partition SD card (It is advised that the size of your partition does not exceed 1.5 GB as a few ROM developers have pointed out - not Sandvold though- I use 512 MB, which is more than enough for me). Set SWAP to 0 Bytes. (i have no idea what swap is, should google it, but most threads advise a swap of 0 B).
That's it, you have your partition.
I use CWM and Sandvold 0.18. If you use this setup, everything should be okay, at least it's ok on my phone.
I use stock a2sd when flashing Sandvold ICS ROMs.
I'm on stock HBOOT, S-OFF, and using the regular Kernel that comes with Sandvold 0.18. (I tried tiamat, but the battery dies after half a day of use!)
Click to expand...
Click to collapse
just to add - I have Amon RA Recovery and I partitioned my SD card by that, it was also working without any problems everytime I did it...
@CzarD - I am glad to hear that the wipe helped you...
You should try out the Amarullz or INT2SD from the Aroma installer. I have INT2SD and I have 1,3G of free space (2G EXT partition)
CzarD said:
Quite confusing indeed. I must say I'm no expert developer or programmer, heck I'm an engineering student. i just experiment on my Desire. But my experience in bricking/unbricking/flashing/etc tells me the following:
Minitool wizard apparently is not okay. I used it at first too but my Desire just could not read or detect the EXT3 partition I created. I tried EXT4. I tried different roms and scripts, none worked for me. (To be honest, I only tried 3 roms and a few scripts).
What I used is plain simple: Clockworkmod Recovery partitioning tools. It works for me!
First restore your SD card to full FAT32 configuration (I might suggest changing the basic storage unit from a few bytes to a few kilobytes as it might increase SD card responsiveness).
BACK IT UP, you will lose everything on it when you partition it in CWM.
Boot into recovery and select partition SD card (It is advised that the size of your partition does not exceed 1.5 GB as a few ROM developers have pointed out - not Sandvold though- I use 512 MB, which is more than enough for me). Set SWAP to 0 Bytes. (i have no idea what swap is, should google it, but most threads advise a swap of 0 B).
That's it, you have your partition.
I use CWM and Sandvold 0.18. If you use this setup, everything should be okay, at least it's ok on my phone.
I use stock a2sd when flashing Sandvold ICS ROMs.
I'm on stock HBOOT, S-OFF, and using the regular Kernel that comes with Sandvold 0.18. (I tried tiamat, but the battery dies after half a day of use!)
Click to expand...
Click to collapse
As I know, swap in linux is somewhat like virtual memory in Windows.
Will be launched when the system is in low memory.
That's exactly everything I know
I'm now Using Revolutionary CWM v4.0.1.4, stock HBOOT, S-OFF
And just follow your way to full wipe then install the system again(stock a2sd)
I still can't get the root access. thus, I can't activate a2sd in terminal
PS: with Beta 0.18
But Beta 0.17.1 currently work!
Okay, I've rooted my n5110 8.0 and manually flashed 4.2.2 XXCMH3. I have reset the flash counter with triangle away. It shows software update is available. Is it possible to use OTA Root keeper to update the OTA update? IM me or answer here please no guesses. Thanks in advance.
capitoldach said:
Okay, I've rooted my n5110 8.0 and manually flashed 4.2.2 XXCMH3. I have reset the flash counter with triangle away. It shows software update is available. Is it possible to use OTA Root keeper to update the OTA update? IM me or answer here please no guesses. Thanks in advance.
Click to expand...
Click to collapse
Yes it should work fine, there have been issues with 4.3 but in a video I watched about the app the update from 4.2.1 to 4.2.2 went smoothly for him. Granted nothing is guaranteed. If you are using superSU you can buy the pro version and it has an OTA survival mode. Alternatively you could also flash the update via odin or recovery but since you're asking about OTA Root Keeper I'm sure that isn't something you are interested in. Make sure you follow the steps and make any other backups you can because you never know.
http://www.youtube.com/watch?v=ky5miA8ilr0&noredirect=1
That's the video I watched also I looked at other posts regarding known issues and it doesn't look like there are problems specifically with certain UI types (Touchwiz Sense etc). GOOD LUCK let me know how it goes
Thanks.
dwibbles33 said:
Yes it should work fine, there have been issues with 4.3 but in a video I watched about the app the update from 4.2.1 to 4.2.2 went smoothly for him. Granted nothing is guaranteed. If you are using superSU you can buy the pro version and it has an OTA survival mode. Alternatively you could also flash the update via odin or recovery but since you're asking about OTA Root Keeper I'm sure that isn't something you are interested in. Make sure you follow the steps and make any other backups you can because you never know.
http://www.youtube.com/watch?v=ky5miA8ilr0&noredirect=1
That's the video I watched also I looked at other posts regarding known issues and it doesn't look like there are problems specifically with certain UI types (Touchwiz Sense etc). GOOD LUCK let me know how it goes
Click to expand...
Click to collapse
Thanks for the response and link, I really appreciate it. I actually do have the pro version of superSU. I was unaware that superSU has that option.
capitoldach said:
Thanks for the response and link, I really appreciate it. I actually do have the pro version of superSU. I was unaware that superSU has that option.
Click to expand...
Click to collapse
Did it all work out?
dwibbles33 said:
Did it all work out?
Click to expand...
Click to collapse
Yeah I'd really like to hear back from the OP about this.
No it didn't
dwibbles33 said:
Did it all work out?
Click to expand...
Click to collapse
Although I do appreciate the time. I was unable to make it work. I was informed by Mr hyde, that this is one of the models that always have +1 if you have a custom recovery or any other changes to the device. Not sure though, because when I when I was on xxchm3 I tried the update and instead of saying device has been altered it said successfully registered. So I'm not sure what that means. Currently I'm having another issue I'm trying to figure out. I have a large amount of misc. Files taking up a few gbs of space. I have factory reset and wiped partition each time, but when I install superSU pro version it says needs to update binary. So I do, it restarts into cwm 6.x and says either erase disable stock recovery, I haven't accepted so I select go back on the bottom of the list, it restarts and everything appears to be working, but now I'm wondering if I am supposed to delete/disable stock recovery or if there's no way to get stock recovery back if I do erase/ disable. And also if that is where my misc. Memory is allocated or it is something else entirely, as when I backup I backup to external sd card. Thanks for the consideration and I will hit the button as well. It is really cool of you to follow up.
capitoldach said:
Although I do appreciate the time. I was unable to make it work. I was informed by Mr hyde, that this is one of the models that always have +1 if you have a custom recovery or any other changes to the device. Not sure though, because when I when I was on xxchm3 I tried the update and instead of saying device has been altered it said successfully registered. So I'm not sure what that means. Currently I'm having another issue I'm trying to figure out. I have a large amount of misc. Files taking up a few gbs of space. I have factory reset and wiped partition each time, but when I install superSU pro version it says needs to update binary. So I do, it restarts into cwm 6.x and says either erase disable stock recovery, I haven't accepted so I select go back on the bottom of the list, it restarts and everything appears to be working, but now I'm wondering if I am supposed to delete/disable stock recovery or if there's no way to get stock recovery back if I do erase/ disable. And also if that is where my misc. Memory is allocated or it is something else entirely, as when I backup I backup to external sd card. Thanks for the consideration and I will hit the button as well. It is really cool of you to follow up.
Click to expand...
Click to collapse
By +1 do you mean the flash counter? If you boot into download mode it'll show you a flash counter. For the binary update select the Normal install not the TWRP/CWM option. You shouldn't have to flash the binaries they SuperSU should be able to update within the app. As for the misc files it could be the partitions are messed up, if you use a root file explorer goto /data/media check those folders, your 0 folder should be your normal files but see if another 0 shows up or it might have a clockworkmod folder that has backups in it (I've seen the backups that are supposed to end up on the extSd end up there so its worth checking). Let me know if you want/need any more help I have worked my way through a lot of crap between my tablet and phone and I wish there was more help out there than there is so please let me know if I can help.
0 file in 0 file like 4 times each dated days I flashed different builds
dwibbles33 said:
By +1 do you mean the flash counter? If you boot into download mode it'll show you a flash counter. For the binary update select the Normal install not the TWRP/CWM option. You shouldn't have to flash the binaries they SuperSU should be able to update within the app. As for the misc files it could be the partitions are messed up, if you use a root file explorer goto /data/media check those folders, your 0 folder should be your normal files but see if another 0 shows up or it might have a clockworkmod folder that has backups in it (I've seen the backups that are supposed to end up on the extSd end up there so its worth checking). Let me know if you want/need any more help I have worked my way through a lot of crap between my tablet and phone and I wish there was more help out there than there is so please let me know if I can help.
Click to expand...
Click to collapse
Ok, so I started over with OUEMFI1 factory rest and wiped partition. I still have misc. files. So, I went to data/media I found the 0 file, inside that file is another 0 file, inside of that file another 0 file, and on and on all with different dates. Should I remove the 0 files within the 0 files, are they necessary, or they left over each time I flash? I did mean flash counter, but I haven't checked it via download mode, I will do that.
capitoldach said:
Ok, so I started over with OUEMFI1 factory rest and wiped partition. I still have misc. files. So, I went to data/media I found the 0 file, inside that file is another 0 file, inside of that file another 0 file, and on and on all with different dates. Should I remove the 0 files within the 0 files, are they necessary, or they left over each time I flash? I did mean flash counter, but I haven't checked it via download mode, I will do that.
Click to expand...
Click to collapse
Okay so what happened with all those 0 files is basically with the ability to change users that number changes if you add more users. For whatever reason when you flash a ROM it creates a new 0 file and pushes your old 0 file further in. If you go through those files you may see folders you used to have on other ROMs containing old stuff you had. So if you have stuff to keep then copy it to the /0 folder then delete the extras. I have been trying to modify a script from the GSIII that basically wipes everything except your external card but it didn't work last time. My advice would be to back your files up to your external, go into recovery and instead of a factory reset go into mounts and format /data (again be sure to back your stuff up because this will take it all out). That should wipe out everything (0 files and such) I would go as far as formatting system too. MAKE SURE you have a ROM on your external card because formatting /system will wipe out your existing ROM, but you will get a fresh start and at that point you know that nothing is hanging around from before.
Hey there,
I have the Galaxy a50 SM-A505Fn and I just broke my internal storage by flashing TWRP and Multidisabler.
First, I should note that I am completely blind, so I use TWRP with ADB in CMD.
First I tried to root my phone with a patched boot image, using Magisc, but that didn't work, so I switched to TWRP.
After flashing it with Odin and booting into the recovery, my pc saw it as Galaxy A50 and the folders inside it were literal giberish and I couldn't paste anything in it, so I switched to a micro SD to flash Disabler and that worked surprisingly well.
Note, I did the wiping before that.
After the disabler worked, I rebooted into TWRP and used the command to reboot into recovery, as I was instructed, then the phone booted up just fine.
I set it up, and gained root with Magisc manager, but after connecting it to the PC to get the sound files I wanted to change it was still giberish and didn't let me make folders or paste anything into it.
The card also looked like it had the internal storage files like you would see on any phone, it had like 256 KB used on it from 2 gb it is formated at since I used it for a pi before and didn't have time to fix the capacity on it back to 64, but again you can't put anything onto it while in the phone.
Any help on how to make it work like normal?
Also apps don't see the storage properly either, so I can't use it for the reasons I rooted it for.
Thanks a lot.
After reading about it, it seems that the storage is encripted.
I managed to flash Infinity os on it, but the thing doesn't talk since it is missing text to speech, so I wanted to flash a zip to make it talking.
After rebooting into twrp, again, still encripted.
Got the zip onto my card, but doesn't flash, which is fine since that can be fixed, but I can't really do anything to fix it.
Does anyone know the command to format data?
twrp format data doesn't work like in the TWRP guide.
Any ideas?
you need to install multidisabler
yamen_tn said:
you need to install multidisabler
Click to expand...
Click to collapse
Did that already, that is how I flashed a rom on it, but was still encripted.
The rom said that there is a problem with my device, but it set up just fine.
I am back on ful stock right now and it decripted, I might try it again in some time.
The only things I want from root is to be able to change system sounds, to add haptic feedback which I already did and tweak it so it works faster.
If I could change the sounds without root and without event sound that would be awesome and would let me stay on stock.
Dragos597 said:
Did that already, that is how I flashed a rom on it, but was still encripted.
The rom said that there is a problem with my device, but it set up just fine.
I am back on ful stock right now and it decripted, I might try it again in some time.
The only things I want from root is to be able to change system sounds, to add haptic feedback which I already did and tweak it so it works faster.
If I could change the sounds without root and without event sound that would be awesome and would let me stay on stock.
Click to expand...
Click to collapse
Good thing you got it decrypted back again, i have had kind of the same issue with internal storage decreasing drastically multiple times, as far as i understood it happens when i install patched AP with magisk then install multidisabler and reboot it without formatting the whole device, maybe try that when your root next time to get past the internal storage issue. Note that mine was in android 9 and device storage was not encrypted unlike yours.
And as a suggestion, if there's someone near you who can help you with actually rooting your device with magisk rather than TWRP it will be much easier.
Regards
SuizShaw said:
Good thing you got it decrypted back again, i have had kind of the same issue with internal storage decreasing drastically multiple times, as far as i understood it happens when i install patched AP with magisk then install multidisabler and reboot it without formatting the whole device, maybe try that when your root next time to get past the internal storage issue. Note that mine was in android 9 and device storage was not encrypted unlike yours.
And as a suggestion, if there's someone near you who can help you with actually rooting your device with magisk rather than TWRP it will be much easier.
Regards
Click to expand...
Click to collapse
I've got the patched image for AP from a friend, also patched TWRP, but it did that after flashing auto disabler and wiping everything, so I still don't get it.
Anyway, it is back for now and I will have to see if it breaks next time I install twrp on it.
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