Related
Hey everyone. I just got an OTA update for my Note 8.0 LTE (AT&T). It's a small update (16.3MB). The new firmware build is I467UCAMF2. This is probably just a bugfix update but OTAs are almost always a good thing.
Sent from my Galaxy S4 using Tapatalk 4 Beta
Yeah got it this morning... was hoping it would fix the screen from becoming unresponsive. Did not fix it
Sent from my SAMSUNG-SGH-I467 using XDA Premium HD app
Update the Software for the Samsung Galaxy Note 8.0 (i467)
Update summary
The latest software package updates the baseband version to I467UCAMF2, and includes improvements to the initial setup process on the device. The update is available for download over a Wi-Fi network connection.
What to expect after the update
Although there should be no impacts to settings or data, we recommend that you back up your media files to an SD card, a PC, or using a favorite application (from the Play Store), prior to upgrading the software. For information on backing up and restoring your phone using Samsung Kies, click here.
How to update
Customers will receive an alert and be prompted to download the update, or have the option to initiate the update manually. When prompted, you can postpone the update up to 3 times, and 4 hours per occurrence. After the update has been postponed for the maximum allowable time, your device will automatically download and install the update.
Note: Before the update can begin, your tablet must be connected to a Wi-Fi network.
To initiate the update manually, go to Settings .
Scroll to the "System" section, and then tap About device > Software update > Check for updates.
Tap OK.
The device will determine if new software is available, and begin downloading the software update. Once complete, the device will restart.
Please wait until your tablet reboots completely, and then tap Done to finish.
How to verify the update
From the home screen, tap Settings .
NOTE: Alternatively, from the home screen, press the Menu key, and then tap Settings.
From the "more" tab, tap About device. The following information will be displayed:
Android version: 4.1.2
Baseband version: I467UCAMF2
Build number: JZO54K.I467UCAMF2
Archon810 said:
Update the Software for the Samsung Galaxy Note 8.0 (i467)
Update summary
The latest software package updates the baseband version to I467UCAMF2, and includes improvements to the initial setup process on the device. The update is available for download over a Wi-Fi network connection.
Click to expand...
Click to collapse
OK so allow me to translate that into English:
"Because we're A, T and f***ing T, we decided to make Samsung replace Google's normal Android setup app with our own called AT&T Ready2Go. The problem is, again because we're A, T and f***ing T, our app sucks. If you have two-step verification enabled on your Google account, you won't be able to sign into your Google account during setup with AT&T Ready2Go. I guess we underestimated how many people actually have it turned on, so oops! Our bad. Here, it's enabled. Happy now?"
I manually updated a couple of hours ago. After playing around with the Note 8 with the update for about an hour I no longer experience the screen stutter/freeze/pause/etc. issue. I hope this in fact is fixed, but so far so good.
cataloochee said:
I manually updated a couple of hours ago. After playing around with the Note 8 with the update for about an hour I no longer experience the screen stutter/freeze/pause/etc. issue. I hope this in fact is fixed, but so far so good.
Click to expand...
Click to collapse
I'm still getting the unresponsive screen issue post-update. I've thought about doing a reset, but haven't actually done it yet.
Would be nice if someone had the OTA zip, as it is possible a root could be made from it if the right images are included.
- Dan
DanMc85 said:
Would be nice if someone had the OTA zip, as it is possible a root could be made from it if the right images are included.
- Dan
Click to expand...
Click to collapse
Nobody cam get the zip file unless they're rooted and root isn't currently possible on the AT&T model.
Sent from my Galaxy Note 8.0 using Tapatalk HD
oldblue910 said:
Nobody cam get the zip file unless they're rooted and root isn't currently possible on the AT&T model.
Sent from my Galaxy Note 8.0 using Tapatalk HD
Click to expand...
Click to collapse
So is this thing super locked down or do not many people have it yet? No root is killing me.
Sent from my SCH-I545 using Xparent Green Tapatalk 2
joshw0000 said:
So is this thing super locked down or do not many people have it yet? No root is killing me.
Sent from my SCH-I545 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
A little of both. The bootloader is encrypted and locked on the AT&T model, but also, very few of us on XDA actually have one. Let's be real. People around here thumb their noses at tablets with an LTE connection a lot of times. They just have no hipster cred in the Android geek community. The in crowd just buys a WiFi-only tablet and tethers it to their phone. It's the geekier thing to do, even if it's a pain in the @$$. You can talk about why LTE tablets are useful until you're blue in the face but it falls on deaf ears more often than not.
Unfortunately, I'm not very optimistic that we'll ever see root unless there comes a time where the WiFi-only root method works on the AT&T model.
Sent from my Galaxy Note 8.0 using Tapatalk HD
oldblue910 said:
A little of both. The bootloader is encrypted and locked on the AT&T model, but also, very few of us on XDA actually have one. Let's be real. People around here thumb their noses at tablets with an LTE connection a lot of times. They just have no hipster cred in the Android geek community. The in crowd just buys a WiFi-only tablet and tethers it to their phone. It's the geekier thing to do, even if it's a pain in the @$$. You can talk about why LTE tablets are useful until you're blue in the face but it falls on deaf ears more often than not.
Unfortunately, I'm not very optimistic that we'll ever see root unless there comes a time where the WiFi-only root method works on the AT&T model.
Sent from my Galaxy Note 8.0 using Tapatalk HD
Click to expand...
Click to collapse
Is it encrypted? I got this tablet 2nd hand and I may never even put service on it. If I can't root it, I'll probably trade it for a wifi version. I know AT&T and Verizon pushed an OTA to the S4's that prevented root. Luckily I was rooted/rom'ed prior to that. My GN8 doesn't have the latest OTA. I'm still hopeful for root and unlock/simunlock so I can grab a pre-paid card for this tab.
Sent from my SCH-I545 using Xparent Green Tapatalk 2
joshw0000 said:
Is it encrypted? I got this tablet 2nd hand and I may never even put service on it. If I can't root it, I'll probably trade it for a wifi version. I know AT&T and Verizon pushed an OTA to the S4's that prevented root. Luckily I was rooted/rom'ed prior to that. My GN8 doesn't have the latest OTA. I'm still hopeful for root and unlock/simunlock so I can grab a pre-paid card for this tab.
Sent from my SCH-I545 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Yes is encrypted and was in the original shipping firmware too, sadly.
Sent from my Galaxy Note 8.0 using Tapatalk HD
oldblue910 said:
Yes is encrypted and was in the original shipping firmware too, sadly.
Sent from my Galaxy Note 8.0 using Tapatalk HD
Click to expand...
Click to collapse
Damn. I couldn't find any info online about it when I got it so I assumed it was just a matter of time before it was rooted like the others.
Sent from my SCH-I545 using Xparent Green Tapatalk 2
Has anyone tried fc or moyochopper?
My device is trying to update but I blocked it (for now)...
If I can root it before the download starts them maybe I can grab the file...
prestonjb said:
Has anyone tried fc or moyochopper?
My device is trying to update but I blocked it (for now)...
If I can root it before the download starts them maybe I can grab the file...
Click to expand...
Click to collapse
I haven't tried personally, but if you want to try, go for it.
oldblue910 said:
Yes is encrypted and was in the original shipping firmware too, sadly.
Sent from my Galaxy Note 8.0 using Tapatalk HD
Click to expand...
Click to collapse
Damm, I was going to try to learn to build a rooted kernel.
If it's not a hassle can you point me to the post that IDed the encryption, or did you verify it?
Here is the Firmware for the newest OTA It has everything you could possibly want. I'm working a double or i would of already cracked it open and at least done something with it.
https://docs.google.com/file/d/0BzgUrWZ7XZ0rRWNZNlU0bmg2Uk0/edit?usp=sharing
dirtydroidx said:
Here is the Firmware for the newest OTA It has everything you could possibly want. I'm working a double or i would of already cracked it open and at least done something with it.
https://docs.google.com/file/d/0BzgUrWZ7XZ0rRWNZNlU0bmg2Uk0/edit?usp=sharing
Click to expand...
Click to collapse
Thanks for this. This is actually the original firmware, not the OTA. The link you provided was for MF1. That's the original shipping firmware. MF2 is the OTA. Still, this is great to have!
oldblue910 said:
Thanks for this. This is actually the original firmware, not the OTA. The link you provided was for MF1. That's the original shipping firmware. MF2 is the OTA. Still, this is great to have!
Click to expand...
Click to collapse
yeah forgot about that little OTA I made a boot.img and pushed it via hemdall, and it took , Im guessing that the everything by-name is writable via odin. Well lol at least im hoping it is haha.
dirtydroidx said:
yeah forgot about that little OTA I made a boot.img and pushed it via hemdall, and it took , Im guessing that the everything by-name is writable via odin. Well lol at least im hoping it is haha.
Click to expand...
Click to collapse
How did you dump that? Are you rooted?
Hey.
Has anyone been able to get the U firmware working on a Tmobile s7 edge? I got an error along the lines of "sw rev check fail fused 3 binary 2".
Thanks.
Sent from my SM-G935T using Tapatalk
Are you on the latest security update? I think the U firmware is patched up to May or so, these device bootloaders won't allow downgrading, maybe with the eng boot you can flash it, but from what I've been reading there's no going backwards, only flashing of the same updates or future.
Dark Nightmare said:
Are you on the latest security update? I think the U firmware is patched up to May or so, these device bootloaders won't allow downgrading, maybe with the eng boot you can flash it, but from what I've been reading there's no going backwards, only flashing of the same updates or future.
Click to expand...
Click to collapse
Ok, so if the U firmware gets updated, will i be able to flash it then?
Thanks.
Sent from my SM-G935T using Tapatalk
I would assume so since they usually have the base the same, the V and other software versions are able to use it, so we should be too once it's on the same update level.
Dark Nightmare said:
I would assume so since they usually have the base the same, the V and other software versions are able to use it, so we should be too once it's on the same update level.
Click to expand...
Click to collapse
Awesome, thank you!
I'll just have to figure out when the U firmware gets updated to the July patch. I'm a bit surprised that T-Mobile is ahead of the U firmware. Any idea why that is?
Sent from my SM-G935T using Tapatalk
I think we're all surprised really, lol, but they missed us on the May patch, so we jumped straight to our current update. U isn't as popular as the carrier versions in the US, so that may also explain the slower updates.
Dark Nightmare said:
I think we're all surprised really, lol, but they missed us on the May patch, so we jumped straight to our current update. U isn't as popular as the carrier versions in the US, so that may also explain the slower updates.
Click to expand...
Click to collapse
Oh. I was thinking of flashing U to get quicker updates, I didn't think they would be slower. I heard N is dropping today, and I want it ASAP.
Sent from my SM-G935T using Tapatalk
nahtnam said:
I heard N is dropping today, and I want it ASAP.
Click to expand...
Click to collapse
I want a blonde with a large chest and a butt that tastes like french vanilla ice cream. Don't expect N for a few months.
entropism said:
I want a blonde with a large chest and a butt that tastes like french vanilla ice cream. Don't expect N for a few months.
Click to expand...
Click to collapse
Of course, but I'd rather wait 3 months than 5.
Sent from my SM-G935T using Tapatalk
Dark Nightmare said:
Are you on the latest security update? I think the U firmware is patched up to May or so, these device bootloaders won't allow downgrading, maybe with the eng boot you can flash it, but from what I've been reading there's no going backwards, only flashing of the same updates or future.
Click to expand...
Click to collapse
Ok, so it looks like the August patch just dropped for the U firmware. So theoretically, will I be able to flash that now?
Also, in firmware zips, I always see a CSC and a HOME_CSC. What is the difference? Which should I use if I want to have a full and complete flash?
Thanks.
Sent from my SM-G935T using Tapatalk
nahtnam said:
Ok, so it looks like the August patch just dropped for the U firmware. So theoretically, will I be able to flash that now?
Also, in firmware zips, I always see a CSC and a HOME_CSC. What is the difference? Which should I use if I want to have a full and complete flash?
Thanks.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
Please let us know how flashing the new August U firmware goes for you. It does look like the new U devices are now on the V2 bootloader.
I have an official SM-G935U and after the update it says on the bootloader page RP SWREV: B2(2, 1, 1, 1, 1) K1 S1. My hope is that at some point I can flash the official T-Mo firmware to my G935U if the G935U falls behind in updates again.
CSC will wipe the device. HOME_CSC will not wipe the device, from what I understand.
tublah said:
Please let us know how flashing the new August U firmware goes for you. It does look like the new U devices are now on the V2 bootloader.
I have an official SM-G935U and after the update it says on the bootloader page RP SWREV: B2(2, 1, 1, 1, 1) K1 S1. My hope is that at some point I can flash the official T-Mo firmware to my G935U if the G935U falls behind in updates again.
CSC will wipe the device. HOME_CSC will not wipe the device, from what I understand.
Click to expand...
Click to collapse
Isn't the T-Mobile firmware on version 3 bootloader? That means the flash from T-Mobile to U won't work. BTW, I've already flashed from U to T-Mobile. I would not recommend flashing the Tmobile firmware because I still don't think it's possible to go back to U.
Sent from my SM-G935T using Tapatalk
nahtnam said:
Isn't the T-Mobile firmware on version 3 bootloader? That means the flash from T-Mobile to U won't work. BTW, I've already flashed from U to T-Mobile.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
Not sure. What do your device show when you boot to download/bootloader mode?
EDIT: are you saying that you have an official SM-G935U that you flashed to T-Mobile's firmware and are now stuck on T-mobile's firmware -- and that you're trying to get back?
tublah said:
Not sure. What do your device show when you boot to download/bootloader mode?
EDIT: are you saying that you have an official SM-G935U that you flashed to T-Mobile's firmware and are now stuck on T-mobile's firmware -- and that you're trying to get back?
Click to expand...
Click to collapse
I get: AP SWREV: B3(2, 1, 1, 1, 1) K1 S2
EDIT: I have a Verizon S7 Edge which I flashed U firmware onto. Then I flashed T-Mobile's firmware and now I'm stuck. I want to get back to U.
nahtnam said:
I get: AP SWREV: B3(2, 1, 1, 1, 1) K1 S2
EDIT: I have a Verizon S7 Edge which I flashed U firmware onto. Then I flashed T-Mobile's firmware and now I'm stuck. I want to get back to U.
Click to expand...
Click to collapse
Ah, then yeah - it looks like everyone aside from T-mobile are on V2 still. Sorry to have gotten your hopes up!
tublah said:
Ah, then yeah - it looks like everyone aside from T-mobile are on V2 still. Sorry to have gotten your hopes up!
Click to expand...
Click to collapse
No problem. Hopefully the U firmware will eventually upgrade to bootloader version 3. I'm kind of scared that it may never be updated because T-Mobile updated it with the July patch, and the U firmware is already at August.
nahtnam said:
No problem. Hopefully the U firmware will eventually upgrade to bootloader version 3. I'm kind of scared that it may never be updated because T-Mobile updated it with the July patch, and the U firmware is already at August.
Click to expand...
Click to collapse
I tried to flash the latest U firmware on my G935T without success though. It stuck at the beginning and I had to restore it using "Switcher". It might happened because I checked "re-partition in Odin.
mishastr said:
I tried to flash the latest U firmware on my G935T without success though. It stuck at the beginning and I had to restore it using "Switcher". It might happened because I checked "re-partition in Odin.
Click to expand...
Click to collapse
When did you try doing this?
Yesterday, about 1 p.m. EST
It looks like mine has BL 3 when the U firmware comes with BL2.
It's really sad but there is no way to flash it on my device.
God, this is a little infuriating. Why is the T-Mobile variant the only one on this new version of bootloader? This T-Mobile S7 is now officially more locked down than even the Verizon or AT&T variant, that's insane.
I'm not rooted but I can't launch s health on the final version of Nougat that my phone updated to today. (Xxu1dplt)
It says about a Knox warning and device compromised?
It's running stock though! Anyone else with the same issue?
Have you ever rooted before and then unrooted? Sorry if stupid question
Sent from my SM-G935F using XDA-Developers Legacy app
Once knox is tripped, game over even if you unroot.
jadaress1 said:
Have you ever rooted before and then unrooted? Sorry if stupid question
Sent from my SM-G935F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Nope. I assumed s health didn't work in earlier beta due to being beta.
I've never rooted this phone. Only thing I did was install beta by applying in the beta app.
Try uninstall and re-install again s-health
Go to download mode by switching off the device then hold Power + Volume Down + Home
Does it say Warranty void: 1?
CuBz90 said:
Go to download mode by switching off the device then hold Power + Volume Down + Home
Does it say Warranty void: 1?
Click to expand...
Click to collapse
It wasn't but it is now. Seems somehow during the beta it has tripped it. I contacted samsung and they're not interested.
It doesn't matter now as i've bit the bullet and installed twrp+renovate edge rom. Ironically renovate edge is running better than the official rom did with better doze despite having all the same apps installed. And s-health works fine on it.
Not sure what samsung are trying to prove by crippling people running the official ROM.
f1ux said:
It wasn't but it is now. Seems somehow during the beta it has tripped it. I contacted samsung and they're not interested.
It doesn't matter now as i've bit the bullet and installed twrp+renovate edge rom. Ironically renovate edge is running better than the official rom did with better doze despite having all the same apps installed. And s-health works fine on it.
Not sure what samsung are trying to prove by crippling people running the official ROM.
Click to expand...
Click to collapse
Ye if Knox has tripped, Samsung will have nothing to do with it, even if it's their fault, they just don't want to hear about it.
f1ux said:
It wasn't but it is now. Seems somehow during the beta it has tripped it. I contacted samsung and they're not interested.
It doesn't matter now as i've bit the bullet and installed twrp+renovate edge rom. Ironically renovate edge is running better than the official rom did with better doze despite having all the same apps installed. And s-health works fine on it.
Not sure what samsung are trying to prove by crippling people running the official ROM.
Click to expand...
Click to collapse
If what you want is to use SHealth on stock nougat with a knox tripped phone, I can give you a working solution with one caveat.
If you were already a beta tester you need to Odin back to BTU mm (or whatever CSC version you used to join the beta) and setup your phone normally. Make sure you also open SHealth. After, if you have not received a notification to update, go to settings and manually search for updates. Depending on which version of marshmallow you went back to, you might receive one update to the latest 6.0.1 available and after that, you will again be prompted to update, this time to 7.0. If you follow these steps, SHealth will work, even with knox tripped, but, if you manually reset the phone. SHealth will be blocked once again.
I know it seems a little complicated, but it's really not that hard.
Hope this helps.
f1ux said:
Nope. I assumed s health didn't work in earlier beta due to being beta.
I've never rooted this phone. Only thing I did was install beta by applying in the beta app.
Click to expand...
Click to collapse
This is weird . There's no way Knox is tripped without you doing anything like flashing TWRP.
joejoe23 said:
This is weird . There's no way Knox is tripped without you doing anything like flashing TWRP.
Click to expand...
Click to collapse
people lie. the dindu nuffins
joejoe23 said:
This is weird . There's no way Knox is tripped without you doing anything like flashing TWRP.
Click to expand...
Click to collapse
yes, i've been flashing my phone for around 10times with official binaries and never tripped knox. I flashed BTU(from INS) and updated to N, s health working fine here
Ive had the same problem, after flashing the official UK Rom. Knox is not triggered but shealth refused to work.
I reflashed the rom using every file incl. CSC and now everything works like it should.
1stlynx said:
Ive had the same problem, after flashing the official UK Rom. Knox is not triggered but shealth refused to work.
I reflashed the rom using every file incl. CSC and now everything works like it should.
Click to expand...
Click to collapse
I am quite new at this, so you basically did this in Odin?
.... can't post link to picture
You add in Odin: BL, AP, CP and CSC ?
I have the same problem in Shealth, and i would really like to stick with warrenty (Currently in the dawnload mode is still 0). And with Shealth compromised, My Knox app doesn't works as well.
Punisher159 said:
I am quite new at this, so you basically did this in Odin?
.... can't post link to picture
You add in Odin: BL, AP, CP and CSC ?
I have the same problem in Shealth, and i would really like to stick with warrenty (Currently in the dawnload mode is still 0). And with Shealth compromised, My Knox app doesn't works as well.
Click to expand...
Click to collapse
Hi,
i used this guide :
https://www.sammobile.com/forum/showthread.php?t=30800
dont know if i am allowed to post the link.
i did step 3.
Way to make shealth working on tripped but stock devices:
Install marshmallow with odin
Run shealth for it to start collecting user data
Update to nougat without wiping device
profit
kartonick said:
Way to make shealth working on tripped but stock devices:
Install marshmallow with odin
Run shealth for it to start collecting user data
Update to nougat without wiping device
profit
Click to expand...
Click to collapse
i have tried that but i wont count steps. so its of no use. when updated it... stopped working completely
poncespr said:
If what you want is to use SHealth on stock nougat with a knox tripped phone, I can give you a working solution with one caveat.
If you were already a beta tester you need to Odin back to BTU mm (or whatever CSC version you used to join the beta) and setup your phone normally. Make sure you also open SHealth. After, if you have not received a notification to update, go to settings and manually search for updates. Depending on which version of marshmallow you went back to, you might receive one update to the latest 6.0.1 available and after that, you will again be prompted to update, this time to 7.0. If you follow these steps, SHealth will work, even with knox tripped, but, if you manually reset the phone. SHealth will be blocked once again.
I know it seems a little complicated, but it's really not that hard.
Hope this helps.
Click to expand...
Click to collapse
Hello,
I am interested with the first solution. Can you please give me more detail how to proced ? Thank you in advance
does samsung pay works with u? i bought a second hand uk handset without having any knowledge of knox which was tripped. though i got it to work following a post here, samsung pay doesnot work evenon stock firmware.
elkhalifi said:
Hello,
I am interested with the first solution. Can you please give me more detail how to proced ? Thank you in advance
Click to expand...
Click to collapse
Thank you poncespr, your solution woked for me.
I am able to launch SHealth again
Trying to figure out why my wifes G935F got an update via OTA and my phone has gotten nada.
Both are UAE - XSG
Both HAD 6.0 XXU1APD1
her's now:
AP:G935FXXU1DQBO
CP:G935FXXU1DQB3
CSC:G935FOJV1DQB7
mine current:
AP:G935FXXU1APD3
CP:G935FXXU1APD1
CSC:G935FOJV1APD1
I've been trying to download the latest xxu1dqas but it takes hours and the download was corrupted somehow.
Smart switch does not show any updates for my phone either.
Any ideas?
was any modification done to your phone.
Like installing TWRP.
Both had CSC updated to use with ATT networks
corbin dallas said:
Both had CSC updated to use with ATT networks
Click to expand...
Click to collapse
Download and run KNOX Status Samsung from the play store.
If your phone had Knox tripped, this program will tell you.
Knox tripped - no OTA.
If it comes back good, take your wife's sim card out and put it in your phone, then check OTA updates that way.
Sent from my SM-G935V using Tapatalk
How did you "update" the CSC?
Just download with SamFirm - fast & free.
Hi,
I have recently bought Samsung s7 edge T mobile unlocked , but it not showing update. The last updated was android 6.0.1 on November 1st, 2016. I have also tried to connected with smart switch pc app but it's not showing any update either. I want to update my device with official firmware so that it will update automatically and regularly. I'm in Pakistan.
I have seen on Sam mobile to update via Odin. I want to know is this official update? I have not rooted and don't want to get rooted , I want to keep it official.
Thank you
WEIRD is knox tripped ?
Could be that the unlock was not done officially by the carrier, and it tripped KNOX or the OTA security bit.
I've been looking for a reputable download for the SM-G935T G935TUVS4BQJ2 firmware. For some reason T-Mobile does not have a download link now.
Westen81 said:
I've been looking for a reputable download for the SM-G935T G935TUVS4BQJ2 firmware. For some reason T-Mobile does not have a download link now.
Click to expand...
Click to collapse
Here you go. They have pretty good download speeds.
http://updato.com/firmware-archive-select-model?record=C0DD01ABD06F11E7A5F9FA163EE8F90B
bsharp8 said:
Here you go. They have pretty good download speeds.
http://updato.com/firmware-archive-select-model?record=C0DD01ABD06F11E7A5F9FA163EE8F90B
Click to expand...
Click to collapse
:good: Thanks for that! yeah, the DL rate on that link is *MUCH* better than the first one I found. The other one was downloading at something like 450kbps.
Westen81 said:
:good: Thanks for that! yeah, the DL rate on that link is *MUCH* better than the first one I found. The other one was downloading at something like 450kbps.
Click to expand...
Click to collapse
No problem. I get all my firmwares from there.:good:
bsharp8 said:
No problem. I get all my firmwares from there.:good:
Click to expand...
Click to collapse
Phone is alive again! Rooted, mildly debloated BQJ2 firmware (by mildly I mean, some sammy apps, LookOut, and T-mobile app removed)
Of note, Substratum made my phone lag for some reason, even with the governors set correctly and whatnot. Will try clearing cache on the app and then clear cache in recovery and see if it works better. The whole reason I had to reflash is that for some reason when I accidentally changed the GPU governor in Kernel Adiutor, it broke Play store.
Can anyone help with this. After updating to QBJ2, it won't detect network anymore, keeps searching!
Anyone got a fix please?
I have virus
What I have to do?