Database Develop

[GUIDE] Dirty flash from lpv to LRX21O

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

Schiziodd's ROM flavors for HTC desire

in the subsequent posts below, you will find all the info you need for not only the device but the ROMs I have had my hands in.
each person who I pulled the files from will get a thanks in the posts as necessary

NonSense 1.04
Disclamer: these files are meant specifically for the HTC Desire 510. Use these files at your peril, you assume any responsibility for loss or damage that may result from use of these files or procedures. what has been included in this tutorial is for the HTC Desire 510
You have been warned.
note: from now on CRI signifies cricket, and B-S signifies sprint/boost if those signifiers aren't used, it applies to both type of this phone
now to the goodies.....
List of supplies:
1. Phone (HTC Desire 510)
2. USB cord that syncs with the PC
3. USB drivers installed for the phone
4. the zip files from this location. click here
4.1 there are 2 different versions of the same ROM, but the *1.04-lean.zip is US only (refer to changes to see why).
4.2 CRI for cricket/att, B-S for boost/sprint
5. read these instructions completely before attempting
before we get started make sure you have supersu (which can be downloaded from here), and NonSense1.04.zip copied to the root of your external SD card
NETWORK UNLOCK (I.E. switching services)​
as this phone is LTE compatible, it takes a SIM card no matter the service to receive calls and data. so it stands to presume all you need to do is network unlock the device (Sprint calls it UICC unlock, others it's the Network Unlock Code)
the phone needs to be network (SIM) unlocked in order to switch it from cricket to sprint, or from sprint to virgin mobile, etc.
to network unlock the phone:
1. make sure you are on stock ROM (the one that came with the phone, not the one listed in this post nor CM)
2. call the respective original service provider of the phone (i.e. cricket, sprint, etc.) and tell them that you are leaving the country (like to Australia) and you want to unlock the SIM so you can use your device for service down there.
2.1 if you bought the phone second-hand or don't have service on it, you will have to find a reputable unlock service online
2.2 for sprint customers, your account HAS to be at least 6 months old before they will give you the UICC(SIM unlock) code
2.3 for boost customers, your account HAS to be at least a year before they will give you the UICC(SIM unlock) code
3. once you have the SIM unlock code, pull battery from phone, remove the original SIM, put your services respective SIM in (i.e. originally a cricket phone now running a T-Mobile SIM), put in battery, boot phone, and enter the unlock code where it asks.
4. once your back into device, you'll notice you will have no data.
4.1 what needs to be done is to program the APN (google will be your best friend here - for example sprint lte apn settings, or T-Mobile lte apn settings).
5. now that you have the APN settings, you can program them into the phone.
5.1 APNs can be found in the device by going to settings, then mobile data, clicking on access point names. in there in the upper right hand corner should be 3 dots that are verticle. click on that and then on new APN.
5.2 add the respective settings, click save and then make sure it has a green dot next to it.
6. sit back and enjoy the fruits of your labor
APNs for this device can only be written once the phone has been UNLOCKED and the original (cricket) service providers SIM is NOT inserted, and your using another service Provider ( sprint, T-Mobile, etc.) SIM.
UNLOCKING BOOTLOADER​
1. for the drivers, use the ones contained here in the HTCDrivers.zip and extract them to the desktop
1. extract and use the file contained in adb.zip to flash unlock token
2. follow this tutorial and choose all other supported devicess when it asks about device.
INSTALLING TWRP AND KERNEL​
in the adb file you should notice a file called recovery.img. that is TWRP recovery for the device
there is also a file called boot.img. this will allow read/write permissions at the System level once root is obtained
if you have either the sprint, boost or another service provider's variety of this phone, try flashing their respective kernel after you install the ROM or before you root (no guarantees that flashing the respective kernel will work. as I have the cricket variety of this phone, I am only developing for that one)
1. from home screen, go to settings and scroll down to power and then scroll all the to the bottom of that and uncheck "fast boot"
2. shut down phone completely
3. go back into fastboot (vol down + power)
4. Select fastboot from the menu list and press the power button.
5. open command prompt and use the CD command to get it to the root of the adb folder (CD C:/users/sky/desktop/adb).
6. plug in device and wait for it to say fastboot USB
7. type in command prompt "fastboot flash recovery recovery.img' (should complete within 4 seconds)
8. in the same command window type "fastboot flash boot boot.img" (should complete within 4 seconds)
8.1 step 8 can be skipped if your just flashing *NonSense1.04*.zip
9. pull battery once that is completed and put it back in.
10. power device on (skip this step if rooting)
OBTAINING ROOT (can be skipped if installing NonSense1.04 as it's already rooted)​
1. re-enter fastboot mode and choose recovery. press power to select it
2. once in recovery select install and go to external SD and select the supersu update package.
3. once selected, you should see a slider on the bottom of the screen that says swipe to confirm. do so
4. once package is installed you should see a button that says reboot device. do so
5. wait for it to fully load
INSTALLING NonSense 1.04​
1. re-enter fastboot mode and choose recovery. press power to select it
2. once in recovery select install and go to external SD and select the NonSense1.04.zip.
3. once selected, you should see a slider on the bottom of the screen that says swipe to confirm. do so
3.1 beware, it may take a bit to install. just be patient, it's working.
4. once package is installed you should see a button that says reboot device. do so
5. wait for it to fully load. be forewarned, it may take about 15 minutes to load
CHANGES​
CRI versions
1. DEODEXed the ROM
2. added external SD support into the ROM
3. fixed FC on clock app (switched clock/alarm from stock worldclock.apk to AOSP clock)
4. changed bootanimation.zip, boot sound, and stock ringtones and sounds.
5. added more stable kernel to flash file.
6. added Pandora (no-ads vers. 5.5), SpiritUL (FM radio support), Facebook, RootBrowser, Adobe reader, Adobe flash player, and Viper4android (DSP/equalizer)
6.1 all apps that have been listed in 6 can be uninstalled without the need for root
7. root and SU have been added and are up to date in this rom as of 11:45PM MST on 3/1/215
8. added apns-conf.xml from CyanogenMod
9. got native APP2sd support thanks to pattyboi's kernel
B-S versions
1. mostly DEODEXed the ROM
2. fixed FC on clock app (switched clock/alarm from stock worldclock.apk to AOSP clock)
3. changed bootanimation.zip, boot sound, and stock ringtones and sounds.
4. added more stable kernel to flash file.
5. added Pandora (no-ads vers. 5.5), SpiritUL (FM radio support), Facebook, RootBrowser, Adobe reader, Adobe flash player, Wifi Tether, and Viper4android (DSP/equalizer)
5.1 all apps that have been listed in 5 can be uninstalled without the need for root
6. root and SU has been added
*1.04-lean
list of removed apps
1. Dropbox (can be found in playstore)
2. Google plus (can be found in playstore)
3. Hangouts (can be found in playstore)
4. HTC Dot View(can be found in playstore)
5. keyboard language packs for Arabic, Chinese, English UK, French, German, Greek, Italian, Portuguese, Russian, and Spanish (not in play store) if needed, flash language.zip found here
6. VPN dialogs (not in play store) if needed, flash missing.zip found here
7. HTC Zoe (can be found in playstore)
BUGS​
CRI versions
1.USB internet pass-through not working
2.WiFi direct (miracast) not working
3. want to get rid of annoying volume too loud warning
B-S versions
1. native hotspot says internet when connected to win 7 machine, but will not allow it to go through. Have included wifi tether as a workaround until the issue can be resolved
THANKS​
CRI versions
I thank wolfaas12345 for his awesome tutorial on bootloader unlocking, pattyboi for providing a more stable kernel, and chainfire for providing a great solution to provide the SU binary and app for rooted devices. and of course, CraviingCritic for providing the original ROM in which this wouldn't be possible
B-S versions
I thank wolfaas12345 for his awesome tutorial on bootloader unlocking, pattyboi for providing the current kernel, and chainfire for providing a great solution to provide the SU binary and app for rooted devices. and of course, LarryBoyG for providing the original ROM in which this wouldn't be possible
please feel free to let me know if there's any issues with this release and i will fix them as they are found for now as this device is the one i primarily use as of right now.
I will also be keeping the links updated for as long as I own the device (being that my HTC Desire 510(Cricket) is network unlocked, that may be a long time - or until I get a better device).
UPDATES​
for those of you who have downloaded the ROM since first release, I will include an CRI_NSupdate.zip or B-S_NSupdate.zip file found here. it will include the changes I have made to the rom since it's initial upload.
the file by the name of NSupdate.szip will include update that pertain to both the CRI and B-S ROMS
to install the updates, just put the update file onto the root of the SD card, reboot into recovery, choose install, pick the update file, swipe the blue button on the bottom, reboot and enjoy.
EDITING THE BOOTUP​
location of files mentioned is in /system/customize/resource
to change boot animation
1. find your favorite boot animation
2. rename it to AIO_bootup.zip
3. copy/move and overwrite the original with a root explorer to /system/customize/resource
to change the boot sound
1. find a sound file you like and want to hear every time the phone boots (can be changed at any time)
2. convert it to wav (the file has to be wav in order for the phone to recognize it)
3. rename it to CRICKET_LOGO_24bit28k_STEREO.wav
4. copy/move and overwrite the original with a root explorer to /system/customize/resource
reboot and enjoy...
THINGS NOTICED WHILE CREATING ROMs​
1. both (cricket and boost/sprint) phones are exactly the same except for the boost/sprint ones contain a CDMA chipset.
1.1 the only things I had to change from the cricket rom to the boost rom was apns.xml in framework-res, apns-conf.xml, and the preferred network type in build.prop.
2. all kernels work for both (US) versions
3. the same recovery is used on both (US based) devices
so essentially, if we develop for the boost/sprint version of the device, change a few things, it will be ready to roll for the cricket version as well
TO FIX NATIVE TETHER ON B-S VERSIONS​
1. Install Script Manager – SManager app from the Play Store.
2. Open the app and grant it root access when prompted.
3. Now, navigate to /system/etc/init.d and tap “tether” script.
4. Click on SU and Boot (Android skull and gear icons, respectively)
5. Click on Run and Save options.
The issue should be fixed now. Reboot and enjoy!
thanks goes to qwerty6532 and LarryBoyG for the fix. now to add that permanently to the ROMs and then they'll be absolutely stable enough for me to be happy and start working on CM11

CM11
I will be building CM11 for the device for both the cricket and boost models. look for the info here as I update it a I need
****edit**** ok so I figured out some of the issue with CM11 not wanting to install apps. I got the internal memory pulling the 1.1 gbs but now I need to symlink the external memory where it goes.
****edit**** so I have figured out what needs to be done...... the kernel for CM11 needs to be built from the ground, up (or one needs to be built that is compatible with it). i'll upload the current one that fixes the memory error (look in downloads).

reserved
so as i have not been actively developing on the phone i will no longer supply updates. all flash files are up to date as of 8 months ago and should be working with out an issue.

again, reserved
same to you...

This would have to be one of the most comprehensive tutorials I have read. 10 out of 10 and kudos. Pity I have a 64 bit device and can't use most of it lol.

Burtrum57 said:
This would have to be one of the most comprehensive tutorials I have read. 10 out of 10 and kudos. Pity I have a 64 bit device and can't use most of it lol.
Click to expand...
Click to collapse
if I had a 64-bit version for this device, I would have it out as soon as I could. and thanks

Great job. Off and running now

I'm not sure how to add the tether fix to the ROM. Not really a developer more of a tester.. Wish I could get into developing don't really know where to start lol.
If you need any help testing or working on CM11 for Boost shoot me a PM I'd be glad to help
Sent from my 0PCV1 using XDA Free mobile app

Question to you Schizoidd......If I install the new 1.04lean over the previous build, do I still need to flash that update or is is already included in 1.04lean. I already falshed that some time ago when you first put it out, so I'm just not sure if its needed again or not. Thanks bro.

CSP III said:
Question to you Schizoidd......If I install the new 1.04lean over the previous build, do I still need to flash that update or is is already included in 1.04lean. I already falshed that some time ago when you first put it out, so I'm just not sure if its needed again or not. Thanks bro.
Click to expand...
Click to collapse
When you flash the new one, wipe the system partition and then use an explorer to remove v4a from the user apps. Which is located in /data/apps and reboot

qwerty6532 said:
I'm not sure how to add the tether fix to the ROM. Not really a developer more of a tester.. Wish I could get into developing don't really know where to start lol.
If you need any help testing or working on CM11 for Boost shoot me a PM I'd be glad to help
Sent from my 0PCV1 using XDA Free mobile app
Click to expand...
Click to collapse
Well it's added to it. It just needs to be activated for now until I can figure out how to add it to automatically start from the first run of the Sprint/boost ROM

schizoidd said:
When you flash the new one, wipe the system partition and then use an explorer to remove v4a from the user apps. Which is located in /data/apps and reboot
Click to expand...
Click to collapse
Sorry, not following "wipe the system partition" ???

CSP III said:
Sorry, not following "wipe the system partition" ???
Click to expand...
Click to collapse
if you in recovery, go to wipe and then advance wipe and check system. wipe it like u would as if ur doing a factory reset

schizoidd said:
if you in recovery, go to wipe and then advance wipe and check system. wipe it like u would as if ur doing a factory reset
Click to expand...
Click to collapse
Yeah, I figured as much. Should have been clearer with my ? Is that before or after I flash the new lean. I though if I did it after, that it would set me back to square one. As in having to start fresh setting everything up again, which I really dont want to have to do. Apologies for my unclearness.

CSP III said:
Yeah, I figured as much. Should have been clearer with my ? Is that before or after I flash the new lean. I though if I did it after, that it would set me back to square one. As in having to start fresh setting everything up again, which I really dont want to have to do. Apologies for my unclearness.
Click to expand...
Click to collapse
it'll leave ur data alone, just delete the OS. do not touch internal memory, davlik, data, or cache and ur stuff will be safe. I have done it and my stuff is fine

schizoidd said:
it'll leave ur data alone, just delete the OS. do not touch internal memory, davlik, data, or cache and ur stuff will be safe. I have done it and my stuff is fine
Click to expand...
Click to collapse
Right on buddy. I'll take you at your word on it. I've never had to do that before so it naturally made me a little nervous. Not that I couldnt have just restored a backup, but still . Many thanks.

Problems
System UI force closes and power button doesn't turn the screen back on when I flash the latest cricket version.

schizoidd said:
I
for those of you that build the kernels, do you think u can build one that is AOSP and compatible with the device for android 4.4.4?
Click to expand...
Click to collapse
we cant really do a "aosp" kernel because of htc's modifications to the board and pins,and they have their own dtb issues...im 99% sure mine works with android 4.4.x because of larry using it in gpe,just repack the ramdisk the zimage and it should be okay

Bobby060 said:
System UI force closes and power button doesn't turn the screen back on when I flash the latest cricket version.
Click to expand...
Click to collapse
If you're going from bone stock to this, you need to do a factory data reset. Just make ssure you back up your data and use nandroid manager to pull it data back into the new ROM

Lineage OS 04.04.17 wifi won't connect

Hello there
I finally completed installing Lineage OS to my Mi5 today, following all the official instructions on the Lineage os page.
Everything installed without error - however I can't connect to wifi!
When choosing the wifi network it says "Connecting" quickly followed by "Saved". Occasionally it will say "Authentication failed" or "Disabled".
I can't get it to connect to either 2.4ghz or 5ghz, and both of these were working fine in Miui Global stable rom.
Any insight would be wonderful.
Cheers!
Edit: solution down the thread.

Hi!
Have you tried to reflash rom?
Are you using stock LOS kernel ou another kernel?

Yes I did reflash the ROM once. I assume I'm using the default kernel, I haven't gone to any efforts to use another (I'm a noob )

Solution
Follow up - after much pulling out of hair and freaking out, this solution finally did the job:
https://forum.xda-developers.com/mi-5/help/wifi-connectivity-problem-t3517777/post70408866
All hail Pekkuky!
"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=957FDC328BF4
Intf1MacAddress=957FDC328BF5
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. "

Anyone found ROM or kernel that allows tether on O or P?

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.

Troubleshooting wifi problems on S2 exynos5433 tablet ONLY discussion for users running any version of Android 10

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.