Related
Under status, Network shows as 'Unknown', Mobile network type shows as 'Unknown', Service state is 'Out of service', and Mobile network state is 'Disconnected'.
IMEI shows as nonnull (valid), and IMEISV shows as nonnull (valid). I'm not sure where the issue is, i'm assuming it is somewhere in the modem, but I flashed the NG3 Modem multiple times.
Not really sure what is wrong, can anyone suggest anything to restore my phone before I try something else again?
..
fffft said:
You didn't give us very much detail about anything from what firmware build you tried to flash to what model of S5 you have, screen shots of your phone information in the settings menu or anything else. Which makes it impossible to delineate what happened.
At a guess and that is all that is possible without a detailed description of your configuration.. it sounds like you may have flashed the wrong firmware - intended for another carrier or S5 variant. Which sometimes screws up wifi /bluetooth or occasionally bricks a phone. Check that your firmware build md5 checksum is valid, that the firmware is intended for your native carrier and variant. And if you were flashing a modem separately, confirm that it is for your carrier and matches your baseband (bootloader). Failing that, restore your backup to recover.
If you don't have a backup for some reason, that should be very high on your list of things to start doing. In that situation, download a full stock firmware that is for your specific phone model and carrier, wipe the cache partition and you should be good. In some cases you may also need to do a factory data reset (do that as a last resort, since it will delete your photos, user files, etc).
.
Click to expand...
Click to collapse
I downloaded the stock tar (the full one) here, and selected AP with it. To be sure that my bootloader is updated, I later used the modem/booloader here and I used the right one (900T) and followed the guide at the top of that page for setting "BP" for bootloader and "CP" for modem. When I run the bootloader check command (getprop ro.boot.bootloader), it returns NG3, so I think that's fine too.
I have the 900T (well, this IS the t-mobile galaxy s5 thread).
I probably should have backed up, but I tend not to because I have rarely ran into issues on my previous Note 2 and the times I did, the backup wouldn't have fixed it (usually because the recovery was too big or the modem got corrupted).
And I did use factory reset multiple times, I don't have much on the phone right now and also have an external sd card where I store most of my things anyways.
Specifically, what part of the settings would you want to see?
..
NG3 Full Stock Tar: http://www.androidfilehost.com/?fid=23578570567722728
^ That was what I used under AP.
When I try to repartition, is says "Erasing USERDATA Partition...\nSECURE CHECK FAIL : PIT".
..
fffft said:
Suggesting that you have partition corruption. The purpose of my earlier suggestion to flash the PIT file was to resolve potential partition corruption. So you could do far worse than follow the suggestions in my last post.
.
Click to expand...
Click to collapse
No longer boots after nand erase all. Since the partition failed, I unchecked it and just left NAND erase checked.
Any other suggestions?
rmanne said:
No longer boots after nand erase all. Since the partition failed, I unchecked it and just left NAND erase checked.
Any other suggestions?
Click to expand...
Click to collapse
I don't know why or what @fffft is trying to get you to do but touching the things you are could end up bricking your device if not too careful.
All you need to do is select the full tar file under "AP" and uncheck the reboot and F reset time options.
EDIT: You need to extract the tar file to get the MD5 file that is what you flash in Odin.
If you have no data, just check that the APN settings are properly configured.
I had to flash the tar file a couple times before the modem upgraded. But don't touch PIT or NAND erase.
..
fffft said:
You can't do a normal boot after erasing the NAND, since that has wiped our your system files. That isn't unexpected. But your phone will still boot to download mode, sometimes called "Odin" mode. Volume down + home + power.
Once your write a replacement firmware image it will boot normally again. Writing a full image is recommended. Odin can be fussy and seemingly a bit more so with larger writes than when flashing smaller writes. And possibly easier with earlier S5 firmware builds (not proven, just an impression).
If you persist Odin will write the image, it just takes several attempts sometimes. If a given write fails, do not reset Odin on your PC, just pull the phone battery, replace it.. boot to download mode again and flash again from the open Odin window. Inevitably the flash will succeed the second time even though Odin balked the first time. If you have persistent problems, try a different USB cable and USB port.
The poster above doesn't understand what the NAND or partition features accomplish, but anyone doing their due diligence would find informed threads supporting my recommendations when partition corruption is suspected or needs to be repaired.
..
Click to expand...
Click to collapse
I didn't just erase the NAND though, I also added the .tar.md5 file that I pointed to earlier, which should have added back the system files. Well in any case, I flashed TWRP, and according to it, the Data partition was not properly partitioned (and thus not mounted) and I wiped that with TWRP, and installed another custom ROM (ViSiX), and it has the same issue right now ("Searching").
I did try the earlier S5 images (NF6, which is what the phone initially came with), and I flashed the proper modem/bootloader there also, but it still has no service.
I know that the sim card is working because I still have my other phone (note 2), and it works fine in that. I still don't understand what about the S5 that is not working. It doesn't even say no service anymore. It's just searching...
by replacement firmware image, do you mean the whole stock rom image? Or do you mean just the firmware, as is given in that stock collection thread.
elesbb said:
I don't know why or what @fffft is trying to get you to do but touching the things you are could end up bricking your device if not too careful.
All you need to do is select the full tar file under "AP" and uncheck the reboot and F reset time options.
EDIT: You need to extract the tar file to get the MD5 file that is what you flash in Odin.
If you have no data, just check that the APN settings are properly configured.
I had to flash the tar file a couple times before the modem upgraded. But don't touch PIT or NAND erase.
Click to expand...
Click to collapse
Also, 'had to flash a couple times'? Why on earth would there be non-determinism involved in a phone? I'm genuinely confused.
APN settings appear to be the exact same as my previous phone, and it shouldn't be the issue anyways because the APN is only useful to look at for network use right? I can't even call/text, since it says that I'm not registered on the network.
rmanne said:
Also, 'had to flash a couple times'? Why on earth would there be non-determinism involved in a phone? I'm genuinely confused.
APN settings appear to be the exact same as my previous phone, and it shouldn't be the issue anyways because the APN is only useful to look at for network use right? I can't even call/text, since it says that I'm not registered on the network.
Click to expand...
Click to collapse
I don't know why but the baseband doesn't always flash. So flashing it twice in a row usually does the trick,
Sent from my SM-G900T using Tapatalk
I did just try the install modem twice in a row with no luck.
What's the best recovery to use with this phone? I'm using the twrp that you can download on their official website right now, but from what I remember, on the Note 2, if you install using the 'wrong' version of TWRP, your service won't work.
Also, another thing that I've noticed is that during the initial one time initialization, instead of saying "Samsung Galaxy S5 (T-Mobile)" (or something like that), it is now saying "Samsung galaxy S5" without the T-Mobile addition to it. I think that it has to do with the recovery that I flashed, since it's what determines the phone model more than anything.
EDIT: used to say "Galaxy S5 ..." and now says "Galaxy S5"
rmanne said:
I did just try the install modem twice in a row with no luck.
Click to expand...
Click to collapse
I'm talking about the entire md5 file.
I use twrp.
Sent from my SM-G900T using Tapatalk
elesbb said:
I don't know why but the baseband doesn't always flash. So flashing it twice in a row usually does the trick,
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Does the download mode have something to do with it?
On mine, it says:
ODIN MODE
PRODUCT NAME: SM-G900T
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 0x1 (2)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
UDC START
elesbb said:
I'm talking about the entire md5 file.
I use twrp.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Yep, I was trying to install the entire md5 ("G900T-UVU1BNG3-MODEM.tar.md5"), unless you meant the full stock rom.
..
fffft said:
We're assuming that your stipulation that the IMEI is valid is correct. I'd look at the service mode menu and check the certificate status to confirm that if you haven't already.
You could also do a search to see if anyone is having problems with the most recent G900TUVU1BNG3 firmware. Or even better temporarily revert to the a known stable, earlier firmware version. If you flash a full firmware image from May, your certificate status is valid and your APN info is correct then you'd have a reasonable basis for suspecting a hardware failure.
Hardware is unlikely though unless you can associate it with trauma or pre-existing symptoms, none of which you mentioned. Network connectivity issues inevitably arise from flashing a modem or firmware image intended for a different platform, a corrupt cache or corrupt system files.
.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2754957
^ I ran through that first post, and did as it said without any improvement.
How do I check the certificate status?
From what I can tell, no one else is having the issue (or at least no one has yet posted about it). And as I've already said, NF6 didn't work either (it was working when I got my phone, but now doesn't work after trying to revert everything to stock).
APN info is certainly correct.
I didn't unbox this phone, so I'm not actually sure that it's the right model, but its first boot showed the 'T-Mobile' display screen, so I see no reason to doubt that it's a 900T. I will recheck this just in case.
EDIT: I found the certificate status i think
The page says "IMEI Certi: PASS, 1\nUnknown"
also includes "REJECT:6, LU_ATT#: 0", "SERVICE : LIMITED", "STATE: DEREGISTR SUB:1", "PA STATE:0(ET),HDET:0", "and a bunch of numeric values above it. Band 4, BW 10MHz, MCC-MNC, TAC, Earfcn_dl, PCI: 0, RSRP -94, RSRQ -10, SNR 17.4-22.1
What does it mean? What is "LU_ATT"?
Solved!
For whatever reason, it seems that the person who sold the phone reported it as stolen (according to T-Mobile customer service, a phone marked as lost will not be able to access network services) at around the same time that I flashed the update. I did think something was fishy since I didn't immediately lose network. I feel like I was on NG3 for at least a few hours before it stopped working, but I thought I might have just been imagining things, since the timing was just too close to properly make a note of.
Well, thanks anyways, I appreciate the time you two took to attempt to help.
I've been asked by lots of folks on how to convert the HTC 10 unlocked US version into a full-featured Verizon version so I figured i'd write an all encompassing guide on how to complete the process.
After following this guide, your phone will effectively be a fully-functioning Verizon variant. IMS, advanced calling, wifi calling and all other Verizon features will work flawlessly!
Note: I am purely compiling this information. I had no part in discovering this process, I simply followed multiple guides and other random posts on XDA to accomplish this! Credits go to @jcase, @beaups, @dottat, and any others that were involved with testing this process. Please make sure to thank these guys for the work they've done.
Step 1: Unlock bootloader and acquire s-off
In order to modify the CID/MID and change the radio, we must first acquire s-off. The easiest way to do this is to follow jcase's well-written guide.
[FONT=Hind, sans-serif][Guide] Root (Optionally s-off) and Keep your radio working[/FONT]
Move on to step 2 after finishing the above guide to completion.
Step 2: Change CID and MID
2a) Download this link, and extract into your directory of choice
https://www.androidfilehost.com/?fid=24545065934258327
2b) Boot your phone into download mode via the button combo (down + power) or by using adb reboot-bootloader with USB debugging turned on and then selecting download mode
2c) Issue the following command while in download mode:
Code:
htc_fastboot oem writecid VZW__001
2d) Issue the following command while in download mode:
Code:
htc_fastboot oem writemid 2PS650000
2e) Reboot phone back into download mode and verify the CID and MID have changed and are correct.
Step 3: Flash Verizon RUU to phone
Now that we have s-off, unlocked bootloader and the proper CID/MID on our device, now we just need the Verizon stock ROM and radio on our device. The Verizon RUU will handle both of these for us in a relatively hassle-free manner.
3a) Download the following .exe file to your local machine (big thanks to @dottat!)
Verizon Stock RUU exe (dottat)
3b) Boot phone into download mode (or Android OS w/ USB debugging enabled) and run the executable file
3c) Follow onscreen instructions and wait for process to finish
3d) Reboot phone (it may take a while to boot so BE PATIENT! mine took about 4-5 minutes if I recall)
After your phone boots, it will be a fully functioning Verizon phone. At this point, you can go activate your phone and it will work. You will be able to take Verizon official OTAs and it will behave identically to the true Verizon variant due to the RUU re-flashing stock recovery and an unmodified system.
OPTIONAL -- Step 4: Re-root phone
The RUU that you deployed on your phone was an unrooted system image with stock recovery. In order to get root back, you will need to re-do steps 1-10 in jcases's Root/s-off guide from step 1.
Here's the link again in case you're too lazy to scroll back up
[FONT=Hind, sans-serif][Guide] Root (Optionally s-off) and Keep your radio working[/FONT]
Reminder: your phone already has s-off so you ONLY NEED TO DO STEPS 1-10! Running Sunshine again will likely just report that your phone already has s-off so no worries if you accidentally do the entire guide again.
Step 5: Activate your phone
This step can be very straightforward or a moderate pain the ass depending on what you have available to you.
There are two ways to activate the HTC 10 now that it's running stock Verizon firmware/software:
1) Pop an existing, activated nano-SIM with your current phone number on it in the device and reboot. Voila!
2) Take your device to a Verizon store and convince the employee that your phone is in fact, a true Verizon phone.
I would highly suggest using an already active nano-SIM if you have that available. I, unfortunately, did not as I was coming from the Verizon LG G4. I had to go three different Verizon stores to convince them to finally activate the device. Your IMEI on your unlocked 10 will not show up in Verizon's IMEI database. The store clerk actually had to pull an IMEI from a display model HTC 10 so that she could get the nano-SIM activated for my 10.
noahjk said:
Good post! I think you're looking for this link: http://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025
Click to expand...
Click to collapse
Good catch, thanks. I updated the links.
Tried this twice, both times my phone gets stuck on 'Preparing your phone...' after flashing and rebooting on the setup wizard.
edit: worked fine after removing SIM. Run through the setup without SIM for anybody having issues. I know this isn't explicitly stated in OP but if you're having issues, make sure you try this.
If anyone is having connection issues after putting in your SIM, you have to change your Preferred Network mode from Global to LTE/CDMA.
Other than that, everything's working great! Even comes with free VZW bloatware
anyone receiving "Htcdm has stopped" on their phone all of a sudden .... i just downloaded a few things, changed the bootanimation, setup my hotspot, and then bam - popups randomly.
codelinx said:
anyone receiving "Htcdm has stopped" on their phone all of a sudden .... i just downloaded a few things, changed the bootanimation, setup my hotspot, and then bam - popups randomly.
Click to expand...
Click to collapse
Haven't seen that before. What did you do to setup your Hotspot?
DoctorB0NG said:
Haven't seen that before. What did you do to setup your Hotspot?
Click to expand...
Click to collapse
That error would be the ota downloader.. what anything frozen I would ask the person who posted
Sent from my HTC6545LVW using Tapatalk
How would I revert back to the stock values and a stock unlocked RUU? Can you put that in the guide with a link to a stock RUU?
Zooks97 said:
How would I revert back to the stock values and a stock unlocked RUU? Can you put that in the guide with a link to a stock RUU?
Click to expand...
Click to collapse
I'd *think* that you just do the opposite of this guide.
Write MID/CID back to UL (UnLocked) Variant version along with then flashing the UL Variant RUU.
I agree it would be a good idea to add the return to stock either in the OP, or possibly a link to another thread explaining how.
andybones said:
I'd *think* that you just do the opposite of this guide.
Write MID/CID back to UL (UnLocked) Variant version along with then flashing the UL Variant RUU.
I agree it would be a good idea to add the return to stock either in the OP, or possibly a link to another thread explaining how.
Click to expand...
Click to collapse
Looks like all the stock information, RUUs, roms, and recoveries are here.
Has the MID/CID for stock there as well. Hope this makes it into the OP.
When I have access to a desktop/laptop I'll update the guide. Thanks for the suggestions.
After following all the instructions, I got to the end where the phone reboots and is supposed to be Verizon. When mine reboots, however, it comes up with the decryption screen asking for my password. Any ideas?
I think I might have figured it out. I did a factory reset/wipe and it looks like it's coming up now.
hunteditor said:
After following all the instructions, I got to the end where the phone reboots and is supposed to be Verizon. When mine reboots, however, it comes up with the decryption screen asking for my password. Any ideas?
I think I might have figured it out. I did a factory reset/wipe and it looks like it's coming up now.
Click to expand...
Click to collapse
Yep that's the fix. The vzw ruu does not wipe.
Sent from my HTC6545LVW using Tapatalk
andybones said:
I'd *think* that you just do the opposite of this guide.
Write MID/CID back to UL (UnLocked) Variant version along with then flashing the UL Variant RUU.
I agree it would be a good idea to add the return to stock either in the OP, or possibly a link to another thread explaining how.
Click to expand...
Click to collapse
Did you pick up a 10 yet?
aer0zer0 said:
Did you pick up a 10 yet?
Click to expand...
Click to collapse
I did.
It's prepared to be sent to Mr. @beaups when they are back doing devices again on May 22nd.
(In my signature below, in green are the devices I currently own, and the ones striked out are previous devices I had but are sold).
Just an FYI, I followed instructions on this guide, did everything without SIM card in and I do not have any advanced calling features. Signal drops to 1x when on a call and there is no Wi-Fi calling option in the advanced calling menu within Android. My guess on the cause is that I flashed TWRP and side loaded SuperSU before I put my SIM in the phone. I will try again from scratch and activate the phone prior to root and recovery and report back. Is anyone else having similar issues?
Light1984 said:
Just an FYI, I followed instructions on this guide, did everything without SIM card in and I do not have any advanced calling features. Signal drops to 1x when on a call and there is no Wi-Fi calling option in the advanced calling menu within Android. My guess on the cause is that I flashed TWRP and side loaded SuperSU before I put my SIM in the phone. I will try again from scratch and activate the phone prior to root and recovery and report back. Is anyone else having similar issues?
Click to expand...
Click to collapse
Did you activate those features on your account using the menu on the phone?
Sent from my HTC6545LVW using Tapatalk
dottat said:
Did you activate those features on your account using the menu on the phone?
Click to expand...
Click to collapse
What menu are you talking about? I went to take a screen shot of my advanced calling menu in settings and now Wi-Fi calling is showing up.. I didn't change a thing, very odd. However, my signal still drops to 1x when placing a call. And my device says non-VZW device when I login to my account online. I'm guessing that is part of the problem.
Light1984 said:
What menu are you talking about? I went to take a screen shot of my advanced calling menu in settings and now Wi-Fi calling is showing up.. I didn't change a thing, very odd. However, my signal still drops to 1x when placing a call. And my device says non-VZW device when I login to my account online. I'm guessing that is part of the problem.
Click to expand...
Click to collapse
Take some screen shots.
Sent from my HTC6545LVW using Tapatalk
Here is my advanced calling menu with Wi-Fi calling now showing up. Haven't tested, but it seemed to let me set it up. I have Wi-Fi tether enabled via default.xml edits. The one feature I'd really like is LTE on call. Had this without problem on my M7 but I think thats because it had multiple radios and didn't have to share a radio while on call. My noob guess anyways.
Maybe it's a setting in the hidden dialer menu *#*#4636#*#*? However, when I enter that into the dialer, nothing happens, the entered numbers just disappear and nothing happens. Thoughts?
Hi everyone, I've followed the WTF thread to unlock the bootloader on a V30 H933 (the Canadian version), but even after unlocking there's no fastboot support on the phone, only the US998 version seems to have it. Trouble is that Rogers, my local operator, only supports VoLTE and VoWiFi on their recognized devices - I tried having US998 running on my phone, calling their support and possibly getting some actual configuration I could put on the phone, but their response was "your phone is defective and needs to be replaced".
All that said, my goal here is to somehow install TWRP on this phone and root under the original ROM, so I can have the features I need from the network. So far, I've been pretty unsuccessful in this, so my plead would be: could anyone chime in to help me either
flash the minimal necessary over US998 to get H933 functionality/network information back as to reenable VoLTE and VoWiFi on my operator
come up with an update.zip or some other file I could use to flash a Magisk-patched boot.img
pack a full flashable ZIP image of the Canadian ROM (my last attempt at this left the phone in bootloop)
an alternative idea I haven't thought about that could help?
Ideally, at the end of the process, I'd like to have TWRP and Magisk installed on the phone, but I could settle for simply Magisk.
Once again, any help or pointers are more than welcome and appreciated.
I think you can extract a h933 kdz and flash individual partitions that do not have to do with recovery or the bootloader. You can probably use the dd command for it. I think the partitions you dont flash are anything with boot in it, abl and recovery. There may be a few more however.
The Elite said:
I think you can extract a h933 kdz and flash individual partitions that do not have to do with recovery or the bootloader. You can probably use the dd command for it. I think the partitions you dont flash are anything with boot in it, abl and recovery. There may be a few more however.
Click to expand...
Click to collapse
I tried something similar, extracted a KDZ and put the necessary BIN files on a flashable ZIP I found around. All I achieved was bootlooping the device...
I have an H933 on Freedom Mobile, and running the stock FM firmware. The loss of VOWIFI (and VoLTE) are exactly what i thought would happen if I proceed with flashing to US998.
I think #1 is right; that you may be able to restore access to network specific functionality but it would depend on being able to isolate the specific required "patch".
With this in mind, take a look at this post from the WTF! Thread:
https://forum.xda-developers.com/showthread.php?p=76613814
That user flashed some files (modem binaries from the original device firmware I think) and was able to restore VOWIFI and VoLTE functionality on the Verizon network.
Sent from my LG-H933 using Tapatalk
My h933 converted to us998 says that my volte is enabled
cre4per said:
My h933 converted to us998 says that my volte is enabled
Click to expand...
Click to collapse
What menu is that from @cre4per? Have you had the opportunity to confirm staying on LTE while receiving a call?
That would be good news to hear VoLTE working on a Canadian network using a generic phone model (instead of proprietary stuff).
Sent from my LG-US998 using Tapatalk
Mad Medik said:
What menu is that from @cre4per? Have you had the opportunity to confirm staying on LTE while receiving a call?
That would be good news to hear VoLTE working on a Canadian network using a generic phone model (instead of proprietary stuff).
Sent from my LG-US998 using Tapatalk
Click to expand...
Click to collapse
*#*#4636#*#*,
and to be honest i never really noticed, will do some checks today to see if i stay on lte, will let you know
cre4per said:
*#*#4636#*#*,
and to be honest i never really noticed, will do some checks today to see if i stay on lte, will let you know
Click to expand...
Click to collapse
Looking at this this morning. I don't think that is an indication that you are connected to a VoLTE service; just that your device is ready to accept it if the right service becomes available. I have that switch turned on and the service menu even says the voice network is LTE too (see image below) but Freedom Mobile doesn't even offer VoLTE service so it isn't possible that I actually have VoLTE operational.
I would interpret the LTE provision switch as turning on or off the functionality in your device, not a connection authorization from the network. Sort of like turning on the HD calling option on your device; it allows the possibility but won't do anything unless the service provider has the capability and authorizes it on your connection.
If someone has VoLTE working, could you check the menu cited by @cre4per, then hit the options (3 dots) and in there, select IMS service status? It lools like this is where you *should* see if the network has connected you to their VoLTE service (see image below).
I don't know how to interpret the, "Voice Network: LTE" on the main menu screen.
Just check and switches to 3g on calls also when going into that ims menu says unavailable
GryphonBR said:
I tried something similar, extracted a KDZ and put the necessary BIN files on a flashable ZIP I found around. All I achieved was bootlooping the device...
Click to expand...
Click to collapse
Out of all the partitions which ones did you flash and which ones did you not flash? Also was the h933 kdz also for oreo?
-deleted-
cre4per said:
My h933 converted to us998 says that my volte is enabled
Click to expand...
Click to collapse
As @Mad Medik mentioned, so far I don't know of any Canadian operators enabling VoLTE (or VoWiFi for that matter) to generic phones. I have a Rogers P10 Plus that's registered under my account as my main phone and which I reflashed to have these features available, but it just won't work. I've had extended arguments with Rogers representatives about it, and the 1+3T I'm presently using even have the same config your phone is showing: VoLTE Provisioned, but IMS shows as Not Registered so nothing else works. I'm waiting on an LS998 I bought to arrive, I'll try flashing H933 on it to see if it actually allows me to register on IMS.
The Elite said:
Out of all the partitions which ones did you flash and which ones did you not flash? Also was the h933 kdz also for oreo?
Click to expand...
Click to collapse
KDZ was for Oreo, indeed. It was the one I used to bring the phone to the latest (at the moment) update available.
As for which partitions I flashed, I was gonna give you a list, but to make it short the only partition not flashed was recovery.
GryphonBR said:
As @Mad Medik
KDZ was for Oreo, indeed. It was the one I used to bring the phone to the latest (at the moment) update available.
As for which partitions I flashed, I was gonna give you a list, but to make it short the only partition not flashed was recovery.
Click to expand...
Click to collapse
As far as I know there are some boot partitions that should not be flashed, which may have caused the soft brick. I know autoprime used to make these zips for the G3 and runningnak3d made one for the V10, you might want to cross reference the partitions they used and what they didnt. Probably the V10 first because the G3 is relatively ancient. I think in essence you should just be able to flash boot, system and modem and rpm though, but you would need 2 combine the split up system images after the extract.
The Elite said:
As far as I know there are some boot partitions that should not be flashed, which may have caused the soft brick. I know autoprime used to make these zips for the G3 and runningnak3d made one for the V10, you might want to cross reference the partitions they used and what they didnt. Probably the V10 first because the G3 is relatively ancient. I think in essence you should just be able to flash boot, system and modem and rpm though, but you would need 2 combine the split up system images after the extract.
Click to expand...
Click to collapse
The reason why I was flashing everything is because I used this thread to recover from a previous soft brick I stumbled upon. Upon speaking to the thread creator, he mentioned I should be able to follow a similar process to achieve an H933 flashable file. Did that and, well, managed to soft brick the phone... I might try your idea, though.
So, from my knowledge of attempting to get VoLTE working on an HTC 10, I suspect you won't get VoLTE working on anything other than Rogers H933 firmware. For whatever reason, the programming required for VoLTE isn't on the USIM card in your phone, but rather programmed into the phone by the provider. This means, unless your phone model is sold and supported for VoLTE on the provider you wish to use it on, you're screwed like I was, trying to get VoLTE working on my HTC 10 on Rogers.
This being said, the good news is we are back to CDMA tech here, where the only thing preventing you from using your third party phone with your provider is knowing what code to enter, and what parameters to program in. Since my H933 is on Telus, my programming won't do you much good.
What you're looking for is the IMS settings or IP Multimedia Subsystem settings, as this is what carries the VoIP packets that consist of VoLTE. If someone were to post the settings from their Rogers H933, you may be able to get VoLTE working on US998 firmware.
Why not just flash system and boot? After unlocked and rooted of course.. Lg up partition DL will let you flash individual partitions. I would have done it that way for my carrier but there is no kdz available..
JWnSC said:
Why not just flash system and boot? After unlocked and rooted of course.. Lg up partition DL will let you flash individual partitions. I would have done it that way for my carrier but there is no kdz available..
Click to expand...
Click to collapse
I tried that last night just bootloops
cre4per said:
I tried that last night just bootloops
Click to expand...
Click to collapse
Did you wipe data?
JWnSC said:
Did you wipe data?
Click to expand...
Click to collapse
Yea. Then went to restore and the restore wouldn't even work anymore. Was saying there was no partitions backed up but I had use that restore numerous of times trying to get los to boot very strange had to start back from scratch
Anyone with H933 from freedom mobile convert to US988? I'm just wondering how the service is after the change. I'm reading mixed reports but once modems extracted and compared there was a difference.
Honestly found it on XDA of all places after looking for it all night
What does 1.16 give us that 1.14 doesn't? Everything honestly. Could not get my Wing recognized to flash with 1.14. No 1.15 Patched exists either
We can downgrade with ChipErase (and restore IMEI), we can modify PDM, we can dump the entire phone (will do tomorrow), can upgrade.
See link here for link: https://forum.xda-developers.com/t/...er-w-fastboot-drivers-and-common_dll.4304181/
This was the only working LGUp_Tool that worked outside of LGUP CMD
I wanted this to try other countries firmware files to see if we get other weird results. This should also allow custom KDZ files? from my understanding
ADDED INFO Nov 8, 2021
How to use LGUp Tool From this Download
1.) Download the LGUp 1.16.03 Patched from the XDA Link above
2.) Run the EXE as admin so it can install Drivers and the software properly
3.) Go to the install directory and run the 2 Bat files that are in the folder as admin
Code:
Default: C:\Program Files(x86)\LG Electronics\LGUp
-- Running LGUP_UI-fixer.bat -- run as admin, follow instructions, run the software when it says to, then close it
-- Run LGUP_UI-Fixer-addon.bat -- run as admin, follow steps, then run LGUp.exe when patch complete
You now have a working LGUP Tool 1.16 Patched for the LG Wing
Explaining the functions of LGUP Tool
Code:
REFURBISH： You will lose all user data（KDZ or TOT）
UPGRADE: Keep data and update your phone（KDZ or TOT) - Select Upgrade to flash kdz firmware to unbrick/restore your phone back to stock.
Chip Erase: Dangerous, This will erase IMEI/efs, do not try this if you do not have a NV backup. - Chip Erase can also remove the Google FRP on many LG devices with Android 5.0, 6.0.
PARTITION DL：Flash the single Partition or selected partitions onto your phone. - This feature can solve “unknown model” issues. This feature can be used to bypass Google FRP by flashing specific tot firmware.
DUMP：Dump all partitions of your phone as backup. - Dump the stock firmware from a working phone as back up and use Partition DL to restore phones.
FOTA Upgrade: This can be used to flash OTA Update file that comes with dot up file extension.
PDM: Change imei, wifi address, bluetooth, mac address
video for how to use LGUP Tool to flash the Wing
Awesome! I just DL'ed.. don't know when I'll have time to mess around with it. Or if I have the skill set to help. But I would definitely try to help out if I can and be excited for rootable firmware.
kaluna00 said:
Awesome! I just DL'ed.. don't know when I'll have time to mess around with it. Or if I have the skill set to help. But I would definitely try to help out if I can and be excited for rootable firmware.
Click to expand...
Click to collapse
I plan on making a video I'll put on the post explaining the tool
KaptinBoxxi said:
I plan on making a video I'll put on the post explaining the tool
Click to expand...
Click to collapse
Holy cow I can’t believe it. You actually found the exact tool that we needed! I went ahead and did a chip erase on my demo model, which had previously been flashed with the Korean firmware from the previous tutorial, and flashed the T-Mobile Firmware. IT WORKED! To get rid of the error at that shows up every time you reboot it, I accessed the hidden menu and changed the TN number to the one associated with TMO_US, as shown in this post.
Thank you!
twocans said:
Holy cow I can’t believe it. You actually found the exact tool that we needed! I went ahead and did a chip erase on my demo model, which had previously been flashed with the Korean firmware from the previous tutorial, and flashed the T-Mobile Firmware. IT WORKED! To get rid of the error at that shows up every time you reboot it, I accessed the hidden menu and changed the TN number to the one associated with TMO_US, as shown in this post.
Thank you!
Click to expand...
Click to collapse
I still can't get mine to accept a sim card and get data but I can make calls/text and use wifi, which is nice.
I wish Partition DL worked, we'd have the boot.img
I flashed Verizon Firmware and put the Verizon NT Code using PDM Mode, still didn't work. Going to try others later
KaptinBoxxi said:
I still can't get mine to accept a sim card and get data but I can make calls/text and use wifi, which is nice.
I wish Partition DL worked, we'd have the boot.img
I flashed Verizon Firmware and put the Verizon NT Code using PDM Mode, still didn't work. Going to try others later
Click to expand...
Click to collapse
Where did you get the Verizon firmware?
kaluna00 said:
Where did you get the Verizon firmware?
Click to expand...
Click to collapse
I found a site that had a "KDZ Downloader" and used that to download it. I can upload it here for those who need it once i redownload it here at work
or you can yourself from this post. Just need the LG URL to the firmware
[LG TOOLS] LG-KDZ-dll-Tool/LGUP_UI-fixer/LG-Kdz-downloader
Please, do not share elsewhere as I want to be able to update if necessary ! LG-KDZ-dll-Tool/KDZ dll extractor (=old version) : this message actually, scroll down a bit... LGUP_UI-fixer LG-Kdz-downloader Share this thread or my blog instead...
forum.xda-developers.com
KaptinBoxxi said:
I still can't get mine to accept a sim card and get data but I can make calls/text and use wifi, which is nice.
I wish Partition DL worked, we'd have the boot.img
I flashed Verizon Firmware and put the Verizon NT Code using PDM Mode, still didn't work. Going to try others later
Click to expand...
Click to collapse
I bought a mint mobile trial sim from amazon and I’m getting calls, text, and 5G data.
twocans said:
I bought a mint mobile trial sim from amazon and I’m getting calls, text, and 5G data.
Click to expand...
Click to collapse
I get calls and text, no cell service at all. I had to manually program in an IMEI. My IMEI comes back as 0 if I just flash it without PDM. IMEI doesn't apply via the service menu either
KaptinBoxxi said:
I get calls and text, no cell service at all. I had to manually program in an IMEI. My IMEI comes back as 0 if I just flash it without PDM. IMEI doesn't apply via the service menu either
Click to expand...
Click to collapse
Interesting. I was able to generate an IMEI in the hidden menu after the chip erase and it worked fine. I did also have to re-add my CSN, because that was also removed, and then my phone did an unprompted factory reset and rebooted.
By the way, when you flashed it, did you use Refurbish? Because with my demo unit, it refused to let me do that and would only allow chip erase. I was reluctant, but it turned out fine. And, the only important thing I was unable to reprogram afterwords was the S/N, but it doesn’t really matter to me. (Too bad the fingerprint scanner still doesn’t work though. That’s the only thing left that still isn’t working after all of this.)
twocans said:
Interesting. I was able to generate an IMEI in the hidden menu after the chip erase and it worked fine. I did also have to re-add my CSN, because that was also removed, and then my phone did an unprompted factory reset and rebooted.
By the way, when you flashed it, did you use Refurbish? Because with my demo unit, it refused to let me do that and would only allow chip erase. I was reluctant, but it turned out fine. And, the only important thing I was unable to reprogram afterwords was the S/N, but it doesn’t really matter to me. (Too bad the fingerprint scanner still doesn’t work though. That’s the only thing left that still isn’t working after all of this.)
Click to expand...
Click to collapse
I plan on testing every function to document what happens, so far I've done Refurbish, Partition DL, Dump, PDM and ChipErase. only Dump didn't work
Nice work fellas!!! Exciting to see some movement towards being able to root/development.
kaluna00 said:
Nice work fellas!!! Exciting to see some movement towards being able to root/development.
Click to expand...
Click to collapse
@KaptinBoxxi
BTW... How do you get to the hidden menu on the Verizon Varient?
kaluna00 said:
@KaptinBoxxi
BTW... How do you get to the hidden menu on the Verizon Varient?
Click to expand...
Click to collapse
I think its the same dial code. I don't have the device in front of me at the moment to say
I tried this earlier...
Post in thread 'LG Wing 5G Network option activation' https://forum.xda-developers.com/t/lg-wing-5g-network-option-activation.4285275/post-85116977
Am I using the wrong dial code for Verizon?
kaluna00 said:
I tried this earlier...
Post in thread 'LG Wing 5G Network option activation' https://forum.xda-developers.com/t/lg-wing-5g-network-option-activation.4285275/post-85116977
Am I using the wrong dial code for Verizon?
Click to expand...
Click to collapse
I have yet to have network work on my demo device regardless of what firmware is on it because my Serial Number and IMEI always come back at 0 and even if I manually enter new ones, it doesn't acivate, although i was able to get to the menu just fine with the standard code in that post.
Interesting, I wonder if there's something different in your firmware or kdz...
looking at the software version. mine is on
F100VM10i
maybe they (Verizon) patched out the hidden menu. your KDZ is labeled
F100VM10d
???
kaluna00 said:
looking at the software version. mine is on
F100VM10i
maybe they (Verizon) patched out the hidden menu. your KDZ is labeled
F100VM10d
???
Click to expand...
Click to collapse
I'm not sure what the final letter signifies, but F100V is verizon, yeah
KaptinBoxxi said:
I'm not sure what the final letter signifies, but F100V is verizon, yeah
Click to expand...
Click to collapse
think that represents the SW iteration identifier between updates... bit of a guess, but i believe that character has changed with updates.
I tried to crossflash my G8X to the US Open A11 software and screwed up quite badly during the process. I've had to restore my phone from having no partitions and do not have the original LUN5 files, only the 7 required for the crossflash. I've also rooted and installed twrp on this device so if anything that could help needs that I'm able to use it.
I expected the fingerprint sensor not to work, however now the light sensor, accelerometer, gyroscope, magnetometer, etc. don't work either.
Is there something I can do to get this functionality back? I've mostly given up on fixing the imei and network issues but I would like to at least have the phone in a usable state on Wifi.
If more details are needed please do tell and I will do my best to provide them.
Guille05 said:
I tried to crossflash my G8X to the US Open A11 software and screwed up quite badly during the process. I've had to restore my phone from having no partitions and do not have the original LUN5 files, only the 7 required for the crossflash. I've also rooted and installed twrp on this device so if anything that could help needs that I'm able to use it.
I expected the fingerprint sensor not to work, however now the light sensor, accelerometer, gyroscope, magnetometer, etc. don't work either.
Is there something I can do to get this functionality back? I've mostly given up on fixing the imei and network issues but I would like to at least have the phone in a usable state on Wifi.
If more details are needed please do tell and I will do my best to provide them.
Click to expand...
Click to collapse
What original firmware was on it?Most definitely,always make a full back up first thing.
Surgemanxx said:
What original firmware was on it?Most definitely,always make a full back up first thing.
Click to expand...
Click to collapse
It was originally on version 20p of the sprint software. And yeah, I definitely hadn't quite read up on all of the important things I needed to backup beforehand.
Guille05 said:
I tried to crossflash my G8X to the US Open A11 software and screwed up quite badly during the process. I've had to restore my phone from having no partitions and do not have the original LUN5 files, only the 7 required for the crossflash. I've also rooted and installed twrp on this device so if anything that could help needs that I'm able to use it.
I expected the fingerprint sensor not to work, however now the light sensor, accelerometer, gyroscope, magnetometer, etc. don't work either.
Is there something I can do to get this functionality back? I've mostly given up on fixing the imei and network issues but I would like to at least have the phone in a usable state on Wifi.
If more details are needed please do tell and I will do my best to provide them.
Click to expand...
Click to collapse
The same thing happened to me, I came from a10 sprint and installed a11 from Canada, I was left without a network and without a fingerprint sensor, but the other sensors work without problem, to fix network and ntcode I think it is only possible by box, I don't know if of the fingerprint sensor is caused by the lack of serial and imei.
if you come up with a solution let me know bro
mclarenf195 said:
The same thing happened to me, I came from a10 sprint and installed a11 from Canada, I was left without a network and without a fingerprint sensor, but the other sensors work without problem, to fix network and ntcode I think it is only possible by box, I don't know if of the fingerprint sensor is caused by the lack of serial and imei.
if you come up with a solution let me know bro
Click to expand...
Click to collapse
Did you restore your 7 bin files after flashing the A11 software?
Guille05 said:
Did you restore your 7 bin files after flashing the A11 software?
Click to expand...
Click to collapse
They don't have a backup,that's the reason I ask what version software it was.
Guille05 said:
It was originally on version 20p of the sprint software. And yeah, I definitely hadn't quite read up on all of the important things I needed to backup beforehand.
Click to expand...
Click to collapse
Use this firmware.It will correct your issues.
Download LG Firmware for LG G8X ThinQ LMG850QM _Unknown kdz stock USA Rom
Download _Unknown KDZ stock firmware for download with direct link
lg-roms.com
Guille05 said:
Did you restore your 7 bin files after flashing the A11 software?
Click to expand...
Click to collapse
I have the backup of the 7 partitions but they are useless if all the original partitions have been deleted, that is what I understand, I restored the partitions of a KDZ a10 and then flashed it to a11
Surgemanxx said:
Use this firmware.It will correct your issues.
Download LG Firmware for LG G8X ThinQ LMG850QM _Unknown kdz stock USA Rom
Download _Unknown KDZ stock firmware for download with direct link
lg-roms.com
Click to expand...
Click to collapse
I've got version 30c of that firmware installed, you think going back one update would fix it?
mclarenf195 said:
I have the backup of the 7 partitions but they are useless if all the original partitions have been deleted, that is what I understand, I restored the partitions of a KDZ a10 and then flashed it to a11
Click to expand...
Click to collapse
When you flashed the A10 kdz, you followed netmsm's guide right? Did you get any errors when flashing the partitions with fhloader? When I extracted the kdz a few files were missing from the ones used by that code but every kdz I've extracted doesn't have them either.
Guille05 said:
I've got version 30c of that firmware installed, you think going back one update would fix it?
Click to expand...
Click to collapse
Yes,go to 30b it will all work.I tried 30c on my sprint model,and had issues with network connectivity as well.
Surgemanxx said:
Yes,go to 30b it will all work.I tried 30c on my sprint model,and had issues with network connectivity as well.
Click to expand...
Click to collapse
I have the 30a, it would be to try
Guille05 said:
When you flashed the A10 kdz, you followed netmsm's guide right? Did you get any errors when flashing the partitions with fhloader? When I extracted the kdz a few files were missing from the ones used by that code but every kdz I've extracted doesn't have them either.
Click to expand...
Click to collapse
yes, the netmsm's guide, fhloader only use it to restore the luns, restore the kdz partitions one by one with qfil, just try what Surgemanxx suggested first and tell me how it goes.
mclarenf195 said:
yes, the netmsm's guide, fhloader only use it to restore the luns, restore the kdz partitions one by one with qfil, just try what Surgemanxx suggested first and tell me how it goes.
Click to expand...
Click to collapse
It works very well.I tried 30c,and noticed it was slow and laggy and rolled back to 30b and it worked flawless.Fingerprint scanning and all worked with a T-Mobile sim with no issues.They should be good with 30b,all but the IMEI issue they have.
All right I completely erased the flash again and reinstalled following the steps very carefully. I'm now on 30b and can confirm that the sensors work once again. Although the major issues I think were deeper than just the update, because I updated before doing a full erase and it still wasn't working. Now I just have to keep trying to fix the IMEI and FP sensor.
Also I think I may have found my IMEI number thanks to having the ftm partition backed up and therefore still having the serial number. The first 8 digits are always 35886110 for the LG G8x sprint model (and maybe others in the US), the next 6 are the last 6 digits of the serial and the last one is a check digit that you can look up online. I've checked the number on multiple sites and it seems legit so I hope it's actually my number. Now I'll try to write it to the phone somehow, but at least having the IMEI back is a very big step forward.
IMEI is fixed, or at least it appears as such in the phone. I went through with the tutty method of installing the IMEI, and after much trouble (and tutty saying error to my command to write the IMEI) I was able to restore the IMEI to the phone. I confirmed this first using EFS Pro and going into qualcomm NV tools. The IMEI was still as 0 in my phone but after putting in a sim it appeared in the OS and has stayed there. However it still appears as permanently locked when a sim is inserted and the nt-code error does still happen, so the network doesn't work yet.
Guille05 said:
IMEI is fixed, or at least it appears as such in the phone. I went through with the tutty method of installing the IMEI, and after much trouble (and tutty saying error to my command to write the IMEI) I was able to restore the IMEI to the phone. I confirmed this first using EFS Pro and going into qualcomm NV tools. The IMEI was still as 0 in my phone but after putting in a sim it appeared in the OS and has stayed there. However it still appears as permanently locked when a sim is inserted and the nt-code error does still happen, so the network doesn't work yet.
Click to expand...
Click to collapse
That LUNS backup is for the Sprint U.S. model G850UM9.The IMEI is stored in modemst1 and 2 which is LUNS5 that I didn't include for that reason.The NT Code error shouldn't be there if it's the same model/region.Keep me posted.
Surgemanxx said:
That LUNS backup is for the Sprint U.S. model G850UM9.The IMEI is stored in modemst1 and 2 which is LUNS5 that I didn't include for that reason.The NT Code error shouldn't be there if it's the same model/region.Keep me posted.
Click to expand...
Click to collapse
I've flashed your backups and the NT Code error indeed disappeared. However I've still got the perm locked error (so my doesn't work), and the fp sensor still refuses record fingerprints. Was your phone network unlocked when you made that backup? Idk if that maybe interferes with the sim or something
Guille05 said:
I've flashed your backups and the NT Code error indeed disappeared. However I've still got the perm locked error (so my doesn't work), and the fp sensor still refuses record fingerprints. Was your phone network unlocked when you made that backup? Idk if that maybe interferes with the sim or something
Click to expand...
Click to collapse
Yes,it was network unlocked for sure.You're not the only one that has faced this after trying to repair the IMEI.It's perma blocked because it's embedded in the chipset itself,and so far I haven't seen any fix for it as of yet.