It took a few days, like many other colleagues in the telegram group https://t.me/lgg7thinqmain in English and https://t.me/lg_g7esp in Spanish. Many of us tried to run android 11 on our LG G7 710ULM, but we always lost the 4G + / LTE + signal. So after several attempts we found a way to run android 11 based roms without losing the 4G + / LTE + signal.
It will not be necessary to wait for Verizon to release android 10 to be able to run custom roms based on android 11, at least, without being able to lose the 4G + / LTE + signal.
Note: This method have been tested only on LG G7 ULM or PM converted to ULM. IF YOU TRY TO EXECUTE THESE METHODS ON OTHER AMERICAN MODELS, IT WILL BE AT YOUR OWN RESPONSIBILITY, ALTHOUGH IT MAY WORK.
I'm not a developer or anything like that. I only share one method to be able to maintain the 4G + / LTE + signal after flashing a custom rom based on Android 11. Any unforeseen event, WILL BE YOUR RESPONSIBILITY.
After so much testing, it has been concluded that the loss of the 4G + / LTE + signal is due to the type of Gapps we use. So in this case, the ones that were perfect to maintain the signal 4G+/ LTE+ were the NikGAPPS
Before starting the process, you should be clear about the following:
1 - You must have the BOOTLOADER UNLOCKED: -------> https://forum.xda-developers.com/t/guide-guide-to-unlock-bootloader-for-every-g7-thinq-except-g710tm-with-photos.4168771/
2 - You must be running ANDROID 10 if you want to have a custom ROM based on ANDROID 11.
3- You must write down, copy or take screenshots of your APN CONFIGURATION that you have in STOCK ANDROID 10.
4 - The ROM to be installed must not include Gapps or previously installed Google services.
Necessary files (In case you do not have them or you are not in the LG G7 development group):
Android 11 based ROM lists:
1 - DotOS ---> DIRECT DOWNLOAD
2 - Paranoid Android 11 ---> DIRECT DOWNLOAD
3 - Fluid 1.2 ---> DIRECT DOWNLOAD
4 - Nusantara 2.5 --->DIRECT DOWNLOAD
OrangeFox.img Boot_a and Boot_B -------------> DIRECTO DOWNLOAD
OrangeFox Recovery Zip V1.2 ------------- > DIRECT DOWNLOAD
NikGAPPS: --------------------> DIRECT DOWNLOAD
Method number 1:
1 -First load the OrangeFox.img by QFIL, you should mount it in Boot_a and Boot_b.
2 -Enter into recovery mode using the key combination. Once inside OrangeFox, flash the ANDROID 11 BASED ROM YOU WANT TO INSTALL. (That's right, without doing the WIPES) (Flash the rom.zip in dirty)
3 -Now flash the OrangeFox-R11.0_1.2-Stable-judyln .. After it is flashed, it will reboot automatically.
4 - If you want to have Magisk continue with this step, otherwise you can skip it and go to the next step.
4 -Since I started the OrangeFox.zip that you flashed earlier, now it flashes the NikGAPPS and Magisk. (In this first point we will flash the NikGapps so that Magisk is not deleted when starting the ROM)
5- Now REBOOT SYSTEM and wait for the rom to start. As you can see, you do not have the NikGapps, only Magisk remained (In case you do have Magisk and the NikGAPPS "CONGRATULATIONS") * We continue ...
6 - Start the rom and you do not have the 4G + / LTE + signal. Now we are going to configuration of Mobile Networks and we are going to CONFIGURE THE APN, just placing the configuration that we had in the STOCK ROM or any other where you had the 4G + / LTE + signal
7- Once the APN is configured, reboot in recovery mode.
8 - Now flash the rom you installed again, on top of the one you already had.
9 - Now flash the OrangeFox-R11.0_1.2-Stable-judyln one more time.
10 - Finally flash the NikGapps and REBOOT SYSTEMA And Congratulations! With this you will not lose the 4G + / LTE + signal.
11 - In case step number 2 does not work for you, you can perform the Wipes, as follows: Wipe System ----> Wipe Cache ---> Wipe Data. ( NOW flash the rom from 0 and continue with the other steps.
12 - If in step 3 you stuck in the logo after flashing the recovery, do it again in step number 1.
Evolution x already have pre installed gapps. So, does it mean that it is okay to flash nikgapps on top of the pre installed gapps?
mizan_sam said:
Evolution x already have pre installed gapps. So, does it mean that it is okay to flash nikgapps on top of the pre installed gapps?
Click to expand...
Click to collapse
You could just try it, along with the rom, to replace the applications that already come in Evolution. I have edited the thread and removed Evo from the list, I had forgotten that it has Gapps included, thank you very much for the clarification.
It will not be necessary to wait for Verizon to release android 10 to be able to run custom roms based on android 11, at least, without being able to lose the 4G + / LTE + signal.
Click to expand...
Click to collapse
how we can install on verizon model because if i install android 10 of any other model it's lose the signal.
What does ULM have to do with Verizon? Pertaining to the original post? ULM is the Unlocked model, not tied to any carrier. LTE will work as long as you Crossflash to AWM use the correct APN settings and make sure All of your phone radio information is correct under dialer *#*#4636#*#*, because AWM is also unlocked firmware, just made for a different region...kind of like how BrightPoint, Google Fi, USA firmware is all ULM just with minor differences which are as simple as certain apps included in all of the firmware, which are enabled based on which SIM card is inserted. When you mentioned not having to wait for Verizon to release Android 10 was that just a typo? I think that's what this confusing me. Did you mean to say "Wait for LG" ?
Also, if you are on ULM20E update to ULM20F before crossflashing to AMW, and cross flash to AMW30d, rather than B
.
Hi I'm running a ULM device under the 30d AWM firmware. My problem is that i can't turn Wifi or Hotspot on.
Do you think the this Gapps can fix it too?!
Edit: Doesn't work!
Yeedatoy said:
What does ULM have to do with Verizon? Pertaining to the original post? ULM is the Unlocked model, not tied to any carrier. LTE will work as long as you Crossflash to AWM use the correct APN settings and make sure All of your phone radio information is correct under dialer *#*#4636#*#*, because AWM is also unlocked firmware, just made for a different region...kind of like how BrightPoint, Google Fi, USA firmware is all ULM just with minor differences which are as simple as certain apps included in all of the firmware, which are enabled based on which SIM card is inserted. When you mentioned not having to wait for Verizon to release Android 10 was that just a typo? I think that's what this confusing me. Did you mean to say "Wait for LG" ?
Click to expand...
Click to collapse
I mean that many people who have the version of VERIZON said that they had to wait for it to launch android 10, to be able to run custom roms based on android 11 or simply be updated, that's why the tutorial, because VERIZON users can make a cross flash to ULM, do the process indicated before and thus not lose the LTE +, because the roms based on android 11, for the AMERICAN models, lose the LTE +
kipinsider said:
Hi I'm running a ULM device under the 30d AWM firmware. My problem is that i can't turn Wifi or Hotspot on.
Do you think the this Gapps can fix it too?!
Edit: Doesn't work!
Click to expand...
Click to collapse
I have bitten some Gapps that allow to have LTE +
kipinsider said:
Hi I'm running a ULM device under the 30d AWM firmware. My problem is that i can't turn Wifi or Hotspot on.
Do you think the this Gapps can fix it too?!
Edit: Doesn't work!
Click to expand...
Click to collapse
Which custom rom are you using?
carlkevin11 said:
Which custom rom are you using?
Click to expand...
Click to collapse
I'm using DotOS.
But I tried with others too... Didn't work
Yeriorlando said:
I have bitten some Gapps that allow to have LTE +
View attachment 5261973
Click to expand...
Click to collapse
I don't have LTE PROBLEMS. But wifi ones
I unlocked bootloader and crossflashed my ULM to awm30d.... I had no service at all. I set network and configured apn .... nomatter what I tried I have no service. I tried flashing 4-5 other firmwares.... No service with any of them. I flashed back to stock and still no service!
I put the sim card in an old phone and service works fine. I dont know what happened.
I would like to flash to dotos and try a different sim/carrier..... Should i use nikgapps?
hi, i follow the steps and when i boot the rom i just get a black screen, if i keep power button pressed it show power menu but everything else is black
Related
This is a patch to fully enable the GSM on CDMA Global phones.
The Global Phones are phones with CDMA and GSM modems but that are usually configured to primarly work on CDMA network and at least to be able to call on GSM network.
The patch is working on every Stock Rom, on every AOSP Rom and on every Android version.
If you are successfully using this patch please comment the thread with your phone model.
This patch will enable:
- GSM/UMTS -> [GSM auto (PRL)] in Testing menù
- SMS
- MMS
- 3G Data
- USSD Code
- Call Forwarding
- Testing menù to manage the baseband accessible dialing the code *#*#4636#*#* (locked on Verizon Phones)
How to install:
- Copy the .zip file to the external memory or memory card
- Reboot your phone and enter on your custom recovery
- From the Install menu select the .zip file and instal withotut signature verification on your Rom
Risk of briking:
- no one: during installation the installer checks everything is ok and stop installation in case of problem; in case of problems after installation the old settings can be restored by simply installing the patch a second time. In this way you can test the gsm settings without any risk.
Advice post-installation:
- If the patch has not been installed on a clean system then you have to do a factory reset
- On the AOSP Roms the Patch is persistent, when you will update your rom you do not have to reinstall the patch
- *#*#4636#*#* -> Phone info -> Set prefered network type -> GSM auto (PRL)
How to uninstall:
- To uninstall the patch you have to reinstall it a second time from the custom recovery
The patch should work on every CDMA Global Phone.
The patch should work on every Rom.
Download the patch here
If someone successfully use this patch on some other model please leave a comment in this page, so I will be able to update the above list.
If someone has edited this patch to support some other phone please inform me so as not to waste information and in this way I can update the patch.
Any help is precious.
HOW TO POST REQUEST FOR HELP:
You have to entirely read this thread, I do NOT answer redundant question.
If you want to know if the patch is compatible with a phone then you have to attach the /system/build.prop in your post in this thread because i don't know all phones. (You can also send me the build.prop as attachment via the contact section of my site.)
If you installed the patch and there are problems you have to attach (and do not post) your /system/build.prop and your /system/build.prop.bak.
I do not answer to requests for help in private, I have neither the time nor the interest in doing so.
Any doubts, questions or requests must be posted in this thread in order to answer a single time and help everyone.
XDA:DevDB Information
Patch CDMA to GSM for Android Global Phones, Tool/Utility for the Android General
Contributors
Mentor.37
Version Information
Status: Stable
Current Stable Version: 4.2.7
Stable Release Date: 2016-04-25
Created 2014-12-04
Last Updated 2016-04-25
The patch has been updated.
The patch has been update.
Everyone can help me to extend support for more phones.
Thanks.
Patch updated for better GSM support.
works flawless on my Razr xt912 in Pakistan using Gsm network.
Thanks a lot man.:good:
Available a new update to solve problems with apns on 4.3.x roms.
It works on my Droid razr Maxx xt912 with CM10.2-20131020-NIGHTLY-spyder ROM, my phone is using GSM carrier
New version working well on Vodafone Ireland with cyanogenmod 10.1.3 on XT912.
This version also leaves the ROM version intact - older version for 10.1.2 seemed to update the string.
The version that changed the string was only for the xt894 with cm 10.1.2, that was the first version.
Works great on my XT912 with MIUI v5. Thanks.
Mentor.37 said:
This is a patch to fully enable GSM on every Stock Rom, on every AOSP Rom and on every Android version.
This in not for US users, in US the GSM is locked in RIL.
Release 1.6 - 20/10/2013
Click to expand...
Click to collapse
I may have misinterpreted the topic I guess, but did install this while I was overseas with my Verizon phone, everything was fine but now it seems as I am unable to find 3G network back in the US. I have changed the specs from GMS/CDMA , etc on the settings but no signal of 3G/LTE.
Anyone has had this issue before? Any way to turn it back to normal so that I can get data here in the US?
blustosa said:
I may have misinterpreted the topic I guess, but did install this while I was overseas with my Verizon phone, everything was fine but now it seems as I am unable to find 3G network back in the US. I have changed the specs from GMS/CDMA , etc on the settings but no signal of 3G/LTE.
Anyone has had this issue before? Any way to turn it back to normal so that I can get data here in the US?
Click to expand...
Click to collapse
In US you can not use the GSM on many Verizon phones, you have to use the CDMA and you have to restore build.props and apns list.
The patch has been successfully tested on droid bionic xt875 in and outside the US and on droid 3 xt862.
Mentor.37 said:
The patch has been successfully tested on droid bionic xt875 in and outside the US and on droid 3 xt862.
Click to expand...
Click to collapse
Mentor.37 said:
I need your build.prop.
Click to expand...
Click to collapse
Mentor I have a question.
I flashed on XT912-Spyder CM 10.1.3 but even before I did flash I would have no service at all , I have Euorpean sim card which has active roaming.
When I put it into iPhone 4S it shows T-Mobile USA but in settings T-Mobile.Poland settings so it roams, it gets signal,receivies texts.
IN XT912 it only shows phone number in settings that is all , i flashed your patch.. I will do it again maybe it will help I don't know.
Can you help me? if I get sim to work I will have my buddy replace screen,battery everything and put this phone into use for someone.
You could try installing the patch on clean system before first boot without restore any backup.
Let's me know.
Mentor.37 said:
You could try installing the patch on clean system before first boot without restore any backup.
Let's me know.
Click to expand...
Click to collapse
EDIT:
Same thing I just did what you told me it instantly showed the European phone number Poland area code +48.
Signal Strength : 0 dBm 99asu
I can't understand how when I put it in Verizon 4S which was Unlocked by VZW it shows signal,receives texts etc.. the droid razr after JB update was suppsed to be unlocked for European use for example.
It even synced local time in Poland which is +6 hours! it seems to pull up number and time but no signal
Is there anything else I can try?
In your recovery: factory reset, wipes, install patch and then reboot phone.
Mentor.37 said:
In your recovery: factory reset, wipes, install patch and then reboot phone.
Click to expand...
Click to collapse
Yep did that and still no ago same thing.
Before I got the phone (Got it for free)
when I first put AT&T simcard it showed me roaming triangle for few seconds ever since that time the signal just does not work.. at all.
The xt 912 is GSM locked in the US and could be locked for AT&T sim outside US too, you could try with another sim.
Mentor.37 said:
The xt 912 is GSM locked in the US and could be locked for AT&T sim outside US too, you could try with another sim.
Click to expand...
Click to collapse
Well yes I know so why when I put in T-Mobile Poland sim card which roams on T-Mobile USA it shows nothing but only phone number? it's weird.
Works fine in 4S unlocked by Verizon.
Here is the link to the tmobile original thread
[ODIN] Stock Nougat Firmware [SM-G935T] S7 Edge
Instuctions provided by jrkruse (original post)
1. You need to be on Verizon Beta Nougat 2
2. In developer options turn on OEM unlock
3. Reboot to download mode
4. Load the files you downloaded in the corresponding slots in odin BL,AP CP, CSC the files are labeled this way
you dont use the G935TUVU4BQB1_Boot_Recovery_Image.tar.md5 until later
5. Install with odin the phone will reboot to recovery to finish the csc install
6. If the csc install in recovery fails reboot to bootloader in stock recovery
7. In odin reflash the CSC file in the CSC slot in odin. The phone will reboot to recovery again and install the csc files
8. Once the phone is done installing and wiping in recovery try and catch the phone as it reboots and reboot back to
download mode (PWR+Home+Vol Down )
9. Use odin Install G935TUVU4BQB1_Boot_Recovery_Image.tar.md5 in the AP slot
10. Let phone reboot and go through setup
11. During Setup you may have trouble typing info in the setup boxes the keyboard has some bugs in setup. I recommend skipping
adding any accounts and do it after your through setup. Or use the alternative method to find your google account
12. Once through setup download 4G LTE Switch and use to Change Network to LTE/CDMA auto (PRL)
13. I recommend downloading Package Disabler Pro (It Works now) and disable all Tmobile Apps
I found samsung pay wasnt working I found that the tmb bootloaders and persist.img needed to also be flashed I made a new odin flashable package and install instructions. All seems to work now except of course volte and wifi calling.
Explanation why you need to be on nougat beta 2
Download:
TMOBILE_NOUGAT_VZW.ZIP
ODIN v3.12.3.zip
Possible Issues and solutions :
Q: after flashing the bootloaders and persist.img, it broke all data and calls and texts again.
A: they need to be all flashed at same time. Maybe Wipe data and it might work
Q: The Google "email or phone" text input box still only accepts one letter and any extra letters overwrite the previous letter typed.
A: The samsung keyboard will work fine if you just goto settings on the keyboard to language and types and change to US english.
Q: So the question is..... this worth flashing or wait for vzw?
A: Other than no volte this definitely the best running Rom so far. It is much better than beta
Q: 13. I recommend downloading Package Disabler Pro (It Works now) and disable all Tmobile Apps
Care to share your list?
A: List of Tmo apps to disable
Q: Except MMS isn't working, for me anyways. VoLTE isn`t working.
A: I got volte working and video calling maybe this will help mms for you
Download App shortcut maker from playstore
Select all activities find IMS Settings and create shortcut
Open the ims settings from the created shortcut
Choose Ims service switch
Click on MMTEL switch
Click on RCS switch
Under MMTEL section I enabled all the options
Q: Cant get this thing to flash CSC...just keep getting the dm-verity error 0x02.
A: 1:Flash all 4 files in zip.
2:let reboot and see if you get dm verity error.
3:if you get the error than reboot to bootloader and reflash all 4 again.
4:after it reboots again it will say error.
5:reboot to bootloader and flash the csc again.
Q: in 4g lte switch, i dont see the option for lte/cdma auto. could this stuff be because csc didnt flash correctly?
A: if you have the verizon data icons you know the 4g lte then it flashed correctly. If you see data icons that ate not verizon then it didnt flash correctly.
When every one is starting over are you flashing a pit file when going pack to ph1. If not you need too.
P.S. All credits goes to jrkruze. :good:
You mentioned to install Nougat beta first before installing t mobile firmware. Is that necessary? Also, any link for Verizon apn?
Sent from my SM-G935V using Tapatalk
junear said:
You mentioned to install Nougat beta first before installing t mobile firmware. Is that necessary? Also, any link for Verizon apn?
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Look at you apn settings and just copy it. I didn't mention about to install nougat beta, I mentioned that it was installed successfully on nougat beta and that you must be on latest bootloader.
Okay so I have T-Mobile Nougat installed on my device, and I've changed my VPN over to VZWINTERNET, and I can't seem to get anything working (calls or data).
I'll continue to toy around with things though.
FoxyDrew said:
Okay so I have T-Mobile Nougat installed on my device, and I've changed my VPN over to VZWINTERNET, and I can't seem to get anything working (calls or data).
I'll continue to toy around with things though.
Click to expand...
Click to collapse
Same here
is there maybe a need to change to verizon csc?
j3ffm1ll said:
is there maybe a need to change to verizon csc?
Click to expand...
Click to collapse
are you meaning swap the pi3 csc to odin vice the csc that came with the firmware. I guess we can try that. worst thing no load, flash back stock.
justinsch03 said:
are you meaning swap the pi3 csc to odin vice the csc that came with the firmware. I guess we can try that. worst thing no load, flash back stock.
Click to expand...
Click to collapse
just a thought I would try it but I am at work and have to have use of my phone while I am here lol
FoxyDrew, radelon from what firmware did you flashed ?
spiderkr said:
FoxyDrew, radelon from what firmware did you flashed ?
Click to expand...
Click to collapse
The T-Mo one you posted. Odin with ap,bl,cp and csc selected.
After toying with tons of things on the Tmo firmware, I tried booting into Odin, and flashing the Verizon pi3 CSC. That gave me a bootloop. I then tried reflashing the entire Tmo Nougat with Odin, but replacing the CSC again with Verizons, same bootloop. So now my phone is being flashed back to the trusty U MM.
I can only assume now that running the Tmo firmware on VZW will require root to make CSC edits. But Verizon will release our own Nougat before we get root.
Now I guess it's just a race between Verizon releasing 7.0, and the G935U getting it.
$50 on Verizon.
Edit: After flashing the G935U firmware again, after the first boot I was greeted with a message saying "your device must update to use new features from your SIM card." And I booted to a weird all blue screen with a big SIM card on it. I've never seen anything like that. I'm not sure if the Tmo firmware messed with stuff, so I'm going to fully flash the G935V firmware, THEN reflash the G935U firmware, just in case the G935T firmware messed something up.
they also did something to disable all package disabler apps even if you go back to MM they dont work. They screwed us goood on this
so @spiderkr were you able to get it working or just going off of other reports?
radelon said:
The T-Mo one you posted. Odin with ap,bl,cp and csc selected.
Click to expand...
Click to collapse
i mean at what firmware where you before you flash t-mo nougat?
spiderkr said:
i mean at what firmware where you before you flash t-mo nougat?
Click to expand...
Click to collapse
Beta 2 Verizon Nougat
Unable to select network
Under "Network Operators" I selected Verizon Wireless, waited 5 minutes, and now got Unable to select network. Then, maybe a minute or so later, it says "Unable to connect. Try again later." Is there a way around this?
jrkruse said:
they also did something to disable all package disabler apps even if you go back to MM they dont work. They screwed us goood on this
Click to expand...
Click to collapse
I noticed this too, thought I was going crazy lol. That was the only think keeping me from rooting, and considering how horrible root is on this phone, I'm going to Verizon tomorrow to get a Pixel.
Im messing with it I got lte can make and receive phone call receive text but cant send
jrkruse said:
Im messing with it I got lte can make and receive phone call receive text but cant send
Click to expand...
Click to collapse
awesome!! getting closer...
jrkruse said:
Im messing with it I got lte can make and receive phone call receive text but cant send
Click to expand...
Click to collapse
How'd you manage to do that? Still can't get anything to work on my end...
device: droid mini xt1030
what ive tried: clean install (wiped cache,data,system etc)
method of flashing: first flashed cm13 unofficial obake via twrp 2.8.4.0(clean) then gapps and reboot.
problem: everything works and rom is smooth, nightly dated sep 22 2017,but all nightlies have same problem. no sim signals,phone info says radio off wont turn on via *#*#4636#*#*. installed many times over,rsd lite-d to stock then tried again,same issue.
zeronexus said:
device: droid mini xt1030
what ive tried: clean install (wiped cache,data,system etc)
method of flashing: first flashed cm13 unofficial obake via twrp 2.8.4.0(clean) then gapps and reboot.
problem: everything works and rom is smooth, nightly dated sep 22 2017,but all nightlies have same problem. no sim signals,phone info says radio off wont turn on via *#*#4636#*#*. installed many times over,rsd lite-d to stock then tried again,same issue.
Click to expand...
Click to collapse
Hi Zeronexus,
Details please:
1] Which bootloader and baseband are you on?
2] What was the last stock firmware version you flashed?
3] Does your radio work on stock firmware?
4] Who is your carrier? GSM or CDMA?
5] Do WiFi, Bluetooth and GPS work?
pbarrette said:
Hi Zeronexus,
Details please:
1] Which bootloader and baseband are you on?
2] What was the last stock firmware version you flashed?
3] Does your radio work on stock firmware?
4] Who is your carrier? GSM or CDMA?
5] Do WiFi, Bluetooth and GPS work?
Click to expand...
Click to collapse
1]bootloader : 30.BA (unlocked) baseband : SU6-7.7_23255_132_81_03R
2]last stock firmware used CFC_obakem_verizon-user-4.4.4-SU6-7.7-release-keys0
3]radio works but needs to toggle airplane mode after restart,no issues afterwards.
4]Telenor Pakistan,gsm.
5]wifi Bluetooth and gps work,everything works except sim on cm13.
zeronexus said:
1]bootloader : 30.BA (unlocked) baseband : SU6-7.7_23255_132_81_03R
2]last stock firmware used CFC_obakem_verizon-user-4.4.4-SU6-7.7-release-keys0
3]radio works but needs to toggle airplane mode after restart,no issues afterwards.
4]Telenor Pakistan,gsm.
5]wifi Bluetooth and gps work,everything works except sim on cm13.
Click to expand...
Click to collapse
Hi Zeronexus,
The obake platform defaults to an expectation of a CDMA network that is configured like Verizon Wireless in the US.
To configure as a GSM phone, you need to issue the following command in bootloader mode:
fastboot oem config carrier gsm
I use Verizon in the US, so I've never tried it on GSM networks, but that's the instructions in the LOS obake README file:
https://github.com/pbarrette/android_device_motorola_obake
Hopefully that works for you.
pbarrette said:
Hi Zeronexus,
The obake platform defaults to an expectation of a CDMA network that is configured like Verizon Wireless in the US.
To configure as a GSM phone, you need to issue the following command in bootloader mode:
fastboot oem config carrier gsm
I use Verizon in the US, so I've never tried it on GSM networks, but that's the instructions in the LOS obake README file:
Hopefully that works for you.
Click to expand...
Click to collapse
tried the fastboot command,doesnt work even though it says ok in fastboot. in phone information it says gsm service: radio off (*#*#4636#*#*)
Anyone who can help?
zeronexus said:
Anyone who can help?
Click to expand...
Click to collapse
Hi zeronexus,
At this point, I'm not sure what you can do.
Basically, you have problems with the radio even using stock firmware. Granted, you have a workaround, but it's still not operating correctly.
So it could be that you have a hardware error.
Or, it could be that your SIM is giving bad instructions as to which radio configuration to enable.
That could be due to having a bad SIM card, or having some kind of incompatibility between your carrier and the phone's radio.
You could post the output of a "adb shell logcat -b all" and a "adb dmesg" performed immediately after a reboot.
I'll have a look at them, but I've never been that great at parsing logcat or dmesg files. Maybe someone else will also see them and have a better understanding.
The other thing you can try is finding the newest possible Pakistani ROM for the Moto-X (2013 model, code-named "ghost"), or for the Droid Ultra. You should be able to flash the radio for that to your Mini since they share the same hardware.
You could try different versions of radio firmware for the obake, obakem and ghost platforms and see if any of them work.
You would have to extract the "NON-HLOS.bin" and "fsg.mbn" files from the stock ROMs and do:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Thanks a lot sir! Even though my issue didn't resolve I appreciate your timely response will try to do what u said,I'm quite familiar with flashing.
If it makes any difference, my device says "device unlocked status code 1" and says Motorola confidential property " on the top,no Verizon logo. These devices have been shipped a lot recently to Pakistan and I doubt these testing devices should be up for sale legally.
It also has a factory mode and some additional boot loader options not available in other droids,I flashed a normal stock ROM but the one it was shipped with had an "S" instead of the KitKat "K" when tapping on android version.
https://www.xda-developers.com/how-...-att-samsung-galaxy-s7-s7-edge/#disqus_thread
Can I flash this with flasfire if so how
SIGMAxB said:
https://www.xda-developers.com/how-...-att-samsung-galaxy-s7-s7-edge/#disqus_thread
Can I flash this with flasfire if so how
Click to expand...
Click to collapse
Won't flash on T-Mobile - it expects AT&T firmware (SM-G930A) - not anything else. I tried it (SM-G930T) and got error 7 in second stage with that exact reference (expected SM-G930A; got SM-G930T). This would have to be edited to take that second-stage reference out to work.)
You can flash if you flash the latest att firmware but the fluidity of the u firmware and battery have me staying put till the official release
Death Cookie Firmware in Non-DeathStar Phones - Yes; However
SIGMAxB said:
You can flash if you flash the latest att firmware but the fluidity of the u firmware and battery have me staying put till the official release
Click to expand...
Click to collapse
Then use A firmware (not U). You can even stick your T-Mobile nano-SIM back in the phone once the firmware is installed (just not DURING the install). I've just finished the install, have my UnCarrier nano-SIM back in the phone, and am currently charging it while restoring all my apps (yes - including the T-Mobile apps). The only loss (which isn't one in my situation) is VoLTE/VoWifi (two features I never use). The rather cute part is that I have more access to e-mail accounts with the AT&T firmware than I did with either UnCarrier firmware or VZW firmware (and with fewer apps, no less). Still, if you DO use VoLTE or VoWifi, this firmware is not an option. You have to reboot a second time (apparently the first reboot post-install doesn't completely flush - which is why the Wi-fi doesn't work; the second boot fixes that). The same should be true with any other carrier (VZW, Sprint, Cricket Wireless, Virgin Mobile, etc.); your only loss will be carrier-specific features.
PGHammer said:
Then use A firmware (not U). You can even stick your T-Mobile nano-SIM back in the phone once the firmware is installed (just not DURING the install). I've just finished the install, have my UnCarrier nano-SIM back in the phone, and am currently charging it while restoring all my apps (yes - including the T-Mobile apps). The only loss (which isn't one in my situation) is VoLTE/VoWifi (two features I never use). The rather cute part is that I have more access to e-mail accounts with the AT&T firmware than I did with either UnCarrier firmware or VZW firmware (and with fewer apps, no less). Still, if you DO use VoLTE or VoWifi, this firmware is not an option. You have to reboot a second time (apparently the first reboot post-install doesn't completely flush - which is why the Wi-fi doesn't work; the second boot fixes that). The same should be true with any other carrier (VZW, Sprint, Cricket Wireless, Virgin Mobile, etc.); your only loss will be carrier-specific features.
Click to expand...
Click to collapse
Which version of att firmware did you flash ? Is it worth flashing the Oreo update
SIGMAxB said:
Which version of att firmware did you flash ? Is it worth flashing the Oreo update
Click to expand...
Click to collapse
The same version in the AT&T Mobility thread (same subject) - the hard part (for me) was that I had to update by dong the updates manually to get to the right version to apply the beta (from an earlier version) - seven updates I had to apply via SDcard - THAT was the real pain, not the application of the beta firmware itself, which was rather painless. I'm still there and have absolutely zero interest in going back to any version of Nougat (stock or L, for that matter), and I came from Project L V.4. In other words, I'm using this as my daily driver.
I DO have one warning (and it's one that makes sense when using firmware from another carrier); take your T-Mobile SIM out before you start the firmware changeover, and don't put in your proper SIM until you start the new-customer steps, as some firmware doesn't take kindly to using a carrier other than the one intended (in the case of what I call "Darth Cookie", AT&T Mobility); remember, we're on T-Mobile - not exactly the "proper" carrier for this firmware. (I was wary on the move to T-Mobile firmware, because the handset itself is VZW-branded - and I was worried about gotchas merely there; amazingly - or more amusingly - because it IS locked firmware - changing carriers is depressingly easy despite the firmware locks.)
Beginning of Round Two - CRB6
PGHammer said:
The same version in the AT&T Mobility thread (same subject) - the hard part (for me) was that I had to update by dong the updates manually to get to the right version to apply the beta (from an earlier version) - seven updates I had to apply via SDcard - THAT was the real pain, not the application of the beta firmware itself, which was rather painless. I'm still there and have absolutely zero interest in going back to any version of Nougat (stock or L, for that matter), and I came from Project L V.4. In other words, I'm using this as my daily driver.
I DO have one warning (and it's one that makes sense when using firmware from another carrier); take your T-Mobile SIM out before you start the firmware changeover, and don't put in your proper SIM until you start the new-customer steps, as some firmware doesn't take kindly to using a carrier other than the one intended (in the case of what I call "Darth Cookie", AT&T Mobility); remember, we're on T-Mobile - not exactly the "proper" carrier for this firmware. (I was wary on the move to T-Mobile firmware, because the handset itself is VZW-branded - and I was worried about gotchas merely there; amazingly - or more amusingly - because it IS locked firmware - changing carriers is depressingly easy despite the firmware locks.)
Click to expand...
Click to collapse
I reset the phone, and kicked off testing of CRB6, and I did one thing differently; I left the SIM in the phone. I had a purpose for that - I was looking for bugbears that apply to non-AT&T carriers (T-Mobile, VZW, Sprint, et. al.) Amusingly, there aren't any. I did the flush (U Firmware version of BRA1) then applied the AT&T version of BQL1 (back-to-back via ODIN). Then came the ADB via SD card single-file updates (recovery mode for these) and there are only two - BQL1 to BRA1 (from Round One) and the new CRB6 update (courtesy of Samsung Firmware Science) labeled update_2.zip. It replaces update.zip, and is not opened or extracted - apply it as-is. After this update applies, follow the new-customer steps as you did for Round One - no changes here.
If anyone needs the newest G930A firmware before this Oreo leak, I have a Google drive Link. PM me.
And that's an Odin friendly
bkup said:
If anyone needs the newest G930A firmware before this Oreo leak, I have a Google drive Link. PM me.
And that's an Odin friendly
Click to expand...
Click to collapse
Can I get a copy please
Why I Did It The Way I Did
SIGMAxB said:
Can I get a copy please
Click to expand...
Click to collapse
When someone gets a proper copy, link it to the thread - the very reason I did NOT do it that way was because a proper copy of AT&T BRA1 didn't exist. (You can't get it from SamMobile or UPDATO either - much to my frustration; the latest ODINable AT&T firmware was BQL1.)
So I've been reading and just trying to verify if I'm using the T-Mobile version of oneplus 8i can't install the betas? If I'm wrong can someone point me to the correct version to install? We just got beta 3
goast said:
So I've been reading and just trying to verify if I'm using the T-Mobile version of oneplus 8i can't install the betas? If I'm wrong can someone point me to the correct version to install? We just got beta 3
Click to expand...
Click to collapse
The T-Mobile software removes the ability to install update from local storage. You would have to convert to Global to be able to install the betas. I am running a T-Mobile OP8, converted to Global, running beta 3 no issues.
Global Version
stompysan said:
The T-Mobile software removes the ability to install update from local storage. You would have to convert to Global to be able to install the betas. I am running a T-Mobile OP8, converted to Global, running beta 3 no issues.
Click to expand...
Click to collapse
Do you have a link as to where i can get Global version or steps for getting it ?
j1232 said:
Do you have a link as to where i can get Global version or steps for getting it ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-8/how-to/guide-convert-to-global-t4105885
Make sure to read everything on the thread. Pull an image of your persist and your modem before flashing global. Some people lose network and/or FP, though having those two files can typically repair them pretty easily. If something bad happens during the conversion, you can use MSM to go back to T-Mobile firmware, but that doesn't fix your FP reader. That's why grabbing the persist is most important. You can do both from booting TWRP. Back up the modem directly in TWRP, and use adb shell along with "dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img" to make an image of the persist. Once on global, you can simply install the update through the local upgrade process and go from there. From what I have read, you do lose 5G SA. I don't know if this is still valid on the latest beta or not, but it is something to note.
stompysan said:
https://forum.xda-developers.com/oneplus-8/how-to/guide-convert-to-global-t4105885
Make sure to read everything on the thread. Pull an image of your persist and your modem before flashing global. Some people lose network and/or FP, though having those two files can typically repair them pretty easily. If something bad happens during the conversion, you can use MSM to go back to T-Mobile firmware, but that doesn't fix your FP reader. That's why grabbing the persist is most important. You can do both from booting TWRP. Back up the modem directly in TWRP, and use adb shell along with "dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img" to make an image of the persist. Once on global, you can simply install the update through the local upgrade process and go from there. From what I have read, you do lose 5G SA. I don't know if this is still valid on the latest beta or not, but it is something to note.
Click to expand...
Click to collapse
How can one tell of phone is using 5g SA on OB3?
crazynapkinman said:
How can one tell of phone is using 5g SA on OB3?
Click to expand...
Click to collapse
Using a program like LTE Discovery will tell you. In my case, it indicates I am connected to NR NSA 5G. I have not ever seen my phone go to SA 5G since converting, and I do live in an SA location and have connected while on T-Mobile software. See screenshot.
Mine says 5G NR
crazynapkinman said:
Mine says 5G NR
Click to expand...
Click to collapse
I have noticed it takes some fiddling with WiFi to get it to display network type. The 5G detection is still a WIP. There are probably other apps that may work better, but I am just used to using LTE Discovery over the years.
I'm also on a tmobile converted to global phone. Using Beta 3 and getting random errors with the sim card where phone says "no sim". Happens 1-2 times per day. Only way to fix is to reboot or eject the sim and reinsert. Either way, back to full bars for a few hours. I backed up modem and persist, but I don't think the Android 10 modem will work on Android 11. Also, can't flash because TWRP doesn't work on Android 11 yet. Very frustrating, looks like lots of reports of this happening on Oneplus 8 phones (Tmobile and unlocked) on here and oneplus forums. No solution found!
xxBrun0xx said:
I'm also on a tmobile converted to global phone. Using Beta 3 and getting random errors with the sim card where phone says "no sim". Happens 1-2 times per day. Only way to fix is to reboot or eject the sim and reinsert. Either way, back to full bars for a few hours. I backed up modem and persist, but I don't think the Android 10 modem will work on Android 11. Also, can't flash because TWRP doesn't work on Android 11 yet. Very frustrating, looks like lots of reports of this happening on Oneplus 8 phones (Tmobile and unlocked) on here and oneplus forums. No solution found!
Click to expand...
Click to collapse
I have Sprint sim and this is not happening.