Database Users

Massive WIFI problem after trying to update to Oreo

Long story short I wanted to update to oreo from the latest version of Oxygen OS so I downloaded the update through a VPN which caused my phone to bootloop. In the process of recovering everything, i had to format all data so I formatted everything and reinstalled a stable version of oxygen os from their site. Now all of a sudden I couldn't connect to wifi as it said it was disabled however I fixed this by defaulting my mac address but apparently that didn't work as it connected to the wifi but nothing actually loads or works. Much help would be appreciated!
Note : Wifi only connects if its set to static IP however when changed to DHCP it gets tuck on obtaining an IP adress.

Same problem... Please help us out, been stuck trying to figure this out for hours now with no success. Thanks

Same here I'm going to look to see if there's a way to reset DHCP then you've given me a clue.
Nope this doesn't seem to be the issue in my case the phone won't even associate with router according to the router.
---------- Post added at 07:29 PM ---------- Previous post was at 07:02 PM ----------
My logcat isn't giving me a lot of clues,
--- redacted ---
Click to expand...
Click to collapse

same problem, downgraded back to nougat and the problem still persists

So I've done some more ground work it appears TWRP can't properly upgrade the phone however the stock recovery can via an ADB sideload.
My suspicion is the DM-verity doesn't actually work right or that magicsk 14.6 is not compatible with our version oreo.
Unfortunately I rely on root for a few important functions so I'm not about to give that up unfortunately it seems the update does something that cause the wifi to stop working.
I'm looking into an update that was floating around during the oreo beta that allowed people to go from Oreo back to Nougat maybe there were some steps in there that fixed your wifi antennas so they weren't perminently broken and you can safely roll back I'm going to try flashing that next wish me luck.

Although I haven't properly solved this issue I decided to flash the no limits rom which is based on oxygen OS and I flashed the stable Oreo version which fixed the wifi problem that I was having, however when flashing this rom I did use the Blu spark TWRP instead of the original and I'm unsure if that made any difference whatsoever.

Ok so I managed to revert back to Nougat proper here's the procedure
1. Flash stock recovery. Stock recovery does apparently more than just flash the system partition during an ADB sideload
2. boot into stock recovery. Wipe everything System, Wipe Cache, Wipe Personal data
3. Enable ADB sideload
4. Flash OxygenOS OTA proper
5. Allow system to boot verify wireless functionality
6. Boot back into stock recovery
7. Flash the roll back build this will fix any wifi driver issues in a hidden partition I bet. It can be found on the oreo beta post here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003 or just download it direclty here [Here]
8. After the rollback build finishes booting verify wireless functionality (optional)
9. Flash back your recovery and it should all be working again.
I guess those of us that want a working root and descrypted data will have to wait for either a working dm-verity for oreo or an updated magicsk the current 14.6 doesn't seem to be all that reliable. And all this on christmas!

I had the same issue. Flashing the oreo OTA worked for me.
twrp-3.1.1-1-cheeseburger
download oreo from here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-5-0-android-8-0-t3724234

RIT35H said:
I had the same issue. Flashing the oreo OTA worked for me.
twrp-3.1.1-1-cheeseburger
download oreo from here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-5-0-android-8-0-t3724234
Click to expand...
Click to collapse
I have now flashed this using the blu spark twrp after getting rid of my custom rom and everything seems to work so thanks!
However I seem to be facing a Magisk issue now no matter what ROM I use when flashing magisk i boot into a black screen until i remove it using the uninstaller

Queried and resolved in below thread.
https://forum.xda-developers.com/oneplus-5/help/wifi-completely-broken-t3721004

vortex-5 said:
Ok so I managed to revert back to Nougat proper here's the procedure
1. Flash stock recovery. Stock recovery does apparently more than just flash the system partition during an ADB sideload
2. boot into stock recovery. Wipe everything System, Wipe Cache, Wipe Personal data
3. Enable ADB sideload
4. Flash OxygenOS OTA proper
5. Allow system to boot verify wireless functionality
6. Boot back into stock recovery
7. Flash the roll back build this will fix any wifi driver issues in a hidden partition I bet. It can be found on the oreo beta post here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003 or just download it direclty here [Here]
8. After the rollback build finishes booting verify wireless functionality (optional)
9. Flash back your recovery and it should all be working again.
I guess those of us that want a working root and descrypted data will have to wait for either a working dm-verity for oreo or an updated magicsk the current 14.6 doesn't seem to be all that reliable. And all this on christmas!
Click to expand...
Click to collapse
Thank you very much. Back on Nougat now without wifi issues!

