Develop Bugs

Latest T-Mobile Update Slowed Down My Phone

Hi guys,
So i just downloaded and installed the latest T-mobile update and now my phone is slower.
Every time I hit the home button, the image blinks and redraws and there's just a hint of stutter.
The app drawer also takes a little longer now.
What the heck?
It used to be so zippy and fast. How do I fix it, anyone know?

cainman said:
Hi guys,
So i just downloaded and installed the latest T-mobile update and now my phone is slower.
Every time I hit the home button, the image blinks and redraws and there's just a hint of stutter.
The app drawer also takes a little longer now.
What the heck?
It used to be so zippy and fast. How do I fix it, anyone know?
Click to expand...
Click to collapse
Might help to post which update you received.

reTARDIS said:
Might help to post which update you received.
Click to expand...
Click to collapse
D85110r

cainman said:
D85110r
Click to expand...
Click to collapse
Try disabling hw overlays in developers options to help with that redraw stutter. Remember you have to set it everytime you boot, unless you're booted with xposed installed, then you could download the module that keeps it active at all times.
This seems to have helped a lot of people with your issue.

Thank you.
It's sadly still doing it.

cainman said:
Thank you.
It's sadly still doing it.
Click to expand...
Click to collapse
Did you take the ota or download one of the twrp upgrades floating around? Either way in your situation you probably need to do a factory reset. Alternatively follow the twrp method HERE if you haven't already and I can personally guarantee a better than ota install. If you want it to be done correctly to fix any problems you need to wipe the system and data partitions before flashing. Also don't forget to download super su if you want to keep root (linked in guide). There is another upgrade twrp file in the development section I think that is not a perfect 1:1 image and could give problems. Not saying that particular rom is bad or that it is the problem, its just not a 1:1 like the guide I linked you to it is directory/installer script dependent. The one I made transfers the whole untouched partition over and inside has all the symlinks and permissions preset by LG.

Factory Reset

G930A_PF2_Stock_DeOdexed_Debloated_ROM (7/12/2016)

**You can begin the following process from any Build but you must already have Root Access**
**Required** [root] FlashFire
Download:
- G930A_PF2_Stock_DeOdexed_Debloated_ROM.zip
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app, grant root access, and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Press "Flash Zip or OTA" and locate and select the ROM. Use the default settings under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and set "Reboot" to "Download."
6. Press the lightning bolt then "Ok" to begin the flash . The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition.
7. Once the flash is complete and the device reboots into "Download" mode, flash the G930A_PF2_Stock_Modem_Recovery_Bootloader using Odin's AP slot. The device will take 10 - 15 mins for the first boot!
8. To regain root access, re-run "root.bat" once the device has fully rebooted. Make certain usb debugging is enabled. Enjoy!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The above process will update your Modem, Non-hlos, System, Bootloader, and Stock Recovery.
3. The ROM will automatically wipe all User Data!
4. Follow this guide if you do not already have root access: http://forum.xda-developers.com/att-...g935a-t3410538

Will it work for g935a? And does it fix lag?
Sent from my SAMSUNG-SM-G935A using Tapatalk

Awesome!

Ok how many folks have successfully flashed this?
It's still using eng boot? And will I be able to update super su script once installed? Also curious if maybe deodexed means I can get v4a running on this bad boy sorry for the question blast just excited to see the att s7 taking off into #root =D in Texas it goes "y'all got root?!"

4. Follow this guide if you do not already have root access: http://forum.xda-developers.com/att-...g935a-t3410538
Click to expand...
Click to collapse
Can you fix the URL? I get a 404 when clicking it.
Thanks,
Aaron

I can confirm. This flashes!
I needed to run root.bat twice to get it to take, but everything is working, AND...
Knox still reads 0x0!

smknutson said:
I can confirm. This flashes!
I needed to run root.bat twice to get it to take, but everything is working, AND...
Knox still reads 0x0!
Click to expand...
Click to collapse
Noticing any difference from original Rom performance wise? I'm thinking about joining ya but I got this thing running so buttery smooth I don't want to fix it if it ain't broke.

Do you fix the lag?
Enviado desde mi SAMSUNG-SM-G930A mediante Tapatalk

noobtxtech said:
Noticing any difference from original Rom performance wise? I'm thinking about joining ya but I got this thing running so buttery smooth I don't want to fix it if it ain't broke.
Click to expand...
Click to collapse
I think I am. It's either this Rom or the eng bootloader, but it runs hotter. It's running in interactive governor but cpu temperature is averaging idle at 45°c whereas on stock it felt much cooler. Something about this installation is causing this thing to heat up.
Carlos Terán said:
Do you fix the lag?
Enviado desde mi SAMSUNG-SM-G930A mediante Tapatalk
Click to expand...
Click to collapse
I'm not sure what lag you're referring to?

noobtxtech said:
Noticing any difference from original Rom performance wise? I'm thinking about joining ya but I got this thing running so buttery smooth I don't want to fix it if it ain't broke.
Click to expand...
Click to collapse
Okay, I figured it out guys.
After flashing, rooting, and starting to set it up, you will probably notice it feels a bit sluggish and runs hot, even after correcting the CPU governor to Interactive.
I believe I found the fix over in the Verizon S7 area.
Head to this thread: http://forum.xda-developers.com/showthread.php?p=67605246
And follow the directions in the Recommended Next Steps section. I flashed the Fix and Debloater zip, and my phone is now fast and running very cool.
OP may need to consider adding this tip to the OP.

