My new OP8Pro is not connecting to ANY wifi networks.
And if it manages to connect it drops connection after 15 seconds.
I'm on OOS 10.5.13 and only using magisk.
What variant do you have?? US? EU? Global? Chinese?
Not sure if safe mode allows WiFi but boot to safe mode and see if the same issue occurs.
If a family member has a mobile, create a hotspot then connect to that and see if it has the same issues.
If say update to 11 as it may be a software issue.
If updating is an issue as you have no WiFi, you may be able to download it from the internet on a pc then copy the firmware over.
Have you tried a factory wipe?
Does removing the magisk modules help?
When you rooted did you extract the boot.img from your own firmware or did you obtain it from someone else, I'd always recommend obtaining your own.
Think there was someone who had issues in the xXx thread, might be worth searching threads to see what was the outcome.
I think they were on a US device, T-Mobile IIRC.
Related
Root MethodAmazon has just released a new firmware update, blocking the fastboot commands necessary for root/custom ROMs (fastboot boot). We need more information about this update. If people could update their tablet to this latest version without getting it stuck in the botloop, we could see the information regarding the update and get root out for this ROM ASAP. Thanks to anyone who sacrifices root/ROMs for development.
List of things you can't do:
Downgrade to an earlier release
Boot a .img from Fastboot
List of things you can do:
Install and use the Google Play Framework and Services
Root
Install Custom ROMS via FlashFire
Remove Lockscreen Ads
Remove Amazon Bloatware
Feel free to comments things that worked/didn't work on your device.
ANYONE WHO IS ON 5.0.x AND WANTS TO GO TO 5.1.1 WITHOUT ANY COMPLICATIONS AND KEEPING TWRP, GO TO THIS LINK: http://forum.xda-developers.com/showthread.php?t=3265594
Can anyone test if the Google Framework Install tutorial works on this update?
It does.
However, DON'T TRY TO DOWNGRADE BACK TO THE 5.0.1 FIRMWARE. IT WILL BRICK YOUR DEVICE. I found that out the hard way. It's stuck in a preloader reboot-loop.
Added list of what you are able to do on the update.
Can someone with a brand new Fire & an open wifi network within range, confirm that it will not automatically connect to wifi? I would appreciate it greatly.
Yes, I do believe that you should have to agree to connect to wifi. And that's what I vaguely recall from my Fire. But I'd like to be 100% sure. Don't want to take the slightest chance. My friend has a new fire in the box & has an open wifi network within range of their place.
blueberry.sky said:
Can someone with a brand new Fire & an open wifi network within range, confirm that it will not automatically connect to wifi? I would appreciate it greatly.
Yes, I do believe that you should have to agree to connect to wifi. And that's what I vaguely recall from my Fire. But I'd like to be 100% sure. Don't want to take the slightest chance. My friend has a new fire in the box & has an open wifi network within range of their place.
Click to expand...
Click to collapse
You have to go through the setup, but originally I just skipped that part, even though I was next to a Starbucks, and it didn't connect.
Doesn't Starbucks wifi require you to click to agree to their terms of use before you can freely browse or download? So Internet would not actually be available initially to the update script.
Pretty much, I trust amazon on this issue, as far as I can throw them. I don't want to presume that a OTA proccess won't silently connect, while the Fire otherwise appears to be waiting for the ok to connect to wifi.
Bloat removal
Hi just to add this thread it looks like you cannot remove any of the bloat as I was able to do on 5.01
craigs23 said:
Hi just to add this thread it looks like you cannot remove any of the bloat as I was able to do on 5.01
Click to expand...
Click to collapse
Thanks, added.
This is bullsh!t. the ENTIRE reason about 5,000 people bought this tab last week is because of root, fastboot and CM. If I get my tab soon I can offer any assistance you need. I'm not sure if it will be possible to dump any part of the system, boot, etc. without fastboot or twrp, but I'm sure we could figure something out.
blueberry.sky said:
Can someone with a brand new Fire & an open wifi network within range, confirm that it will not automatically connect to wifi? I would appreciate it greatly.
Yes, I do believe that you should have to agree to connect to wifi. And that's what I vaguely recall from my Fire. But I'd like to be 100% sure. Don't want to take the slightest chance. My friend has a new fire in the box & has an open wifi network within range of their place.
Click to expand...
Click to collapse
When I setup mine it asked to turn on wifi I skipped it and said later.
Sent from my SM-N910T3 using Tapatalk
Has anyone tried kingroot on 5.1.1?
Experts please take a look at this
What was changed in OS 5.1.1?
If anyone can get the frimware update or capture it id like to test it out
running 5.1.1 & all I could manage to load was Google Account manager. The rest (Framework Services, etc) says something like "App not installed" & nothing else, every time I try.
scratch that..... found found a couple that did load for me.
Damn! I did this (tried to downgrade, got bricked) a day before you posted this. I should probably replace mine...
My unrooted Fire upgraded to 5.1.1 last night before I had any idea it was coming. I'm willing to try whatever is needed to assist with further research if I could be of any help.
unlikely it would work, but did anyone on 5.1.1 try
Code:
fastboot -i 0x1949 boot twrpfilename
Sent from my KFFOWI using Tapatalk
5.1.1 update file
Here is the 5.1.1 update file
snap42.com/update-kindle-full_ford-37.5.4.1_user_541112720.bin.zip
Hey guys,
After discovering the latest root method I was excited to try it out. Unfortunately, I botched it up and had to reflash the stock firmware. I downloaded the T-Mobile PD8 file from Sammobile for the G935T and flashed all the packages. I got root working, and everything seems to be fine except for the absence of these three features. There are no options for any of them in settings or their respective apps. I live in an area with bad coverage so I am pretty dependent of Wi-Fi calling. Even reflashing that HOME_CSC file didn't help. Now I'm not sure what I have to do to get these features back.
Any help would be appreciated.
You're sure that you used HOME_CSC for T-Mobile? I'm thinking that either you didn't download the correct firmware (example being that you may have downloaded for Cricket or something of that sort) or you could have used the CSC_TMB file by mistake. As far as I know, they should both be the same, only HOME_CSC doesn't wipe the data from your device. Remember seeing an error of any kind after flashing?
Binary100100 said:
You're sure that you used HOME_CSC for T-Mobile? I'm thinking that either you didn't download the correct firmware (example being that you may have downloaded for Cricket or something of that sort) or you could have used the CSC_TMB file by mistake. As far as I know, they should both be the same, only HOME_CSC doesn't wipe the data from your device. Remember seeing an error of any kind after flashing?
Click to expand...
Click to collapse
Yeah I'm pretty sure it's the right file...
HOME_CSC_TMB_G935TTMB3APD8_CL7856276_QB9546824_REV02_user_low_ship_MULTI_CERT.tar.md5
No errors, I also reflashed the BL and CP to no effect... Not gonna do the AP because it will make me lose root.
bump
I flashed the entire stock firmware and the features are STILL missing. I'm getting tired of reinstalling all my apps. Does anyone have any ideas?
TheDoolster said:
bump
I flashed the entire stock firmware and the features are STILL missing. I'm getting tired of reinstalling all my apps. Does anyone have any ideas?
Click to expand...
Click to collapse
Without going through the why or how that all happened and the ways to resolve without reflashing, I'd just recommend that you download the full PD8 firmware from this thread http://forum.xda-developers.com/showthread.php?t=3331528
I would skip the repackaging .tar part to preserve /data. Worked for me and hopefully will for you.
(PROVIDING YOU STILL ARE EXPERIENCING THAT ISSUE)
Before yesterday, I found myself in the exact same situation. I had a rooted device with all of my apps installed - including Xposed modules. But I had lost WiFi Calling. I didn't even see VoLTE settings in the Phone app. So I started from scratch. I wiped out my system. I then used ODIN to flash ADB8 firmware from T-Mo. WiFi Calling was there. I then used ODIN to flash EngBoot. WiFi Calling was still there. I then rebuilt my entire system w/o Xposed. WiFi Calling was still there. I then started to add all of my modules, one at a time. After loading everything, WiFi Calling was still there.
I then started AFWall+. Lo and behold, WiFi Calling completely disappeared. I turned off the firewall. WiFi Calling was there. So I left it turned off and started to configure my modules. WiFi Calling worked - until I loaded the crowd-sourced rules for XPrivacy. I turned of XPrivacy and WiFi Calling returned.
It all makes sense. I know know that the Phone app must connect to a wireless network via TCP/IP. And if it can't, then WiFi Calling is disabled. So I spent several hours working through XPrivacy and AFWall+ rules. And at the end, I now have a fully functional phone.
I don't know if you use AFWall+ or the XPrivacy Xposed module. But you might check any control systems that could limit the connection between the Phone app and the network.
Don't use HOME_CSC. Use CSC. This will wipe data unfortunately, but i had different issues using home. And using the non-home fixed them.
Flashing the July 9th updated firmware from sammobile worked for me. Lost root, but I would rather have these features.
I unrooted my Galaxy s7 edge with Rogers and I am miss the option for volte any ideas on how to get it back?
Not the right csc
The home_csc is not the right one for t mobile. It should be home_tmb_csc
So, I'm having a particularly strange issue here. I recently got this Sprint Note 4 and activated it. However, there appears to be a missing option under settings. Tethering and Hotspot is straight up gone. To clarify, I have pictures attached showing the item listing, and one without it.
Clarifications of troubleshooting I've tried so far:
I have attempted a factory reset of the device
I have attempted to do a reset with ##72786#
I have tried updating Profile, PRL,
I am using a DeOdexed PH4 6.0.1 ROM. I have tried reflashing per instruction (triple wiping Cache, Dalvik, Internal, System, etc)
I have tried flashing a STOCK OTA PH4 ROM to see if it would show up there. It does not.
I called Sprint technical support to reprovision my phone. They pushed out a a reprovisioning that I accepted. No change.
At one point, Wanam/Xposed was attempted to be installed. I checked for system/csc/features.xml. It was not there
http://forum.xda-developers.com/note-4-sprint/development/rom-stock-ph4-bloated-deodexed-t3473610/ is the custom ROM i'm using. However, it doesn't seem like a ROM specific issue.
If I use Activity Launcher or itools, i can access the actual wifi hotspot MENU (the toggle off and on, LAN settings, etc). I can enable it and the system will broadcast the SSID. However, if I try connecting to it, no devices are able to successfully connect.
here is the Activity Launcher referenced, for other readers:
http://forum.xda-developers.com/showpost.php?p=66713935&postcount=7
but anyways, regarding devices not being able to connect, sometimes the data connectivity (through hotspot only, not for the entire phone) will go dead if you don't start using it immediately after first unlocking and activating tether.
in my experiences, if you keep data alive by immediately connecting a device after your first time turning tether on (after unlock) by downloading a large file or somewhat frequently reloading web pages (on the connected device!) -- anything that will keep data sending and receiving -- it will stick, and the data service to connected device issues will stop.
it's not foolproof, it's not a silver bullet, but this is the method to the madness I have learned and worked for me many times when changing roms and even getting new phones.
it's been a couple months since I had to fiddle with it last, so I can't remember if it was necessary to re-unlock after a failed attempt at keeping data alive. you might only have to toggle data off then back on for another attempt.
when I had the problem of connected devices losing internet access, it would only happen after having worked for a few seconds to a few minutes. it'd work then abruptly stop, and this is my "fix"
My issue seems more in line with the devuces failing to validate to begin with. Not losing connection.
I had something like this before, I vaguely recall it having to do with using Odin vs. OTA stock. So did you try wiping your phone completely then Odin the stock PH4 tar, or did you OTA to PH4?
beezar said:
I had something like this before, I vaguely recall it having to do with using Odin vs. OTA stock. So did you try wiping your phone completely then Odin the stock PH4 tar, or did you OTA to PH4?
Click to expand...
Click to collapse
The very very very first time, I OTA'd to PH4. The next two tries were wiping completely and using the PH4 tar file. So both methods have been attempted.
I was referring to loss of internet connection, not signal related. I thought that was clear, sorry
Sterist said:
I was referring to loss of internet connection, not signal related. I thought that was clear, sorry
Click to expand...
Click to collapse
I thought you meant loss of internet connection in the sense of anti-tether provisioning from Sprint. My phone's LTE never goes down (and I am able to still browse the internet from the mobile device while tethering).
The connected devices never successfully "connect". They aren't listed as connected devices under the mobile hotspot. My other Android phone (without mobile data) is forever connecting. My macbook claims it has an assigned IP but is "unable to access the internet". So I'm not sure what the hell is going on with that.
At this point, I have restored my Note 3 as my active device until I get this resolved. I'm willing to re-write everything down to the barest metal I can.
Somebody in another topic mentioned something about PIT. I don't know anything about that sort of thing. My knowledge extends about as far as installing recovery and flashing ROMs.
I'm confident I could follow procedure, but could use a guiding hand on where to go from here.
sounds like the tether unlock method you used was not done correctly, whether by whoever made it or yourself
method 2 in Galaxy Tools should work just fine. there are several threads in the Sprint note 4 seconds that contain the apk or ppl that will pm it to you. the author discontinued the public/free version of the app and now chargers $35+ per person for a 1 time use lol once you get a copy of the free one, make copies and store on multiple devices forever.
it's primarily for Sprint Sammy devices, so you prob won't see much if anything about it here in the collective note 4 forum.
may work on some boost or even tmo, but yeah.
edit:
you'll want either 3.1.5, easy install n msl read broken on MM and less features
or 3.1.8, troublesome install with msl read working but unreliably, more features.
Sterist said:
sounds like the tether unlock method you used was not done correctly, whether by whoever made it or yourself
method 2 in Galaxy Tools should work just fine. there are several threads in the Sprint note 4 seconds that contain the apk or ppl that will pm it to you. the author discontinued the public/free version of the app and now chargers $35+ per person for a 1 time use lol once you get a copy of the free one, make copies and store on multiple devices forever.
it's primarily for Sprint Sammy devices, so you prob won't see much if anything about it here in the collective note 4 forum.
may work on some boost or even tmo, but yeah.
edit:
you'll want either 3.1.5, easy install n msl read broken on MM and less features
or 3.1.8, troublesome install with msl read working but unreliably, more features.
Click to expand...
Click to collapse
Came back around to this, as I am running a multi-rom and am still encountering this issue. I never attempted any hotspot unlockers. The hotspot was missing from the get-go.
Gamemaster1379 said:
Came back around to this, as I am running a multi-rom and am still encountering this issue. I never attempted any hotspot unlockers. The hotspot was missing from the get-go.
Click to expand...
Click to collapse
Just a thought and question: when you Odin stock tar to recover from this condition, are you using the rooted extended power menu to boot to download mode? Or, do you prevent the auto reboot of stock tar flash with Odin options?
A noted developer, @idone from Galaxy Tool app, once shared with me that rooted shortcut or preventing auto reboot can prevent the normal flash of Odin booting to recovery momentarily to set csc options. csc options flashed may not restore on any boots if you skip that initial auto boot.
The suggested method is to power down and pull battery for 30 seconds our more before reinserting battery and manually booting to downloaded mode. And do not uncheck auto reboot or pull battery but use Odin defaults and let phone auto boot. Doing this allows the phone to boot into recovery to do its thing briefly before booting system. I usually just let it perform the setup wizard and didn't activation just in case.
I rarely do the the data profile update or PRL because if letting the phone setup this way and phone prompts to reboot later, I believe this all done. But since this may allow ItsOn to bootstrap initialize, after flashing TWRP and backing up, I wipe internal memory and factory reset before flashing a custom ROM. Data format is optional; I don't always do that.
But if you do all that and don't see hotspot in Settings of stock, that's a problem. Maybe from dead stock, try KIES or Smart Switch to restore latest stock and check again?
Sent from my SM-N920P using Tapatalk
Hi,
I open this thread because I detected this issue after doing a downgrade of the STOCK ROM.
- After apply the OTA for NPNS25-137-33-11 (RETEU) and return to NPNS25-137-33-5 I start to see very annoying troubles. Sometimes, when the WIFI state changes (mainly when stating it, or enable hotspot mode, or chaging from one to other network) in this case the phone hangs. The only solution is a hard power-off. Also I noticed that the WIFI range is very small.
I listen before that some users have troubles with WIFI. I haven't detected any problem before, only now. My assumption is that the OTA has updated some partition with RADIO data. Then, now the driver is unstable.
Perhaps some others have a similar problem because an upgrade using a flash backup and not upgrading their RADIO partitions.
Please, share your experiences to see if the problem is widespread?
Thank you!
I have a Zenfone 3 ZC520TL US model phone (apparently there are multiple versions of the ZC520TL).
First question: Is there a LineageOS available for this phone? Or any plans for it? I don't see it listed on LineageOS's website. But there was a thread here a few months ago about it, although I'm not sure if that was specifically for the ZC520TL or the US specific ZC520TL.
Second question: Is it possible to root this phone? From the best I can tell, the only way to do this is with Magisk Manager, creating a patched boot image. Although, I'm not sure what the probability of bricking the phone is by doing this. I would assume you could always manually install the stock firmware, but I'm not sure if that would work.
Third: Is root even needed? The only reason I think I'd really need root is to enabling tethering on the phone. I'm currently with an MVNO that doesn't specifically allow tethering. I'm not sure how providers go about detecting tethering these days, I'm sure they probably could detect it regardless of whether the phone is rooted or not. But I rarely tether, in fact I rarely use over 1GB of data a month period. But the last thing I really want is to be stuck out some where when I have to be away from home for a few days and not being able to tether to my laptop for work. Or when I'm sitting outside an arm's length away from my home's wifi signal.
Do you still need to add the net.tethering.noprovisioning=true line to the build.prop file in order to tether?
Fourth: I used Asus's UnlockTool from their website. But I don't know if it truely unlocked the phone. When entering fastboot mode, I no longer see the message about CSC, I see a message that says FASTBOOT mode... But fastboot getvar unlocked still shows no. Although, I'm not sure if there is a TWRP for this phone or a LineageOS or alternative that would really necessitate any of this anyway.