Related
hello xdadev,
i really need your help. I am a newbie in android world [just purchased my first android device] last month [samsung galaxy tab p6800]. since then, i was really excited to explore android world and its features where I was led to this site.
now, heres my problem: just this afternoon, at first, i used my wifi to access a shopping mall internet connection. but minutes after turning my wifi off, when i turned it on again to connect to another network, i was surprised that it wont start and when i open the settings menu, under it says error. im really worried.
had my unit restored to factory settings but still no changes. Rooted my galaxy tab but today, i unrooted it thinking that the rooting caused the trouble.
im also hoping to update my tab to ICS but with this problem, im really stuck! i dont know how to access my apps in the appstore.
is this a firmware error or a hardware problem? please help me. my tab helps me a lot.
thanks in advance. im willing to add some details if you could help me.:crying:
try to go back to the mall where it 1st connected, if it still doesn't connect, then use your warranty and ask for replacement.
7.7 is notorious for being a bit choosy when it comes to wifi, sometimes, it just stuck with "obtaining IP address" then will revert back to scanning.
I also encountered your error before, but I just simply turn the wifi on and off again
before going back to your retailer, try to totally deplete the battery first (it's like removing the battery) then charge your unit and try to connect again
good luck
the last thing i could remember was busybox got updated but failed to install. is there any possibility that the failure caused the problem?
nope
biopsin said:
nope
Click to expand...
Click to collapse
Ah, sorry, busybox could, and may very likely be the culprit! An older version did just that to my (I have the 6810), and a number of others, tabs.
This was for Stericson's version 8.0 and here was his reply to my email:
Sadly you fell prey to a bug that was in Version 8.0 of my installer. I fixed it in 8.1, but it seems many still got the bugged version.
To fix the issue, you need to reflash your current rom. You do not need to wipe or clear any data.
You can also look in this thread: http://forum.xda-developers.com/showthread.php?t=1691410&page=2
It has an update method that should fix your issues.
Again, I apologize for this error
Please let me know if you need anything else from me.
I did just that and reflashed my rom using Odin and then re-rooted. I haven't, since, re-installed Stericson's busybox although later versions supposedly fixed the problem. I see there has just been another update in the Play store.
Damn I got the same error today, also after a lot of updates came trough.
Still working on fixing it. Will restore backup first after full wipe..
EDIT : Ok just went to recovery via power+volume up , factory reset, a nandroid restore and wifi working again.
Phew.
Ah! Got my tab working again. Thanks guys for the link and comments. The (update. Zip), did fix the issue. Busybox related bug. Starting to re download my apps again since I got my tab data wiped. :-(
Sent from my GT-P6800 using xda app-developers app
Not rooting my phone as of now. Will wait for the ICS first before rooting again. Tab is fully working already.
Sent from my GT-P6800 using xda app-developers app
Well, here is my story...
My cell phone is a Samsung Galaxy S3 mod. GT-I9300. Locked for Digitel (Venezuela mobile carrier). Android Stock Rom version: 4.1.2.
Preamble:
I bought this cellular a year ago, and it worked flawlessly almost for 12 months straight. I haven't experienced any single freezing or rebooting problem. I downloaded KIES and the program detected that a new version of Android was available for downloading for my phone. Bump! Error. I should have backed up my EFS first before doing the upgrading. BACKUP YOURS, IMPORTANT!)
NOTE: Backup your personal data as well since any ROM installation will remove for sure your personal data and info.
After upgrading and a few days later, my cellphone started to act somewhat funny. I started to got some freezing. To be specifically, my phone started to freeze, the screen just froze and nothing happened when I touched the screen, pressed any button. The only thing worked was to restart the cell (by pressing and holding the POWER button or by removing the batteries). Anyway, the freaking freezing problems continue occurring.
By the way, the warranty expired just a few days ago...
Since I couldn't do anything to stop the freezing problems, I decided to root the cell and install a new version of Android not official for Samsung and test its performance. But before that, I factory reset my cellphone, but it didn't work at all.
I tested several Android version I could find on internet: cm-11-20140....-i9300.zip, specifically, the SNAPSHOT, STABLE, NIGHTLY version. None of that worked, I also tested the cm-10-20... without luck. In fact, the freezing problems with those versions got worse and worse.
Taking the above in consideration, I decided to re-install the stock rom version (ver. 4.1.0) the one that was shipped with my phone when I bought it. You can find these version for any carrier in the world at: sammobile
I flashed and I used it for almost a day or so. During that period of time, I could feel that the freezing issues were gone, not even a freezing event. But unfortunately, I couldn't connect to any Mobile Network!!, so I had just bricked my cell phone !!! I took it to the cell carrier company (DIGITEL) and they could not do anything since my warranty already expired. WTF ! I was alone with my own problem now to sort it out.
SOLUTION !!
By no means I mean this is a cure but I have just stopped getting the hellish freezing and rebooting problems, and I just wanna share my experience with you so maybe I could help you to get rid of this annoying issues for the time being.
Picking up where I was left off, all I had was my bricked phone and a working ROM: ver. 4.1.2, So I decided to to reinstall this version back on my phone and see if it connected to the mobile carrier.
I reinstalled it and of course, after erasing cache partitions and making a factory reset. The procedures to install any ROM on your cellphone you can find it on internet (for instance, youtube may help a lot).
After I installed the version 4.1.2. my cellphone could connect to the mobile carrier once again... phewww!! But the freezing problems continued to appear in the fuc# phone. Well, now the only option I had to test thoroughly my cell was to install any application one after another but testing if the application was the culprit for the freezing issue.
But right after installing the stock Rom, I got a error message when my phone run to the first screen (Home Screen): TOUCHWIZ stopped responding... it lit my LIGHT BULB! I searched the web for the TOUCHWIZ and found out reports regarding many problems with Touchwiz.
Holy craps! The TOUCHWIZ is a BUGGY APPLICATION that comes with the STOCK ROM developed by SAMSUNG.
My friends there is no way to UNINSTALL that application but to use another LAUNCHER. I fired up and decided to download KIT KAT Launcher. Well, I downloaded the launcher and when you first run this application a windows pops up so you can decide what launcher the cellphone may use and the time to use it. I select ALWAYS I press the HOME button, the launcher to use is KIT KAT.
In addition to that I disable various stuffs, follows (you have to go through the setting app):
Disable Touch wiz (delete CACHE, and FORCE STOP)
Disable GPS
Disable Multi Windows
Disable Swipe Lock ( I found my cellphone freezes a lot while this is on)
I don't use a lot of widgets... but only one: The Clock and Alarm widget.
So far (it has passed 5 days straight without freezing). My phone froze on me while I was downloading something (maybe the phone was updating an app) and at the same time I was texting someone. I am suspicious that there is something to do with the downloading system too and the phone that could trigger a freeze.
Anyway, if you have experienced the freezing issue on your Galaxy S3 just like me, then try what I just outlined and give it a test. But do not download a bunch of program at the same time, just pick one by one, and allow some time to test your application and check if your phone is stable before continue with the next app to download and so forth. I have downloaded so far: whatsapp, BBM, sudoku and other games.
Hope you can get rid of the freezing problems just the way I did, any question feel free to ask.
I will continue posting any advance with my phone.
FROYCARD
PS: excuse my standard English.
Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom
kariiim said:
Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom
Click to expand...
Click to collapse
Nope,, it didn't work with my cellphone. I already tested it. As a matter of fact, I can name you all the ROM I flashed to my cellphone:
cm-11-20131115-UNOFFICIAL-i9300-V2
cm-11-20140104-SNAPSHOT-M2-i9300
cm-11-20140117-UNOFFICIAL-temasek-i9300-V36
cm-11-20140125-NIGHTLY-i9300
cm-10.2.0-i9300
None of the above rom I used stopped the freezing issue, that's why I needed to return to stock rom, and since then I am using it without experiencing any laggy or freezing.
Thanks anyway. :good:
Isnt it possible to create a rom with all of Samsungs bloat ripped off (TouchWiz included) and replaced with stock apps?
The problem is that non stock kernel roms use up a lot more battery than the stock one...
what?
i havent got this
Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.
jinosong said:
Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.
Click to expand...
Click to collapse
Yeah,,, you may be right I am a newbie... but since I stopped using TOUCHWIZ, I have experienced fewer a fewer lock-ups. I dunno what it is happening with my phone, but that is a fact. I am using KITKAT launcher.
The current stock ROM I am using is: 4.1.2 .... (I9300UBEMH2)
I am not familiar with undervolting to lower my phone's temp... maybe you can guide me about using it, or I could search the web for it.
UPDATE: I installed TWITTER Apps yesterday and each time I used it, it froze my phone for 12 min approx. Any suggestion?
Read the freezing thread sticky .
Delete this non working fix as well .
JJEgan said:
Read the freezing thread sticky .
Delete this non working fix as well .
Click to expand...
Click to collapse
Why should I? Are you a moderator of this forum?
Well I just want to update my post.
Yesterday I just wanted to continue figuring this freezing problem out. Since I published my experiences about freezing until yesterday the problem appears to have reduced significantly. I was using stock ROM ver. 4.1.2 flashed with KIES.
But I wanted to continue testing other ROM's. I tried to install a ROM named SAMMY'S ROM developed by guy named JustArchi (that I found in this forum). However I could not install it on my phone (SGS3 - GT-I9300) since it gave me some errors when I tried to install: ERROR STATUS 7
A margin note: This techie or nerdie called JustArchi gave me the boot from his thread for trying to seek help on this error.. so I trashed this SAMMY'S ROM and move on with another solution.
Whatever, I downloaded another official stock Rom ver. 4.3, released by SAMSUNG, intended for IRELAND - I am not from Ireland, but Venezuela (I founded it at SAMMOBILE under the top 10 latest firmware just released). By using ODIN, I flashed my phone, and to tell the truth, my phone feels differently. I haven't experimented any sluggish or lagging, not even a freezing so far (knocking on wood).
For precaution, I am installing one app at the time, and giving it time to see if everything is stable.
Conclusion: to any guys who is getting the annoying freezing, I think you must stick with it until your mobile carrier makes ROM ver. 4.3 available. Otherwise, if you are like me, wanting to work things out for yourself, download any ROM (ver. 4.3 compatible with your phone model) and test it on your phone. Before doing that, you just have to search the Internet for directions to do so, I am not responsible for what you do with your phone. I'll keep updating if another problem arises.
Note: since I am getting some rude comments from senior members who think they are too techie to read newbie's comments, queries, etc. I am not interested in their replies since they are not helping at all, thus I just ignore your lame comments from now on. Just scram.
Dude, you're really not helping anybody here with your information here. I don't know what you think you're sharing. The error 7 pertains to recover error which can be eliminated by installing an alternate recovery version.
I don't care if you're a newbie or not but you are spreading false info.
I'll scram now.
Hi guys,
after finally getting a new screen for my D802 (whole other story) I installed it and it worked great. Next step was to update to a newer ROM and Android etc. so I wanted to try out Lineage 14.1.
I got AutoRec to install TWRP, which went fine until it rebooted. The display started showing nothing but white stripes.
Because of anti-spam reasons I can't link to external websites and I can't find any way to upload pictures so I'm cheating with the link and hope that is okay, if not please delete the link and tell me how else I can show you pictures.
PICTURES HERE imgur.com/a/VcLR3
The first two are during the "LG" boot animation, the latter two are when it has loaded up the OS (I assume).
Did I somehow destroy my new display? I've looked around and found similar problems for some obscure ROMs and such, but it was never the whole display but rather just a few lines to the side, nor was it with such a simple, everyday task like AutoRec that seems to be working for a million people.
Is there anything I might be missing?
Assuming the display actually IS broken and I replaced it again, would the current configuration kill the new one as well? Since I don't have even 1% of screen to play with I don't see myself changing anything back to stock or so.
Thank you so much for any help.
Edit: I just found this thread https://forum.xda-developers.com/showthread.php?t=2680948, do you reckon this is my problem? There are no pictures, sadly. And if yes, how on earth can I do anything with no screen?
Just reflash stock kdz
Sent from my SM-G930F using Tapatalk
Thank you, I flashed some stock stuff and the display is working again. I would never have thought it was a software issue. Thanks!
My M30s (bought in September 2019) started rebooting randomly about a week ago. The last software update on the phone was in June 22nd (evidently the latest One UI Core update to version 3.1) . Device care did not show any red flags, but the restarts happen without any specific indication. I've sent error logs multiple times to Samsung support through the Samsung Members app, plus a log dump to a email address that was specified by another user on the Members site.
On the side I tried a lot of different things to try to stop these restarts, but nothing is helping.
I found out on Twitter that a number of Samsung Galaxy phones that came with same/similar Exynos processor have all faced this issue. And Samsung is apparently recommending a motherboard replacement.
https://twitter.com/i/web/status/1415681717919047700
If anyone else is seeing the same problem and has resolved this (without motherboard replacement), please reply with your solution!
But beyond that, I am trying to see if rooting the device and installing another will help. As a n00b, I have been struggling with that for the last two days. I've gone through the rooting process multiple times & patiently starting from scratch (flashing a stock ROM) every time.
But will rooting plus a custom ROM (Pixel Experience, potentially) get me past this random reboot issue?
Physically the phone still seems good and I have had no other issues before this random reboot problem started. So if persisting with a custom ROM install will help, please let me know. Otherwise, I will just shut this exercise and buy a new phone.
(P.S: Am a n00b. If someone can help me troubleshoot or can point me to a n00b proof rooting procedure), do let me know. The phone is no longer stock because I'm in the middle of another rooting exercise.)
I don't think you would have to root for that. You can just flash your original firmware to system which was working normally. You can find the files on the internet. You can use Odin and it'll be fine.
superstarksa said:
My M30s (bought in September 2019) started rebooting randomly about a week ago. The last software update on the phone was in June 22nd (evidently the latest One UI Core update to version 3.1) . Device care did not show any red flags, but the restarts happen without any specific indication. I've sent error logs multiple times to Samsung support through the Samsung Members app, plus a log dump to a email address that was specified by another user on the Members site.
On the side I tried a lot of different things to try to stop these restarts, but nothing is helping.
I found out on Twitter that a number of Samsung Galaxy phones that came with same/similar Exynos processor have all faced this issue. And Samsung is apparently recommending a motherboard replacement.
https://twitter.com/i/web/status/1415681717919047700
If anyone else is seeing the same problem and has resolved this (without motherboard replacement), please reply with your solution!
But beyond that, I am trying to see if rooting the device and installing another will help. As a n00b, I have been struggling with that for the last two days. I've gone through the rooting process multiple times & patiently starting from scratch (flashing a stock ROM) every time.
But will rooting plus a custom ROM (Pixel Experience, potentially) get me past this random reboot issue?
Physically the phone still seems good and I have had no other issues before this random reboot problem started. So if persisting with a custom ROM install will help, please let me know. Otherwise, I will just shut this exercise and buy a new phone.
(P.S: Am a n00b. If someone can help me troubleshoot or can point me to a n00b proof rooting procedure), do let me know. The phone is no longer stock because I'm in the middle of another rooting exercise.)
Click to expand...
Click to collapse
I too was facing random freezing reboot etc
I tried every custom rom ,flashing old firmware, nothing worked.
But today I finally found 100% Working solution and did short yt video so please watch and share I it worked for you.
superstarksa said:
My M30s (bought in September 2019) started rebooting randomly about a week ago. The last software update on the phone was in June 22nd (evidently the latest One UI Core update to version 3.1) . Device care did not show any red flags, but the restarts happen without any specific indication. I've sent error logs multiple times to Samsung support through the Samsung Members app, plus a log dump to a email address that was specified by another user on the Members site.
On the side I tried a lot of different things to try to stop these restarts, but nothing is helping.
I found out on Twitter that a number of Samsung Galaxy phones that came with same/similar Exynos processor have all faced this issue. And Samsung is apparently recommending a motherboard replacement.
https://twitter.com/i/web/status/1415681717919047700
If anyone else is seeing the same problem and has resolved this (without motherboard replacement), please reply with your solution!
But beyond that, I am trying to see if rooting the device and installing another will help. As a n00b, I have been struggling with that for the last two days. I've gone through the rooting process multiple times & patiently starting from scratch (flashing a stock ROM) every time.
But will rooting plus a custom ROM (Pixel Experience, potentially) get me past this random reboot issue?
Physically the phone still seems good and I have had no other issues before this random reboot problem started. So if persisting with a custom ROM install will help, please let me know. Otherwise, I will just shut this exercise and buy a new phone.
(P.S: Am a n00b. If someone can help me troubleshoot or can point me to a n00b proof rooting procedure), do let me know. The phone is no longer stock because I'm in the middle of another rooting exercise.)
Click to expand...
Click to collapse
Rooting or flashing custom rom won't help as I've tried everything with my galaxy a50 but the issue still persists. It's related to hardware of the device. Maybe some loose connections in the motherboard. Unfortunately, we don't have skilled local repair guys in India(assuming you too belong to India) who could look into this.
abhi-km said:
I too was facing random freezing reboot etc
I tried every custom rom ,flashing old firmware, nothing worked.
But today I finally found 100% Working solution and did short yt video so please watch and share I it worked for you.
Click to expand...
Click to collapse
Dude under clocking it won't help. You're just garnering views, nothing else. Stop being silly dude, just wasted my time watching your video.
abhishekpandey.468 said:
Dude under clocking it won't help. You're just garnering views, nothing else. Stop being silly dude, just wasted my time watching your video.
Click to expand...
Click to collapse
If you under clock all cores below 1ghz and set selinuxe to permissive mode then magic happens.not even single reboot in last 26 days. Before it was restarting every 5, 10 minutes.
I am also facing the same issue with my M21, downgraded to android 10, but it didn't help. Any suggestions?
After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa
TommyQuid said:
After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa
Click to expand...
Click to collapse
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.
kanesglove said:
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.
Click to expand...
Click to collapse
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.
kanesglove said:
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.
Click to expand...
Click to collapse
you guys offer little information at all so this is why no one helps you. Maybe tell what firmware version you flashed what root version you did etc. There is a big difference between bootloader revB/11 and the others
Holy ****. Did I just get constructive suggestions from jrkruse?! Dude if you told me I could fix my phone by sucking a fart out of a wallaby's ass I'd do it cuz the advice came from you, and if there's one thing I know it's that you know your ****. You're ****in' awesome. I feel so special now. Ok sorry about that...
Well, I'm not too sure about the OP but I can tell you about the phone I have that seems to have the same issue.
My S7 Edge is a SM-G935V on android 7.0 on update 4BQK2. Prior to rooting I put everything to stock then I did a NAND erase and repartition. No issues with any of that.
I rooted my phone from this post
G935V Root Method. No Lag! No Heat!
G935V Root Method. No Lag! No Heat!
I AM NOT RESPONSIBLE FOR ANY OF YOUR ISSUES! ALL I CAN DO IS RECOMMEND A GOOD PSYCHOLOGIST! Hey guys. Stumbled on this by accident. I HAVE ABSOLUTELY NO IDEA WHY IT WORKS, BUT IT DOES. THE METHOD HAS BEEN TESTED BY ME AND A FEW OTHER PEOPLE HERE...
forum.xda-developers.com
which directs to your older method for gaining root privileges.
[DISCONTINUED] ROOT Method For Nougat
DISCONTINUED New Thread Found Here This Root Method For S7 Nougat Nougat_S7_Root_2_82_All_Carriers_V2.zip Includes Fingerprint Fix [Latest Verison] Nougat_S7_Root_2_81_All_Carriers_V2.zip Includes Fingerprint Fix Nougat_S7_Root_2_79_All.zip...
forum.xda-developers.com
I also flashed Unzip the Nougat_S7_Root_2_82_All_Carriers_V2.
Then I flashed the BL file in the BL slot from the G935U firmware with odin checking "Phone Bootloader Update". I used the BL file from G935UUES4BRA1 since it's the closest update for the U brand to the firmware this phone is on (G935VVRU4BQK2)
I'm aware that there are newer methods for gaining root access but I chose this method cuz I used it back in 2017-2018, I had read all the posts in the thread, and I knew it worked.
I currently have 3 S7 Edge phones all on the same firmware and build and are all rooted with the same combo method I just explained. The other 2 phones also have xposed installed and they both work well.. expect mine says weird stuff instead of the callers information. I think it only does it if they're a contact but in the notification tab it says an example like this 5556661234;verstat=No-TN-Validation. No clue how to fix that.
The phone that is having the same issue as the OP still had access to the private/secure folder when it was rooted; which I thought was weird cuz mine doesn't and from what I understood private mode gets disabled if the phone's rooted. Maybe it only gets disabled if you install xposed? I don't know. My son had the phone with the issue and it was his first smart phone and he dropped it a few times (with a case) so I was thinking it's an effect from something he downloaded from the play store (he's 20 now but pretty still very ignorant with android). Now I'm not sure if it's a software or hardware issue since the problem persisted after the NAND erase.
Something to note about my sons old phone also is that it has 2 thin pink lines running down one side of the screen (defective/dead pixels) and when the screen turns off it it flashes once before actually turning off. One time over the phone I tried troubleshooting the issue with him and he ended up being able to use his camera immediately after rebooting the phone though once he exited the camera app it wouldn't open again. We were trying a bunch of things, force closing any app I thought would be related to the issue. Not sure what allowed it work when it did, but even now right after a reboot the camera app still crashes.
This was long ago, I've since lost the phone. But, I was on the A bootloader and on OREO rooted using @/billa's method using an ENGboot file. I tried everything possible to get the camera to work including flashing back to stock but nothing helped. I just gave up finally. @kanesglove maybe try safely updating the firmware. Hope it helps