smknutson said:
Okay, I figured it out guys.
After flashing, rooting, and starting to set it up, you will probably notice it feels a bit sluggish and runs hot, even after correcting the CPU governor to Interactive.
I believe I found the fix over in the Verizon S7 area.
Head to this thread: http://forum.xda-developers.com/showthread.php?p=67605246
And follow the directions in the Recommended Next Steps section. I flashed the Fix and Debloater zip, and my phone is now fast and running very cool.
OP may need to consider adding this tip to the OP.
Click to expand...
Click to collapse
You tried to get v4a sound mod running by chance? Also are you running xposed framework/modules?

noobtxtech said:
You tried to get v4a sound mod running by chance? Also are you running xposed framework/modules?
Click to expand...
Click to collapse
Haven't tried v4a but Wanams modified Xposed is working and I have several modules operational.

smknutson said:
Okay, I figured it out guys.
After flashing, rooting, and starting to set it up, you will probably notice it feels a bit sluggish and runs hot, even after correcting the CPU governor to Interactive.
I believe I found the fix over in the Verizon S7 area.
Head to this thread: http://forum.xda-developers.com/showthread.php?p=67605246
And follow the directions in the Recommended Next Steps section. I flashed the Fix and Debloater zip, and my phone is now fast and running very cool.
OP may need to consider adding this tip to the OP.
Click to expand...
Click to collapse
Did you use the modified Odin to flash the bootloader or did you use the regular Odin?
Thank you

dirtydodge said:
Did you use the modified Odin to flash the bootloader or did you use the regular Odin?
Thank you
Click to expand...
Click to collapse
Modified Odin for both EngBoot and this threads addon .zip

smknutson said:
Modified Odin for both EngBoot and this threads addon .zip
Click to expand...
Click to collapse
Ok thank you. Figured so but just wanted to make sure. I'm downloading the Rom now. Glad you found the fix and debloat from the Verizon thread, I seen that the other day and used it and his other guide on how to set up Greenify and amplify. My phone is running awesome on the stock rooted but I always like to grab muniz's deodex versions and run them.

Also, if you want to get rid of the Custom icon on boot and reset it to Official in status, use the XTouchWiz xposed module.

Is this rooted? Id love to flash a deodex, debloated rom but have no root on it...

joe3681 said:
Is this rooted? Id love to flash a deodex, debloated rom but have no root on it...
Click to expand...
Click to collapse
You have to be rooted prior to flashing this.

Clearly. I meant post flash

joe3681 said:
Clearly. I meant post flash
Click to expand...
Click to collapse
" To regain root access, re-run "root.bat" once the device has fully rebooted. Make certain usb debugging is enabled. Enjoy! " is copy pasted from the OP so that would imply that it isn't rooted until you root it, as for why you would want a deodexed Rom (which is a performance hit) without root is beyond me. From what I gather reading this short thread you will need root and possibly even xposed to get it running right. In order to do that you would have to do some more reading. Hope this helps.

[ROM][Status Official] Verizon TMO Hybrid method for Debloating Stock ROM With Knox

This method creates the ability to debloat the Verizon GS7 (non-Edge Snapdragon) by modifying @jrkruse's method for the S7 edge posted here. Huge thanks to jrkruse for making the GS7 what it should be without massive bloat.
After my OP, he and @CVertigo1 evolved the method to fix the safetynet fail issues, so it now should work perfectly. I personally have not yet tried the updated method but will do so tomorrow. I'm copying instructions from the CVertigo1 thread here, but also keeping the old instructions below in post 1.
Knox counter is still 0x0, and I can confirm I have repeatedly used Samsung pay.
New CVertigo1 method:
CVertigo1 said:
Yet again, all thanks go to @jrkruse for this one. I have modified his zip to work on the Verizon S7 flat. The ROM is silky smooth since it uses the factory kernel. I'm going to tweak his instructions to work for the flat. I can confirm that SafetyNet passes using this method.
Download
ODIN v3.12.3.zip
Firmware bundle for the G930. Includes VZW and TMO firmware (G930VVRU4BQA2 and G930TUVU4BQB1) as well as engineering bootloader and stock boot_recovery.image
S7_SU_2_79_Root_Unroot_WO_Tweaks.zip
VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V5_VZWS7FLAT.zip
Install Instructions From Any Build
Warning: This will wipe your device. Some of these instructions are redundant, but they will ensure that everything goes as planned. If you don't follow them to the T, don't complain.
1) Unzip Odin and the firmware bundle zips. Boot the phone into download mode and flash the G930T BL, AP, and CP files in Odin.
2) Don't bother logging into any accounts, as the phone will get wiped again. Copy the FlashFire.apk and VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V5_VZWS7FLAT.zip to your SD card.
3) Shut off the phone and boot into download mode (volume down, home, and power). Flash the S7 Nougat root kernel in the AP slot in Odin. This file was in the firmware bundle.
4) When the phone reboots, unlock developer options and enable USB debugging. Unzip the S7_SU_2_79_Root_Unroot_WO_Tweaks.zip and run root.bat from your PC.
5) Now install FlashFire. Go into FlashFire settings and click option to allow flashing Bootloaders.
6) Now click flash firmware and chose AP_G930TUVU4BQB1_CL10376601_QB12449107_REV02_user_low_ship_MULTI_CERT_meta.tar.md5 SELECT ALL OF THE PARTIONS!!!
7) Now click install zip and choose VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V5_VZWS7FLAT.zip Make sure to click mount system when FlashFire asks. View attachment 4073928
VERY IMPORTANT NOTE: MAKE SURE TO UNCHECK INJECT ROOT AFTER ADDING THE ZIP!!!!!!!- Thanks @dclutter1
8) The phone will restart and FlashFire will flash the firmware first(it will take a couple minutes to find and flash everything), then the Aroma installer will start.
9) In Aroma, select wipe data(DO NOT KEEP SU)
10) The phone will say custom status on first boot, but it goes away after setup and reboot.
Click to expand...
Click to collapse