It seems like it's probably magisk support since 14.6 current build doesn't work on nougat either.

How to flash 930U firmware to 930P with BL5/BL6

UPDATE:
Samsung is testing a new firmware for the unlocked S7 and will be a bootloader version 8
<latest>G930UUEU8CRJ2.DM/G930UOYM8CRJ2/G930UUEU8CRJ2</latest> Verizon
How to do this :
Step 1 : You need root your phone. Check the post HERE This works for Oreo And Nougat Roms
Step 2 : Use FlashFire to install custom binary from 930U firmware (tar have Recovery -Boot -System-Cached img). DOWNLOAD HERE (Extract tar file)
- Click the Red + button and choose 'Flash Firmware Package' and choose 'G930UUES4CRG3.tar' select all partitions
- Click on EverRoot, and disable/uncheck inject supersu option
- Click the Red + and choose 'Wipe' (Wipe data/Factory reset all your app)
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Ensure Mount /system read/write is CHECKED AND "Process Cache" DISABLED (cause bootloop after flash with flashfire)
- Press the big FLASH button.
After the flash it complete, you will have 930U Firmware run on 930P Bootloader v5/v6 with no root.
Enjoy pure Stock 930U Rom ​
On attached My phone run CRG3 latest U rom on 930P Bootloader. Rooted with custom kernel

When you give us the files and instruction how to flash?

tahasmarty said:
When you give us the files and instruction how to flash?
Click to expand...
Click to collapse
There was a thread posted a few weeks ago with the info. Results have been mixed in terms of network connection. The main thread linked to a site called gsmzambia . Will probably work unless you are on Sprint, but you will have a few errors and bugs.
Hopefully, he found something new out.

tahasmarty said:
When you give us the files and instruction how to flash?
Click to expand...
Click to collapse
File is now uploading .....
@lvpre
Bugs free :good:

binh24 said:
File is now uploading .....
@lvpre
Bugs free :good:
Click to expand...
Click to collapse
Will this also give you the weird submenus under settings: T Roaming; GiGa LTE? Under the GSMZambia version, I never could get service. Have you tried this with Sprint or another carrier?

lvpre said:
Will this also give you the weird submenus under settings: T Roaming; GiGa LTE? Under the GSMZambia version, I never could get service. Have you tried this with Sprint or another carrier?
Click to expand...
Click to collapse
Weird submenus show when rom has no CSC.
Try to flash my file !

binh24 said:
Weird submenus show when rom has no CSC.
Try to flash my file !
Click to expand...
Click to collapse
Did you take all the parts from the CRG3 firmware? cache.img is from CSC, correct? Do you basically take the stock firmware for the XAA variant?
Also, did you have to convert the files from img.ext4 to img files? What did you use for this? I've used sgs4toext4 to convert those files to a quasi img file to open in LinuxReader, but you are unable to edit them. When I downloaded the Oreo firmware the file structure was ext4. I can open normal img files in 7zip, but not img.ext4 files.
Thanks.

lvpre said:
Did you take all the parts from the CRG3 firmware? cache.img is from CSC, correct? Do you basically take the stock firmware for the XAA variant?
Also, did you have to convert the files from img.ext4 to img files? What did you use for this? I've used sgs4toext4 to convert those files to a quasi img file to open in LinuxReader, but you are unable to edit them. When I downloaded the Oreo firmware the file structure was ext4. I can open normal img files in 7zip, but not img.ext4 files.
Thanks.
Click to expand...
Click to collapse
Cache from CSC. All img.lz need to convert back to img for FlashFire can flash

binh24 said:
Cache from CSC. All img.lz need to convert back to img for FlashFire can flash
Click to expand...
Click to collapse
Cool. What/How did you use to convert the img file? Or do you have a link?

