Related
I did a clean install via fastboot. Version mumber is MPD24.107-52.
Although runinng or bike riding, total distance is always equal to zero.
Google Maps or other gps apps are neither working. They keep saying "Looking for GPS signal".
Someone else with same problem?
After OTA i didn't get this problem. Try reflash it
Enviado desde mi XT1563 mediante Tapatalk
I apparently fixed this problem by running the following commands:
fastboot erase modemst1
fastboot erase modemst2
I treid that, but it does not look like it fixed the issue for me...
EDIT: Sorry, it seems to have worked after all, but GPS seems a little worse than before the 6.0.1 Update...Is there a chance of finding an alternate Mode file for the X Play? This was easy for Samsung devices, they usually had hundreds of Modem files linked, but I can't seem to find a collection for the x Play...
Just out of curiosity...is there any reason not to flash the 6.0 modem file on 6.0.1?
EDIT: I just flashed the non-hlos.bin from the 6.0 RETEU release, and it worked, did not lose dual sim or anything.
It's still showing the baseband as EMEA_DSDS_Cust though . Not sure about better reception or anything yet, but it appears to be compatible at least.
EDIT2: While everything seems to be working perfectly, the battery stats show a completely red status for mobile signal since I flashed the modem. This is strange, since I really don't notice any actual reception problems...I'll see if it's gone tomorrow...
Same issue here
I have the same problem here after installing a 6.0.1 OTA update. Let me know if you find an solution. It's now near impossible to use navigation and to track my exercises.
I am running all stock. I just bought a LG Watch Urbane 1st gen earlier this week. I am all caught up with OTAs for both phone and watch. But I keep getting a "Unfortunately, Bluetooth Share has stopped." error message ON the watch only. Bluetooth is constantly disconnecting and reconnecting the watch. I used my old Note 3 and same problem so I am tempted to blame the watch. I have factory reset the watch over 20 times. I have done same with my Nexus 6P but only twice.
Is it possible to roll back from 7.0 (NRD90M) to latest 6.0.1 (MTC20F)? I am thinking if I could try this, I might find out if my new watch will be more stable under MM. Feel free to comment.
Flash the latest factory image from this site
https://developers.google.com/android/nexus/images
That will roll you back to MM
Thanks! Will do that now. It seems any changes made in the Android Wear app crashes the bluetooth connection. I can't tell if it crashes on the phone and affects the watch or just crashes on the watch alone. And I do not use bluetooth on my phone for anything else so I can't tell how stable my bluetooth has been on my phone to begin with.
Thank you kingmikel! It worked fine once I unlocked bootloader, etc. I reverted successfully to latest MM version for Nexus 6P. I waited for all default apps to catch up with updates. I installed Android Wear. Made sure watch was unpaired/reset. Guess what? Same freaking issue. So now I am stuck with pretty much two things: version of software/build on LG Watch Urbane and version of Android Wear that could be creating this issue. I am blaming either or both unless someone can think of something else.
Download the MM stock firmware and extract all of it to a folder. Then open a cmd/terminal in the download folder (shift and right click in windows I believe, just right click and there will be a option in linux).
Then do these steps in order BACK UP YOUR APPS!!
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
The names will be a little different, and if you want twrp put it in place of the stock recovery!
PS: Don't flash userdata
Thanks TnT_! I got it done with the factory image. But I came across same instructions you posted in case things become difficult. For newbies like me, it's all about patience and making sure the steps are taken EXACTLY as described in the instructions! It's funny because I always came across typos in instructions which eventually leads to not working at all. It's absolutely rare if not ever that I got a typo leading me to doing something really bad. what I mean is that if there is a typo, commands or steps will just not work, period. Now start coming up with your own content with someone else's instructions is definitely a recipe for disaster. I have been around here since the Note 1st generation days and did some pretty dumb things as I learned the hard way. But, knock on wood, never killed any device for good. Always revived them with XDA's help if I ended up bricking it.
So my GPS was acting up (losing signal like every 30 seconds) and I tried to fix it by deleting modemst1 and modemst2 via fastboot, but after I did that my phone no longer recognizes my SIM card.
I've seen other people have the same problem but their IMEI dissapears while mine is still intact, does anyone know how may I fix this? I don't have an EFS backup btw (I know, I'm a retard)
extraterra1 said:
So my GPS was acting up (losing signal like every 30 seconds) and I tried to fix it by deleting modemst1 and modemst2 via fastboot, but after I did that my phone no longer recognizes my SIM card.
I've seen other people have the same problem but their IMEI dissapears while mine is still intact, does anyone know how may I fix this? I don't have an EFS backup btw (I know, I'm a retard)
Click to expand...
Click to collapse
Never restore an EFS to a Moto device... It doesn't work.
Never heard of issues related to erasing modemstX partitions.
What system version and build?
acejavelin said:
Never restore an EFS to a Moto device... It doesn't work.
Never heard of issues related to erasing modemstX partitions.
What system version and build?
Click to expand...
Click to collapse
Right now I have 6.0 MPH24.49-18 (downloaded from here https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833) but when all of this started I had the latest crDroid 7.1.2 build.
I've flashed like 3 different ROMs but the issue persists.
extraterra1 said:
Right now I have 6.0 MPH24.49-18 (downloaded from here https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833) but when all of this started I had the latest crDroid 7.1.2 build.
I've flashed like 3 different ROMs but the issue persists.
Click to expand...
Click to collapse
Flash 18-8 and OTA to 18-16...
There is no known software issue on this device with GPS, not sure how to help. Have you considered it maybe a hardware issue?
acejavelin said:
Flash 18-8 and OTA to 18-16...
There is no known software issue on this device with GPS, not sure how to help. Have you considered it maybe a hardware issue?
Click to expand...
Click to collapse
Do you know where I can find the flashable 18-8? Thanks in advance
Honestly at this point idgaf about the GPS Issues, I just want the radio to work again:crying:
extraterra1 said:
Do you know where I can find the flashable 18-8? Thanks in advance
Honestly at this point idgaf about the GPS Issues, I just want the radio to work again:crying:
Click to expand...
Click to collapse
All firmware images are flashable with fastboot... Check https://firmware.center
I have had a moto g6 plus for some time now, but nowadays I am not able to detect SIM cards and wifi does not turn on, what is happening?
Wellfare11 said:
I have had a moto g6 plus for some time now, but nowadays I am not able to detect SIM cards and wifi does not turn on, what is happening?
Click to expand...
Click to collapse
Can you tell us more?
How did it start?
Did something happen to it, or did you just notice it is not connecting?
The most easy things first, is your sim card correctly in place?
Which ROM are you on and have you reflashed it?
weazie said:
Can you tell us more?
How did it start?
Did something happen to it, or did you just notice it is not connecting?
The most easy things first, is your sim card correctly in place?
Which ROM are you on and have you reflashed it?
Click to expand...
Click to collapse
The phone started with problems since I upgraded to Android Pie, I have taken care of it very well but I do not know if it is a hardware failure, but note that in baseband turns out to be unknown, I installed several stock roms from fastboot without any success, also I thought it would be a problem of the EFS partition, but everything is fine I even took a backup in case the doubts, what could happen?
Wellfare11 said:
The phone started with problems since I upgraded to Android Pie, I have taken care of it very well but I do not know if it is a hardware failure, but note that in baseband turns out to be unknown, I installed several stock roms from fastboot without any success, also I thought it would be a problem of the EFS partition, but everything is fine I even took a backup in case the doubts, what could happen?
Click to expand...
Click to collapse
Did you originally update via OTA, meaning, was it the official update?
Then when you noticed it's not working, you tried to flash several stock ROMs?
One possible problem that comes to mind, is that for some reason, you have the wrong radio/modem firmware. That can happen for example, if you have flashed a ROM, which is not meant for your region.
weazie said:
Did you originally update via OTA, meaning, was it the official update?
Then when you noticed it's not working, you tried to flash several stock ROMs?
One possible problem that comes to mind, is that for some reason, you have the wrong radio/modem firmware. That can happen for example, if you have flashed a ROM, which is not meant for your region.
Click to expand...
Click to collapse
Yes, upgrade to Android pie via OTA
I already put a stock rom of the same region, following each fastboot command one by one, but everything continues the same, I even installed RROS 7, to see if at least it turned on the wifi, and it is in bootloop.
Wellfare11 said:
Yes, upgrade to Android pie via OTA
I already put a stock rom of the same region, following each fastboot command one by one, but everything continues the same, I even installed RROS 7, to see if at least it turned on the wifi, and it is in bootloop.
Click to expand...
Click to collapse
Go with the modding guide index: how to restore stock ROM etc., and flash a stock ROM that you know will work. Flash the radio/modem file too, and make sure it's the correct one.
Just to say, I had connection problems too, and in the end they were because the sim card did not latch correctly in place i.e. was not correctly in place.
weazie said:
Go with the modding guide index: how to restore stock ROM etc., and flash a stock ROM that you know will work. Flash the radio/modem file too, and make sure it's the correct one.
Just to say, I had connection problems too, and in the end they were because the sim card did not latch correctly in place i.e. was not correctly in place.
Click to expand...
Click to collapse
I already tried, I installed the rom corresponding to the model of the cell phone and the wifi still does not work, the base band is still unknown, I also checked if the sim card was correctly placed, and everything is fine
weazie said:
Go with the modding guide index: how to restore stock ROM etc., and flash a stock ROM that you know will work. Flash the radio/modem file too, and make sure it's the correct one.
Just to say, I had connection problems too, and in the end they were because the sim card did not latch correctly in place i.e. was not correctly in place.
Click to expand...
Click to collapse
I have an idea, but I need someone to help with a backup of the files, Radio, Modem, and Persist to flash in twrp
Wellfare11 said:
I have an idea, but I need someone to help with a backup of the files, Radio, Modem, and Persist to flash in twrp
Click to expand...
Click to collapse
Great that you have an idea. ?
Here's an idea: take a backup of your current config in twrp, move it to the computer, take a copy. Replace the files in that copy with the ones that you want to flash.
Did you mean this? You are aware that you can try different radio/modem files through fastboot, not having to flash everything else every time? That said, go with your idea. ?
weazie said:
Great that you have an idea.
Here's an idea: take a backup of your current config in twrp, move it to the computer, take a copy. Replace the files in that copy with the ones that you want to flash.
Did you mean this? You are aware that you can try different radio/modem files through fastboot, not having to flash everything else every time? That said, go with your idea.
Click to expand...
Click to collapse
I already tried and still does not give results curiously I have noticed that even in bootloader shows, Baseband not fund
Wellfare11 said:
I already tried and still does not give results curiously I have noticed that even in bootloader shows, Baseband not fund
Click to expand...
Click to collapse
Does the phone ask for a pin code at any point?
weazie said:
Does the phone ask for a pin code at any point?
Click to expand...
Click to collapse
does not request any code at any time
Wellfare11 said:
does not request any code at any time
Click to expand...
Click to collapse
Ok, but WiFi should work even if there is no mobile data available.
I probably can't help at this point, apologies! My suggestion is to flash a stock ROM, lock the bootloader and send the phone for repairs. There could be a solution to this, but I'm out of ideas. ?*
weazie said:
Ok, but WiFi should work even if there is no mobile data available.
I probably can't help at this point, apologies! My suggestion is to flash a stock ROM, lock the bootloader and send the phone for repairs. There could be a solution to this, but I'm out of ideas. *
Click to expand...
Click to collapse
from what I see, if there is no baseband it does not detect the sim card and it does not turn on the wifi, I will try to force an OTA retail update
it did not work
Wellfare11 said:
from what I see, if there is no baseband it does not detect the sim card and it does not turn on the wifi, I will try to force an OTA retail update
it did not work
Click to expand...
Click to collapse
Hello, colud you solve the problem? Because I am havig a very similar one...
Hello group friends, I'm new here. I have a similar problem, I was using the Havoc 2.4 rom, when upgrading to 2.6 I no longer recognize my SIM card and the wi-fi does not connect, I can not install another rom anymore, nor rom stock, recovery TRWP has been replaced by the Havoc and the Wipe System function does not work, and for a few days you can not stay in recovery mode anymore, it restarts every 3 seconds, not the time to click the options. Can someone help me. I'm without a cell phone, and I need it.
I have a similar issue after flashing the latest firmware. SIM goes to "SIM locked" every ten seconds or so, and Wifi drops at the same tie. It's like networking is being reset every 10 seconds. No network settings I've tried change that.
I've flashed several stock ROMs; the one I had previously, newest, oldest, both for RETEU and retail. I used Lenovo restore to upgrade but that resulted in soft brick, after that I flashed the latest firmware via Fastboot and that's when the problem started.
With Oreo, wifi and cellular don't work at all, nothing detected. With Pie they're connected and dropped in a loop. I can't help thinking that the Lenovo restore broke this somehow, but modem files have been reflashed several times after that with no change. I'm not getting the baseband error.
bitstuff said:
I have a similar issue after flashing the latest firmware. SIM goes to "SIM locked" every ten seconds or so, and Wifi drops at the same tie. It's like networking is being reset every 10 seconds. No network settings I've tried change that.
I've flashed several stock ROMs; the one I had previously, newest, oldest, both for RETEU and retail. I used Lenovo restore to upgrade but that resulted in soft brick, after that I flashed the latest firmware via Fastboot and that's when the problem started.
With Oreo, wifi and cellular don't work at all, nothing detected. With Pie they're connected and dropped in a loop. I can't help thinking that the Lenovo restore broke this somehow, but modem files have been reflashed several times after that with no change. I'm not getting the baseband error.
Click to expand...
Click to collapse
I have the exact same problem, I wasn't able to repair it so I sent it to service and tomorrow they will try to fix it for $35. The problem with goign back to previous versions is that you loose the IMEI and MAC . The problem with the pie version I believe is the baseband. If the service is able to fix it I will post the solution here for you to fix it .
bitstuff said:
I have a similar issue after flashing the latest firmware. SIM goes to "SIM locked" every ten seconds or so, and Wifi drops at the same tie. It's like networking is being reset every 10 seconds. No network settings I've tried change that.
I've flashed several stock ROMs; the one I had previously, newest, oldest, both for RETEU and retail. I used Lenovo restore to upgrade but that resulted in soft brick, after that I flashed the latest firmware via Fastboot and that's when the problem started.
With Oreo, wifi and cellular don't work at all, nothing detected. With Pie they're connected and dropped in a loop. I can't help thinking that the Lenovo restore broke this somehow, but modem files have been reflashed several times after that with no change. I'm not getting the baseband error.
Click to expand...
Click to collapse
Service couldn't fix it. Being honest they were quite incompetent, when I explained the problem he said "we should hire you" ( I am 16 years old) . Anyway, could you fix it? Because I am not even close
---------- Post added at 03:00 AM ---------- Previous post was at 02:54 AM ----------
caradobeco said:
Hello group friends, I'm new here. I have a similar problem, I was using the Havoc 2.4 rom, when upgrading to 2.6 I no longer recognize my SIM card and the wi-fi does not connect, I can not install another rom anymore, nor rom stock, recovery TRWP has been replaced by the Havoc and the Wipe System function does not work, and for a few days you can not stay in recovery mode anymore, it restarts every 3 seconds, not the time to click the options. Can someone help me. I'm without a cell phone, and I need it.
Click to expand...
Click to collapse
Sorry I answer so late, I didn's see the message before.
I believe you already tried puting it into bootloader mode. If that's the case, I had a similar problem recently an it solved alone, I let it loop for a while and suddenly fell, into dtock recovey, i factory reset (with stock recovery) and somehow stock was booted ( i believe it was because it was in inactive slot).
Hope this helps you
juampapo546 said:
Service couldn't fix it. Being honest they were quite incompetent, when I explained the problem he said "we should hire you" ( I am 16 years old) . Anyway, could you fix it? Because I am not even close
---------- Post added at 03:00 AM ---------- Previous post was at 02:54 AM ----------
Sorry I answer so late, I didn's see the message before.
I believe you already tried puting it into bootloader mode. If that's the case, I had a similar problem recently an it solved alone, I let it loop for a while and suddenly fell, into dtock recovey, i factory reset (with stock recovery) and somehow stock was booted ( i believe it was because it was in inactive slot).
Hope this helps you
Click to expand...
Click to collapse
I am still working on this, I actually did this to a work phone (I had permission to root/unroot). Something that has helped me so far is just getting familiar with the whole flashing process - https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/. I think from this article the problem lies in the modem/radio rom. That *should* be the only thing you need to flash on. However, I have noticed with a lot of roms on here, a modem rom is not included on the stock firmware. But that needs to match well to your phone from what I understand. I have tried a few modem roms already, unfortunately, but no luck.
Hi, I have to say I didn't expect that this would be such a ride when I got into this. I am now simply trying to have a working phone again.
I will briefly sum up what I've done so far :
So I got a brand new V20 a few weeks ago with the intention to root it and install a custom rom. It came as a H91010l with a security patch from dec 2016.
I got everything ready it took a while but then went ahead and followed this guide [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151
A few minor hicups on the way but I got the bootloader unlocked, twrp installed and then LOS 18.1. I thought everything would be fine and I didn't make a backup... It worked well except that I had no mobile data (French carrier SFR), only sms worked and also some notification issues.
After a break and looking for solutions I tried another OS tonight (/e/) and the same issues were present. No mobile network.
It's not to do with the APN (which I made sure was configured properly) but likely some incompatibility after tweaking the system with the root procedure. Maybe something to do with US996 files being used.
So I decide that I needed to go back to stock since I wouldn't find a solution from there and I did a wipe before flashing a stock US996 firmware in TWRP taken in this thread, the US99610f - SPL 2016-12-01
Result : I lost the fast boot and TWRP, the phone is stuck on the LG logo.
Only one thing works at this point, firmware update download mode, so I did a full partition dl flash of the following H91510e_00_VTR_CA_OP_1205 kdz which according to many posts should be fine. Nope, it doesn't boot it's stuck on the LG logo.
I have tried a second one that is old, US99610f_00_1205 kdz which should work too. It boots and I get into setup but it reboots within a minute/30s on top of being really slow.
So what I'm looking for right now is a solution to go back to stock. I have no backup and no root. I can only use LGUP. And it seems that my model is pretty non cooperative. What can I do ?
Thank you.
I was going to follow the instructions in this post and install the F800K10e.kdz but the lg-firmwares.com website is limiting me to 2 files per 24h so I decided to give the H91510e_00_VTR_CA_OP_1205.kdz another go. It wouldn't boot again until I formatted the data, it seems to be working so far.
I'm sure this is some noobie knowledge but most posts/guides didn't say to do that and I am indeed a beginner. I will update this thread with information on what I do next if relevant and if I can get my mobile data working somehow.
Edit : SMS work, 4G works but the sim card crashes when I call or get called.
Unfortunately I didn't even try my sim card when I got the phone so maybe it was the same onthe H91010l. Looks like I'll have to redo the unlocking procedure and continue fixing this mess.
Edit 2 : Notifications don't work properly either like on the custom roms... For example skype messages.
Xanvast said:
Hi, I have to say I didn't expect that this would be such a ride when I got into this. I am now simply trying to have a working phone again.
I will briefly sum up what I've done so far :
So I got a brand new V20 a few weeks ago with the intention to root it and install a custom rom. It came as a H91010l with a security patch from dec 2016.
I got everything ready it took a while but then went ahead and followed this guide [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151
A few minor hicups on the way but I got the bootloader unlocked, twrp installed and then LOS 18.1. I thought everything would be fine and I didn't make a backup... It worked well except that I had no mobile data (French carrier SFR), only sms worked and also some notification issues.
After a break and looking for solutions I tried another OS tonight (/e/) and the same issues were present. No mobile network.
It's not to do with the APN (which I made sure was configured properly) but likely some incompatibility after tweaking the system with the root procedure. Maybe something to do with US996 files being used.
So I decide that I needed to go back to stock since I wouldn't find a solution from there and I did a wipe before flashing a stock US996 firmware in TWRP taken in this thread, the US99610f - SPL 2016-12-01
Result : I lost the fast boot and TWRP, the phone is stuck on the LG logo.
Only one thing works at this point, firmware update download mode, so I did a full partition dl flash of the following H91510e_00_VTR_CA_OP_1205 kdz which according to many posts should be fine. Nope, it doesn't boot it's stuck on the LG logo.
I have tried a second one that is old, US99610f_00_1205 kdz which should work too. It boots and I get into setup but it reboots within a minute/30s on top of being really slow.
So what I'm looking for right now is a solution to go back to stock. I have no backup and no root. I can only use LGUP. And it seems that my model is pretty non cooperative. What can I do ?
Thank you.
Click to expand...
Click to collapse
If you did not make a dump backup there is not much you can do that I know of. You can try and delete the modemst1 and modemst2 and see if that fixes your no signal issue.
hold vol down plug phone into computer USB cable.
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
restart phone into os see if that fixes the issue.
If so make a backup of you EFS in twrp and save it.
Your EFS got corrupted when you flashed the stock KDZ to root the H910 happen to me also. This would explain why your phone is crashing and no signal.
Darnrain1 said:
If you did not make a dump backup there is not much you can do that I know of. You can try and delete the modemst1 and modemst2 and see if that fixes your no signal issue.
hold vol down plug phone into computer USB cable.
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
restart phone into os see if that fixes the issue.
If so make a backup of you EFS in twrp and save it.
Your EFS got corrupted when you flashed the stock KDZ to root the H910 happen to me also. This would explain why your phone is crashing and no signal.
Click to expand...
Click to collapse
I didn't flash any kdz to root initially. I just started flashing stuff once I lost my bootloader and TWRP. I managed to have the H91510e working that's where I'm at currently as per the second post. I will try and root it again following this procedure soon. I have to look into why I can't call or get called first. We'll see what happens, but according to this thread I will lose mobile network when I root the H915 version. I'll see when I get there.
Xanvast said:
Hi, I have to say I didn't expect that this would be such a ride when I got into this. I am now simply trying to have a working phone again.
I will briefly sum up what I've done so far :
So I got a brand new V20 a few weeks ago with the intention to root it and install a custom rom. It came as a H91010l with a security patch from dec 2016.
I got everything ready it took a while but then went ahead and followed this guide [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151
A few minor hicups on the way but I got the bootloader unlocked, twrp installed and then LOS 18.1. I thought everything would be fine and I didn't make a backup... It worked well except that I had no mobile data (French carrier SFR), only sms worked and also some notification issues.
After a break and looking for solutions I tried another OS tonight (/e/) and the same issues were present. No mobile network.
It's not to do with the APN (which I made sure was configured properly) but likely some incompatibility after tweaking the system with the root procedure. Maybe something to do with US996 files being used.
So I decide that I needed to go back to stock since I wouldn't find a solution from there and I did a wipe before flashing a stock US996 firmware in TWRP taken in this thread, the US99610f - SPL 2016-12-01
Result : I lost the fast boot and TWRP, the phone is stuck on the LG logo.
Only one thing works at this point, firmware update download mode, so I did a full partition dl flash of the following H91510e_00_VTR_CA_OP_1205 kdz which according to many posts should be fine. Nope, it doesn't boot it's stuck on the LG logo.
I have tried a second one that is old, US99610f_00_1205 kdz which should work too. It boots and I get into setup but it reboots within a minute/30s on top of being really slow.
So what I'm looking for right now is a solution to go back to stock. I have no backup and no root. I can only use LGUP. And it seems that my model is pretty non cooperative. What can I do ?
Thank you.
Click to expand...
Click to collapse
I know what's wrong. You cant use lineageos to make calls on AT&T network. You can get internet but no VoLTE. So your going to have to use a deblaoted Stock Oreo rom if you want a rooted phone with phone calls.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
Darnrain1 said:
I know what's wrong. You cant use lineageos to make calls on AT&T network. You can get internet but no VoLTE. So your going to have to use a deblaoted Stock Oreo rom if you want a rooted phone with phone calls.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
Click to expand...
Click to collapse
Thanks for your reply. I am using SFR, a French carrier. Is it the same issue ?
There has been developments since my last post. I started from the H91510e like I said and followed the [ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED) guide by runningnak3d supported by a video from NewTechBegins. It went well until the flashing from TWRP.
I think it was my mistake to do like the video and flash h910-10r.rar followed by Magisk-v19.0. This resulted in not being able to boot, I kept getting the secure boot with password even after formatting. And after a couple of times it turned into a green screen crash. I couldn't get to recovery either for some reason even though I'm sure it was still there. The corruption warning message would appear almost instantly at boot and not allow me to do the volume down + power shortcut, and fastboot reboot recovery would not work either.
Reflashing the H91510e with LGUP worked but the system was particularly slow at first, it seemed to do better after a few minutes. Going over everything again, the part where we boot into recovery for the first time ended up the same with a green screen crash.
What seems to have solved it is to flash boot1.img from the root package in this [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151, which is different from the boot without extension of the other guide. I also reflashed the recovery several times, it didn't change anything until this.
I will continue updating this thread with the results of what follows next. I just have to install the h91010r now and manage to get to setup.
Edit : I just installed the h91010r with having wiped + formatted before and formatted after, it still goes into secure boot...
Xanvast said:
Thanks for your reply. I am using SFR, a French carrier. Is it the same issue ?
There has been developments since my last post. I started from the H91510e like I said and followed the [ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED) guide by runningnak3d supported by a video from NewTechBegins. It went well until the flashing from TWRP.
I think it was my mistake to do like the video and flash h910-10r.rar followed by Magisk-v19.0. This resulted in not being able to boot, I kept getting the secure boot with password even after formatting. And after a couple of times it turned into a green screen crash. I couldn't get to recovery either for some reason even though I'm sure it was still there. The corruption warning message would appear almost instantly at boot and not allow me to do the volume down + power shortcut, and fastboot reboot recovery would not work either.
Reflashing the H91510e with LGUP worked but the system was particularly slow at first, it seemed to do better after a few minutes. Going over everything again, the part where we boot into recovery for the first time ended up the same with a green screen crash.
What seems to have solved it is to flash boot1.img from the root package in this [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151, which is different from the boot without extension of the other guide. I also reflashed the recovery several times, it didn't change anything until this.
I will continue updating this thread with the results of what follows next. I just have to install the h91010r now and manage to get to setup.
Click to expand...
Click to collapse
I would flash Auto_Debloat you get Oreo Debloat rom.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
But to answer your question a lot of cell carriers are going to VoLTE only and LOS does not have that on the H910.
I made Auto_Debloat so if you need help just let me know.
Darnrain1 said:
I would flash Auto_Debloat you get Oreo Debloat rom.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
But to answer your question a lot of cell carriers are going to VoLTE only and LOS does not have that on the H910.
I made Auto_Debloat so if you need help just let me know.
Click to expand...
Click to collapse
I added an edit at the bottom of my post, it displays the warning really quick and goes into secure boot everytime. Could it be that the h910-10r.rar package you shared at the end of the thread is not identical to the original post ? It simply won't boot into setup for me. Any ideas ?
I will try installing something quick tonight to have a working system with recovery I'm done messing around for the day. I will look into your custom rom in the coming days thanks for your help !
Xanvast said:
I added an edit at the bottom of my post, it displays the warning really quick and goes into secure boot everytime. Could it be that the h910-10r.rar package you shared at the end of the thread is not identical to the original post ? It simply won't boot into setup for me. Any ideas ?
I will try installing something quick tonight to have a working system with recovery I'm done messing around for the day. I will look into your custom rom in the coming days thanks for your help !
Click to expand...
Click to collapse
Yes your data partition is encrypted still. You need to format it in twrp.
Darnrain1 said:
Yes your data partition is encrypted still. You need to format it in twrp.
Click to expand...
Click to collapse
That's the thing, it still goes into secure boot after formatting it.
So I flashed the boot1 again and twrp to be safe, it now doesn't display the warning anymore but goes into the green screen crash after a minute or so.
I'm now back to twrp, I'll just wipe everything and install LOS to try. If at least it has mobile data that would be more than before.
Xanvast said:
That's the thing, it still goes into secure boot after formatting it.
So I flashed the boot1 again and twrp to be safe, it now doesn't display the warning anymore but goes into the green screen crash after a minute or so.
I'm now back to twrp, I'll just wipe everything and install LOS to try. If at least it has mobile data that would be more than before.
Click to expand...
Click to collapse
Yes you need a kernel. Your still running stock kernel that's why your getting the green screen.
Darnrain1 said:
Yes you need a kernel. Your still running stock kernel that's why your getting the green screen.
Click to expand...
Click to collapse
Oh I see now, so it's indeed not the same package. That is why you had to flash H910_BTTF-mk2000.zip
Thanks for your time and patience.
I installed LOS 18.1 and it works fine with 4G this time (before reading your reply). Unsurprisingly calls in and out make the phone kernel crash with a black screen. I really like LOS and android 11, is there something I can do to make calls work ? Like flashing another kernel ? Does /e/OS have the same issue ?
If not I can absolutely live without calls for the moment, no problem.
Edit : I'm not getting notified of messages for Discord/Skype and not getting the call if the app is not open actively. Seems like it's not running the services in the background.
Xanvast said:
That's the thing, it still goes into secure boot after formatting it.
So I flashed the boot1 again and twrp to be safe, it now doesn't display the warning anymore but goes into the green screen crash after a minute or so.
I'm now back to twrp, I'll just wipe everything and install LOS to try. If at least it has mobile data that would be more than before.
Click to expand...
Click to collapse
It's complicated,
Xanvast said:
Oh I see now, so it's indeed not the same package. That is why you had to flash H910_BTTF-mk2000.zip
Thanks for your time and patience.
I installed LOS 18.1 and it works fine with 4G this time (before reading your reply). Unsurprisingly calls in and out make the phone kernel crash with a black screen. I really like LOS and android 11, is there something I can do to make calls work ? Like flashing another kernel ? Does /e/OS have the same issue ?
If not I can absolutely live without calls for the moment, no problem.
Click to expand...
Click to collapse
Yep your welcome, no problem. You may just need to setup LOS with your network provider. Do a google search for APN carrier settings for your cell provider. Take care.
Darnrain1 said:
It's complicated,
Yep your welcome, no problem. You may just need to setup LOS with your network provider. Do a google search for APN carrier settings for your cell provider. Take care.
Click to expand...
Click to collapse
That's the first thing I've done, I entered the APN settings from this page (3), and the results reported are from after. So do you know about other OS like /e/, any that would not behave the same ? Or anything I can flash on top to fix it ?
Have a good evening.
Xanvast said:
That's the first thing I've done, I entered the APN settings from this page (3), and the results reported are from after. So do you know about other OS like /e/, any that would not behave the same ? Or anything I can flash on top to fix it ?
Have a good evening.
Click to expand...
Click to collapse
I am in the USA so it's in the afternoon for me.
You may want to try and flash you EFS from fastboot mode.
Manually reinstall your EFS on the Lgv20.
You need to find your Original DUMP of the rom your Lgv20 phone was on, before you downgraded your firmware for rooting.
Note: COM21 is what ever com port you were using at the time.
Reboot into fastboot mode
With the phone powered off hold the down vol and plug in usb to computer.
Info on what the files are
/fsg
A backup of your modemst1 and modemst2 files. So if you erase modemst1 and modemst2 /fsg should restore the partitions automatically. But if /fsg is corrupted then it will not restore them.
/misc
This partition contains miscellaneous system settings.
/modemst1 /modemst2
Modemst1 and modemst2 store information like IMEI.
fastboot flash fsg fsg_COM21
fastboot flash misc misc_COM21
fastboot flash modemst1 modemst1_COM21
fastboot flash modemst2 modemst2_COM21
fastboot reboot
Darnrain1 said:
I am in the USA so it's in the afternoon for me.
You may want to try and flash you EFS from fastboot mode.
Manually reinstall your EFS on the Lgv20.
You need to find your Original DUMP of the rom your Lgv20 phone was on, before you downgraded your firmware for rooting.
Note: COM21 is what ever com port you were using at the time.
Reboot into fastboot mode
With the phone powered off hold the down vol and plug in usb to computer.
Info on what the files are
/fsg
A backup of your modemst1 and modemst2 files. So if you erase modemst1 and modemst2 /fsg should restore the partitions automatically. But if /fsg is corrupted then it will not restore them.
/misc
This partition contains miscellaneous system settings.
/modemst1 /modemst2
Modemst1 and modemst2 store information like IMEI.
fastboot flash fsg fsg_COM21
fastboot flash misc misc_COM21
fastboot flash modemst1 modemst1_COM21
fastboot flash modemst2 modemst2_COM21
fastboot reboot
Click to expand...
Click to collapse
Unfortunately as stated in my first post, I have no backup of the state of the phone when I got it as a H91010l. I didn't do one either while on the H91510e because I didn't see the point, it was already modified and calling didn't work.
Thank you for the explanation.
Something I'd like to mention for other readers is that there is one main visible difference between the first root (from H91010l with the old guide) and second one (H91510e with newer guide). The first time the warning message with the red triangle during boot was very distorted and duplicated. It was unreadable. Now it is clear. I don't know enough to say what was causing it or point at what made 4G work in the second case but this was something worth noting.
Alright, going into this de-Googling trip I did not know that many apps relied on Google Play Services to work and the Google cloud services, Firebase cloud etc... to send their notifications. I had no idea that Google was managing the notifications for most of the world and so much more. That only reinforces my desire to get away from it.
So these apps like Discord, Skype and others that don't send notifications it's directly because of the lack of Google Play Services. I noticed today that MicroG has a Cloud Messaging option but I will not enable it.
Signal works fine without any of it. I also found Skype Lite to send notifications so that's what I'll use from now on. Discord is going into the trash. I've read that Telegram is supposed to work too. So another problem solved. I have no issues making concessions on my convenience to be freer.
A website I came across which references how apps behave without Google : https://plexus.techlore.tech/
Darnrain1 said:
It's complicated,
Xanvast said:
Oh I see now, so it's indeed not the same package. That is why you had to flash H910_BTTF-mk2000.zip
Thanks for your time and patience.
I installed LOS 18.1 and it works fine with 4G this time (before reading your reply). Unsurprisingly calls in and out make the phone kernel crash with a black screen. I really like LOS and android 11, is there something I can do to make calls work ? Like flashing another kernel ? Does /e/OS have the same issue ?
If not I can absolutely live without calls for the moment, no problem.
Edit : I'm not getting notified of messages for Discord/Skype and not getting the call if the app is not open actively. Seems like it's not running the services in the background.
Click to expand...
Click to collapse
Yep your welcome, no problem. You may just need to setup LOS with your network provider. Do a google search for APN carrier settings for your cell provider. Take care.
Click to expand...
Click to collapse
I took photos of my Kernel crashes, now it doesn't just happen with calls, which I could live with but also while using Skype Lite and looking out of the app for example, when I'm doing something taxing for the device or sometimes the phone would just reboot. Several times a day.
It seems to be very similar to what is mentioned in this post. Do you or anybody think that I should do the same and flash h915freedommobilemodem.img ? How do I go about it if so ? Is that something you do in fastboot ?
Also what are the risks if it goes bad ? I'm tired of dealing with repairing the mess and I'd like to avoid more problems.
Thanks.
Xanvast said:
I took photos of my Kernel crashes, now it doesn't just happen with calls, which I could live with but also while using Skype Lite and looking out of the app for example, when I'm doing something taxing for the device or sometimes the phone would just reboot. Several times a day.
It seems to be very similar to what is mentioned in this post. Do you or anybody think that I should do the same and flash h915freedommobilemodem.img ? How do I go about it if so ? Is that something you do in fastboot ?
Also what are the risks if it goes bad ? I'm tired of dealing with repairing the mess and I'd like to avoid more problems.
Thanks.
Click to expand...
Click to collapse
If I am not mistaken your running LineageOS. I would ask in that post for help. I run Stock Oreo on my H910 because everything works.
[OFFICIAL] LineageOS 18.1 for the LG V20
Darnrain1 said:
If I am not mistaken your running LineageOS. I would ask in that post for help. I run Stock Oreo on my H910 because everything works.
[OFFICIAL] LineageOS 18.1 for the LG V20
Click to expand...
Click to collapse
Yes the post is in that thread. I didn't have this problem the first time I used LOS 3 weeks ago so I assume it has to do with the green screen crash caused by the kernel I didn't flash after the h910-10r.rar. So it's still unaddressed in my opinion. Should I go ahead and flash that missing kernel or the H915 modem ? I don't know what's the difference and both seem plausible.
It's fine if you aren't sure and I will end up asking there.