search

Suicide-Squirrel / issues_pie

LG G4 stuff has been completely moved here: https://github.com/LGgFour
8 stars 0 forks source link

vs986: no RIL/cell service on Verizon networks #41

Closed steadfasterX closed 3 years ago

steadfasterX commented 5 years ago

original report: https://forum.xda-developers.com/showpost.php?p=79380937&postcount=176

I am not able to test vs986 ROMs due to the fuses it blows on booting my h815 so this cannot be solved without help (mainly flashing and catching logs)

if you wanna help:

https://forum.xda-developers.com/showpost.php?p=79491366&postcount=191

chat / help / communication

https://webchat.freenode.net/ channel: #carbonfusion-user

say my nick there (steadTAB, ENTER)

I am there from Mo-Fr, 9am - 5pm (UTC +2)

refs

steadfasterX commented 5 years ago

ok .. do you have telegram? or signal? or IRC? or Gtalk? ICQ?

ANDROID2468 commented 5 years ago

ok .. do you have telegram? or signal? or IRC? or Gtalk?

nope, I don't.

steadfasterX commented 5 years ago

https://webchat.freenode.net/ channel: #carbonfusion-user

say my nick there (steadTAB, ENTER)

ANDROID2468 commented 5 years ago

ril_stock.txt

ANDROID2468 commented 5 years ago

ril_los.txt

ANDROID2468 commented 5 years ago

ril_los2.txt

ANDROID2468 commented 5 years ago

ril_los3.txt

ANDROID2468 commented 5 years ago

ril_los4.txt

steadfasterX commented 5 years ago

thanks mate.

Now I need a full logcat on STOCK as well:

http://bit.do/logcat --> in step 3 choose option A) once you got cell service

and still on STOCK:

adb shell getprop > getprop.txt (will be stored in your local dir)

ANDROID2468 commented 5 years ago

