Anyone have the issue where the SIM card isn't recognized? I'm on the RR newest ROM and the card isn't being recognized...I'm about to try the stock ROM and see how that goes.
Similar problem
I`m in a similar position I think. However, my phone recognizes the SIM but when checking the SIM-status the mobile radio seems to be off. I can´t change preferred network type, it just jumps back to "TD-SCDMA/GSM/WCDMA/LTE , I get no results when searching for mobile networks and when I use the *#*#4636#*#* - menu the "Turn on radio"-option wont respond. I`m on latest stock firmware and the phone is still displaying IMEI-numbers. I bought my unlocked European version of Oneplus X yesterday on an auction site, the seller has good reputation and he claims that it worked fine for him. I got a new SIM-card today thinking that would have solved the problem, no luck there however. I also did a hard reset and downgraded to an earlier version of a stock firmware and the error is still there. I noticed I had TWRP v.2.8.7.0 blu_spark r5 preinstalled when I bought it, its a custom kernel right? Could something related to the kernel be the root of the problem or the baseband? Any suggestions on what to do next?
Hi all!
I bought an S6 Edge second hand and after flashing a stock ROM, I had the "emergency only" calls issue, I tried everything I could find in the forums to no avail and I ended up taking it to a repair service. I did not think they could fix it but they did and I would like to know what they did to it in order to prevent it from happening again and to know if I can leave it as default (not custom OS) so that it can upgrade.
State of phone when bought:
So, the phone was working well with all carriers (from Colombia). The only thing I was able to notice after I bought it was that it was still on Marshmallow (6.0.1) with carrier branded stuff. It was in perfect shape otherwise.
So I downloaded a stock ROM and installed it using Odin. After this the phone would not let me make calls as it was not registering on the network. It did not even let me make emergency calls despite getting full bars of signal and being able to recognise the list of carriers when attempting to manually connect to them.
Important: The ROM downloaded was for the right version of the phone which was the G925i and the IMEI, serial number and baseband were not altered from the original. Also, I checked the phone to see if it was reported as lost/stolen and it was not (of this I'm sure because in Colombia you can consult a centralised database on any carrier's webpage). Also.. Here in Colombia it is illegal for carriers to lock phones.
Steps I took to fix it:
Downloaded ROMs for all carriers, branded and unbranded, I even installed one from Trinidad and Tobago and a LATAM one.
I performed all the tricks to disable and enable flight mode, location services, try con connect manually to the networks, changing to GSM only, GMS/CDMA, international roaming, etc.
I also extracted modem.bin from an earlier version and flashed the modem.bin with Odin (6.0.1 moden on 7.0, 5.1.1 moden on 6.0.1 and 5.1.1 moden on 7.0). All modems flashed correctly and the issue remained exactly the same.
So I finally gave up.. I installed the latest stock ROM which was an unbranded Nougat (7.0) version and took it to a repair service and they fixed it in a couple hours.
What I noticed after the phone was "repaired":
- The phone was rooted, SuperSu was installed, no other root app was installed.
- On SuperSu, there are entries for ADB shell (they all say Superuser command contents have not been logged for this entry) in a two minute timespan.
- The android version was downgraded to 6.0.1, I was told not to try to update it.
- Developer options was enabled with USB debugging turned on.
- The boot option (the one where you can wipe data and cache partition) was left as original (not the TWRP one).
- The ROM used to downgrade was the same I had before but only downgraded the version.
I suspect this same procedure was performed before on the phone but it had the original ROM carrier branded so it seems as if they installed a custom ROM, rooted it, connected with pc and performed some command line stuff to fix it, then cleaned the bootloader to a stock one.
The questions:
Any ideas what did the repairman do to fix the phone? Also, would it be safe to make a full backup with TWRP and flash again a stock ROM upgraded to 7.0 and then flash the backed up modem to get it working? Or would that possibly screw up the repair?
Thank you all in advance for any help. I'm sure there are lots of people out there experiencing the same "emergency only" issue I had but there does not seem to be a fix around, but clearly there is one! So I hope this sheds some light into what could possibly happen.
Hey guys,
since one week my phone doesn't connect to my mobile provider anymore, it says emergency calls all the time. When I restart my phone it requires the pin to unlock it - so my phone detects the SIM also the strength of the signal changes and I can also search for other providers but I can't connect to any of them. I've checked the SIM Card in another phone without problems. I did a reset of the connection settings but without any success.
It's making me crazy because im travelling right now and my mobile is pretty useless also I don't have a PC with me to reflash the ROM...
TWRP is flashed and the phone runs with Fulmics Rom 3.5
edit: after updating to Fulmics Rom 4.0 the mobile connection worked for a few hours but now it's the same problem again. I did a clean flash with a factory reset...
The Problem is resolved for OP. However, we are keeping it open just in case someone else runs into the same problem and wishes to discuss their issue.
Hello there fellows, i'll try to make my question simple. My uncle got a new phone so he threw away his old one which i took, its an LG V10 H901 its T-Mobile if i'm not mistaken, Anyways I'm out of Canada for a long time now and the phone is fully unlocked and runs on all the networks i was able to test, but its running android lollipop and i really upgrade to nougat, but from a previous experience with a Galaxy S6, upgrading just like that might lock back the network, and i have no idea if its the same case for this V10 too, as i am not in Canada anymore even contacting T-Mobile won't be that easy at all (tried before), so what i wanna know is, will the network get locked if i upgrade the Android ? as i'm going to do it manually since i can't receive OTA outside the region.
All informations are appreciated, and thanks in advance.
Edit: In T-mobile website where i enter the IMEI to see if my device is illegible for unlocking i got a congratulations saying my device can be unlocked.
- Also, The phone is rooted so my guess the bootloader should be unlocked right ? (Stock recovery btw). Now the weird part about that is that when i try to reboot to fastboot/bootloader from Terminal/ ADB/ Volume Down And USB/ Application With Root, there is no fastboot or bootloader i guess, i even found a similar post on the forums here but no answer for it too!
Now my guess that flashing the KDZ will flash all partitions and fix it but i am still afraid of the carrier lock!
In general, once a phone is unlocked, it stays unlocked forever as long as it disables the sim lock check in the phone and updating the software or doing factory reset doesn't change that. From what I have read and researched previously, the sim unlock status is stored and enforced via a certain partition on phone for example, in some phones it is nvram or nv data partition, the same partition that stores phone's IMEI number as well. It is not likely that you will loose sim unlock status just by updating to nougat.
But do keep in mind that that some of the LG V10 H901 T-Mobile versions have a korean motherboard where LG Bridge tries to update it with the wrong version of the rom bricking the phone, and people have reported here on XDA that even after unbricking they lost their IMEI info from the phone permanently and phone modem stops working.
I would suggest that you make sure which sub-variant of the H901 you have before you attempt to do any flashing, especially through LG UP.
I personally just bought a used H901 myself and was trying to decide if my phone is one of the ones with korean motherboard.
I'm puzzled ...
I have two G5s (the wife uses one), both are UK, carrier-free, and seem to be identical. One has OTA updated to Oreo, the other hasn't and shows no inclination to do so. There is one difference though, they run/ran slightly different versions of Nougat:
The one that updated was previously running v20v-EUR-XX. The one that won't runs v20r-234-10. I don't know what that build is. It has previously received incremental updates to Nougat with no problem. Is it somehow an invalid region to receive an Oreo update?
Both phones were bought used, so I don't know their exact history.
If it's not going to update OTA then I will try flashing the update. TBH there's almost too much information here about flashing ROMs - I'd like to know the simplest way to flash a stock ROM, I don't want a rooted phone (been there, done that, fun, but banking apps etc. I depend on won't run). My desktop & laptop run Linux, so Windows-based tools won't help (unless they'll run under Wine ).
TIA to anyone who can help me out here.
LG H850 Oreo Update
ONLY LG H850(GBR) and H850 (VDF) received the Oreo Update.
Thanks, so what region is 234-10? Doesn't seem to correspond to any listed ROMs.
Any pointers to the best simple no-frills flash guide?
Looks like yours have branding, check which operator folder you got in "cust" folder.
Thanks for the hint.
The cust folder contains stuff on all UK operators. I don't entirely understand how this info works, but in op_list.cfg is the line 23410,O2=/OP/TLF_COM, which I guess means it was originally O2 branded. There's no trace of anything O2 on it now, but it would have originally shipped with AOS 6, and had already received 7 when I got it. That upgrade probably dropped anything specific to O2.
Is there any way to hack this so it appears to be running generic EUR software, or do I have to manually flash it to get 8?
Thks
There is GB euro open version but when I tried on my EE g5 it install french orange "jeus" app plus crap from Vodafone Romania, on the top of that you will get pop up error every time you restart your mobile about wrong customisation or something like that , other than that I loved oreo. Because of above I revert back to original ee software and just checking for update. G5 is not my primary phone so I don't have pressure about. EE was always slow on updates so this is normal in that case,not sure about other UK operators.
The EUR-XX build runs OK on my other G5, it updated OTA. This phone with O2 region code is not on O2 any more - I don't think it was ever carrier locked, but must have been bought from O2 originally. So even if O2 builds do update OTA, presumably it will only happen if they've got O2 SIMs in - I don't really follow how all this stuff works!
How did you install the ROM you tried out? I'm still trying to understand what the various tools being touted actually do.
I have the same problem.
I have an H850 with an unlocked bootloader and rooted.
There is no OTA update.
When I check on https://imei.guru/ I get:
Model: LGABCD
Region: ABC
When I check on https://proimei.info/en/checker/lg I get:
SUFFIX AO2UTN
BUYER O2U
BUYERNAME O2
I can try LG Bridge but I don't want to cause any issues since I'm rooted and the bootloader is unlocked.
Do I ned to use LG UP instead? And will I lose my data?
Any suggestions very welcome.
Thanks
As you're already unlocked and rooted, it should be a simple matter to flash a new system ROM. AFAIK you won't have to lose data. It's when you unlock the boot loader that it wipes all data.
In my case I don't have root, and I don't want a rooted phone after an upgrade. I'd prefer not to have to wipe and restore if possible too, but I can't work out how to do that.
I downloaded kdz and flashed with lg up, you can try if you really want oreo before O2 release. In worse case you can wait, and it doesn't matter what sim is in the mobile, when update is ready you will receive notification, I got different sim in my old g5 and previous updates was downloaded and installed without any problems.
Ah, thanks for that, maybe I'll just wait for O2 to get their act together! I can't use LGUP as I don't run any Windows machines, I'm all Linux. The closest I can get is XP running in a VM, but even though I can map a USB port into the VM it still doesn't recognize either of my devices. Uppercut doesn't help either .
konio25 said:
I downloaded kdz and flashed with lg up, you can try if you really want oreo before O2 release. In worse case you can wait, and it doesn't matter what sim is in the mobile, when update is ready you will receive notification, I got different sim in my old g5 and previous updates was downloaded and installed without any problems.
Click to expand...
Click to collapse
Which LG UP did you use?
Because this thread recommends not using LG UP and using UPPERCUT instead.
However, VirusTotal shows lots of issues:
https://www.virustotal.com/#/file/d...366b6643a5922cd3b09a3b1a9296b8c0a8f/detection
and so I would prefer to use LG UP instead, if it's compatible with H850.
Thanks
I can't remember exactly which LGUP I used, I tried a couple. A bit worrying about the virus reports in uppercut, one advantage of running in a VM, I can always just trash the image and go back to the previous state.
As I understand uppercut, it doesn't replace LGUP, just tries to fix some device detection issues then launches LGUP to do the actual update. But that still didn't work
No Expert said:
Which LG UP did you use?
Because this thread recommends not using LG UP and using UPPERCUT instead.
However, VirusTotal shows lots of issues:
https://www.virustotal.com/#/file/d...366b6643a5922cd3b09a3b1a9296b8c0a8f/detection
and so I would prefer to use LG UP instead, if it's compatible with H850.
Thanks
Click to expand...
Click to collapse
Hi,
I used version 1.14.3 (apparently this is the latest).
I flashed my g5 H850 several times as I wasn't sure if this bloatware from VDF Romania and french operator Jeux wasn't a issue of incorrect files. After all exercises i back to original EE soft.
All that with LG UP. I tried to use uppercut but my antivirus report as well on this so I don't bother and just use LG up.
konio25 said:
Hi,
I used version 1.14.3 (apparently this is the latest).
I flashed my g5 H850 several times as I wasn't sure if this bloatware from VDF Romania and french operator Jeux wasn't a issue of incorrect files. After all exercises i back to original EE soft.
All that with LG UP. I tried to use uppercut but my antivirus report as well on this so I don't bother and just use LG up.
Click to expand...
Click to collapse
Thank you.
Did you use the LG UP from here: https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
Because I that's the version I used but unfortunately on my PC it cannot detect my phone.
I'm not sure from where I downloaded, when I was looking for latest version I just search through google. Are you sure you have all drivers installed? Did you plug in your phone in download mode?
konio25 said:
Did you plug in your phone in download mode?
Click to expand...
Click to collapse
Ah - helpful tip! Because of the other messing around I'd been doing, it was in debug mode, D'oh I've got further, but still baulking.
From other threads re. XP and VMs, I found I needed to install an XP USB 3 driver, and switch to a USB virtual port in the VM. With all that, launching LGUP 1.14 via Uppercut the phone is detected and I can start an upgrade process.
It reboots the phone, which then displays the Firmware Update screen, but stays resolutely on 0%. LGUP shows "Build : U" as the step with progress at 4%. After 11 minutes it times out with a popup saying "Error: 0x2000 [ERROR] RX Timeout : 3.0". The barely readable little console window on the phone starts off with some info about the phone, then changes to simply "633E 1B00" after a couple of minutes.
I've tried using both physical USB 2 & USB 3 ports on the PC.
Any ideas?
Thks
Try to use lg up without uppercut, maybe your pc is a bit slow on vm. Once i startet flashing with lg up the whole process take about 5 min. Do you have hdd or ssd on your pc? Also check if there is no restriction for vm regarding size, make sure drive space is big enough. Also try to assign at least 2gb of ram for vm and if you have multi core cpu try to assign at least two cores. I believe if you will tweak settings on your vm it should be good to go. Check for vm tools update if needed update to latest.
LGUP without Uppercut doesn't work, it won't recognise the device. That's the only reason I downloaded Uppercut to start with.
I'm pretty convinced it's a USB connectivity problem. When the phone reboots there's no USB, then the USB interface comes up again, and LGUP has to continue talking to it in firmware-update mode. There are issues with the way the USB device is being captured by the VM. For some reason the MTP interface is still exposed to the host even though VBox says it's captured by the guest. In VBox terms this shouldn't happen, an interface is either accessible to the host, or is mapped to the guest and invisible to the host.
MTP is a bit of a weird beast though, and I think there's some black magic going on with the way this Linux (Ubuntu 18.04) is grabbing MTP devices. I've been trying to turn off every rule relating to Vendor 1004, Device 633e, as well as defaults, but it still has some magic default that means it spots an MTP device. I'm sure this is blocking proper communication through to the XP guest OS.
I shall keep tinkering ...
Well, I got it to work! I could not stop the host from seeing the USB interface, no mater how much of MTP I disabled, but the solution was to disconnect and re-connect the USB device to the VM, after the phone rebooted into flashing mode and LGUP was waiting to re-connect. I did it a couple of times, second time the connection to LGUP succeeded, and flashing completed in 3 - 4 mins.
Well that's it done on my spare slightly-broken test phone - I collect these things! - (took it from AOS 6 to 8), now to take a deep breath and do it on my real device I depend on. Time to back everything up again