binh24 said:
File is now uploading .....
@lvpre
Bugs free :good:
Click to expand...
Click to collapse
After updating my phone is on bootloop and not even goto recovery i have done all the steps correctly root successfully then install U firmware successfully after that phone is on bootloop then i tired rooting again and flash the root boot file from here S7_Oreo_Su_Binary_Only_ADB_Root.zip then phone is boot normally but when it comes to setup screen phone reboots automatically what can i do now?

Can anyone confirm if SafetyNet passes with this method? I have a spare S7 on Sprint nougat v5 that I use for Pokemon Go and require SafetyNet to pass.

Sprint BLv5
Has anyone with BLv5 actually gotten this method to work?
I have tried this several times now. Followed GSMZambia directions making my own tar to flash and followed this thread. Both resulted in phone getting stuck in a boot loop, flashing the custom firmware lock screen then restarting.

driverdis said:
Can anyone confirm if SafetyNet passes with this method? I have a spare S7 on Sprint nougat v5 that I use for Pokemon Go and require SafetyNet to pass.
Click to expand...
Click to collapse
I am also interested about knox in this case.

You cannot update to Oreo if you are on BLv55. Installing Nougat this way worked while being on BLv5, however, this does NOT seem to work with Sprint even if you flash the cache.img file from the csc file.
It gets stuck on AutoPreconfig and makes you reboot as soon as you put the sim card in and then gives an error when on the sim card blue screen so it is never able to set up the services.
I tried disabling AutoPreconfig through adb and that does remove the popup message and allows me to search for networks under the network operator settings and Sprint does come up but it is never able to connect to the network.

Agree with all the above comments this method is not working properly... i am again on stock sprint v7 bootloader firmware

tahasmarty said:
Agree with all the above comments this method is not working properly... i am again on stock sprint v7 bootloader firmware
Click to expand...
Click to collapse
Aggiedude said:
You cannot update to Oreo if you are on BLv55. Installing Nougat this way worked while being on BLv5, however, this does NOT seem to work with Sprint even if you flash the cache.img file from the csc file.
It gets stuck on AutoPreconfig and makes you reboot as soon as you put the sim card in and then gives an error when on the sim card blue screen so it is never able to set up the services.
I tried disabling AutoPreconfig through adb and that does remove the popup message and allows me to search for networks under the network operator settings and Sprint does come up but it is never able to connect to the network.
Click to expand...
Click to collapse
This method probably works great if you have anything other than Sprint or Sprint MVNO, but something is conflicting like it does during a typical root of the G930P. Someone suggested to see if the phone was reporting an IMEI number. Since Sprint still uses CDMA, it doesn't really depend on the SIM for service. Maybe one idea is to flash an edited build prop in flashfire at the end of the 'install' when some changes like the old root method required. But then it may mess if/when you pop in another SIM card

I tried the method several times. But everytime flashfire finishes installing the rom, the phone reboots in a bootloop. I can't even get on recovery mode, only download mode. Why does it happen? I have a spint S7 G930P on Android Oreo 8.0, Rev0. 6 and baseband version G930PVPU6CRE7. Can anybody help me?

pikolush said:
I tried the method several times. But everytime flashfire finishes installing the rom, the phone reboots in a bootloop. I can't even get on recovery mode, only download mode. Why does it happen? I have a spint S7 G930P on Android Oreo 8.0, Rev0. 6 and baseband version G930PVPU6CRE7. Can anybody help me?
Click to expand...
Click to collapse
Yeah, this method has some issues and bugs. I did the nougat version of this. Android worked great, but it wouldn't connect to the Sprint network. What type of bootloop are you receiving? Some people have complained of a sim card provision one using Sprint

lvpre said:
Yeah, this method has some issues and bugs. I did the nougat version of this. Android worked great, but it wouldn't connect to the Sprint network. What type of bootloop are you receiving? Some people have complained of a sim card provision one using Sprint
Click to expand...
Click to collapse
Just after i flash the zip file with G930U firmware with flashfire, i have bootloops. I can't even get on recovery mode. Only download mode. I am overseas and i don't use sprint sim card on the phone.

