I have a small problem i installed font installer from the market and now after uninstalling the keyboard is stuck on the font that was last installed by the app. I have gone through the root of my sd to find the apk from which the keyboard is installed and cannot for the life of me find it. I thought maybe if i could find it wiping cache and data on that apk would remove it. If there is anyone out there that may be able to help i would greatly appreciate it.
As seen in pic its only the keyboard. Also kote that swype keyboard and gingerbread keyboard are both the same as the system font for some reason its only this keyboard and that is it.
Sent From My BloodyS2
Flash your last back up from cwm?
Or try to install the app again and set it to the default font then uninstall it.
In the future use the built in flipfont.
Deebo took your bike too?
Hey there everyone. Here is the story in list format.
- Got first Galaxy S2 (Tmobile)
- after a few days rooted the phone using odin
- uninstalled bloatware via titanium back up pro
- installed a few apps(fb, twitter, swift key x, mobli, two different font changers)
- everything was running smoothly until i actually installed a font and the app prompted for a reboot.
- i reboot and the booting process freezes at the bootloader logo (tried countless times)
- i enter recovery mode to wipe phone.
- wipe phone.
- same issue.
- i thought then that the phone had some sort of issue in itself.
- i take the phone to tmobile a few days later and tell em some bs.
- get my new phone.
- root it again same way.
- uninstall all the bloatware i want gone and install all the apps i want.
- again SAME thing happens when i install this font changing program.
the program downloads previews for 146ish fonts. you select one. it actually downloads it and reassigns the default font with the font you download and after a reboot it should work.
except i get a frozen bootloader screen. so this time around i am convinced of the app somehow messing with the bootloader settings (etc...)
soooo...i decide to flash "SGH-T989 UVKID // Insecure // Root // Busybox" by bubby323.
odin says its successful, but still same freezing issue at bootloader.
help please.
Your problem is with the ROM. Boot into recovery, mount USB, put the ROM on your SD card and flash it from recovery.
Also, stop using that app
The_Biz said:
Flash your last back up from cwm?
Or try to install the app again and set it to the default font then uninstall it.
In the future use the built in flipfont.
Deebo took your bike too?
Click to expand...
Click to collapse
I will try thanks for ur response
Edit... Reinstalling app did not work but reflashing backup did thanks ... Idk why i didnt think of reflashing
Sent From My BloodyS2
i do not have an external sd card, so is there any other method? i can always go and purchase one tomorrow. there is no way for me to put the file onto the internal sd memory because windows never recognizes the phone because it never boots up.
and trust me, i learned my lesson....never downloading that program again.
jeikazou said:
i do not have an external sd card, so is there any other method? i can always go and purchase one tomorrow. there is no way for me to put the file onto the internal sd memory because windows never recognizes the phone because it never boots up.
and trust me, i learned my lesson....never downloading that program again.
Click to expand...
Click to collapse
There are drivers posted in the dev section, be sure to try and download them again.
Your phone's "/sdcard/" location is actually an internal SD card. So when you use CWM to mount the sdcard, it will mount both the internal, and external SD card if it can. So you should still be able to do it.
as you said i was able to mount and copy over the rom, but after i copied over the rom file, it does not show on the android cwm file menu. maybe if i restart the phone?ill try it now.
still no go the rom file is not showing, the drivers have been installed. i reinstalled them JUST in case.
maybe i'm doing something.
- i mount usb storage
- copy over rom tar files
- unmount and look for it in the apply update from sd card and install zip from sd card selections but both show no files.
alright well after a few hours of trying a million different things...the only thing that worked was eaglesblood rom via cwm mount. thanks romanb for helping.
I just uploaded tiny noot, a very minimal root tool for the NST glowworm. I think it would probably also work for the simple touch, but I've lent mine out and cannot test it to confirm.
I am basically a cobbler here; many thanks to GabrialD, DeanG and the folks with the minimal touch root tools, which this is based on - and of course to mali100 and the CWR team for getting that on the Touch and Glowworm. Everything below is put together with parts from those projects using what I've learned at XDA and from Dean's nook color repartitioning scripts.
They make it possible for someone like me to knock out a package that's a little more convenient to work from than booting noogie and manually copying in files.
I am using the clockwork recovery zip installation mode for copying in the minimal set of files - I'm not trying to support the google apps or the many interesting screen refresh hacks.
I am not including a modified uRamdisk - the stock uRamdisk supports ADB, and you can get root via adb wireless simply by typing su, so I chose to leave well enough alone.
GabrialD has already released a modified uRamdisk for the glowworm (to support root by default as well as the light) but since stock works for my purposes, I'm not using the modified one.
What it does include:
su and busybox
nook color tools in /system, so that nonmarket apps can be installed
adb wireless
ADW launcher
Amazon appstore, so there's at least once source of "easy" apps
Button Savior
Nook Touch Tools
Supermanager and the Busybox updater interface
The install process is three steps. Four if you decide - and you should - to make a backup of your device before you start. (that process is: make the noogie disk. boot from noogie. connect to your computer. dump the NSTG or NST using dd or another disk imaging tool, and is described in more detail with tips for lots of different operating systems at http://forum.xda-developers.com/showthread.php?t=1142983 That backup will let you restore your entire device to a known working configuration.
Download mali100's nook touch CWR disk discussed in this thread:
http://forum.xda-developers.com/showthread.php?t=1360994
the file itself is here:
http://forum.xda-developers.com/attachment.php?attachmentid=806433&d=1323121269
unzip the file and then write the .img file to an sdcard with your disk imaging tool of choice (dd in linux or win32 disk imager are two I use)
Once you've imaged the SD card, copy in these two zipfiles - leave them zipped:
http://www.mediafire.com/?ig75l5b9c24e7q6
http://www.mediafire.com/?2tfitzt97qqfaw7
Apply 1 of 2, then reboot, then
Apply 2 of 2
then remove your SD card and reboot. Although I have not gotten all the commands to run out of a single zipfile, Zydraka noticed, I think correctly, that you can run first the one and then the second without needing to reboot in between. I have done it that way successfully.
I tried putting all commands (copying the files, then setting permissions) into one file and the rooting process aborted in an ugly way. I ultimately needed to reimage the device to restore the oddly hosed /rom partition. After reimaging I was able to root successfully by running the two clockwork scripts back to back without a reboot.
A (very brief) guide to the CWR interface, for those who don't know it:
You will know your card is made correctly when you put it in your device and power on, and you see a clockwork gear nibbling at a nook N. Be patient while CWR loads; you will get to a screen with selectable menu choices.
Navigate up and down with the righthand buttons; navigate back with the lefthand upper button; choose an item or run a command using the raised n button.
Navigate down to "install zip file from sdcard" and hit N
Hit N again to "Choose Zip File from SDcard"
Navigate down to the first zip (labeled 1 of 2) and hit the n button
navigate to "yes - install"
hit the N button
once the first script is done, use the N button to navigate to and apply zip 2 of 2.
navigate back to the reboot menu using the lefthand side buttons. Once you are at the reboot menu item, you can pull the card, then reboot.
I used a 256 meg sdcard I had in the house for making the CWR disk. I find that to be a very convenient size for these disks - big enough to put a few files onto, not so big I wish I hadn't set it up as a CWR disk.
Thanks roustabout! It works great and it was super easy to do! I just got done installing a bunch of apps from Amazon.
Update: I just posted a tutorial with a video for noobs on my blog.
One thing to note, I didn't do the reboot that you mention in between the 1 and 2 packages and everything worked fine. I just installed 2 right after 1 and haven't had any problems.
Thanks for this, rooted last night everything is as it should be, the only issue I've run into is that I can't seem to install the Kindle app. It's not in the amazon market place, I tried backing up the APK from another device via EStrong and transferring the apk to the microSD, and I get a parsing file error. Any tips?
I have not been able to get Tasker to install yet, either.
One thing which sometimes works where other approaches fail (if you have the .apk file) is to ssh into your device (I use quicksshd) and log in as root, then cd to the directory the APK was copied to and issue the command
pm install blah-blah.apk
I have not yet tried that with Tasker, but it may also help with the Kindle app? I did need to do it for one of the apps I use, although I can't recall which one.
Edit: the 3.1 kindle app Zydraka points out works for me as well.
By default, the Kindle app is pretty unusable, very slow page turns. But by using the gesture-enabled screen refresh hack, it's very useable. (I found that using the no gesture version led to lots of apps just ignoring the hack's presence. I think Renate has a way around that, but I haven't read up on it.)
http://forum.xda-developers.com/showthread.php?p=22800284#post22800284
I got Tasker to install, but needed first to copy in the Maps jar and xml (to framework and permissions respectively) reboot and install via ssh - it might have worked just to reboot.
Since others may want Tasker available, putting the maps.jar and maps.xml files into the tinynooter is trivial, and I'll probably get to it soon.
I found that the older version of the Kindle app works, version 3.1.0.30. There's a donwload for it at Android Freeware. http://www.freewarelovers.com/android/app/kindle
So, after this, will the glowlight work in all apps? I need to make sure that, moon+ reader and EZpdf will glow in the dark, before I purchase the new nook.
thanks.
The glowlight seems to work in all apps. I'm not clear on how exactly it's turned on and off; it might be possible to have an app that uses a long press on the N button for something else, and that might interfere, but so far it works fine in the launcher, in the Kindle reader, in fbreader, in Newsrob (that I know I've tested.) even if you had an app that was doing something funny with that long press, you ought to be able to turn it on from the settings menu that comes up on a short press.
Once the glowlight is on, it seems to stay on until your screen goes to sleep, regardless of what applications you may also be using.
This is part of why I didn't get into the boot environment at all in this approach - I knew from manual rooting that I didn't have to change out uRamdisk so I decided to leave it all alone.
Thanks for tinynoot! It's working well for me, and glowlight behaves normally.
roustabout said:
I just uploaded tiny noot, a very minimal root tool for the NST glowworm. I think it would probably also work for the simple touch, but I've lent mine out and cannot test it to confirm.
I am basically a cobbler here; many thanks to GabrialD, DeanG and the folks with the minimal touch root tools, which this is based on - and of course to mali100 and the CWR team for getting that on the Touch and Glowworm. Everything below is put together with parts from those projects using what I've learned at XDA and from Dean's nook color repartitioning scripts.
They make it possible for someone like me to knock out a package that's a little more convenient to work from than booting noogie and manually copying in files.
I am using the clockwork recovery zip installation mode for copying in the minimal set of files - I'm not trying to support the google apps or the many interesting screen refresh hacks.
I am not including a modified uRamdisk - the stock uRamdisk supports ADB, and you can get root via adb wireless simply by typing su, so I chose to leave well enough alone.
GabrialD has already released a modified uRamdisk for the glowworm (to support root by default as well as the light) but since stock works for my purposes, I'm not using the modified one.
What it does include:
su and busybox
nook color tools in /system, so that nonmarket apps can be installed
adb wireless
ADW launcher
Amazon appstore, so there's at least once source of "easy" apps
Button Savior
Nook Touch Tools
Supermanager and the Busybox updater interface
The install process is three steps. Four if you decide - and you should - to make a backup of your device before you start. (that process is: make the noogie disk. boot from noogie. connect to your computer. dump the NSTG or NST using dd or another disk imaging tool, and is described in more detail with tips for lots of different operating systems at http://forum.xda-developers.com/showthread.php?t=1142983 That backup will let you restore your entire device to a known working configuration.
Download mali100's nook touch CWR disk discussed in this thread:
http://forum.xda-developers.com/showthread.php?t=1360994
the file itself is here:
http://forum.xda-developers.com/attachment.php?attachmentid=806433&d=1323121269
unzip the file and then write the .img file to an sdcard with your disk imaging tool of choice (dd in linux or win32 disk imager are two I use)
Once you've imaged the SD card, copy in these two zipfiles - leave them zipped:
http://www.mediafire.com/?ig75l5b9c24e7q6
http://www.mediafire.com/?2tfitzt97qqfaw7
Apply 1 of 2, then reboot, then
Apply 2 of 2
then remove your SD card and reboot. Although I have not gotten all the commands to run out of a single zipfile, Zydraka noticed, I think correctly, that you can run first the one and then the second without needing to reboot in between. I have done it that way successfully.
I tried putting all commands (copying the files, then setting permissions) into one file and the rooting process aborted in an ugly way. I ultimately needed to reimage the device to restore the oddly hosed /rom partition. After reimaging I was able to root successfully by running the two clockwork scripts back to back without a reboot.
A (very brief) guide to the CWR interface, for those who don't know it:
You will know your card is made correctly when you put it in your device and power on, and you see a clockwork gear nibbling at a nook N. Be patient while CWR loads; you will get to a screen with selectable menu choices.
Navigate up and down with the righthand buttons; navigate back with the lefthand upper button; choose an item or run a command using the raised n button.
Navigate down to "install zip file from sdcard" and hit N
Hit N again to "Choose Zip File from SDcard"
Navigate down to the first zip (labeled 1 of 2) and hit the n button
navigate to "yes - install"
hit the N button
once the first script is done, use the N button to navigate to and apply zip 2 of 2.
navigate back to the reboot menu using the lefthand side buttons. Once you are at the reboot menu item, you can pull the card, then reboot.
I used a 256 meg sdcard I had in the house for making the CWR disk. I find that to be a very convenient size for these disks - big enough to put a few files onto, not so big I wish I hadn't set it up as a CWR disk.
Click to expand...
Click to collapse
You know, it should be nice if before using the packages other people create, for your own project, you asked them for permission to use them, if not, at least create your own scripts.....
Yes I'm refering to me.... thats not cool.
Anyway, the two step process is not necessary here, thats just for preventing some Gapps database corruption, you edited that code away allready and there are no Gapps installed, so add the code to correct the permissions on the first zip, and everything should work fine, no need to rm dalvik either if you arent modifying framework.jar, etc, it should also speed the first boot time.
I apologize - this was intended to be a quick hack and largely for my own use (as I was testing stuff on both my and my girlfriend's glowworms) but I realized there were a lot of folks trying to root their gw's manually. I thought it worked well enough to share.
I didn't intend to present it as original and if I appeared to I apologize.
Say the word and I will yank the thread outright, and I would have no objection to your asking the mods to do so, either.
roustabout said:
I apologize - this was intended to be a quick hack and largely for my own use (as I was testing stuff on both my and my girlfriend's glowworms) but I realized there were a lot of folks trying to root their gw's manually. I thought it worked well enough to share.
I didn't intend to present it as original and if I appeared to I apologize.
Say the word and I will yank the thread outright, and I would have no objection to your asking the mods to do so, either.
Click to expand...
Click to collapse
Don't worry, just stating that before creating a thread with others people work, you should ask them.
Everything is fine, It didn't even pass my mind the idea of reporting it, we are a small niche community, active members must be praised, so dont worry, and I encorage you to keep deving ^^, just that before using other peoples work and starting a thread with it, ask them for permission, no one is gonna deny it and it's the kind way of doing things .
I'm planning to get my hands on a Glow tonight, so over the weekend I should be able to get together a full Nooter for it.
tiny noot - also works for older NST
Just so folks know, I've confirmed that the tinynoot rooter also works on the NST running 1.1.2 firmware.
It will probably work on earlier firmware also, since it is not replacing uRamdisk or framework files.
Are Supermanager and the Busybox Updater supposed to work? Supermanager crashes back to home, and Busybox won't install.
Did you apply both files, and is there an sd card in your device? I just tested the busybox updater and was able to get it to update the installed busybox. It requires that you have an sdcard inserted to work - I remember being puzzled by that the first time I tried using it on a device.
supermanager is crashing. I hadn't tried running it on the device before, and hadn't noticed that.
Looking at logcat, yes, supermanager's crashing in the background quite a bit. It seems to be looking for things which are not available, for instance, a dialer, and erroring out when it can't find them.
roustabout said:
[...] supermanager is crashing. I hadn't tried running it on the device before, and hadn't noticed that.
Click to expand...
Click to collapse
Supermanager has always been a problem, at least for me, using TouchNooter. I believe it's intended to provide file manager capability, particularly for installing APKs on uSD. Once I get Market (Play Store) access, reinstalling supermanager fixes the problem. At that point, I don't need it anymore.
I've always had to work around this when rooting my Touch devices. I'd suggest a basic file manager be provided instead for Day 1.
I'm rooted with tinynoot. Recently I've been experiencing excessive battery drain. I'm eliminating apps I'd installed to if that helps. Wondering if anyone has experience with apps that are problematic in that regard? Dropbox? Amazon Appstore? Facebook? 1Mobile Market? I assume nothing that was provided by default with tinynoot. Thanks.
Hi Glowco,
I'd suggest installing task management apps to get a view of what is actually running (not all processes relate to an installed app icon that you can uninstall). I use Advanced Task Manager to view running apps, and Autorun Manager to control what processes start up at boot time.
Ian
Thanks, I'll keep that in mind. In the meantime, as an experiment I uninstalled several apps including Amazon Appstore, 1Mobile Market, FB, and Wireless ADB. Good result - my battery charge hasn't decreased in an hour and a half. If I decide I miss them I can try adding them back and use your method.
That's good news!
I'd suggest that Wireless ADB is not to blame, since it does not stay resident once it's closed and in any case does nothing until you click the big red button
Of the others, I have Amazon Marketplace installed and I don't experience any battery issues (I'm Glownooted not Tinynooted but don't think that's relevant in this discussion), but I can't speak for the other two apps. If I were paranoid (and I am! ) I would point at Facebook, since it's purpose is marketing and wants to follow your every move
Ian
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.
I successfully rooted my Samsung Galaxy A320FL following more or less this guide (I know, it's a video and that's annoying, but it's also very clear. And there is a text version linked in description), with some modifications though.
I will write here what differs / is not specified in that guide.
I also attach all the files I used; they can also be found on the internet with some search.
Make sure to have installed on your PC Samsung USB driver for mobile phones, available on Samsung website.
I used different versions of the files needed (that guide is for Samsung 8). With the following files, everything worked well:
twrp-3.4.0-0-a3y17lte.img.tar
no-verity-opt-encrypt-6.0.zip
RMM_Bypass_v3_corsicanu.zip (learned this from another guide on this forum)
Magisk-v20.4.zip
Once TWRP is installed, the guide instructs you to install no-verity, then reboot to recovery and immediately after that reboot to system; only later, transfer and install magisk. THIS MESSED UP everything, in my case at least.
The solution was even faster: once TWRP is installed
plug USB and transfer all needed files (listed above) at once
install no-verity and reboot to recovery;
install RMM_bypass and reboot to recovery;
install magisk and reboot to recovery
reboot to system
Now you proceed following the rest of the guide.
After rooting, you may want to fix a few problems you may encounter: see next post.
HOW TO FIX FINGERPRINT AFTER ROOT
When your Galaxy A3 is rooted, unfortunately fingerprint will not work properly to log in on your apps (but it will work to unlock your phone). To fix this:
install from Google Play a file manager (like Solid Explorer)
in the left menu select ROOT folder, then rename
/system/priv-app/SamsungPass_1.3/SamsungPass_1.3.apk
to
/system/priv-app/SamsungPass_1.3/SamsungPass_1.3.apj
remove /data/app/com.samsung.android.samsungpass-1
reboot
This will remove SamsungPass. You will not be able to use SamsungPass anymore on your rooted phone, so forget the ability of saving passwords on websites and confirm them with fingerprint (you can still save passwords in browser or use google autofill; you just can't confirm them with fingerprint).
But, with the method above, at least you will be able to use fingerprint to log in those apps which natively support fingerprint login (like banking apps).
HOW TO MAKE BANKING APPS WORK ON A ROOTED PHONE
...Banking apps, though, tend to stop working when they detect a rooted phone. You can try to fix this using Magisk Hide feature.
Open Magisk and tap on the shield icon
Tap MagiskHide
Check your bank apps and any other app that want to prevent from detecting root. (According to the guides I read, hiding too many apps can be a problem: stick to what is really needed).
HOW TO MOVE WHATSAPP MEDIA FOLDER TO SD CARD
This was the main reason why I decided to root my phone: I was running out of storage. So I bought a high-quality and fast sd card (yes, it deserves your 20 €) and did the following:
Download "Apps2SD" (the original by Vicky Bonick; it's free) and follow instructions on how to create partitions.
You can create upto 3 partitions: 1st fat32/exfat/f2fs/ext4/ext3/ext2 (it's your SD card), 2nd ext2/ext3/ext4/f2fs (it is used to link the apps), 3rd swap partition (it's optional).
IMPORTANT: With Apps2SD you can LINK apps (they will end up in 2nd partition) or use FOLDER MOUNT (the chosen folder will end up in 1st partition, the one that looks like your normal SD card).
Please note that for Whatsapp media folder you will use FOLDER MOUNT method: so it will end up in the 1st partition. Create the 1st partition large enough for your whatsapp media.
Use "folder mount (app analyzer)" feature: it's like folder mount, but it's pre-set for some common apps, including Whatsapp. With this feature, you can successfully move Whatsapp media folder to SD, in one clic.
To understand what folder mount means: see FAQ.
In my case everything worked fine. When I reboot I have to re-mount folder, but it takes one second (just open Apps2SD, tap Folder Mount, slide "whatsapp other").
By the way, with App2SD you can do much more: you can move virtually any app to your SD card using the "Link apps to SD card" feature, as explained in Vicky's video.
...Hope this will save you some time!
airali said:
I successfully rooted my Samsung Galaxy A320FL following more or less this guide (I know, it's a video and that's annoying, but it's also very clear. And there is a text version linked in description), with some modifications though.
I will write here what differs / is not specified in that guide.
I also attach all the files I used; they can also be found on the internet with some search.
(...)
Click to expand...
Click to collapse
Thank you! I successfully used your compilation for a T-Mobile branded unit, all works after some tinkering. I didn't have the fingerprint problem, possibly the Samsung security thing is not the same on the carrier-modified ROM.
I had problems first making root work because of the succession of operations - basically, everything needs to be formatted in TWRP so it can mount partitions. Once I boot up the ROM, TWRP won't mount anymore → every zip you want to install, you need to do in one go before you reboot to Android.
I tried to root mine, but it didn't show up in odin, it did show up in device manager but I can't do anything with it, no transfering files via usb, etc.
The drivers are installed, I reinstalled them a couple of times, tried a different USB port, etc...
No sucess so far, I hope someone here can help me
Tap tap tap