Related
Hey all. Fist off, sorry about the new account and posting here in the Q&A and not development, but let me explain. I have been a member of XDA for a few years- my main account(and only account until being forced to create this one) is andr0id23. However, I am unable to login to that account. I keep getting an incorrect password error message and am constantly locked out of my account. I have emailed the people who can help with this issue, but still not having any luck. They did reset my password(even though I knew my password), but that still doesn't work. I try it once but it says i have used up all my attempts and locks me out for what is supposed to be 15 minutes, but seems to be forever instead. But I digress, just wanted to explain why I am posting from a brand new account and in this section(new accounts are not allowed to post in development). Now on to my issues I am hoping someone can help with. I typed it up in notepad last night while waiting for my account to be accessible and am just going to copy and paste it:
Hi all, I was hoping to get some help on my Galaxy Note 8.0. It is model number GT-N5110. It was given to me by a friend, who likes
to try rooting his devices, but has no experience and is actually quite computer illiterate. When I received it it wouldn't boot up,
but only go do a screen that says something like "Downloading. Please do not power off". I have no idea what is on there as far as firmware
or custom ROMs.
I am pretty comfortable with Android development as far as flashing custom ROMs, rooting, unlocking bootloaders, etc, but haven't been active for
some time now. I have owned a Droid, Droid 2, HTC Incredible, Droid X, HTC Thunderbolt, and Motorola Xoom and have rooted,
unlocked, and/or installed custom ROMs on all of them, ass well as doing so on several devices that aren't mine. I have used "one click" type methods
as well as more hands-on adb methods. I just mention so to show that while I am far from an expert, I do have some experience.
But I am stuck on this tablet. I can boot into Download Mode and was able to flash CWM Recovery via Odin. In CWM I tried
wiping data, cache and Dalvik cache, but when I go to reboot I get a message saying the device is not rooted and would I like to root. It doesn't seem to do any
good. I did try rooting thru odin, and it said it was successful. I have also flashed the stock firmware thru odin, but am still not able to boot. The
closest I get is a boot loop. Also, Kies does not recognize my device.
So, I can boot into download mode and CWM Recovery(though I don't know if I am actually rooted
and it will be of any use), and Odin does recognize the device. I have tried flashing stock firmware to no avail. If anyone
has any suggestions, I would be greatly appreciative and definitely willing to try. I can give you any additional info you
request. I was thinking of flashing a custom ROM, but not sure as I don't know what the tablet is currently running. If anyone
has anything to try as far as flashing a ROM or firmware, a d/l link would be greatly appreciated if at all possible.
I have been having the worst luck with samfirmware or sammobile(two sites that are named something like that). I have spent
literally hours waiting for the downloads, and the 2 times i did get lucky, the files were messed up. Again, I would be
extremely greatful for any and all help.
Nashtar said:
Hey all. Fist off, sorry about the new account and posting here in the Q&A and not development, but let me explain. I have been a member of XDA for a few years- my main account(and only account until being forced to create this one) is andr0id23. However, I am unable to login to that account. I keep getting an incorrect password error message and am constantly locked out of my account. I have emailed the people who can help with this issue, but still not having any luck. They did reset my password(even though I knew my password), but that still doesn't work. I try it once but it says i have used up all my attempts and locks me out for what is supposed to be 15 minutes, but seems to be forever instead. But I digress, just wanted to explain why I am posting from a brand new account and in this section(new accounts are not allowed to post in development). Now on to my issues I am hoping someone can help with. I typed it up in notepad last night while waiting for my account to be accessible and am just going to copy and paste it:
Hi all, I was hoping to get some help on my Galaxy Note 8.0. It is model number GT-N5110. It was given to me by a friend, who likes
to try rooting his devices, but has no experience and is actually quite computer illiterate. When I received it it wouldn't boot up,
but only go do a screen that says something like "Downloading. Please do not power off". I have no idea what is on there as far as firmware
or custom ROMs.
I am pretty comfortable with Android development as far as flashing custom ROMs, rooting, unlocking bootloaders, etc, but haven't been active for
some time now. I have owned a Droid, Droid 2, HTC Incredible, Droid X, HTC Thunderbolt, and Motorola Xoom and have rooted,
unlocked, and/or installed custom ROMs on all of them, ass well as doing so on several devices that aren't mine. I have used "one click" type methods
as well as more hands-on adb methods. I just mention so to show that while I am far from an expert, I do have some experience.
But I am stuck on this tablet. I can boot into Download Mode and was able to flash CWM Recovery via Odin. In CWM I tried
wiping data, cache and Dalvik cache, but when I go to reboot I get a message saying the device is not rooted and would I like to root. It doesn't seem to do any
good. I did try rooting thru odin, and it said it was successful. I have also flashed the stock firmware thru odin, but am still not able to boot. The
closest I get is a boot loop. Also, Kies does not recognize my device.
So, I can boot into download mode and CWM Recovery(though I don't know if I am actually rooted
and it will be of any use), and Odin does recognize the device. I have tried flashing stock firmware to no avail. If anyone
has any suggestions, I would be greatly appreciative and definitely willing to try. I can give you any additional info you
request. I was thinking of flashing a custom ROM, but not sure as I don't know what the tablet is currently running. If anyone
has anything to try as far as flashing a ROM or firmware, a d/l link would be greatly appreciated if at all possible.
I have been having the worst luck with samfirmware or sammobile(two sites that are named something like that). I have spent
literally hours waiting for the downloads, and the 2 times i did get lucky, the files were messed up. Again, I would be
extremely greatful for any and all help.
Click to expand...
Click to collapse
I would download stock ROM and flash with Odin 3.07. There are a number of threads that explain the process. Here is one... http://forum.xda-developers.com/showthread.php?t=2728370&page=3
GT-N5110 & GT-N5120 - 64GB 633x on board, Status Official on SafeRooted OEM ROMs with Wanam Xposed and RootCloak. The only way to fly 8+ hours!
This badboy don't play with Play & Triangle away!
gooberdude said:
I would download stock ROM and flash with Odin 3.07. There are a number of threads that explain the process. Here is one... http://forum.xda-developers.com/showthread.php?t=2728370&page=3
GT-N5110 & GT-N5120 - 64GB 633x on board, Status Official on SafeRooted OEM ROMs with Wanam Xposed and RootCloak. The only way to fly 8+ hours!
This badboy don't play with Play & Triangle away!
Click to expand...
Click to collapse
I was never able to grab any downloads from SamMobile or SamsungUpdates. It just loads forever until it times out. I did, however, grab a stock firmware download from another thread. I flashed it with Odin 3.07 but it did nothing for me. I am attempting to download the files from the 2 sites again now. Hopefully I'll have better luck. Thanks
Idiot
Ok so I am a complete tool. I was able to get it going. I knew what to do, and was doing it, but was doing it wrong. The thread you linked made it dawn on me. I was able to flash the stock firmware through odin 3.7. Sorry if I wasted your time and I thank you wholeheartedly. Now time to root and have some fun :good:
I've had my M8 since about the end of 2014. Originally on Android 4, have since done OTA upgrades to 5 and 6 as they were flagged as available by my carrier (UK, O2).
I've never managed to get HTC Backup on my PC to recognise the phone, even with the original USB cable, so have never done a proper backup (Yes. I know). Fortunately for me, my Gmail contacts list was almost up to date, and apart from my calendar, that was the most important thing to save, so I've just had to grin and bear it.
Because of the lack of proper backup and therefore the facility to restore from one, I'd never done a factory reset after the various OS upgrades, which I've been told might have avoided my present situation, which is that I can't get any further than a bootloop situation. Other than that, I can get into recovery mode, but no further.
I've tried clearing the cache, I've tried a factory reset. Neither of those have got me anywhere.
I've no great desire (at present) to go fiddling with rooting or anything clever with the phone, I'd just like to get it working again. I've downloaded Android Studio to get the SDK for ADB but don't really know what I'm doing, and if I mess around without expert advice I could end up with a hard brick - which is why I'm here.
Can anyone give me some guidance about what I need to do to get my phone working again?
Thanks in advance...
Hi, I have the same problem, started a few days ago when I was trying to download VLC from the play store, the phone rebooted and said optimizing apps.... It has been in an optimizing apps bootloop since - it gets to the end, then says starting android then freezes and reboots, then starts again... I tried clearing the cache and doing the factory reset as well but nothing helps. We could really use some expert help on this :S
If a stock phone isn't booting, and factory reset doesn't help, the OS is possibly damaged or corrupted in some way; and needs to be restored.
If your version has RUU, you can try to run that.
If no RUU for your version, then probably your only choice is to unlock the bootloader, install custom recovery, so you can restore a stock TWRP backup from the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I am in a very similar situation, apparently because of a botched automatic system update, almost same symptoms as airick94. I haven't tried a factory reset yet though, because I want to try to recover what I can from the internal storage first. Can I do that through ADB even if my phone is not recognised as a device by the computer?
Hi, everyone! I have an unrooted, stock firmware (well, not anymore), Verizon Galaxy Note 4 (N910V).
Now, after I attempted to update, through the prompt in my status bar... everything went haywire. I can't even do a factory reset from recovery, and all I can get to is the Verizon logo as it turns on. And nothing else. I went to a Samsung Tech Center in a Best Buy, but because my phone (somehow, never rooted it and did a factory reset after I tried and failed) says Custom on the first bootup screen, the guy wouldn't touch it. How can I fix this myself? I have Odin, and the Samsung Drivers. I have searched around the web, but I have been unable to find a STOCK version of 6.0.1 to flash using Odin. If someone could help me find a way to fix this, even if it doesn't involve flashing, I'd be greatly appreciative. I've searched around on countless forums, including this one, and I haven't found any ways to fix this so I was attempting to do it myself. But, being unable to find a stock version of 6.0.1 for the device itself, or, at least my specific version, I can't do anything right now and I have now been without a phone for two days. Not a huge amount of time, but when you're waiting on a call for a job interview, it's nerve wracking. Thanks in advance!
firmware
CodytheFox said:
Hi, everyone! I have an unrooted, stock firmware (well, not anymore), Verizon Galaxy Note 4 (N910V).
Now, after I attempted to update, through the prompt in my status bar... everything went haywire. I can't even do a factory reset from recovery, and all I can get to is the Verizon logo as it turns on. And nothing else. I went to a Samsung Tech Center in a Best Buy, but because my phone (somehow, never rooted it and did a factory reset after I tried and failed) says Custom on the first bootup screen, the guy wouldn't touch it. How can I fix this myself? I have Odin, and the Samsung Drivers. I have searched around the web, but I have been unable to find a STOCK version of 6.0.1 to flash using Odin. If someone could help me find a way to fix this, even if it doesn't involve flashing, I'd be greatly appreciative. I've searched around on countless forums, including this one, and I haven't found any ways to fix this so I was attempting to do it myself. But, being unable to find a stock version of 6.0.1 for the device itself, or, at least my specific version, I can't do anything right now and I have now been without a phone for two days. Not a huge amount of time, but when you're waiting on a call for a job interview, it's nerve wracking. Thanks in advance!
Click to expand...
Click to collapse
hsbadr has all the firmware listed here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937, he has uploaded the full Odin flashable firmware for Retail N910v in that thread Full Firmware: https://www.androidfilehost.com/?fid=24588232905720218
Hope that helps you.
CodytheFox said:
Hi, everyone! I have an unrooted, stock firmware (well, not anymore), Verizon Galaxy Note 4 (N910V).
Now, after I attempted to update, through the prompt in my status bar... everything went haywire. I can't even do a factory reset from recovery, and all I can get to is the Verizon logo as it turns on. And nothing else. I went to a Samsung Tech Center in a Best Buy, but because my phone (somehow, never rooted it and did a factory reset after I tried and failed) says Custom on the first bootup screen, the guy wouldn't touch it. How can I fix this myself? I have Odin, and the Samsung Drivers. I have searched around the web, but I have been unable to find a STOCK version of 6.0.1 to flash using Odin. If someone could help me find a way to fix this, even if it doesn't involve flashing, I'd be greatly appreciative. I've searched around on countless forums, including this one, and I haven't found any ways to fix this so I was attempting to do it myself. But, being unable to find a stock version of 6.0.1 for the device itself, or, at least my specific version, I can't do anything right now and I have now been without a phone for two days. Not a huge amount of time, but when you're waiting on a call for a job interview, it's nerve wracking. Thanks in advance!
Click to expand...
Click to collapse
With a "Custom" on the opening splash screen, someone's been messing with the phone. When you can come clean with what you did to your phone, we might be able to help. Otherwise, use the search function to find out how to fix your phone when you've screwed it up.
Why LIE about what you did to the phone to XDA? Sure, lie to Samsung, VZ, BestBuy, etc, but what possible reason would you have to lie here when you are asking for help?
So yesterday, the beta for Fortnite on android came out and I obviously signed up immediately. I selected my device, signed up, and downloaded the installer which would not open. I did not do any research, but assumed that the problem had to do with xposed. I disabled xposed and sure enough, the installer opened, but now it said that my device was not compatible. After some research, i saw that the beta was only going to be for samsung devices for about 30 days so, naturally, i tried to figure out a way to circumvent this restriction. I thought back to my early android days and my spoofing of devices with build.prop and decided to replace some of the entries such as "ro.build.vendor", "ro.build.model", etc. with those from the Galaxy S9. After a quick reboot, it actually worked to my surprise. I was clearly excited at this point and spent about 45 minutes on mobile data downloading Fortnite and then downloading the game files. Finally, the game was downloaded, i was signed into my account, and I was waiting to join a Lobby. After entering a lobby and dropping out of the bus, I was descending towards tomato town to test out my favorite game on my favorite device when suddenly the loading screen came back up(this is where my luck took a turn for the worst). I was returned to the main menu and given a message along the lines of "Fortnite cannot be played on devices that do not pass safetynet, have an unlocked bootloader, or are rooted... Attempting to bypass this check may result in permanent account ban" At this point I began to get annoyed and figure that since I had come all this way I would just keep going. I went and turned on magisk hide from the magisk manager and set it to hide xposed. I then used the option to reinstall magisk under a different package name. I continued to enable exposed again and enable x privacy(I was planning on attempting to do exactly what i had been warned against by Fortnite). I then rebooted and... well, didn't reboot. I got stuck on the green RAZER circle for a bit then the screen just went black. After a few reboots i decided to restore my build.prop through TWRP. This didn't help at all so I decided to clear the cache and dalvik(this didnt work). At this point i decided to back up my photos and the Fortnite apk to my sd card and do a reset through TWRP. The reset did nothing so i figured I would try installing a custom ROM. I downloaded and installed resurrection remix. On the first boot i was greeted with the storage decryption prompt. I entered my password and it said that it was successfully decrypted but was corrupt and i had to factory reset. I pressed the button and the device went to the RAZER logo then turned off. I tried another boot tand the same thing happened so I went to TWRP manually and did yet another reset..... it failed. This is where i panicked. I went through twrp and did a bunch of **** like try to fix contexts and repair data until finally something succeeded and I was able to wipe data. From there I again booted into resurrection remix where it just hung on the boot gif. I plugged the phone into my pc and ran "adb logcat" and it said something about missing files in vendor. I then remembered that I had the RAZER factory images downloaded. I tried the flashall.bat and that just hung on the first command that was only supposed to push 44kb. I knew I had severely fluckled up at this point so seing as there was nothing else to lose I went back into twrp and tried to flash Resurrection again. After that succeeded and i pressed reboot on TWRP I was warned that no system image was installed. Remembering about the vendor thing from before, I pulled the stock vendor image and installed it through TWRP. I was going to flash all the images manually. I was unaware that flashing to vendor would remove TWRP so afte ra unwanted reboot, TWRP was gone for good. Since then, I have tried numerous things in download mode and am always met with messages such as "write failed {no error}", "a/b permissions not supported", "bootloader update required", and many moooore.
At this point I feel that all hope is lost but I feel that I have learned a valuable lesson and can be used as a perfect example of why you should think before you act. I would like to still ask for help from peers who are most likely infinitely more knowledgeable than I am. If you feel that you can help contribute to saving my baby(RAZER phone) in any way or you feel that this helped you in some way, don't hesitate to reply to this thread.
Thank you all for reading to this point and thank you in advance for any insight you have to offer.
Firstly, may I empathize with your pain, and I do need to say..."whooops". Maybe this can only be repaired from a RMA to Razer themselves. I'm not someone who roots his Android devices as I prefer them "as is" but I am a major Linux user and faff with those OSes till I break them. maybe contact Razer with the issue, maybe they can help. And again.....you have my sympathys.
Yeah, I'm going to wait a few days and see if either I can figure anything out or someone else can help me, but after that I will probably contact them. I just hope this doesn't end up being an expensive repair if it comes to sending an RMA. Thanks for your sympathy btw ???
I hate to say this, but today I finally got Fortnite installed and ready for use, totally officially, from epic games, and I'm now awaiting my email with my login access...yes, you may kick me, I will accept a virtual kick.
See, this hurts, it really does. I’m not going to virtually kick you though. I like to be kept in the loop on developments like this. ?
Just to make sure...did you try installing the stock image?
Why don't you just flash a fastboot image from MR1?
https://s3.amazonaws.com/cheryl-factory-images/cheryl-o-global-5038.zip
Yes I tried. That was the first thing I did when things started going south for the winter but it did not do anything. It kept giving the errors that i spoke of such as "unknown command" or "failed(no error)".
So without coming here first. I got my Fortnite invite, went through the install, jumped out of the bus and ...... then received the, you can't be rooted error message. #EPICfail
I haven't done anything else yet except close Fortnite. I'm now afraid to reboot for fear of ending up in the same position as @ShaneRagans. And I really feel like Epic Games should have announced that rooted phones wouldn't be compatible. Kinda pissed about it really.
lostnsound said:
So without coming here first. I got my Fortnite invite, went through the install, jumped out of the bus and ...... then received the, you can't be rooted error message. #EPICfail
I haven't done anything else yet except close Fortnite. I'm now afraid to reboot for fear of ending up in the same position as @ShaneRagans. And I really feel like Epic Games should have announced that rooted phones wouldn't be compatible. Kinda pissed about it really.
Click to expand...
Click to collapse
Did you do everything else the OP did, like changing build.prop? Or were you able to just install and attempt to play then it shut you out?
I received that same error message, but I'm not rooted, it seems the beta hasn't been properly coded to see changes in device status and architecture as ok. I also believe that epic games have bypassed the Google play store as they cannot guarantee the stability of the app and it would be seen by Google play store as defective. Maybe its something we need to wait for them to get fixed. Remember this is a "beta" version and is still in development.
lostnsound said:
So without coming here first. I got my Fortnite invite, went through the install, jumped out of the bus and ...... then received the, you can't be rooted error message. #EPICfail
I haven't done anything else yet except close Fortnite. I'm now afraid to reboot for fear of ending up in the same position as @ShaneRagans. And I really feel like Epic Games should have announced that rooted phones wouldn't be compatible. Kinda pissed about it really.
Click to expand...
Click to collapse
As long as you did not edit anything within your system, you should be fine. The game itself did not brick my phone, I bricked my phone because I was careless. I do however agree 100% that there should have been some sort of prior notice that rooted phones would not be compatible because it would have given me some time to do proper research on returning to stock before hand.
ShaneRagans said:
So yesterday, the beta for Fortnite on android came out and I obviously signed up immediately. I selected my device, signed up, and downloaded the installer which would not open. I did not do any research, but assumed that the problem had to do with xposed. I disabled xposed and sure enough, the installer opened, but now it said that my device was not compatible. After some research, i saw that the beta was only going to be for samsung devices for about 30 days so, naturally, i tried to figure out a way to circumvent this restriction. I thought back to my early android days and my spoofing of devices with build.prop and decided to replace some of the entries such as "ro.build.vendor", "ro.build.model", etc. with those from the Galaxy S9. After a quick reboot, it actually worked to my surprise. I was clearly excited at this point and spent about 45 minutes on mobile data downloading Fortnite and then downloading the game files. Finally, the game was downloaded, i was signed into my account, and I was waiting to join a Lobby. After entering a lobby and dropping out of the bus, I was descending towards tomato town to test out my favorite game on my favorite device when suddenly the loading screen came back up(this is where my luck took a turn for the worst). I was returned to the main menu and given a message along the lines of "Fortnite cannot be played on devices that do not pass safetynet, have an unlocked bootloader, or are rooted... Attempting to bypass this check may result in permanent account ban" At this point I began to get annoyed and figure that since I had come all this way I would just keep going. I went and turned on magisk hide from the magisk manager and set it to hide xposed. I then used the option to reinstall magisk under a different package name. I continued to enable exposed again and enable x privacy(I was planning on attempting to do exactly what i had been warned against by Fortnite). I then rebooted and... well, didn't reboot. I got stuck on the green RAZER circle for a bit then the screen just went black. After a few reboots i decided to restore my build.prop through TWRP. This didn't help at all so I decided to clear the cache and dalvik(this didnt work). At this point i decided to back up my photos and the Fortnite apk to my sd card and do a reset through TWRP. The reset did nothing so i figured I would try installing a custom ROM. I downloaded and installed resurrection remix. On the first boot i was greeted with the storage decryption prompt. I entered my password and it said that it was successfully decrypted but was corrupt and i had to factory reset. I pressed the button and the device went to the RAZER logo then turned off. I tried another boot tand the same thing happened so I went to TWRP manually and did yet another reset..... it failed. This is where i panicked. I went through twrp and did a bunch of **** like try to fix contexts and repair data until finally something succeeded and I was able to wipe data. From there I again booted into resurrection remix where it just hung on the boot gif. I plugged the phone into my pc and ran "adb logcat" and it said something about missing files in vendor. I then remembered that I had the RAZER factory images downloaded. I tried the flashall.bat and that just hung on the first command that was only supposed to push 44kb. I knew I had severely fluckled up at this point so seing as there was nothing else to lose I went back into twrp and tried to flash Resurrection again. After that succeeded and i pressed reboot on TWRP I was warned that no system image was installed. Remembering about the vendor thing from before, I pulled the stock vendor image and installed it through TWRP. I was going to flash all the images manually. I was unaware that flashing to vendor would remove TWRP so afte ra unwanted reboot, TWRP was gone for good. Since then, I have tried numerous things in download mode and am always met with messages such as "write failed {no error}", "a/b permissions not supported", "bootloader update required", and many moooore.
At this point I feel that all hope is lost but I feel that I have learned a valuable lesson and can be used as a perfect example of why you should think before you act. I would like to still ask for help from peers who are most likely infinitely more knowledgeable than I am. If you feel that you can help contribute to saving my baby(RAZER phone) in any way or you feel that this helped you in some way, don't hesitate to reply to this thread.
Thank you all for reading to this point and thank you in advance for any insight you have to offer.
Click to expand...
Click to collapse
I feel your pain i locked me bootloader and bricked my phone crying atm
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
i tried many thing as well but if your bootloader is unlocked try use the 7.1.1 ver and add -i 0x1532 to the command
btw anyone wanna buy a paper for lol
Do any of you guys that bricked your phones happen to have 3 rescue?
It costs £100 but you'll get a new phone next day no questions asked.
I did this when I bricked my Samsung galaxy S6 edge+ last year.
It's expensive, but surely better than having a £500 paper weight.
Just wanted to let everyone know that Razer repaired it for $15.
Hello all!
I recently got gifted a Samsung Galaxy Z Fold4 and it's one of the nicest phones I've had. I am not sure why I can't find any info online about this phone or the topic on this forum but I am in search of some answers. I don't know how I got to this state but I broke the phone.... I was playing around installing some apk games when all of the sudden one of them didn't install. I searched for the app but it was nowhere in sight. I am not sure if the phone is virused(after countless factory resets) but it started behaving really weirdly after. No apps where loading(it was just an infinite loading screen), when I tried to log in into apps it was nearly impossible because of the infinite loading which after some time turned into an "operation failed" screen. After I factory reset the phone, I noticed even stranger behavior. The "Getting your phone ready" screen was taking ages and sometimes even failing. then, when I tried to log in with iCloud in smart switch, I would get blocked by an infinite loading which required a restart. The first time I fixed the phone by going into the boot screen(or however it's called) by connecting to a PC and then erased cache partition and factory reset. This seemed to fix the phone. Fast forward some time later, I was messing with another game apk when the same thing happened again but this time, the previous solution was tried but to no avail. Now I am stuck with a bricked phone which is slower than a Nokia and sometimes it even fails completely. Also tried booting into bootloader but the phone would just restart itself and not work. I am in desperate need of help since I can't see this brick on my desk getting dustier day by day. I can provide all the info needed if necessary.
I'm sorry if this is the wrong topic or not the right place. I am new to this community.
Thanks in advance
My first question is have you tried to reflash the stock firmware with ODIN? see if that fixes any issues.
secondly, why install dodgy apks twice? once should have been the warning needed.