Related
So like many of you who were running the awesome LPV build for the past few months and just recently tried updating to official Lollipop (LRX21O) have likely run into issues on first boot (black screen with only a back button). In this state/issue the phone will respond to "OK Google" but nothing else. The pulldown shade will also be present but show nothing. The issue appears to be related to the lock screen. The following is how I fixed my issue, and I will be looking at this thread to try and update the OP as we pin down the EXACT issue, but I believe I have a fix:
NOTE: If you've already updated and are AT the black screen, I hope you have a backup to restore as you'll need to revert to change some settings. If not, you may find flashing the system.img or zip of your old build (LPV) allows you access to your phone again to access these settings.
1. Restore backup or revert if necessary so you can access settings BEFORE flashing LRX21O.
2. Settings-Security-Screen Lock Make sure you have one set other than swipe so you can perform the next step (we will change this back later)
3. Go to "Trust Agents" on the same screen (Security) and turn OFF SmartLock
4. Go back to screen lock, now select SWIPE (or none if present, but I don't believe it's an option on most)
5. (Optional) I chose to both enable USB debugging as well as going into SuperSU (if present) and setting it to grant all requests. I did not need this, however if you're having issues it may help your troubleshooting to have root adb access.
6. With your lock screen set to swipe and smart lock off, now try flashing LRX21O, followed by a custom kernel (or boot.img if you have it) and/or root in that order if you'd like.
7. Upon boot, it SHOULD have resolved the black-screen issue. I did still have the "non-working home button" issue that was quickly resolved by running the setup wizard again with the following command via adb:
adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity
When it asks about restoring backups or setting up as a new device, choose set up as new device. The "Restore" would simply re-download and restore apps that are already installed. "Set up as new device" simply tells setup to do nothing, which is fine, because all your data is already there
8. SDcard Fix (root required): If you have issues seeing SD card content, use these ADB commands below (credit to rootSU here
su
restorecon -FR /data/media/0
That's IT! You should be set. I love dirty flashing (I know everyone hates it because yes, it does cause a lot more chatter in the forums, but that's half the fun ) and problem solving. Everytime I see someone claiming they fixed a problem by factory resetting I'm thinking "...that's like saying you fixed your car by buying a new car". I hope I this makes other's lives a little easier
Root SM-T707A on Lollipop with SuperSu - Xposed & Debloated - Part II
Where are we right now?
* Part I: Flash Stock Lollipop 5.0.2.
* Part II: Gain Root access for Lollipop with SuperSU. <---- YOU ARE HERE!
* Part III: Flash Xposed Framework thru Flashfire.
* Part IV: Debloat the tablet from both AT&T and most of Samsung stuff.
* Part V: Improve usability and aspect with Xposed Modules.
Once again, some words of our sponsors: NO, I'm NOT resposible for any consequence originated from the use of this guide, being that the death of your tablet, or your smart tv, the Panama Papers or Luis Suarez just playing rough with Filipe Luiz's foot. Whatever happens to your tablet, it's ON YOU.
Introduction (PLEASE READ!):
This guide works as a continuation of Part I, so we assume you flashed KitKat and applied Lollipop updates as described.
If you are already on Lollipop and have several weeks using it, of course you can try this guide, but I STRONGLY SUGGEST to start from zero, backup your files and use the guidelines on Part I of this guide.
Part II: Gain Root access for Lollipop with SuperSU
IMPORTANT - During the first boot on our brand new lollipop, don't try to connect to your WiFi and remove your SimCard if availble before even selecting any option. We don't want any internet at this time.
Our first move in Lollipop is to Reject all the AT&T offers..
Then accept terms of Samsung EULA (and hit No Thanks below)...unless you want to share information with Sammy.
Then you can put your name (I didn't), it' s up to you.
Disable the 3 checkboxes for location services (you can enable this later).
Then skip the Samsung Account creation and hit also Next on my "Find my mobile" screen without doing nothing.
Finally, you'll reach the Android Desktop.
Setting the stage for rooting with KingRoot
Still avoiding any conection to the internet, go to your apps and tap Settings.
Before doing nothin, I strongly suggest you change your language to english in case you use another.
If your first language is English, you're good.
If it's not, you can change it on General TAB, then "Language and Input".
After this, tap the Device tab, choosing then Display option on the left.
Choose Screen timeout and select 10 minutes.
Now select Lock screen on your left and Screen lock on your right. Tap "None".
Now go to "General" tab and tap "Security".
Enable the Unknown sources checkbox and press OK on the popup.
Press home button. Now you can connect to your Wifi.
The moment you got Internet, Samsung will start forcing some updates on your tablet.
At the same time, several Google popups will ask you to "regularly check device for security".
Decline them all the time!
There is a "Games" app that loves to open itself without asking
When that happens, it will introduce you to an agreement that you will REJECT.
If it doesn't show, better. But it will eventually.
Now enter the Play Store and Log in with your credentials.
Accept the playstore conditions when prompted. If you are kicked out of the app just enter again.
Still inside Playstore, now swipe from your left side border to gain access to the menu.
Tap "My Apps" and use the "Update All" button on the right.
Accept all APP Permisions (seven times in my case).
The update process will start. This will take some time so BE PATIENT and do nothing else.
When everything is updated, you'll notice some warning on your status bar.
Swipe down your status bar. It will ask several times to Update Google Play Services.
Tap any of update offers for Play Services. Playstore will open again offering the update.
Hit Update and Accept. When the update of Google Play Services is finished, hit the Open button.
You gain access to Google Settings. Tap Security.
Disable "Remote locate this device" - "Allow remote lock and erase".
Disable also "Scan device for security threats" and "Improve harmfull app detection" (unless is greyed out).
Hit the home button and go back to desktop.
Installing KingRoot
For the next step, you need to download these files on your PC:
* Kingroot V4.90
* RemoveKing
Copy them on your tablet's internal memory. Specifically on the root of your internal memory. If you copy them inside a folder, later commands will fail.
Back to your tablet's desktop, look for the folder icon on the bottom left corner. This will open the Samsung File Manager. Look for "Device Storage" on the left column. If you copied the files correctly, you'll find both on the right pane of the display. Extract the RemoveKing.zip file by tapping it and clicking "OK". A RemoveKing folder will appear on the root of your filesystem.
Now open the Kingroot V4.90 file. Hit Next and then Install.
If a google warning appears citing - "Installation blocked". Hit "Install anyway" (unsafe).
If it doesnt, just hit Open. A blue screen shows up with the legend "ROOT auth".
Swipe upwards twice (assuming you're holding your tablet in portrait).
Now hit the "Try it" button. The app will verify root status in a matter of seconds.
Now tap the "TRY THE ROOT" button at the bottom.
When the root is sucessful, you'll be asked to "Forbid Knox".
Tap Cancel and press the home button. Now you are rooted with Kingroot.
Installing and preparing Terminal Emulator
Now that we are rooted, enter the playstore and install the app "Terminal Emulator for Android". Open it. You'll notice some small font selected so, hit the 3 dots on the right upper corner and go to preferences. On Font Size choose 24 pt. Hit the back physical button of the tablet. Now the "white letters" become readable. And it shows something like:
Code:
klimtlteatt:/ $
Next type the following and hit enter:
Code:
su
A Kingroot popup will ask for root permission. Tap "Allow".
Now the $ symbol will change for #.
Next you hit the HOME button to exit the app briefly (don't close the app in any other way, just hit the HOME button).
Uninstalling KingRoot
After that, go to your apps and enter the KingRoot app.
Now tap the 3 dots on the upper right corner and select "General Setting". Disable "Smart Authorization", then disable "Enable Root Authorization". Finally choose below "Uninstall KingRoot". Hit Continue. Uncheck "Backup Root" when prompted and hit OK. When all is over, you're back to the desktop. Go back again to your apps and uninstall Purify.
Applying the Scripts
Open again Terminal Emulator app (thru the app Icon) . Now we need to hit a couple of scripts by moving first to our extracted folder by entering the following command on the terminal (plus enter):
Code:
cd /sdcard/RemoveKing/
To run the first script type (then press enter):
Code:
./step0.sh
It just takes 3 seconds, then type the following and press enter:
Code:
./step1.sh
This last script will ask for a confirmation during its process.
Type just an "y" and hit enter: (WARNING, the Y won't appear on your display after typing it)
Code:
y
You'll notice a bunch of errors, don't mind them.
Installing SuperSU
Now hit the home button and go to the play store.
Search and Install SuperSU (free version). Open it. Choose Expert.
The app will ask "The SU binary needs to be updated, continue?".
Hit Continue and then choose "Normal" when asked on the next popup.
You'll receive an "Installation Sucess!". Tap the Reboot option.
Congratulations! You are now rooted with SuperSU.
After rebooting, enter the Terminal app once more, and tap the X on the right upper corner and hit OK.
That will finish the current terminal session.
If you're interested in getting Xposed Framework, go to part 3 of this guide.
If you're just interested in debloating the SM-T707A and improve its performance, go to part 4 (Soon).
Part 5 is where I discuss the modules I'm using on Xposed and also some Playstore apps to improve functionality, and remove as much Touchwiz as possible, while also working on better battery life (Soon too).
Final Considerations (suggested reading - not mandatory)
While this guide may seem easy to carryout, it took me almost a month to get SuperSu to work on Lollipop.
I'm no coder (a soon to be Certified Public Accountant), and the real magic to pull this off was to try many combinations of different app versions, different situations with google services and several strategies with the script and superSU. In fact, most of KingRoot versions don't work on this tablet to get root, also tried SuperSume app from the playstore. The same could be said for KingoRoot (don't confuse it with KingRoot), it worked but I couldn't remove it without losing root.
Why I'm telling you this? Because using KingRoot and similar apps to root this tablet, your mileage may vary while doing it. In fact, even while applying my first two guides there's a respectable chance of KingRoot tool failing to root your tablet. If you followed this couple of guides to the last comma, your chances of success are very close to 100%. But I have noticed in similar Galaxy Tab S threads, that the use of KingRoot and KingoRoot to achieve root is just a matter of using the root tool many times until it works, and I wanted to avoid you guys going thru that. To take sucess rate as close as it gets to 100%, we took all of this steps. They were included to avoid many failures. I believe they're are 99% flawless to achieve root on Lollipop with SuperSU.
Also, the second script won't remove many KingRoot files, because it was thought for KingoRoot on KitKat.
I have to give myself more time to develop something that could really clean up the last traces of KingRoot.
Special Thanks
* @chixvicious - For showing how to achieve the same over KitKat and KingoRoot instead.
* @bakageta - For creating these scripts for the Alcatel smartphone over KingoRoot.
* @Kingxteam - For developing KingRoot to allow us to root our device.
Oh wow, I had forgotten all about those scripts. Glad to see someone getting some use out of them.
bakageta said:
Oh wow, I had forgotten all about those scripts. Glad to see someone getting some use out of them.
Click to expand...
Click to collapse
They were life-savers, thanks a lot for them!!
Broken links?
First and foremost, thank you for the thorough walkthrough.
I've come across an issue with the provided links to KingRoot and RemoveKing. When I click on either, I receive the following message:
"Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Do you have any alternate links available?
EDIT: I did find an alternate method that worked for proper replacement of KingRoot with SuperSU. All good, and glad for the compatible xposed framework.
zopert said:
First and foremost, thank you for the thorough walkthrough.
I've come across an issue with the provided links to KingRoot and RemoveKing. When I click on either, I receive the following message:
"Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Do you have any alternate links available?
EDIT: I did find an alternate method that worked for proper replacement of KingRoot with SuperSU. All good, and glad for the compatible xposed framework.
Click to expand...
Click to collapse
Thanks for the heads up!!. I'll check them ASAP.
EDIT: All links are fixed!!
kainanmaki said:
Thanks for the heads up!!. I'll check them ASAP.
EDIT: All links are fixed!!
Click to expand...
Click to collapse
Man, can't thank you enough for this...So great for someone like me with little knowledge for all this magic. I am gonna do this when I get back from vacation. Can't wait for the rest of it!
Thanks again
ElCid43 said:
Man, can't thank you enough for this...So great for someone like me with little knowledge for all this magic. I am gonna do this when I get back from vacation. Can't wait for the rest of it!
Thanks again
Click to expand...
Click to collapse
I hope to get part IV and V in no more than 10 days...
I'm in the process of testing removing/freezing many services, just a sneak preview:
So far I was able to disable close to 180-190 apps/services from a total 250-260 (can't remember the exact number).
Of course there are some key services removed (for e.g multi windows, but that's just one service).
Still you can easily remove like 165 without losing any stock functionality. That's how much bloated the tablet is.
Removing useless stuff from samsung and 3rd party (eg. VPN, Policy Updates) or more evident like MultiWindow, the gallery app or even the file browser.
Or the weird ones like the phone app that is hidden and you can't use (you can disable it and still keep LTE Data).
More to come.
Need Help - Having Untimely Reboot Issues
Wow...Thanks SO MUCH for this guide! It gives me hope that I can actually enjoy using my T707A to the fullest!
Alas, I need some assistance PLEASE:crying:
I'm following your guide to the letter, and I've successfully achieved Part 1. Part 2, however, alludes me even after many, many tries. Here is what is going right and wrong:
a) Achieved root with KingRoot
b) installed and achieved SU with Terminal
c) ISSUE - KingRoot (or something) reboots the tablet during Uninstall, which kills SU access obtained with Terminal
d) ISSUE - after reboot, I no longer have permission to run the scripts to uninstall KingRoot
Is there another way for me to do this? As long as the tablet is rebooting during uninstall of KingRoot I have no SU access, so can't do anything but start over and experience the same thing time after time.
ANY assistance would be so very much appreciated...MOST humbly & sincerely...Tom
Where did you find the alternate method??
zopert said:
First and foremost, thank you for the thorough walkthrough.
I've come across an issue with the provided links to KingRoot and RemoveKing. When I click on either, I receive the following message:
"Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Do you have any alternate links available?
EDIT: I did find an alternate method that worked for proper replacement of KingRoot with SuperSU. All good, and glad for the compatible xposed framework.
Click to expand...
Click to collapse
Hi...I am VERY interested in your "alternate" method for replacement of KingRoot with SuperSU that actually worked. Would you be so kind as to share that with me? I'm having huge troubles (see my post) replacing KingRoot as it reboots thus killing my SU access necessary to run the uninstall scripts provided in OP. Any help would be GREATLY appreciated. MOST humbly & sincerely...Tom
TomandJonna said:
Wow...Thanks SO MUCH for this guide! It gives me hope that I can actually enjoy using my T707A to the fullest!
Alas, I need some assistance PLEASE:crying:
I'm following your guide to the letter, and I've successfully achieved Part 1. Part 2, however, alludes me even after many, many tries. Here is what is going right and wrong:
a) Achieved root with KingRoot
b) installed and achieved SU with Terminal
c) ISSUE - KingRoot (or something) reboots the tablet during Uninstall, which kills SU access obtained with Terminal
d) ISSUE - after reboot, I no longer have permission to run the scripts to uninstall KingRoot
Is there another way for me to do this? As long as the tablet is rebooting during uninstall of KingRoot I have no SU access, so can't do anything but start over and experience the same thing time after time.
ANY assistance would be so very much appreciated...MOST humbly & sincerely...Tom
Click to expand...
Click to collapse
I had that problem many times, the uninstall reboots the tablet before you can establish SuperSu.
The most reliable way I found of overcoming this is to follow the exactly in this order and without stopping to much because google wants to run updates behind scenes that mess with our process (that's why sometimes it works and sometime it doesn't). My recommendation is to start over from scracth again (I know it's boring). I'll probably do it again on my tablet just to validate and to try some other things related to the original services).
TomandJonna said:
Hi...I am VERY interested in your "alternate" method for replacement of KingRoot with SuperSU that actually worked. Would you be so kind as to share that with me? I'm having huge troubles (see my post) replacing KingRoot as it reboots thus killing my SU access necessary to run the uninstall scripts provided in OP. Any help would be GREATLY appreciated. MOST humbly & sincerely...Tom
Click to expand...
Click to collapse
Other thing I forgot to ask, did you started clean from the first part or just started with part 2 of the guide?
Will this method trip Knox?
i need * RemoveKing file now...
Hi all,
After unlocking my phone which is a global version 64gb model, I had installed CM13. Wifi was working fine previously. After CM was installed I cannot get wifi to connect. It will show authentication failed and obtaining ip but won't obtain. It shows its mac address and scans wifi just fine. I can run wifi analyzers but it just won't connect. I have tried installing other roms, even installing the original roms and re-locking the device to stock with no success. I have reset my router and verified other devices can connect as well as trying other open wifi ssid's. I have also completely formating the whole phone and reinstalled roms from scratch, again no success. I have been searching through forums for about 2 weeks now and every recommendation has not worked. I love this phone but not having wifi is killing me. I am experiencing no other issues. One clue I do have which google is not providing answers to is the error i got when CM first installed and other times which i can't determine the scenarios to recreate which is
E:Unable to write to ums lunfile '/sys/module/g_android/parameters/file'
Unable to locate storage device.
Any help would be greatly appreciated.
Thanks Much
I have the same problem. I've installed CM 21.11 and gaaps stock via TWRP 3.0.2.0 and after this wi-fi can't authenticate. I did the same steps as topic starter and also tried different wi-fi settings in router and wi-fi without pass. Nothing helped
Please help! Any thoughts can be helpful.
I have exactly same issue as OP. I did everything like him and got no result.
Please help someone. I love my MI5 but i need wifi.
I have exactly the same issue and posted about it just a little earlier
http://forum.xda-developers.com/mi-5/help/wifi-connectivity-problem-t3517777
The difference being that the WiFi was working just fine even when I installed CM 13.1 for the first time. WiFi stopped to connect when I did a full Swipe in TWRP (all partitions).
It would be great if someone could help...
Try to give a chance to CM14.1 installed after a full wipe, I am using WiFi every day with wpa2 shared key and also radius auth 2.4 and. 5 GHz without problems and the overall performances are good
I have CM 14.1 at the moment and the problem is the same.
I'm no specialist but it doesn't seems to be a ROM related issue.
In this case I would try with stock MIUI after a full format and wipe, then in case of success again with CM14.1. Format is important because with encrypted data wipe isn't enough
matteo.gspace said:
In this case I would try with stock MIUI after a full format and wipe, then in case of success again with CM14.1. Format is important because with encrypted data wipe isn't enough
Click to expand...
Click to collapse
Thanks for your assistance.
Done that but didn't solve the issue...
I had the same problem, same symptoms.
I too flashed a new ROM and couldn't connect to any AP, I tried various ROMS, MIUI 7 & 8 and CM 13 & 14.1.
Though I think I found a solution (it worked for me ). I simply changed my MAC-adress and I was able to connect to my home WiFi.
I'm running CM 14.1-2016225-NIGHTLY-gemini on MI5.
This is what I did to fix my WiFi:
First prepare an new MAC-address. I personally don't know when a MAC-address is considered valid, so I just took one from an other device. I used the mac address of my previous mobile phone, which could connect to my router.
1. Disable WiFi.
3. Enable debugger settings (Setting>about Phone>Press build number repeatedly).
2. Enable root (Develepor settings>root access set to "Apps and ADB").
3. Open the file manager app.
4. Give the file manager app root access (menu>Settings(cog in lower left corner)>General settings>Access mode set this on "Root Access mode").
5. Now find the file root/etc/firmware/wlan/qca_cld/ and open wlan_mac.bin.
You should see something similar to:
Code:
Intf0MacAddress=XXXXXXXXXXXX
Intf1MacAddress=XXXXXXXXXXXX
END
6. Change the first to your new MAC-address, but first write down the old one, so you can change it back if this method doesn't work for you.
The last X of the next line should be a digit higher than the previous line. E.g:
Code:
Intf0MacAddress=957FDC328BF[B]4[/B]
Intf1MacAddress=957FDC328BF[B]5[/B]
END
(This MAC-address most likely won't work).
7. Save the file. You might need to press the save button a few times.
8. Check if the file has changed.
9. Check if you MAC-address has changed (Settings>WiFI>Configure-WIFI(cog in right upper corner)).
10. Enable WiFi.
I hope this works for everyone that has the same problem.
I'm on MIUI EU 8.1.70 Nougat then i fastboot flash or recovery mode to MIUI Global 8.1.2.0 Marshmallow WIFI NOT WORK
But,
I managed to get the wifi working again with edl mode flashing with MIUI Global 8.1.20.
I will try to move to CM again, maybe this time wifi will work..
Wish me luck, will post the result later
RESULT:
Not Worked.
---------- Post added at 12:03 PM ---------- Previous post was at 11:23 AM ----------
Pekkuky said:
I had the same problem, same symptoms.
I too flashed a new ROM and couldn't connect to any AP, I tried various ROMS, MIUI 7 & 8 and CM 13 & 14.1.
Though I think I found a solution (it worked for me ). I simply changed my MAC-adress and I was able to connect to my home WiFi.
I'm running CM 14.1-2016225-NIGHTLY-gemini on MI5.
This is what I did to fix my WiFi:
First prepare an new MAC-address. I personally don't know when a MAC-address is considered valid, so I just took one from an other device. I used the mac address of my previous mobile phone, which could connect to my router.
1. Disable WiFi.
3. Enable debugger settings (Setting>about Phone>Press build number repeatedly).
2. Enable root (Develepor settings>root access set to "Apps and ADB").
3. Open the file manager app.
4. Give the file manager app root access (menu>Settings(cog in lower left corner)>General settings>Access mode set this on "Root Access mode").
5. Now find the file root/etc/firmware/wlan/qca_cld/ and open wlan_mac.bin.
You should see something similar to:
Code:
Intf0MacAddress=XXXXXXXXXXXX
Intf1MacAddress=XXXXXXXXXXXX
END
6. Change the first to your new MAC-address, but first write down the old one, so you can change it back if this method doesn't work for you.
The last X of the next line should be a digit higher than the previous line. E.g:
Code:
Intf0MacAddress=957FDC328BF[B]4[/B]
Intf1MacAddress=957FDC328BF[B]5[/B]
END
(This MAC-address most likely won't work).
7. Save the file. You might need to press the save button a few times.
8. Check if the file has changed.
9. Check if you MAC-address has changed (Settings>WiFI>Configure-WIFI(cog in right upper corner)).
10. Enable WiFi.
I hope this works for everyone that has the same problem.
Click to expand...
Click to collapse
This method work, thanks a lot.
But, for me it's required a valid MAC-address
Pekkuky!
Thank you for your time sharing your knowledge on this topics many days old.
Awesome! You made my day. It work.
I just want to add my experience that might be useful for others.
I tried with a automatically generated MAC and it didn't work.
I followed your advice and repeated with a MAC address of an old e-reader and it worked instantly.
Thanks again!
Pekkuky, thanks a lot. Now I can use CM derived ROMs, great.
Later on after trying solution by Pekkuky, i have problem in turning on hotspot tethering and usb tethering. Anyone can confirm this or this is just me.
Hotspot tethering is working on mine. Before this fix it didn't.
Haven't tried usb tethering though.
Pekkuky said:
I had the same problem, same symptoms.
I too flashed a new ROM and couldn't connect to any AP, I tried various ROMS, MIUI 7 & 8 and CM 13 & 14.1.
Though I think I found a solution (it worked for me ). I simply changed my MAC-adress and I was able to connect to my home WiFi.
I'm running CM 14.1-2016225-NIGHTLY-gemini on MI5.
This is what I did to fix my WiFi:
First prepare an new MAC-address. I personally don't know when a MAC-address is considered valid, so I just took one from an other device. I used the mac address of my previous mobile phone, which could connect to my router.
1. Disable WiFi.
3. Enable debugger settings (Setting>about Phone>Press build number repeatedly).
2. Enable root (Develepor settings>root access set to "Apps and ADB").
3. Open the file manager app.
4. Give the file manager app root access (menu>Settings(cog in lower left corner)>General settings>Access mode set this on "Root Access mode").
5. Now find the file root/etc/firmware/wlan/qca_cld/ and open wlan_mac.bin.
You should see something similar to:
Code:
Intf0MacAddress=XXXXXXXXXXXX
Intf1MacAddress=XXXXXXXXXXXX
END
6. Change the first to your new MAC-address, but first write down the old one, so you can change it back if this method doesn't work for you.
The last X of the next line should be a digit higher than the previous line. E.g:
Code:
Intf0MacAddress=957FDC328BF[B]4[/B]
Intf1MacAddress=957FDC328BF[B]5[/B]
END
(This MAC-address most likely won't work).
7. Save the file. You might need to press the save button a few times.
8. Check if the file has changed.
9. Check if you MAC-address has changed (Settings>WiFI>Configure-WIFI(cog in right upper corner)).
10. Enable WiFi.
I hope this works for everyone that has the same problem.
Click to expand...
Click to collapse
I was really thinking I would have to throw away the phone. Love for you, really, worked flawlessly. Used this website to generate a MAC http://www.miniwebtool.com/mac-address-generator/
Pekkuky said:
I had the same problem, same symptoms.
I too flashed a new ROM and couldn't connect to any AP, I tried various ROMS, MIUI 7 & 8 and CM 13 & 14.1.
Though I think I found a solution (it worked for me ). I simply changed my MAC-adress and I was able to connect to my home WiFi.
I'm running CM 14.1-2016225-NIGHTLY-gemini on MI5.
This is what I did to fix my WiFi:
First prepare an new MAC-address. I personally don't know when a MAC-address is considered valid, so I just took one from an other device. I used the mac address of my previous mobile phone, which could connect to my router.
1. Disable WiFi.
3. Enable debugger settings (Setting>about Phone>Press build number repeatedly).
2. Enable root (Develepor settings>root access set to "Apps and ADB").
3. Open the file manager app.
4. Give the file manager app root access (menu>Settings(cog in lower left corner)>General settings>Access mode set this on "Root Access mode").
5. Now find the file root/etc/firmware/wlan/qca_cld/ and open wlan_mac.bin.
You should see something similar to:
Code:
Intf0MacAddress=XXXXXXXXXXXX
Intf1MacAddress=XXXXXXXXXXXX
END
6. Change the first to your new MAC-address, but first write down the old one, so you can change it back if this method doesn't work for you.
The last X of the next line should be a digit higher than the previous line. E.g:
Code:
Intf0MacAddress=957FDC328BF[B]4[/B]
Intf1MacAddress=957FDC328BF[B]5[/B]
END
(This MAC-address most likely won't work).
7. Save the file. You might need to press the save button a few times.
8. Check if the file has changed.
9. Check if you MAC-address has changed (Settings>WiFI>Configure-WIFI(cog in right upper corner)).
10. Enable WiFi.
I hope this works for everyone that has the same problem.
Click to expand...
Click to collapse
works like a charm
thanks mate, u saved my phone! :highfive:
using this website for generating an mac-adress too
http://www.miniwebtool.com/mac-address-generator/
Thanks Pekkuky for the trick. This problem appeared after flashing lineage os 14.1 using twrp. Then I tried different versions of global stable/developer roms (both fastboot and recovery) but nothing worked. Finally this trick worked Used the miniwebtool site for generating mac-address.
Tether used to work fine on Nougat, then in Oreo and Pie, google baked-in the inability to add "dun" to an apn whether existing or new, resulting in an error message of "carrier does not allow apns of type dun." This resulted in a really slow, erratic tether function in the ROMs I tried.
Anyone found a ROM, or kernel, or know of a dev that is actively adding the same functionality as was present on Nougat--that is, tethering worked properly out of the box, or adding dun to the apn makes it work properly? I know for a fact that SOME Oreo and Pie ROMs now allow one to add the dun parameter to the apn, but it still didn't make tethering fast and stable like before.
lineageos
I'm a little surprised no one else has weighed in on this--it is as if @namanjr and I the only ones who have an interest in tethering.
namanjr said:
lineageos
Click to expand...
Click to collapse
Incorrect.
Neither LOS 15 (Oreo) nor LOS 16 (Pie) tether as well as Nougat, and neither allow the dun parameter to be written into the APN. Their tether speed is less than 1/10 of the speed with Nougat.
Furthermore, using either one of them will probably result in the downgrade "Encryption Unsuccessful" error in attempting to re-flash Nougat, meaning that the only way to downgrade is to format interior storage.
pbergonzi said:
Incorrect.
Neither LOS 15 (Oreo) nor LOS 16 (Pie) tether as well as Nougat, and neither allow the dun parameter to be written into the APN. Their tether speed is less than 1/10 of the speed with Nougat.
Furthermore, using either one of them will probably result in the downgrade "Encryption Unsuccessful" error in attempting to re-flash Nougat, meaning that the only way to downgrade is to format interior storage.
Click to expand...
Click to collapse
You have to use the CLI tools or edit the xml with all the APN.
Try "settings put global tether_dun_required 0" in adb shell or terminal emulator.
Something like "settings put global tether_dun_apn APNHERE" would manually add a APN+DUN if you know the input format of the command. Just turn data off and on after and test hotspot.
namanjr said:
You have to use the CLI tools or edit the xml with all the APN.
Try "settings put global tether_dun_required 0" in adb shell or terminal emulator.
Something like "settings put global tether_dun_apn APNHERE" would manually add a APN+DUN if you know the input format of the command. Just turn data off and on after and test hotspot.
Click to expand...
Click to collapse
I've tried "put global..." in one or two other roms, with no success.
One of the other roms would also allow editing the APN, but even with the dun parameter, it didn't perform properly.
Did you do this to your own rom and see an effective before and after?
pbergonzi said:
I've tried "put global..." in one or two other roms, with no success.
One of the other roms would also allow editing the APN, but even with the dun parameter, it didn't perform properly.
Did you do this to your own rom and see an effective before and after?
Click to expand...
Click to collapse
I edited /system/etc/apns-conf.xml manually. Copy and paste your existing APN and change the name, then edit it to allow tethering. You will loose changes when updating unless you make a backup script for it, a magisk module, or get you or a dev to add it to a rom.
namanjr said:
I edited /system/etc/apns-conf.xml manually. Copy and paste your existing APN and change the name, then edit it to allow tethering. You will loose changes when updating unless you make a backup script for it, a magisk module, or get you or a dev to add it to a rom.
Click to expand...
Click to collapse
Thanks. If I decide to upgrade to pie again, I will do this.
Dirty Unicorns V13 (Pie)
ZVNexus said:
Dirty Unicorns V13 (Pie)
Click to expand...
Click to collapse
Thank you. Can you tell me or show a screenshot of your tether download speed with (and/or without) the DU rom or with the dun parameter in/absent from the apn, illustrating the difference in quality?
I am lax to immediately install another P rom knowing that if I need to come back to N, there is extra work/risk involved.
Hey, I've also been struggling in this boat for a few months now. Went from a nexus 6p with Los 14.1 to the oneplus 3t. Only rom available at the time was 15.1 , which I remember kind of sucked when it first came out the gate on the nexus 6p, so I was hesitant to use it. Quickly ran into this issue where the tethering speed was dramatically terrible. For months I've just assumed it was the oneplus 3t's fault. Maybe the radio is weaker, or my carrier doesn't approve of this Chinese import versus the other...
I bounced between Stock, Ice Cold, and Los trying to find the best settings for the best result. With my carrier (tmo) the trick was to make a new apn and set it up to use a different address, meant for devices without lte support. "epc.tmobile.com" . This immediately made everything fast again, however it sort of pipelines any tethering activity. So like it would have the good expected transfer rate with one thing, but if you tried to load anything else, that thing would hang until the first thing finished transferring.
I'm glad I finally caught wind of this question/thread. It's relieving to know that it's just because google f***ed with something in oreo and pie, and not that Los suddenly updated into inconvenience. I'm going to try Dirty Unicorns 13 as ZVNexus suggested, and will report back to you with results. Also if any of you can help better articulate this 'global dun 0 apns-conf.xml trick' for me that'd be great and I'll gladly try that out and give results. I flashed magisk and navigated to the apns-conf.xml file just to be suddenly reminded I have no idea what on earth I'm looking at.
** Dirty Unicorns 13 Result
A big maybe? Tmobile out of the box shoots down tethering speed to ~70 kb/s . I usually use the TTL trick to work around this, but that requires I set/use any APN protocol to IPv4. For whatever purposes, the version I tried (du_oneplus3-v13.0-20190109-0432-RC) doesn't allow you to edit the initial APN settings, however I can see that it has "dun" listed in the types. Inconvenient, but I figured whatever I'll just make my own BUT NO. It won't let you save a new APN with dun anywhere in the types. So in the end I can't give any solid result, sorry. If it means anything the upload speed was good, so this could be an issue exclusive to my carrier.
The S2 wifi blobs have now been incorporated into the Aug 25 17.1 builds.
Please take 10 minutes to read all of post #1 and #2. lpedia and I have spent 5 days troubleshooting this together and want to present our wifi findings. DO NOT USE this thread to report any other problems, it's only for exynos5433 S2 tablet wifi. If this is unreasonable, then stop reading. Thank you.
If your device's wifi is not connecting after a restart and/or wake from sleep, and/or dropping out at random, this could be because the 17.1 code is using Samsung Galaxy S6 wifi blobs instead of its stock S2 wifi blobs. This commit was made in 17.1 at
gts2: Import Galaxy S6 BCM4358 firmware · universal5433/[email protected]
@lpedia has confirmed that LineageOS 17.1 on his T710 has the wifi problems when using S6 blobs, but not after the S6 blobs have been replaced with stock S2 blobs. This appears to fix both non-connection at boot and not reconnecting on wake from sleep. Random dropouts are less common and were not seen during the limited testing, so it's not certain that they're gone.
FAQ
Q1. Will changing from S6 wifi blobs solve all my wifi no reconnect or disconnect problems?
A1. This has only been tested on the T710, and there's no guarantee it will help the other devices. If you want to try, follow the instructions below. Before you try, make sure to back up all your data. The following should write the stock S2 blobs to the /system partition only, but if you make a mistake you could lose your data! Back up first.
It's an easy test to see if the stock S2 blobs will help or not. If your current rom does not connect to wifi after a restart, try our proposed solution. Before you do, reboot your current rom 5 times in a row. After each reboot, see if your wifi connects. After you install stock S2 blobs, reboot your device again 5 times in a row and see if wifi connects. This will easily tell you if the S2 stock blobs have solved this one particular problem or not.
As for wifi not connecting after long/deep sleep, you should notice over 2 or 3 days if wifi connects or not after deep sleep.
Q2. Will this work on SM-T710, SM-T810, etc?
A2. Same answer as A1. It should work on any S2 tablet exynos5433 device that uses the S6 wifi blobs that are the default in 17.1 or Android 10. These instructions are only for exynos5433 devices.
As the thread grows bigger, you can see who is responding back with either positive or negative feedback and what model they have.
Q3. Will this work on RR, Havoc or LineageOS (Android 10 or 17.1)?
A3. The instructions below replace the S6 blobs with the original stock S2 blobs. The instructions provided should work regardless if it's Havoc, RR or LineageOS. All these variant OSes share the same repo (i.e. code and blobs) on github.
Q4. Is this post relevant to Android 9 or LineageOS 16.0?
A4. NO. The github repos show that Android 9 or LineageOS 16.0 used the stock S2 wifi blobs. This was changed to S6 wifi blobs in Android 10 or LineageOS 17.1. I don't know why it was changed to S6 blobs as I'm not involved with that change.
Q5. Why do I need my model and code name?
A5. In order to follow the instructions below, you need to know your model number and it's code name. The model number or device name is settings, about tablet.
You can find the code name at (scroll almost all the way down to the bottom)
Samsung
This is the Team Win website and the official home of TWRP! Here you will find the list of officially supported devices and instructions for installing TWRP on those devices.
twrp.me
For example, SM-T710 is gts28wifi.
Q6. Does it matter if my wifi is 2.4Ghz or 5Ghz or a mix of both?
A6. When reporting back to us, please state whether your network is 2.4Ghz only, 5Ghz only, or a mix of 2.4Ghz and 5Ghz. In addition, if its a mix, please let us know if it's one wifi network (same ssid) or two separate wifi networks. That is, 2.4Ghz is one ssid and 5Ghz is another ssid.
Q7. If this works, how will this be fixed for the next release of code and the future?
A7. If enough people say it fixes their wifi problems, I can submit a git pull request to Anan to revert the S6 wifi blobs back to S2 wifi blobs.
Instructions
1. Make sure adb debugging is enabled in developer options. To enable developer options, tap settings, about tablet, build number 7 times until it says developer options unlocked. Go back to settings, system, advanced, developer options, enable android debugging and rooted debugging.
Note if you are running Magisk, see posts regarding Magisk if you cannot see rooted debugging.
2. You will need git. There are instructions and download links for installing git on Windows, MacOS, and Linux at Git Guides - install git | GitHub.
3. After you install git, follow the instructions exactly below.
Bash:
# make temporary vendor directory
mkdir temp
# cd to that directory
cd temp
# git the 16.0 stock drivers
git clone https://github.com/universal5433/proprietary_vendor_samsung -b lineage-16.0
# change directory to proprietary_vendor_samsung/<your device>/proprietary/system/vendor/etc
# or if Windows, to proprietary_vendor_samsung\<your device>\proprietary\system\vendor\etc
# where "<your device>" is your device's code, for example gts28wifi for the T710:
cd proprietary_vendor_samsung/gts28wifi/proprietary/system/vendor/etc
# start adb root
adb root
# remount /system as rw (it's read only by default)
adb remount
# start adb shell
adb shell
# delete S6 blobs from wifi directory
cd /system/vendor/etc/wifi
rm bcm*
rm nvr*
# There should be only .conf files left now
ls -al
exit
# you should be back at your desktop terminal prompt now
# now push all stock drivers to /system/vendor/etc/wifi
adb push wifi /system/vendor/etc
# check to make sure it got pushed okay
adb shell ls -al /system/vendor/etc/wifi
# now reboot Android
adb reboot
If the above does not work for you, or if it causes other problems, just reflash the last rom. That will overwrite the /system partition and everything will be restored.
If you do try this, please report back to this thread about whatever happened and include your device and what wifi network you are running.
Reserved.
Thanks for the instructions!
I had to boot my T810 (gts210wifi) into TWRP and mount /system from there before adb root and adb remount was possible. Everything else worked as described.
Observations after 5 reboots: WiFi available after reboot each time! Much better than before!
I will observe it now for a while regarding wifi-off after sleep or sporadical wifi-off.
Btw. for the random reboots of the unmodified linageos17.1 (ripee) I'm pinging my DNS-server all 2mins using Tasker. Fixed reboots since 2 month at least on my system.
Yogi555 said:
I had to boot my T810 (gts210wifi) into TWRP and mount /system from there before adb root and adb remount was possible.
Click to expand...
Click to collapse
The above might be due to you not having adb root enabled in developer options. I will update the instructions to make sure that's enabled.
Strangely the setting seems not there in my system. But I remember that in some system its available. Can the installed Magisk be the reason?
Yogi555 said:
Strangely the setting seems not there in my system.
Click to expand...
Click to collapse
It's there.
Short update: The S2 wifi blobs are a huge improvement. With S6 blobs I had reliable dropoffs at medium router-signal combined with heavy wifi-load (no dropoffs with full router signal). With the S2 blobs no single dropoff even at weak router-signal and heavy wifi-load for several hours now.
Again, to enable developer options, tap settings, about tablet, build number 7 times until it says developer options unlocked. Go back to settings, system, advanced, developer options, enable android debugging and rooted debugging.
As I said earlier, the routed debugging option is missing in my developer-options (with installed Magisk). Everything else is looking identical to the attachement of post 6. But maybe we should not cover this thread with the different ways to adb root. The really important thing is that the proposed fix works really great! At least for me and hopefully for everybody else who is willing to try it
Yogi555 said:
As I said earlier, the routed debugging option is missing in my developer-options (with installed Magisk). Everything else is looking identical to the attachement of post 6. But maybe we should not cover this thread with the different ways to adb root. The really important thing is that the proposed fix works really great! At least for me and hopefully for everybody else who is willing to try it
Click to expand...
Click to collapse
Thanks, @Yogi555! It's great to know that replacing the blobs works on one of the other S2 models! We could only test it on gts28wifi (T710).
@Yogi555, about the Rooted debugging option: my T710 doesn't show that option, either, and I think it's because I have Magisk installed (@retiredtab doesn't).
If the device is not rooted, "adb root" temporarily restarts the adbd daemon on the device as root (there's a timeout period after which it will remove root access again).
I'm guessing that if the device is rooted, that isn't necessary - because adbd is probably already running as root . The Rooted debugging option is therefore unnecessary, and isn't shown.
In either case, when you do "adb root" on the PC, there should be a prompt on the device asking you if you want to allow access. Did you see the prompt? If you don't explicitly allow it, root access won't be given.
Also, "adb root" works on Windows (for an account that's in the Administrators group) without needing to be Run As Administrator, but I think Linux requires the command to be run as root (eg, sudo adb root).
Update2: after the night the T810 with S2 blobs was immediately connected to wifi this morning. Great!
Regarding "adb root" with Magisk: I'm running it from Win10 PC. Independent if normal commandline or commandline as administrator - after "adb root" there is no output at all, but a sound like connecting or disconnecting a device. After "adb remount" next, an error is displayed:
Not running as root. Try "adb root" first.
remount failed
Maybe my adb is too old (version 1.0.40)
However "adb reboot recovery" works and "adb root" then in TWRP as well. So strange, but no problem
Yogi555 said:
Update2: after the night the T810 with S2 blobs was immediately connected to wifi this morning. Great!
Regarding "adb root" with Magisk: I'm running it from Win10 PC. Independent if normal commandline or commandline as administrator - after "adb root" there is no output at all, but a sound like connecting or disconnecting a device.
Click to expand...
Click to collapse
Did you check the device to see if it's prompting you to allow this access? The prompt times out fairly quickly, so you might not see it if you don't check straight away. It does give a notification sound.
The prompting came yesterday at the very beginning of the activity and I allowed it (including the always checkbox). "adb device" shows the device id.
I don't understand why you'd see anything different from what I see. I use a Windows PC, I have Magisk (version 23.0) installed on the T710, and have previously allowed adb root access "always".
What I see is this:
Code:
> adb version
Android Debug Bridge version 1.0.41
Version 31.0.2-7242960
> adb root
adbd is already running as root
> adb remount
remount succeeded
> adb root
gts28wifi:/ #
I think there could be something wrong with your Magisk configuration. What version is it?
Downloaded adb version 1.0.41. Now I get "ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options"
Updated Magisk from 20.4 to 22.1. and App to 23.0 => No difference :-(
In Magisk App adb is not listed in Superuser-tab. Can I add it somehow?
Yogi555 said:
Downloaded adb version 1.0.41. Now I get "ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options"
Updated Magisk from 20.4 to 22.1. and App to 23.0 => No difference :-(
In Magisk App adb is not listed in Superuser-tab. Can I add it somehow?
Click to expand...
Click to collapse
I think I know what's going on now.
I've just uninstalled Magisk, and (after the enforced reboot) I can now see the "Rooted debugging" setting in Settings > System > Developer Options > Debugging.
Mine was ON, but had been hidden by Magisk's presence, as I suspected.
If you uninstall Magisk, I think you will find that your "Rooted debugging" is OFF. If so, turn it on, then try "adb root" etc. You don't need to root the device in order to use adb root functions. If you want the device to be rooted, by all means re-install Magisk - but with that setting still ON.
I'll be very interested to hear what happens.
The simplest way to check that adb root has actually given you root access is to "adb shell". The prompt will end in a "#" if the shell's running as root. As mentioned in an earlier post.
Want to also quickly confirm in here that the S2 Blobs are working real fine for me as well.
lpedia said:
I think I know what's going on now.
I've just uninstalled Magisk, and (after the enforced reboot) I can now see the "Rooted debugging" setting in Settings > System > Developer Options > Debugging.
Mine was ON, but had been hidden by Magisk's presence, as I suspected.
Click to expand...
Click to collapse
I've just re-installed Magisk and proved to myself that Magisk 23 is hiding the setting. I found that Magisk 22 didn't hide it - I re-installed using a version 22 zip that I had on hand, checked the "Rooted debugging" setting, which was still visible, then updated to Magisk 23 via the app. After the reboot, the setting had disappeared again.