I have a G930P with Binary 6, went to the entire process and succeeded to flash BL 4 Firmware U, even the Model of the phone changed to G930U in the settings menu but it didn't recognize my sim card, it said "No Sim Card" :v I tried killing Knox and sprint daemons with ADB shell but no success to get my sim cards to work, I'm outside US without access to a sprint sim card :/ ##3424# ##3666633# and *#0808# already tried once in U Firmware failing again... Is any one running smoth on this method on AT&T or Verizon?

[URGENT HELP] Cannot turn Wifi On

After i tried to restore my backup from TWRP can't open wifi. When i try to turn it on it turns immediately off by itself. What to do ?

Maybe your boot.img was modified and you need the stock one.

ccalixtro said:
Maybe your boot.img was modified and you need the stock one.
Click to expand...
Click to collapse
Well in fact is it a modified one since i'm rooted with magisk. But the problem is that i restored by boot.img with a TWRP backup that i made from december but since then i haven't updated with the jan OTA update... I downloaded the stock one from the official xiaomi server 10.0.0.2 update but can't boot into the stock one, the fastboot logo, when i trype fastboot devices it doesn't shows anymore as a connected device so i need to reboot into the bootloader.
Can a boot.img cause wifi issues ?

Custom Kernel killed my FP Sensor, Camera, and WiFi modem. Help!