older method just for the record
Here is an OLDER METHOD with ADB install
Download stuff:
ODIN v3.12.3.zip
Firmware bundle for the G930. Includes VZW and TMO firmware (G930VVRU4BQA2 and G930TUVU4BQB1) as well as engineering bootloader and stock boot_recovery.image
ROM: There are two basic options to choose from:
PlayStore Rom - so called because it has almost NO apps and you download what you want from the PlayStore. Has an experience very similar to the Pixel.
Hybrid ROM - close to Samsung Stock experience by massively debloated
Method:
Reboot phone to recovery wipe data
Reboot to bootloader
In odin flash:
In BL slot: BL_G930TUVU4BQB1_CL10376601_QB12449118_REV02_user_ low_ship_MULTI_CERT.tar.md5
In AP slot: AP_G930TUVU4BQB1_CL10376601_QB12449118_REV02_user_ low_ship_MULTI_CERT_meta.tar.md5
In CP slot: CP_G930TUVU4BQB1_CL10376601_QB12449107_REV02_user_low_ship_MULTI_CERT.tar.md5
Leave CSC slot Blank
Go through setup don't add any accounts your going to wipe again when finished reboot back to bootloader
In odin Flash Engineering Boot.img from above (in AP slot)
When phone reboots and computer reconnects to phone Open HYBRID_PLAYSTORE_ROM.zip folder
Click Verizon_TMO_PlayStore_Install.bat
When done click press to continue the phone will reboot back to download mode
In odin flash:
In CSC slot: CSC_VZW_G930VVZW4BQA2_CL10280325_QB12417265_REV02_user_low_ship_MULTI_CERT.tar.md5
In AP slot: G930TUVU4BQB1_Boot_Recovery_Image.tar.md5.tar
Phone will reboot to recovery and fail
In Recovery click Mount System
Wipe data
Reboot phone
During Boot Phone will Say Custom Status this will change after phone is setup and a reboot is performed
Once through setup open Rom Control App
Navigate to Phone and Settings
Click on IMS Settings
Choose Ims service switch
Click on MMTEL switch
Click on RCS switch
Under MMTEL section I enabled all the options
Click Back Button until your back to Phone and Settings Menu in Rom Control
Choose Activate Advanced Calling
Make sure under Advanced Calling that HD and Video calls are enabled
Activate WifiCalling
Known issues:
Safety net check fails (so Venmo does not work)
Some sites are blocked. Turning on "data saver" in Chrome settings worked for me but not everyone
I found that I had to go into settings > applications > phone and explicitly choose the phone as my default application for calls before it would correctly create a notification when the phone rang.
Some slightly more varsity moves:
Keeping apps from your stock:
You can modify the .bat file to not remove any apps you want to keep.
For example, I wanted to keep the "always on" display, so I deleted these lines from the .bat file:
Code:
adb shell rm -r /system/priv-app/AODService_v20
You can also further delete apps. Essentially during steps 5 - 7 above, the phone is rooted. During that time you can remove other packages. (My advice would be to pull them to your computer so you can push them back if needed)
For instance, I wanted to remove Hangouts, the AOSP browser (I use Chrome) and VisualVoiceMail. So I repeated step 5, then did:
Code:
adb root
adb remount
adb pull /system/app/VisualVoicemail
adb shell rm -r /system/app/VisualVoicemail
adb reboot bootloader
Then repeat steps 9 - 11
Wipe CACHE, (NOT data)
Reboot

Cool, cant wait to walk a friend thru this.

Just got up and running on PlayStore, everything seems good except I can't get the call recording to work. Thanks for putting this together
Sent from my SM-G935V using Tapatalk

JPSloan1 said:
...
7. Click Verizon_TMO_PlayStore_Install.bat.
...
Click to expand...
Click to collapse
Where is this .bat file?
Also, on jrkruse's thread, I only see a single ROM for download: VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V2.zip. Am I missing something?
Edit: I found the Play Store ROM; it contains the .bat file. The new ROM in jrkruse's OP won't work with this method, I assume.