well Sh**, I forgot to remove my password before I did my backup. :( well I guess I have to start from fresh now.

ANDROID2468 commented 5 years ago

@steadfasterX here you go: getprop.txt full.txt

steadfasterX commented 5 years ago

well Sh**, I forgot to remove my password before I did my backup. :( well I guess I have to start from fresh now.

next time: https://www.howtogeek.com/240657/how-to-fix-pin-errors-after-restoring-from-twrp-android-backups/ ;)

ANDROID2468 commented 5 years ago

Thanks, I will definitely need that guide in the future. 😊

steadfasterX commented 5 years ago

Thanks, I will definitely need that guide in the future.

are u avail now? if so.. webchat :) I am online the next 7 hours there..

other then that we need this for the next test: download: http://leech.binbash.it:8008/lineage/oreo/vs986-UsU/experimental/rilblobs5_qmi.tgz

ANDROID2468 commented 5 years ago

logs: logcat.txt ril_los_qmi.txt

ANDROID2468 commented 5 years ago

here

logcat.txt ril_los_qmi.txt

ANDROID2468 commented 5 years ago

ril_los_qmi-and-no4.txt

steadfasterX commented 5 years ago

ok next:

ANDROID2468 commented 5 years ago

ok next:

* download and flash and boot it:
  http://leech.binbash.it:8008/lineage/oreo/vs986-UsU/experimental/lineage_vs986_usu_201908081516.zip

* then also download:
  http://leech.binbash.it:8008/lineage/oreo/vs986-UsU/experimental/rilblobs_full_2ba.tgz

* exec :
adb root
adb remount
adb push rilblobs_full_2ba.tgz /sdcard/Download/
adb shell
setenforce 0
tar xvzf /sdcard/Download/rilblobs_full_2ba.tgz
strace -y -f -a 120 -s 200 -tt -p 1 2>&1 | egrep "faccessat|fstatat64|openat|denied|fail" > /sdcard/Download/ril_los_2ba.txt &
(do not forget the ampersand at the end)
logcat -b all -c
(will clear the logcat)
stop real-ril-daemon
start real-ril-daemon
(wait ~30s)
exit
adb pull /sdcard/Download/ril_los_2ba.txt
adb logcat -b all -d -D > logcat.txt
* share ril_los_2ba.txt and logcat.txt

logcat.txt ril_los_2ba.txt

MB3hel commented 5 years ago

@steadfasterX and @ANDROID2468 If it would help to have another device I have a VS986 that is not my primary phone (I'll flash whatever on it).

steadfasterX commented 5 years ago

@steadfasterX and @ANDROID2468 If it would help to have another device I have a VS986 that is not my primary phone (I'll flash whatever on it).

sure any help is appreciated. It is not necessary to have results from both of you (unless I mention) so if I request something then feel free to reply if @ANDROID2468 hasn't already. If you have telegram or IRC it would help as well. Also it would be good if you have FWUL ready when needed

numericOverflow commented 5 years ago

@steadfasterX any update on VS986 BLOBs, or something you need help testing at this point? I'm definitely willing to help if possible. 👍

tullyp commented 5 years ago

@steadfasterX ,I would like to volunteer to help with this also. This is my primary phone, but I would do what I can.

tullyp commented 5 years ago

So happy. Latest update of @steadfasterX lineage-16.020191106-Unofficial-vs986... working on my phone with full Verizon cell service. So far everything I use works. Banking, text, phone, maps, etc. only two days so far, but never could get previous update of this Pie to work on cell at all let alone N, or ,O.

steadfasterX commented 5 years ago

So happy. Latest update of @steadfasterX lineage-16.020191106-Unofficial-vs986... working on my phone with full Verizon cell service. So far everything I use works. Banking, text, phone, maps, etc. only two days so far, but never could get previous update of this Pie to work on cell at all let alone N, or ,O.

uhm... wtf?! wow.. thx for reporting but could you pls share your firmware version of the bootloader + modem (if you don't know: what was the last stock firmware flashed)?

@numericOverflow , @ANDROID2468 can you confirm that?

tullyp commented 5 years ago

I was on stock USU'd marshmallow. Use 207 latest twrp. Only thing I did different this time is I flashed and booted without google apps. Waited for a while 5-10 minutes, and it worked got signal. Had to turn off wireless also. Flashed gapps after. Tell me how to post a screen shots and I will. Works in both Global settings and Lte, cdma settings.

I have not posted over at main forum because someone else claimed to get it to work several versions ago, and when I PM d to him got no response. So did not know if worked for anyone else.

It is VERY much faster than my 6.0 and runs much cooler. I was using Kernal Audetor to stop 3 cores to keep cool.

steadfasterX commented 5 years ago

I was on stock USU'd marshmallow. Use 207 latest twrp. Only thing I did different this time is I flashed and booted without google apps. Waited for a while 5-10 minutes, and it worked got signal. Had to turn off wireless also. Flashed gapps after. Tell me how to post a screen shots and I will. Works in both Global settings and Lte, cdma settings.

I have not posted over at main forum because someone else claimed to get it to work several versions ago, and when I PM d to him got no response. So did not know if worked for anyone else.

It is VERY much faster than my 6.0 and runs much cooler. I was using Kernal Audetor to stop 3 cores to keep cool.

nope no one with verizon network was able to get it working yet. the users where it works do not use verizon but the vs986.

could you pls do and provide a TWRP backup just with:

attaching files is just drag & drop or click on the text

image

tullyp commented 5 years ago

@steadfasterX, Bootloader and Firmware TWRP file zipped is 77MB. I can only attach up to 10 MB. Anything else I can do?

steadfasterX commented 5 years ago

@steadfasterX, Bootloader and Firmware TWRP file zipped is 77MB. I can only attach up to 10 MB. Anything else I can do?

the attachment hint was meant for screenshots as you wanted to add one. anyways for the backup itself just use e.g. https://workupload.com/ or https://www.sendspace.com/ or your google drive or whatever else you like

tullyp commented 5 years ago

2015-01-02--14-57-50_lineage_vs986_usu-userdebug_9_PQ3A190801002.zip

Here is Bootloader zip alone...I think. I'll try Firmware next if this worked. Firmware much bigger.

tullyp commented 5 years ago

Nope, Firmware still too big.

steadfasterX commented 5 years ago

Nope, Firmware still too big.

what do you mean by too big? I gave you 2 examples above which allows 300 MB which is fully enough?!

tullyp commented 5 years ago

Sorry, did not see your comment above. You will get these. Just busy right now with other things as you.

tullyp commented 5 years ago

screen shot InkedScreenshot_20191111-112146_Settings (1)_LI

tullyp commented 5 years ago

Here is a link to my Twrp file in google drive. Tell me if worked. First time used link.

https://drive.google.com/file/d/1-ak5np9g_T7XBSeCQn6yQSLeoVssQLbQ/view?usp=drivesdk

ANDROID2468 commented 5 years ago

@steadfasterX I'm downloading the LOS 16 firmware right now to check. well, This was unexpected.

numericOverflow commented 5 years ago

Hmmm... I installed lineage-16.020191106-Unofficial-vs986 and I've got no voice calling, only LTE data, same as all previous builds. FYI - my "About Phone" version info matches the screenshot shown 3 comments above.

Is it possible (safe) for me to flash tullyp's bootloader & firmware files attached to this ticket over the top of my device to see if I can replicate his success?

ANDROID2468 commented 5 years ago

@numericOverflow same here ;( but this is good news! we got one person with a VS986 with working RIL/cell service. we just got to figure out how his works.

steadfasterX commented 5 years ago

Is it possible (safe) for me to flash tullyp's bootloader & firmware files attached to this ticket over the top of my device to see if I can replicate his success?

That's what I wanna check asap..

tullyp commented 5 years ago

@Numericoverflow. I have full voice cell use. If you are in USA I'll call you on my number. Xxx 335-0281

tullyp commented 5 years ago

Btw, anyone know why twrp always name files as in 2015? I changed name od backup to 2019.

steadfasterX commented 5 years ago

@tullyp many thanks for your help here. while I have a clue already why it is working for you could you pls do this:

  1. TWRP backup of "BL unlock state"
  2. starting SALT and doing a screenshot of the main window (just hide the IMEI there)

The first is more important but beware that this will contain your IMEI so maybe share the link by a PM on XDA or Telegram. If you are too scared sharing that with me I can give you the linux(!) commands you could do instead.

TWRP pie should show the correct time but you have to boot once into Android and set the time there correctly. If it still does not show the correct time in TWRP just boot to TWRP and share the recovery log

tullyp commented 5 years ago

@steadfasterX, Did you get my BL unlock State file I PM'd in XDA?

Here is screenshot you requested.

Don't know if this matters: Had a scare that I lost cell service after entering "download mode" and getting this screenshot. Several phone restarts before I did this screenshot I had checked the box in "Developer Options" for "advanced start", but it did not show with other options in any previously restarts. Well after I did this screenshot, the options to enter ""recovery and fastboot" did show up in power menu, and phone would not show cell service. I unchecked "advance boot" and I am back with service. Don't know if this is a coincidence or matters. But I'm not about to recheck that box. SALT screenshot 11 12 19

steadfasterX commented 5 years ago

@steadfasterX, Did you get my BL unlock State file I PM'd in XDA?

yes thx! you can remove it from there !

Here is screenshot you requested.

thx! ok that IS weird..

Don't know if this matters: Had a scare that I lost cell service after entering "download mode" and getting this screenshot. Several phone restarts before I did this screenshot I had checked the box in "Developer Options" for "advanced start", but it did not show with other options in any previously restarts. Well after I did this screenshot, the options to enter ""recovery and fastboot" did show up in power menu, and phone would not show cell service. I unchecked "advance boot" and I am back with service. Don't know if this is a coincidence or matters. But I'm not about to recheck that box.

well ok THAT is weird.. I cannot think of a context but hey.. @ANDROID2468 , @numericOverflow feel free to test that approach (enabling, disabling advanced restart in dev options)

It would be great to grab a adb logcat -b all -c (requires root or adb root before) adb logcat -b all while re-producing this.

@tullyp : sorry to bother you that much but it is really strange whats going on here and you are the only one where it works.. could you do a boot logging? as described here: https://bit.do/logcat --> option C) FULL BOOT log (requires Linux / FWUL)

ANDROID2468 commented 5 years ago

@steadfasterX nope, still nothing. here is a log anyways... log1.txt

numericOverflow commented 5 years ago

@steadfasterX - "Advanced start" disable/enable did nothing for me either. I don't have immediate access to a computer with ADB installed while at work, so I don't have a log, but I can get on later today if you still want it.

steadfasterX commented 5 years ago

Ok .. I expected that.. Thx for trying this anyways. Maybe the boot log will help . It's really weird tbh..

tullyp commented 5 years ago

Ok, I took a chance and rechecked the "advanced start". After about 15 seconds I had cell service again, so that was a false flag. Sorry.

I have not used FWUL in a long time, so have to update it and work on it, but I will be going on a trip for next two days so doubt Ill have log until after I return.

ANDROID2468 commented 5 years ago

@tullyp BTW, you don't have to use FWUL. you can use any Linux distro like the one from your screenshot you took earlier ;)

MB3hel commented 5 years ago

Probably not really all that helpful at this stage, but I flashed the latest build and its not working for me either. If there's anything I can do the help just let me know. Its a good sign that it works for someone.