Device: ZB602KL 4gb
I was using the latest Liquid Remix 10.0.6 with the stock darkonah kernel for a wee after having just updated from LR 10.0.5 and Singh 2.7. When I noticed he released a stable update for his kernel to 2.8 I downloaded it and flashed it as normal. Upon booting into LR, the lockscreen no longer responded to my fingerprint. It wasn't even turning the screen on. After inputting my password, I noticed that my wifi wouldn't turn on. And later when I tried the stock gcam, it kept crashing. Cam2API Probe is completely blank.
Things I've done to try and fix this:
1. Rebooted multiple times.
2. Someone suggested wiping /system and /vendor only and dirty flashing the rom. Did that, dirty flashed LR, openGApps(wasn't sure I needed to, did it anyway), and Magisk 19.
3. Clean flashed stock 340, decrypt and magisk19.
4. Flashed fw_only-X00T-WW-16.2017.1902.037.zip. I had previously flashed fwpie050.zip(the one from opendesktop) when updating LR before all this happened.
5. Fully wiped phone including internal storage and flashed the latest HavocOS which I am on right now as I've given up and just need it to work as a phone for the meantime.
Camera seems to be working again on Havoc, though. Fingerprint is still missing from Security settings and WiFi will not turn on.
Any help would be appreciated. Thanks!

I also got bootloop by using magisk 19.0,use magisk 17.1 or 18.1.

How did you clean flash stock 340 ? If it was through TWRP then try fastboot ROM

Tianhe said:
How did you clean flash stock 340 ? If it was through TWRP then try fastboot ROM
Click to expand...
Click to collapse
Yes, through twrp. What are the adb commands to do it through fastboot? I used Avinash's modified stock340 btw.
I think the modem firmware is corrupted somehow. I cannot receive or make calls but can get 4g data connection and SMS. My wifi mac address sometimes is "Uknown" or 02:00:00:00:00:00.

defurious said:
Yes, through twrp. What are the adb commands to do it through fastboot? I used Avinash's modified stock340 btw.
I think the modem firmware is corrupted somehow. I cannot receive or make calls but can get 4g data connection and SMS. My wifi mac address sometimes is "Uknown" or 02:00:00:00:00:00.
Click to expand...
Click to collapse
Flash fastboot stock rom it will fix the issue.
https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
Hit thanks if it helped

Flashing stock rom thru adb basically reverts your phone to factory state so everything should be fixed unless somehow your hardware is damaged

farhanshaikh671 said:
Flashing stock rom thru adb basically reverts your phone to factory state so everything should be fixed unless somehow your hardware is damaged
Click to expand...
Click to collapse
Yeah, i understand. I'm just a little confused because the steps in the linked post above are for 334. I don't know how to do it using 340. Should I just follow those steps then after relocking, manually update to 340, and then unlock bootloader again?
Is there any way to flash fastboot rom without relocking bootloader?
To me it seems that i'm having some problems with pie beta firmware. After flashing 339 and then LR 10.0.5 which is the last version before requiring pie beta firmware, everything is working normally again. But as soon as i try to update to 10.0.6 or latest Havoc with pie beta firmware, the wifi and fpsensor stop functioning. But the strange thing is, I was on LR 10.0.6 for a week before flashing Singh 2.8 kernel which then killed my hardware.
Now I'm wondering if I should just wait for official Pie release from Asus.

defurious said:
Yeah, i understand. I'm just a little confused because the steps in the linked post above are for 334. I don't know how to do it using 340. Should I just follow those steps then after relocking, manually update to 340, and then unlock bootloader again?
Is there any way to flash fastboot rom without relocking bootloader?
To me it seems that i'm having some problems with pie beta firmware. After flashing 339 and then LR 10.0.5 which is the last version before requiring pie beta firmware, everything is working normally again. But as soon as i try to update to 10.0.6 or latest Havoc with pie beta firmware, the wifi and fpsensor stop functioning. But the strange thing is, I was on LR 10.0.6 for a week before flashing Singh 2.8 kernel which then killed my hardware.
Now I'm wondering if I should just wait for official Pie release from Asus.
Click to expand...
Click to collapse
Just Flash Stock rom via fastboot to fix this issue. Dont bother about bootloader getting relocked.( U may unlock it ri8 after flashing)
And one more thing.
If u flash Decrypt.zip used for Stock Oreo roms on Stock Pie, you will loose wifi and fingerprint options.(I experimented this thoroughly)
So flash decrypt.zip for pie on Pie Stock(Beta or Stable).
Tested personally and worked fine.:good:
Hit thanks if it helped,

akhil850 said:
Just Flash Stock rom via fastboot to fix this issue. Dont bother about bootloader getting relocked.( U may unlock it ri8 after flashing)
And one more thing.
If u flash Decrypt.zip used for Stock Oreo roms on Stock Pie, you will loose wifi and fingerprint options.(I experimented this thoroughly)
So flash decrypt.zip for pie on Pie Stock(Beta or Stable).
Tested personally and worked fine.:good:
Hit thanks if it helped,
Click to expand...
Click to collapse
This must be the problem then because I didn't know there was a decrypt for pie beta and i usually do flash decrypt coz i have a phobia that my internal data will get encrypted with no password to recover. ?
Can you provide a link for pie beta decrypt please? I can't find it here in xda. Thanks

defurious said:
This must be the problem then because I didn't know there was a decrypt for pie beta and i usually do flash decrypt coz i have a phobia that my internal data will get encrypted with no password to recover. ?
Can you provide a link for pie beta decrypt please? I can't find it here in xda. Thanks
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/as...w-to/decrypt-zip-asus-stock-pie-roms-t3923265
Hit thanks if i helped.

[Guide] Convert to Global [WIP]

*** Use this at your very own risk.
***Backup your persist.img. There is a guide to fix it if needed.
*** Backup your working modem. Sometimes it is as simple as restoring it if you lose signal.
*** When flashing, you must understand the difference between fastboot and fastbootd to avoid flashing errors.
*** Backup your files in a safe place.
*** Some users are reporting that the whole thing is not working and going on a blame streak. So if you're not quite ready, please don't attempt this.
Basic Instructions: "I will test again since some users are losing signal after flashing". There is a debate whether msm and update the tmobile firmware, or flash the global. Again this is a WIP.
MSM. Here is the thread.
Unlock bootloader or re-unlock bootloader ... Enable OEM Unlock in developer options. flash token.
Fastboot
Code:
fastboot flash cust-unlock <unlock_token.bin>
Code:
fastboot oem unlock
and now your bootloader is unlocked.
Here is the t-mobile article for the 6t. same instructions for the 8 if you're new to this.
NEXT:
Link to fastboot thread
https://forum.xda-developers.com/oneplus-8/how-to/rom-stock-fastboot-roms-oneplus-8-t4084629
Download the global fastboot rom from here.
Unzip and flash all.
Link to twrp thread:
https://forum.xda-developers.com/oneplus-8/development/recovery-unofficial-twrp-oneplus-8-t4101315
If you want to root.
Boot into twrp or flash the twrp installer. TWRP 3.3.1-10 Test by mauronofrio and or TWRP 3.3.1-10 Test Installer by mauronofrio "newer ones may work"
After booting, you can flash magisk with-in twrp and you're rooted.
I have used oxygen updater to update the firmware while rooted. After the local install, open magisk and flash on the inactive slot.
---------------
If you ever want to revert, use the msm tool. Here is the thread.
https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043
---------
Old information from the old thread is below, if you want to use it only for reference or for backing up the FP persist
---------------
Old Instructions
Here we go .....
This is fairly new and hasn't been tested so, proceed with caution. There are more knowledgable people here. This was just tested quick and it worked.
Requirements
1-Be on T-mobile firmware and update to the latest version. If you are bootloader unlocked, you mean not be able to take OTA's and you may need to reflash with MSM and update, then unlock the bootloader again. Thread Thanks @Some_Random_Username
2 - Unlock your bootloader.
3- --! IMPORTANT: Make a TWRP backup of your MODEM because we'll restore that later, why? because t-mobile sim doesn't work on the Global Modem. You can also back everything up in TWRP just in case.
If you have OTG, make the backup there so it is safe. You can restore the modem through TWRP with the OTG.
4-Backup your persist. Otherwise you may lose the fingerprint.
You'll need root.
Code:
adb shell
HTML:
su
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Then
Code:
adb pull sdcard/persist.img
Then copy it from from Sdcard to a safe place
*** You may lose signal again if you update the global version. It is a WIP but keep your modem backed up!
With all the above:
It is simple. Download the global firmware and flash it through fastboot. Here is the thread
.. I tested with "10.5.5-GLOBAL-OnePlus8Oxygen_15.O.14" Thanks @mauronofrio
Reboot to fastboot
Unzip and flash-all
It will reboot to the global firmware. "Now you won't get cellphone signal"
Skip the setup and reboot to fastboot.
reboot to twrp, do not flash it.
Code:
fastboot boot twrp.img
link to twrp thread. . I used TWRP 3.3.1-2 Test by @mauronofrio
plug in the OTG or locate the backup and Restore the Modem" to get signal
Reboot and you'll have signal.
To root. you can flash the patched boot located in the sourceforge folder " Patched-Stock-Boot" on this thread
Code:
fastboot flash boot filename.img
You can also flash magisk in twrp. I prefer the patched boot.
Bonus: I am running the Nolimit magisk rom Thanks @xXx
https://forum.xda-developers.com/on...gisk-rom-xxx-nolimits-11-0-speed-ram-t4088609
Thanks @Some_Ghost for testing.

B-E-A-UTIFUL!
I'll wait to see others' results before I brick my phone.

rjp0615 said:
B-E-A-UTIFUL!
I'll wait to see others' results before I brick my phone.
Click to expand...
Click to collapse
It works no bricking. If something happened you can go back with MSM.

matteosaeed said:
Here we go .....
This is fairly new and hasn't been tested so, proceed with caution. There are more knowledgable people here. This was just tested quick and it worked.
Requirements
1-Be on T-mobile firmware and update to the latest version. If you are bootloader unlocked, you mean not be able to take OTA's and you may need to reflash with MSM and update, then unlock the bootloader again. Thread Thanks @Some_Random_Username
2 - Unlock your bootloader.
3- --! IMPORTANT: Make a TWRP backup of your MODEM because we'll restore that later, why? because t-mobile sim doesn't work on the Global Modem. You can also back everything up in TWRP just in case.
If you have OTG, make the backup there so it is safe. You can restore the modem through TWRP with the OTG.
4-Backup your persist. Otherwise you may lose the fingerprint.
*** You may lose signal again if you update the global version. It is a WIP but keep your modem backed up!
With all the above:
It is simple. Download the global firmware and flash it through fastboot. Here is the thread
.. I tested with "10.5.5-GLOBAL-OnePlus8Oxygen_15.O.14" Thanks @mauronofrio
Reboot to fastboot
Unzip and flash-all
It will reboot to the global firmware. "Now you won't get cellphone signal"
Skip the setup and reboot to fastboot.
reboot to twrp, do not flash it.
Code:
fastboot boot twrp.img
link to twrp thread. . I used TWRP 3.3.1-2 Test by @mauronofrio
plug in the OTG or locate the backup and Restore the Modem" to get signal
Reboot and you'll have signal.
To root. you can flash the patched boot located in the sourceforge folder " Patched-Stock-Boot" on this thread
Code:
fastboot flash boot filename.img
You can also flash magisk in twrp. I prefer the patched boot.
Bonus: I am running the Nolimit magisk rom Thanks @xXx
https://forum.xda-developers.com/on...gisk-rom-xxx-nolimits-11-0-speed-ram-t4088609
Thanks @Some_Ghost for testing.
Click to expand...
Click to collapse
Am I understanding correctly, we will have to re-flash the modem after EVERY update?

rjp0615 said:
Am I understanding correctly, we will have to re-flash the modem after EVERY update?
Click to expand...
Click to collapse
For the global, we don't know until we get it, but @Some_Ghost checked with the euro and signal stays, so you can do the euro version instead of the global and still keep the the signal without reflashing your modem.

Does anybody have the modem backup I lost mine and can't find fastboot for tmobile

The EU modem dont fix it I just need tmobile modem if anyone can can someone give be the modem either tarp backup or .img file so I can use data

very easy fix for modem get the ota after you flash global you do ota and modem works fastboot wont flash modem right

delete
---------- Post added at 02:38 AM ---------- Previous post was at 02:32 AM ----------
ecompton59 said:
The EU modem dont fix it I just need tmobile modem if anyone can can someone give be the modem either tarp backup or .img file so I can use data
Click to expand...
Click to collapse
If you flash your modem backup with Euro firm it sticks throughout updates so far... It didn't work for me on global. You still need to restore your modem backup on either firmwares. Global so far modem doesn't stick after updates, euro so far, it stays after updates.

Some_Ghost said:
delete
---------- Post added at 02:38 AM ---------- Previous post was at 02:32 AM ----------
If you flash your modem backup with Euro firm it sticks throughout updates so far... It didn't work for me on global. You still need to restore your modem backup on either firmwares. Global so far modem doesn't stick after updates, euro so far, it stays after updates.
Click to expand...
Click to collapse
I fixed it with ota if you flash global do the enable and and dev settings I waited to install magisk. Ayer first boot put ota for global and it works because ota has modem in it and fastboot can't flash modem yet with bat file but I have no issues I have global modem and global ROM and from here on ota will work no need for modem

not really converting to Global then? this is just so you can use dev ROM, but since DEV rom hasnt come about there really is no reason to do this.

Vio281 said:
not really converting to Global then? this is just so you can use dev ROM, but since DEV rom hasnt come about there really is no reason to do this.
Click to expand...
Click to collapse
What? He used global ROM. Not a DEV ROM.

ecompton59 said:
I fixed it with ota if you flash global do the enable and and dev settings I waited to install magisk. Ayer first boot put ota for global and it works because ota has modem in it and fastboot can't flash modem yet with bat file but I have no issues I have global modem and global ROM and from here on ota will work no need for modem
Click to expand...
Click to collapse
I will try this thanks ??

Does the Global ROM share the same 5G compatibility introduced in the new TMO ROM?

joemossjr said:
What? He used global ROM. Not a DEV ROM.
Click to expand...
Click to collapse
Thats what I'm saying, this is to flash rom, it not necessarily converting the phone to a global phone since it still need Tmobile Modem bin file in order to be function as a phone. If you take the phone outside the U.S it questionable if it works, that is why I say this is only for Dev Rom and in this case stock global rom but it is not a global phone.

@joemossjr
Vio281 said:
Thats what I'm saying, this is to flash rom, it not necessarily converting the phone to a global phone since it still need Tmobile Modem bin file in order to be function as a phone. If you take the phone outside the U.S it questionable if it works, that is why I say this is only for Dev Rom and in this case stock global rom but it is not a global phone.
Click to expand...
Click to collapse
Well check @ecompton59 's response. He was able to get things working.
The modem does work, just there is an issue with the fastboot flashing the modems. The TWRP restore of the modem is to get cell signal right away.
Here is what I did:
After I did what is in the first post in the thread:
I used oxygen updater to download the EU update and flashed it via "Local Upgrade" @Some_Ghost tested that as well.
There is signal. I believe that it may have flashed the modem "maybe", unlike fastboot.
While I was on the EU version, I downloaded the update for the global, and did a "Local Upgrade" again, and got signal.
I did all of this with Magisk being installed and after each "local upgrade, before reboot" I install Magisk on the "inactive slot, ota".
Technically speaking and don't quote me 100%, the first flash to the global is what gives issues with the sim, but that's the way to get the ability to do "local upgrade" because it is disabled on the t-mobile firmware.
Theoretically and I haven't tested.
Unlock bootloader >> Flash global "won't flash everything properly" = no signal
Global to another global or EU update >> will flash the modem >> signal will work "as it will properly flash everything"

matteosaeed said:
@joemossjr
Well check @ecompton59 's response. He was able to get things working.
The modem does work, just there is an issue with the fastboot flashing the modems. The TWRP restore of the modem is to get cell signal right away.
Here is what I did:
After I did what is in the first post in the thread:
I used oxygen updater to download the EU update and flashed it via "Local Upgrade" @Some_Ghost tested that as well.
There is signal. I believe that it may have flashed the modem "maybe", unlike fastboot.
While I was on the EU version, I downloaded the update for the global, and did a "Local Upgrade" again, and got signal.
I did all of this with Magisk being installed and after each "local upgrade, before reboot" I install Magisk on the "inactive slot, ota".
Technically speaking and don't quote me 100%, the first flash to the global is what gives issues with the sim, but that's the way to get the ability to do "local upgrade" because it is disabled on the t-mobile firmware.
Theoretically and I haven't tested.
Unlock bootloader >> Flash global "won't flash everything properly" = no signal
Global to another global or EU update >> will flash the modem >> signal will work "as it will properly flash everything"
Click to expand...
Click to collapse
again, this does not make it a global sim unlock phone, you are flashing a previous Tmobile Modem on top of a Global rom.

Vio281 said:
again, this does not make it a global sim unlock phone, you are flashing a previous Tmobile Modem on top of a Global rom.
Click to expand...
Click to collapse
It at least we can run different firmwares on T-Mobile. You could try the global msm on T-Mobile and report back. As being sim unlocked depends on the bands enabled in other countries but should work with any sim.

matteosaeed said:
It at least we can run different firmwares on T-Mobile. You could try the global msm on T-Mobile and report back. As being sim unlocked depends on the bands enabled in other countries but should work with any sim.
Click to expand...
Click to collapse
is there different functionality between the tmobile modem and global modem firmware? I flashed the global rom and am using that with tmobile modem flashed through twrp. I haven't done a local update yet to get the global modem. if I do, what is the difference running that vs the tmobile modem? im in seattle using tmobile anyway.... would I see a difference in anything? speed? I had updated to the tmobile ota right before I flashed, they supposedly updated something with the modem in that update. im just wondering if there is a benefit to using the global modem or not. I definitely see the benefit in using he global rom though....lol

bluemoel said:
is there different functionality between the tmobile modem and global modem firmware? I flashed the global rom and am using that with tmobile modem flashed through twrp. I haven't done a local update yet to get the global modem. if I do, what is the difference running that vs the tmobile modem? im in seattle using tmobile anyway.... would I see a difference in anything? speed? I had updated to the tmobile ota right before I flashed, they supposedly updated something with the modem in that update. im just wondering if there is a benefit to using the global modem or not. I definitely see the benefit in using he global rom though....lol
Click to expand...
Click to collapse
you'll be fine, my signal hasn't changed since flashing it remained the same as far as I can tell
---------- Post added at 12:34 PM ---------- Previous post was at 12:30 PM ----------
Vio281 said:
again, this does not make it a global sim unlock phone, you are flashing a previous Tmobile Modem on top of a Global rom.
Click to expand...
Click to collapse
Be happy that people actually take the time to experiment and work on things like this for the community so we can root and run different firmwares, kernels, and recoveries etc. At the least we aren't stuck on TMO firmware with lack of updates and missing features and as far as we can tell everything is working and odds are you aren't going to be using a T-Mobile SIM when going out of country anyway. Any issues will be ironed out when we cross that path I am sure ??