thrillerbee said:
Where is this .bat file?
Also, on jrkruse's thread, I only see a single ROM for download: VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V2.zip. Am I missing something?
Edit: I found the Play Store ROM; it contains the .bat file. The new ROM in jrkruse's OP won't work with this method, I assume.
Click to expand...
Click to collapse
Yes It appears he updated his method to one that uses a different kind of temporary root as well as flashable files. I'll have to look at it and see if it's customizable the way the other one was, but it looks like you found the correct playstore ROM zip from before. Here is the other ROM. Sorry for the confusion.

Do we need to flash the Verizon modem? And if so would you have a flashable file? Thanks,

if i want to just put the tmobile firmware on my verizon phone and still use verizon service, do i just flash the tmobile firmware and then the verizon csc file and call it a day? not looking for the debloat and all that other stuff. just straight up tmobile firmware working on verizon.

t1231 said:
Do we need to flash the Verizon modem? And if so would you have a flashable file? Thanks,
Click to expand...
Click to collapse
I tried but the .zip kept failing so maybe I didn't create it right.... So ultimately I did not bother and my service seems just fine at the moment.

Hobson318 said:
if i want to just put the tmobile firmware on my verizon phone and still use verizon service, do i just flash the tmobile firmware and then the verizon csc file and call it a day? not looking for the debloat and all that other stuff. just straight up tmobile firmware working on verizon.
Click to expand...
Click to collapse
I think that would work (and wouldn't think you need to bother with the engineering bootloader steps either then) but to be honest it might be safer to ask jrkruse, because I don't deeply understand it - really just adapted his method for the S7 flat.

You speak of rebooting into recovery and wiping the cache. How exactly? All I seem to get is a dead robot on my screen.
Am I missing something?
Attempting this on a G930V, FWIW.

S3NTYN3L said:
You speak of rebooting into recovery and wiping the cache. How exactly? All I seem to get is a dead robot on my screen.
Am I missing something?
Attempting this on a G930V, FWIW.
Click to expand...
Click to collapse
After which step?
At one point I did get a robot with a yellow triangle saying "no instructions" or something, but I waited a DL few minutes and pressed a few buttons and it booted into recovery.

JPSloan1 said:
After which step?
At one point I did get a robot with a yellow triangle saying "no instructions" or something, but I waited a DL few minutes and pressed a few buttons and it booted into recovery.
Click to expand...
Click to collapse
Step 10.
Hmm, It seems that I wasn't holding the buttons down long enough.
If DL = Damn Long, then, yes, I agree.

OK, made it to step 15 and now I'm boned.
I had to install that ROM Control app manually as it didn't get pushed to the phone for some reason.
While attempting to follow along by clicking on IMS Settings, a toast message complains about no CSC binary or customer.xml
EDIT:
Hmm, I'll just wait a bit until you all get this sorted out I guess. In the meantime, it's back to stock for me.

S3NTYN3L said:
OK, made it to step 15 and now I'm boned.
I had to install that ROM Control app manually as it didn't get pushed to the phone for some reason.
While attempting to follow along by clicking on IMS Settings, a toast message complains about no CSC binary or customer.xml
EDIT:
Hmm, I'll just wait a bit until you all get this sorted out I guess. In the meantime, it's back to stock for me.
Click to expand...
Click to collapse
If ROM control didn't install manually it's because the .bat file didn't execute correctly. Did you modify it? Did it successfully acquire root and execute all the commands all the way through to the "click to continue" prompt? OR did it give error messages along the way? (There will be a few during the remove steps because it's removing packages that only exist on the S7 edge, not flat.
I would try it again if you have the patience.

I didn't modify anything.
I only recall a few minor errors regarding removal of non-existent directories.
Yes, the script went through to the end.
Yes, the phone had root and the TMobile rom wouldn't let me forget it, lol.
It kept complaining the whole way through.

JPSloan1 said:
Basically this method temporarily roots the phone to modify the packages installed, removes a ton of them, and then reverts. So with this method, Knox counter is still 0x0, and I can confirm I have repeatedly used Samsung pay
Click to expand...
Click to collapse
Can you do me a huge favor and install 'Phone info *Samsung*' from the PlayStore and upload a screenshot of the firmware page. I replicated jrkruse method since he changed it, but swapped the boot.img for the S7 flat images. Everything works great, but I fail SafetyNet. I need to find out where I'm mixed up. If I can figure this out, then I believe I can make a simple zip to take care of everything else.

CVertigo1 said:
Can you do me a huge favor and install 'Phone info *Samsung*' from the PlayStore and upload a screenshot of the firmware page. I replicated jrkruse method since he changed it, but swapped the boot.img for the S7 flat images. Everything works great, but I fail SafetyNet. I need to find out where I'm mixed up. If I can figure this out, then I believe I can make a simple zip to take care of everything else.
Click to expand...
Click to collapse
Yeah attached. I think I also have this problem as do those in the other thread, and that's why I get an error on device check with Venmo.

I thought you posted that Samsung Pay worked for you in the OP.

CVertigo1 said:
I thought you posted that Samsung Pay worked for you in the OP.
Click to expand...
Click to collapse
I followed the method in the OP, installed Play Store version. Samsung Pay is working for me.
Sent from my SM-G935V using Tapatalk

[FIRMWARE] [STOCK] Pre-rooted, optimized, stock firmware for HD 10 Suez [APRIL 2019]

Pre-Rooted, Optimized, Stock ROM
This thread contains stock firmware for the Fire HD 10 SUEZ, which has been pre-rooted and optimized. Please see the respective section for your FireOS version. Later FireOS versions ARE supported, but I am going to need a few days. Downgrading from a newer version of FireOS is NOT recommended and can potentially damage your device. This ROM has NOT been 'de-bloated'. By installing this ROM, you do so at your own risk. Results may not always be the same.
****THIS GUIDE REQUIRES AN UNLOCKED DEVICE WITH TWRP.****
Features:
- Zipaligned - All system and framework apks have been zipaligned.
- Deodexed - The whole system has been successfully deodexed. Among many things, this makes uninstalling system apps easier and greatly lowers the risk of a bootloop, though not promised. It also saves a little bit of space in the system when uninstalling system apps.
- No OTA - Never worry about an accidental Over The Air Update. Both APKs have been removed. You can sign into your network the very first boot.
- Pre-rooted. - Magisk, by XDA member and developer @topjohnwu, is stepping up to the plate this time. The ROM is pre-rooted with the latest stable version 18.1. SuperSU cannot be flashed on this tablet. Doing so will result in an endless display of the beautiful orange fire logo. It is possible to manually root the ROM with SuperSU, but I will need to do a lot of testing. If you prefer SuperSU, this ROM is not for you and you will have to root using one of the several guides available in this forum.
- Busybox - Contains the latest busybox by XDA member and developer @osm0sis.
If it were not for the tool, SuperR's Kitchen, this ROM, and hopefully others, wouldn't be possible. I have trouble linking his username here, but if someone can direct superR to this thread so he can see the endless thanks I give to him for creating this amazing tool.
These ROMS do NOT contain any of my tricks or hacks. They're simply pre rooted ROMS in case you need to return back to stock FireOS. No apps have been removed except the above mentioned and none have been added, except the above mentioned.
Downloads:
- For HD 10 SUEZ on 5.6.1.0: 5.6.1.0_Fire_HD_10_optimized_pre_rooted_stock_rom-signed.zip
- For HD 10 SUEZ on 5.6.2.0: 5.6.2.0_Fire_HD_10_optimized_pre_rooted_stock_rom-signed.zip
Installation:
1. Download the ROM then plug your tablet into the PC and place the zip on your internal storage.
2. BACKUP ALL VALUABLE DATA. YOU WILL BE ERASING THE SYSTEM AND DATA. Reboot to TWRP (recovery), tap wipe and select dalvik, cache, system and data ONLY and swipe to confirm. When finished tap the home button, reboot then recovery.
3. When back in recovery, tap install and select the ROM then swipe to confirm. When done, reboot and enjoy.

Reservation
Sent from my MotoG3 using XDA Labs

Is there any benefit to flashing this if I'm already rooted? I mean, "optimized" sounds nice, but my data.... lol

Anyone try this yet?
EDIT: Flashed and got a black screen at first, spooped me for a few seconds there, then showed the Amazon and (now currently) Fire logos. And now we wait for it to do its optimization.

To be clear: your instructions don't have any prerequisites of already being rooted or modded in any other way? So a person could do these steps on an unmodified HD 10 2017 Suez that is running 5.6.1.0?

phanguy said:
To be clear: your instructions don't have any prerequisites of already being rooted or modded in any other way? So a person could do these steps on an unmodified HD 10 2017 Suez that is running 5.6.1.0?
Click to expand...
Click to collapse
I would think you would need to have TWRP installed, at least. The instructions do call for that.
Also, it appears to be working without at hitch. I'm inputting my WiFi password as I type this.
EDIT: I kept getting a DHCP error when connecting to my home hotspot, so I'm using my phone's hotspot instead. WiFi icon has an exclamation mark next to it, but internet seems to be working fine.
EDIT 2: Spoke too soon. Don't have internet. No matter what I do. Can't seem to connect properly. Every network I try just keeps saying "Obtaining IP address," never connects. Eventually throws the error, "IP Configuration Failure, IP configuration failed due to DHCP error."
EDIT 3: Phone hotspot is working, for now. Guess I'll stick with that until the router is fixed.

GuyInDogSuit said:
I would think you would need to have TWRP installed, at least. The instructions do call for that.
Also, it appears to be working without at hitch. I'm inputting my WiFi password as I type this.
EDIT: I kept getting a DHCP error when connecting to my home hotspot, so I'm using my phone's hotspot instead. WiFi icon has an exclamation mark next to it, but internet seems to be working fine.
EDIT 2: Spoke too soon. Don't have internet. No matter what I do. Can't seem to connect properly. Every network I try just keeps saying "Obtaining IP address," never connects. Eventually throws the error, "IP Configuration Failure, IP configuration failed due to DHCP error."
EDIT 3: Phone hotspot is working, for now. Guess I'll stick with that until the router is fixed.
Click to expand...
Click to collapse
This is on a 2.4.ghz band that you are trying to connect to I'm assuming?
Edit: @DragonFire1024 thank you so much for your continued and dedicated work with these tablets! Can't wait to see what you can do when you really get down on making a ROM for this beast.

tylerhole said:
This is on a 2.4.ghz band that you are trying to connect to I'm assuming?
Click to expand...
Click to collapse
It most likely is. The router's SUPPOSED to output 5GHz as well, but someone f*cked it up and now it only does 2.4.

GuyInDogSuit said:
It most likely is. The router's SUPPOSED to output 5GHz as well, but someone f*cked it up and now it only does 2.4.
Click to expand...
Click to collapse
Do you know/are you able to find out what the channel width is set at? If it's set at 40 instead of 20 that could be why the phone hot spot works and the router doesn't.

tylerhole said:
Do you know/are you able to find out what the channel width is set at? If it's set at 40 instead of 20 that could be why the phone hot spot works and the router doesn't.
Click to expand...
Click to collapse
Could be. I'll check and try the other setting. It's worked before this ROM, so I dunno if that's the cause...
EDIT: Nope, that wasn't it. Where's the f*cking WPS option on this tablet?! Thanks, Amazon!

GuyInDogSuit said:
Could be. I'll check and try the other setting. It's worked before this ROM, so I dunno if that's the cause...
Click to expand...
Click to collapse
Very well could not be then, was just the first thing that popped into my head.
Sent from my SM-G9650/DS running stang5litre Pie ROM

tylerhole said:
Very well could not be then, was just the first thing that popped into my head.
Click to expand...
Click to collapse
Nothing works so far. I need to fix this damn router or replace it. I'm tired of AT&T and their sh*tty hardware and even sh*ttier service.

I'm having the same WiFi issue. Just gets stuck on obtaining IP address.
Sent from my SM-G9650/DS running stang5litre Pie ROM
---------- Post added at 10:14 PM ---------- Previous post was at 10:07 PM ----------
It appears that the tablet is not liking DHCP. If you configure a static IP address it connects fine and internet works.
Sent from my SM-G9650/DS running stang5litre Pie ROM

GuyInDogSuit said:
It most likely is. The router's SUPPOSED to output 5GHz as well, but someone f*cked it up and now it only does 2.4.
Click to expand...
Click to collapse
I wonder...perhaps installing my framework and settings APK will fix this. Looks like I have a lot of tests tomorrow.
Sent from my MotoG3 using XDA Labs

Wonder why it works (sometimes) with my phone hotspot? I'll try the static IP. That actually had crossed my mind, @tylerhole, but i didn't have time to try it before work.

DragonFire1024 said:
I wonder...perhaps installing my framework and settings APK will fix this. Looks like I have a lot of tests tomorrow.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
In the "optimizing" you did for this ROM did any of it have to do with wifi?
Sent from my SM-G9650/DS running stang5litre Pie ROM

DragonFire1024 said:
I wonder...perhaps installing my framework and settings APK will fix this. Looks like I have a lot of tests tomorrow.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
if you're referring to what you have in this thread then it didn't work for me. i removed everything but the boot animation, framework stuff, and the settings apk. still getting wifi issue though.

Took a chance and tried this coming from the original 5.1.1 Fire OS (what I thought was 5.1.1, but now im not sure what version I had, read on)
Did the wipe as instructed and everything looked good during the flash but on reboot it looks like the 5.1.1 persisted somehow.
EDIT. getprop ro.build.version.release reports 5.1.1 but the system updates reports 5.6.1.0. I had blocked system updates just to make sure that was disabled but in doing so you cant get the version from the settings. So I'm good, except for the WIFI not working.
Miles

phanguy said:
if you're referring to what you have in this thread then it didn't work for me. i removed everything but the boot animation, framework stuff, and the settings apk. still getting wifi issue though.
Click to expand...
Click to collapse
Ok I do know the kernel source contains the wifi drivers. I'm not at home to look, but I'm willing to bet $150 that the needed wifi firmware is not in the system partition. This is the last hurdle I believe and I think everything to this point are intentional blockades. If one can hunt down the system wifi drivers it shouldn't be an issue to include them in another build.
Sent from my MotoG3 using XDA Labs

beachmiles said:
Took a chance and tried this coming from the original 5.1.1 Fire OS (what I thought was 5.1.1, but now im not sure what version I had, read on)
Did the wipe as instructed and everything looked good during the flash but on reboot it looks like the 5.1.1 persisted somehow.
EDIT. getprop ro.build.version.release reports 5.1.1 but the system updates reports 5.6.1.0. I had blocked system updates just to make sure that was disabled but in doing so you cant get the version from the settings. So I'm good!! Thanks.
Miles
Click to expand...
Click to collapse
5.1.1 is the Android version not FireOS version which is 5.6.1.0.
Sent from my MotoG3 using XDA Labs

TWRP (Ianmacd) Images, New Space.

This is NOT my work (Ianmacd) and guide is written by Mr Pickles all credits to him for his install method.
Also this is just a copy and paste but the guide is well written and TWRP should cause less issues.
I'm sure Gieti94 is just perhaps busy with other commitments, credit also to him for his fantastic efforts.
Just a new space for the currently working TWRP so all don't get in a pickle.
----------------------------
Download Maintained By Pickles (best all in one convenient place) will have everything necessary for twrp functionality. Credit to pickles.....:good:
http://bit.ly/2VlcqYd
Excellent installation Guide below
Install Guide
---------------------------
- NOT A SINGLE STEP IS UNNESSECARY
- DO THEM _ALL_ EXACTLY!
- ALL YOUR DATA WILL BE GONE - BACKUP!
---------------------------------------
DO NOT INSTALL MODPACK FROM SOLDIER - IT BREAKS TWRP!
---------------------------------------
If you have any problems - contact @PiCkLeS or on Telegram by PiCkLeS or @rp4k
---------------------------------------
All development is by @ianmacd (Ian Macdonald).
---------------------------------------
0 - No matter what you have today, no root or Magisk-only solution or TWRP with Magisk-solution, do ALL the steps..
1 - Make sure you copy the "Magisk_Manager_Ian_install.apk" file and "Multidisabler-g97x_by_Ian.zip" file to your sd-card before you start!
2 - Download latest firmware via Samfirm or Frija or in any way you can, and unpack.
3 - Boot your phone to Download mode (Power+Bixby+VolDown) and remember to have the USB connected to your computer, it won't boot to DL-mode otherwise
4 - Keep autoboot etc in Odin settings, put each file in its place (AP, BL, CSC etc) and _dont_ use HOME_CSC, use CSC-only-file.
5 - After Odin is done, your phone will reboot automatically - let it! It can feel like forever, but let it do its restarts and stuff until you are in system-setup
6 - Do the setup as per usual, CONNECT TO WIFI but you can safely just say Skip on sign in and other stuff
7 - When setup says its all finished and you get to the standard launcher - go into Settings and enable Developer settings
8 - This step IS necessary.. If you don't do this step, you might get in pre-normal rrm state and you will have wait 7 days to try again: Enter Developer settings and look for the "OEM Unlock" switch - if you are rooting for the first time, Enable it. If you already have root since before or unlocked your bootloiader before, just confirm that its Enabled and graded out.
9 - If you already have an unlocked bootloader, skip to step 12. If not, continue with step 10.
10 - IF you never have unlocked your bootloader before, Power off the phone and boot into download mode again. You will see the long press volUp option for unlock bl, do that.
11 - IF you never have unlocked OEM before, boot the phone again, do the setup without signing in etc but connect to wifi, enable dev settings, go into dev settings and check that OEM now is enabled and grayed out.
12 - Reboot the phone in recovery mode (Power+Bixby+VolUp and keep holding until you are in stock recovery. Choose and do a factory reset.
13 - Reboot to bootloader with option in Recovery.
14 - Flash the tar you got (S10x-TWRP+Magisk_fixed_by_Ian.tar I Odin in the AP-slot. DISABLE auto reboot in Odin first!
15 - When the tar has flashed - Do as instructed on the phone, hold Power+VolDown for a few seconds and AS SOON AS THE SCREEN GOES BLACK -> quickly press power+bixby+volUp for a _long_ time, and I mean it can feel as if its a full minute! After a while you will see TWRP starting with its start screen, you can now let go and enter TWRP.
16 - FORMAT data, then WIPE data AND Cache. DO NOT LET IT REBOOT
17 - Flash "Multidisabler-g97x_by_Ian.zip" from SD card
18 - Go back to start screen of TWRP, Choose Reboot, Choose Recovery - YOU MUST ALWAYS CHOOSE REBOOT TO RECOVERY and _NOT_ system!
19 - Let the phone reboot into system, it will do some reboots it self, and again it will feel like it takes FOREVER - Just let it do its thing and DO NOT PRESS ANY KEYS!
20 - When your phone is finally done booting, just do the normal setup/signing for real this time.
21 - When you are done and in system/launcher, install "Magisk_Manager_Ian_install.apk" from SD card and verify that you now have Magisk Manager installed.
22 - Start Magisk Manager and say YES to what it says, it will do some stuff and then say "Rebooting in 5 seconds" - LET IT BOOT AND DO NOT TOUCH ANY KEYS this time either..
23 - Now when booted to system, start Magisk Manager and see that you have all green and its installed.
24 - Now you have root.
** Every time you reboot manually, be prepared to hold Power+Bixby+VolUP until you see the Samsung S10x-logo, then release and let it reboot, you will have root.
** Every time you power off the phone, when you power ON again, hold Power+Bixby+VolUP until you see the Samsung S10x-logo, then release and it will boot with root.
** Every time you want to enter TWRP-recovery, do as above but KEEP HOLDING THE KEYS UNTIL TWRP-start screen shows then release. Remember to choose reboot to recovery afterwards and you will boot with root.
** IF you screw up and forget or miss the key combo, just let it boot to system, immediately when system is up - reboot again and do the key combo and all is fine again.
This is me just trying to get an emergency first aid space, nothing more, I'm NOT trying to take any credits or dismiss Gieti94.
Thanks All

Duncan1982 said:
This is NOT my work (Ianmacd) and guide is written by rp4k all credits to him for his install method.
Click to expand...
Click to collapse
This is my tutorial and not r4pk. And I'd prefer that you use the download I provide here and no where else to make sure the right files gets downloaded when updated.
http://bit.ly/2VlcqYd
/P

Yea I can keep the OP updated, this is just an emergency first aid thread, thanks to Pickles for his well written guide.
I'm really not wanting to offend anyone, just for all to make life a bit easier....

very nice to have a reliable twrp solution, pitty that we don't have too many things to flash in recovery

Please remove the alternate download link, I have updated the multidisabler zip with a important update, v1.1 and the one download link for all is just for things like that, the other download link still have the old zip.
Very important that everyone uses Ian Macdonald's new v1.1 multidisabler script.
/P

I can update the mega link with the new disabler I reposted it to mega because I can't access Google @PiCkLeS
And yes I never said I wrote the guide I just added myself for helping people

rp4k said:
I can update the mega link with the new disabler I reposted it to mega because I can't access Google @PiCkLeS
Click to expand...
Click to collapse
I understand. But that doesn't seem to be a big problem for any one else and the bigger problem is that you risk having a link that is being used by the people only see it here and don't read anywhere else, or this message, and end up with old information or even worse, outdated files.
I can help you get the files on PM but please remove these links outside of my drive, which I maintain every day and keep up to date. It's not for vanity, it's for safety.
For now please edit your text and remove the link. All must use v1.1 of the multidisabler zip by Ian.
/P

Maybe this thread was a bad idea, as stated I am around and willing to keep things up to date
I know the importance, and how things are at present.

Duncan1982 said:
Maybe this thread was a bad idea, as stated I am around and willing to keep things up to date
I know the importance, and how things are at present.
Click to expand...
Click to collapse
Listen, just to be clear. I and I dont think Ian have a problem with you having this thread.
All I am worried about is the download link. Things can and are happening fast. If there are multiple sources for downloading files in this case, and today one was updated with important improvements, and there are many places to download from people can miss that and download old files that can cause big problems.
Keep the downloading to one good source and everything will be fine. The thread in it self can do much good by showing that there is an alternative, it works and right now almost 100 people in 24 hours have used it. Fantastic!
So I dont think it was a bad idea, I just dont want PM:s from people in a week or two asking why their device suddenly lost data, only to find out that they downloaded from a source that didnt have the latest files.
Thats all.
//P

PiCkLeS said:
Listen, just to be clear. I and I dont think Ian have a problem with you having this thread.
All I am worried about is the download link. Things can and are happening fast. If there are multiple sources for downloading files in this case, and today one was updated with important improvements, and there are many places to download from people can miss that and download old files that can cause big problems.
Keep the downloading to one good source and everything will be fine. The thread in it self can do much good by showing that there is an alternative, it works and right now almost 100 people in 24 hours have used it. Fantastic!
So I dont think it was a bad idea, I just dont want PM:s from people in a week or two asking why their device suddenly lost data, only to find out that they downloaded from a source that didnt have the latest files.
Thats all.
//P
Click to expand...
Click to collapse
I fully appreciate and understand that, the reason I created as I have plenty of time to maintain, and will keep it up to date I have been around for quite some time, if you look at my posts (search) I have had almost every device you can think of, currently have the Vivo IQOO also, I have enough experience to understand the important and implications.
I don't want your PM's to be going crazy so I'll fully respect your decisions and will keep everything updated also. But it is better if everything is tody and not one thing here and there, OP has been updated with your direct link, is this cool?
Just thought by creating this thread that it might help, my sincere and good intentions are hopefully evident

PiCkLeS said:
Please remove the alternate download link, I have updated the multidisabler zip with a important update, v1.1 and the one download link for all is just for things like that, the other download link still have the old zip.
Very important that everyone uses Ian Macdonald's new v1.1 multidisabler script.
/P
Click to expand...
Click to collapse
Can I install multi Disabler 1.1 withouth lost data?

zubi182 said:
Can I install multi Disabler 1.1 withouth lost data?
Click to expand...
Click to collapse
Yes just flash it in twrp, nothing will be lost.
/P

I assume this is only for the Exynos version? Or does it work for Snapdragon as well?

mistermidas said:
I assume this is only for the Exynos version? Or does it work for Snapdragon as well?
Click to expand...
Click to collapse
You have a working snapdragon root? How did you get past step #9 of launching stock recovery after you flashed magisk

rp4k said:
You have a working snapdragon root? How did you get past step #9 of launching stock recovery after you flashed magisk
Click to expand...
Click to collapse
Man... did you even read my comment???
I was asking if this would work for Snapdragon, not saying I got it to work. It doesn't mention if it's a method for both versions in the OP or not.

mistermidas said:
Man... did you even read my comment???
I was asking if this would work for Snapdragon, not saying I got it to work. It doesn't mention if it's a method for both versions in the OP or not.
Click to expand...
Click to collapse
Sorry I responded when I was half asleep. My fault.

I will try this out and post and update, i had no luck with previous twrp, always boot loops regardless of what i do.
My bootloader is unlocked but not grayed out. Can i still do it?

mercifool said:
I will try this out and post and update, i had no luck with previous twrp, always boot loops regardless of what i do.
My bootloader is unlocked but not grayed out. Can i still do it?
Click to expand...
Click to collapse
Yes, just do exactly all the steps and use the new files in the link and you will be fine.
//P

deleted

Carotix said:
hi ,
do you have the OEM switched to on?
if not , you need it ..... if you can't get it because you are waiting the 7 days , you can make this trick
open settings and set the date 8 days before ... then reboot
so you can enable OEM in developer settings
Click to expand...
Click to collapse
Hi there, are these instructions for Exynos only or can I apply it to Snapdragon as well, please advise. Thank!