So, recently, I've been struggling with a strange issue which I think that it's a hardware issue. Let me explain you all the things I've done so far.
I was on LOS 14.1 and wanted to go back to stock rom. I had used Nougat for long time and never used stock MM on my G4. I just wanted to give MM a try. Maybe it could give me better battery life and performance. I don't know.
Since I have an UsU'd H815, I properly flashed stock mm boot, mm system, mm modem and then the UsU H815 baseband. However, when the device boots, I got "com.android.phone stopped" warning all the time. Then I went into recovery mode, flashed UsU mm boot and stock MM modem. Now, I got cellular working, set up everything but then I realized that camera didn't work this time. So, basically,
Stock boot + stock modem + UsU baseband = no cellular - camera works
UsU boot + stock modem + stock baseband = cellular works - no camera
Stock boot + stock modem + stock baseband = must crash with blue screen. But now, it just boots and everything works except cellular
Thinking that since I had on LS991 bootloader and maybe it is necessary for both baseband and the bootloader to be the same model/version, I flashed LS991 baseband. During boot animation, the phone got an instant reboot. I don't remember if it booted to either that blue modem crash screen or android system. Most probably it was Android system. Anyway, cellular didn't work anymore.
I've flashed whole backup (except aboot, laf, raw_resources) that I had created with SALT before UsU'ing my device. Still no luck. I always get null imei from *#06# and unknown baseband. When I launch hidden menu (*#546368*#815#), I also get force close on SVC Test > Version info. The information there about baseband, hw version, and NT code say that 'should be implemented'. So far, I think that it's a hardware issue.
Well, but with
Code:
cat /data/loggers/modem**a file including modem in its name**
, I see my IMEI and factory version. Somehow, some things recongize my imei number. I also see my imei on imei screen (power off the phone and hold down vol -, vol +, and the power button at the same time until it gets into imei screen).
I tried erasing modemst1, modemst2, and fcg which a reboot followed that proccess as it's stated and confirmed by some others to work here (ofc I restored my backup, still no luck).
Everything made me think that it was a software issue until I see this thread. The screenshot that the op shared on his 2nd post is same with mine. It says null for everything. And his 8th reply and the 3rd option I listed above (Stock boot + stock modem + stock baseband) makes me think that this is totally a hardware issue. Why the 3rd option makes me think that this is a hardware issue is that some/a part is damaged on the main board, and the device/chip/whatever cannot connect to it. Thus, cellular service cannot start, and since it cannot start, the things that must be going wrong with modem just go well.
I feel like I'm ready to try anything (which won't make it completely dead) to get cellular work on my G4, including flashing LS991's ARB 2 TOT file. I'm open to new thoughts and ideas.
Edit: So, according to my researches, I have found out that RX Module is about cellular (@madiweb also stated that on his 8th post on his thread I linked above). I've checked the service manual of H815. It is told there that if there is no gsm/wcdma/lte signal, RX Module (EAT62994301) has to be replaced. I'll ask to LG Customer Care and surely will add info here for the ones who need it.
berkantkz said:
[....]
Thinking that since I had on LS991 bootloader and maybe it is necessary for both baseband and the bootloader to be the same model/version, I flashed LS991 baseband.
[....]
Edit: So, according to my researches, I have found out that RX Module is about cellular (@madiweb also stated that on his 8th post on his thread I linked above). I've checked the service manual of H815. It is told there that if there is no gsm/wcdma/lte signal, RX Module (EAT62994301) has to be replaced. I'll ask to LG Customer Care and surely will add info here for the ones who need it.
Click to expand...
Click to collapse
I never wrote anywhere that you should flash a baseband of another device. Just think about it: I have created for every model its very own baseband package. Why should I do that when you could cross flash them? Wouldn't make sense right? The main reason (while there are others) is: ARB and signature checking within the modem files. I knew it from VS986 which also heavily uses the ARB "feature" in their firmwares: when you flash a modem firmware of the vs986 to the h815 it will break signal forever. The same may apply to others liek the LS991 which also makes heavy use of the ARB "feature" in their firmwares.
The ONLY way I know to recover from here (for the h815) is replacing the hardware (or in my case faking the device as bootloop affected and sending it to LG for repair). I cannot tell you which one blows the fuse but maybe it is that module you found above.
.-
steadfasterX said:
I never wrote anywhere that you should flash a baseband of another device. Just think about it: I have created for every model its very own baseband package. Why should I do that when you could cross flash them? Wouldn't make sense right? The main reason (while there are others) is: ARB and signature checking within the modem files. I knew it from VS986 which also heavily uses the ARB "feature" in their firmwares: when you flash a modem firmware of the vs986 to the h815 it will break signal forever. The same may apply to others liek the LS991 which also makes heavy use of the ARB "feature" in their firmwares.
The ONLY way I know to recover from here (for the h815) is replacing the hardware (or in my case faking the device as bootloop affected and sending it to LG for repair). I cannot tell you which one blows the fuse but maybe it is that module you found above.
.-
Click to expand...
Click to collapse
So, my G4 tour ends here. I'd make it bootlooped and send to LG for repair. However, it has been more than 2 years, and the warranty time is 24 months. So, I am out of warranty. Instead of repairing this device, I guess I would buy something new.
Thank you for your help. Fortunately, G4 community have a person like you!
Related
Hey guys,
Does anyone know how we can get the rollback number on our devices? I was reading this thread here:
http://forum.xda-developers.com/g4/...wngrade-g4-t3197675/post62748057#post62748057
I guess you need to know your rollback number to do a KDZ becasue there is a chance of a hard brick. I tried the numbers highlighted below but it didn't work for Verizon. Anyone know how we could get this information?
waylo said:
This was not written anywhere specifically on the LG G4 forums that I could find. But every flash-addict needs to be warned. It is something you want to know before you continue tinkering.
Several users (myself included) have made the unfortunate mistake of attempting to downgrade their bootstack (for various reasons) to a former version.
DO NOT DO THIS (at least for the USA T-Mobile H811 version, and possibly other USA versions, per @autoprime)! It will result in a hard brick! Specifically, this results in the "Qualcomm QDLoader HS-USB port ( 9008 )" error. Connecting your phone to a PC will pop up with this active connection, but nothing else. There is no download mode. There is no publicly available fix as of yet.
This WILL happen both through KDZ restore as well as flashing bootstack .zips.
Yes, an official KDZ image can BRICK your USA phone, if you try to rollback.
This is in stark contrast to other manufacturers (i.e. Samsung), where the attempt to flash an older bootloader/modem/radio will simply fail, but your phone is not bricked.
I have conferred with @autoprime, who confirmed that with each OTA firmware release (on T-Mobile it was 10H, and now 10N), the version # increments. Flashing a lower version # will result in brick.
I have searched far and wide for a DIY fix. Without the proper firmwares in the right format, as well as the right flashing software, your phone is done and must be sent in for LG repair.
To check what antiroll-back version you are on, input this sequence in the dialer (T-Mobile and ATT) and scroll down:
*#*#244773825625#*#*
Flashing a bootstack version less than this # (through KDZ or zip) will brick the phone. You are free to flash anything equal or higher than the version listed.
Click to expand...
Click to collapse
sefirosu0522 said:
Hey guys,
Does anyone know how we can get the rollback number on our devices? I was reading this thread here:
http://forum.xda-developers.com/g4/...wngrade-g4-t3197675/post62748057#post62748057
I guess you need to know your rollback number to do a KDZ becasue there is a chance of a hard brick. I tried the numbers highlighted below but it didn't work for Verizon. Anyone know how we could get this information?
Click to expand...
Click to collapse
If you are still on the original software version 10b, then you have v0. If you took the OTA (or flashed the KDZ) to 11a, then you have v1.
We have a new OTA out now, 12a. I'm not sure what version that one is, but I'm willing to bet it is v2, and you will not be able to rollback if you install it.
laurasaurisrex said:
If you are still on the original software version 10b, then you have v0. If you took the OTA (or flashed the KDZ) to 11a, then you have v1.
We have a new OTA out now, 12a. I'm not sure what version that one is, but I'm willing to bet it is v2, and you will not be able to rollback if you install it.
Click to expand...
Click to collapse
Yeah right now I'm stuck with 11A and I'm not sure what I should do. Even though my phone sucks the way it runs, I'm gonna hang in there and wait a couple weeks. See what comes out of 12A.
Well I don't believe there is a way to check or there is a known way of finding it yet. Apparently there is an APK app that reads it. Perhaps we can rip it from another rom and access the APK via the same method we do for accessing the Themes (using a launcher to do custom shortcuts).
The inability to KDZ back to original software is ridiculous. Just like 12A and the broken notifications. How stupid is it to force broken updates yet make it impossible to go back to previous backup/software. I am half tempted to just take the 12A update and force Verizon to give me another phone just to emphasize my dislike for their method of locking the system down.
I have a question that might be simple to answer, but i need confirmation because i don't want to brick my device recklessly.
When i got my Moto Z play, i immediatley unlocked it, flashed TWRP and installed LineageOS. So my device (including bootloader and baseband) are still on the state it arrived i guess. But my OS ist the newest LineageOS (so android 7.1.2).
My Moto Z play is an XT1635-02 32GB (bootloader adds P7 as variant), software channel must be RETEU.
My bootloader is C0.14 (from 2016-07-11)
and my baseband is M8953_10208.08.04-47e (bootloader says M8953_10208.08.04.47R ADDISON_ROW_CUST)
Are there newer versions of baseband (which might more important) and booloader? And can i flash them without problems?
Just flashing the NON-HLOS.bin in fastboot and i'm fine? Can i also use the 7.0-modem from RETAIL?
Sorry, these questions might be dumb and too careful for old users, but i'm only used to nexus devices and i am scared of bricking my Z play! Nexus factory images always had baseband and bootloader version written in the filename so it was easy to find out if you need to update. In addition there was just one "software channel" which made it hard to brick a device or flash something wrong.
McFlypants said:
I have a question that might be simple to answer, but i need confirmation because i don't want to brick my device recklessly.
When i got my Moto Z play, i immediatley unlocked it, flashed TWRP and installed LineageOS. So my device (including bootloader and baseband) are still on the state it arrived i guess. But my OS ist the newest LineageOS (so android 7.1.2).
My Moto Z play is an XT1635-02 32GB (bootloader adds P7 as variant), software channel must be RETEU.
My bootloader is C0.14 (from 2016-07-11)
and my baseband is M8953_10208.08.04-47e (bootloader says M8953_10208.08.04.47R ADDISON_ROW_CUST)
Are there newer versions of baseband (which might more important) and booloader? And can i flash them without problems?
Just flashing the NON-HLOS.bin in fastboot and i'm fine? Can i also use the 7.0-modem from RETAIL?
Sorry, these questions might be dumb and too careful for old users, but i'm only used to nexus devices and i am scared of bricking my Z play! Nexus factory images always had baseband and bootloader version written in the filename so it was easy to find out if you need to update. In addition there was just one "software channel" which made it hard to brick a device or flash something wrong.
Click to expand...
Click to collapse
I'm running the original bootloader and baseband from 6.0.1 without any issue, so I would suggest leaving it.
I don't want to get on the wrong side of you but that wasn't my question.
I wanted to know this because i'm not sure if i get the most out of my phone with an older baseband. I can't use VoLTE for example which possibly is activated with a newer baseband. Or it might improve the signal.
McFlypants said:
I don't want to get on the wrong side of you but that wasn't my question.
I wanted to know this because i'm not sure if i get the most out of my phone with an older baseband. I can't use VoLTE for example which possibly is activated with a newer baseband. Or it might improve the signal.
Click to expand...
Click to collapse
Well I'll suggest you only flash the baseband that comes with your specific firmware, if you flash the baseband from another firmware package you will end up without a IMEI and you'll have a expensive brick, which you will send to me so I can use the screen to get my mzp working again. That will be payment for warning you
Good one, flashallthetime
Back in, uh, I think Atrix time or even HTC Desire it was normal to flash/change radio baseband. It supposed to improve radio, prolong battery life... In reality, most of the time didn't do anything, sometimes broke something...
So in theory, you can do that. Should be fine but I wouldn't recommend.
If you have to, to get VoLTE, I would make a backup of the current rom, follow guide to flash back to stock and then restore backup. But be extremely careful, so many users over here bricked their devices. As far as I can see, downgrading and the accepting OTA.
Sent from my LG-V940n using Tapatalk
flashallthetime said:
Well I'll suggest you only flash the baseband that comes with your specific firmware, if you flash the baseband from another firmware package you will end up without a IMEI and you'll have a expensive brick, which you will send to me so I can use the screen to get my mzp working again. That will be payment for warning you
Click to expand...
Click to collapse
Good idea, please return it to me afterwards if it's working! :good:
Hi guys i recently bought a refurb phone and i want to unlock it and put some custom rom but i cant identify the real model of this device. i also tried opening the back and see if it has some model print on the motherboard but its not there i think. so ill put the pics of relevant info on my phone to help to identify it so thanks a lot for those who can help i would appreciate it
You must take out the motherboard. It is written on the backside
thanks its there turns out i have an 810 variant. Any tips for me to install marshmallow on my phone and usu it? because on my version of the device i cant update thru system updates its still on LP. should i flash stock 810 rom and update to marshmallow that way?
kukel21 said:
thanks its there turns out i have an 810 variant. Any tips for me to install marshmallow on my phone and usu it? because on my version of the device i cant update thru system updates its still on LP. should i flash stock 810 rom and update to marshmallow that way?
Click to expand...
Click to collapse
First thing is check your kdz version that you have installed - use steadfasterX's SALT program to do this. It will also establish your ARB version (must be less than or equal to 2 - if not, i.e., if greater than 2, UsU is a no-go in your case). It will also let you know your GPT compatibility to show you what custom roms versions you can install.
Once that is ascertained, if you are rooted, re-install your stock LP kdz first (important), then proceed to upgrade to Marshmallow (MM) using LG Bridge first (download from LG site, it will sometimes work when OTA doesn't). If that doesn't work, you'll have to download an MM kdz for your model and carrier and upgrade it with LGUP-NEW. Then, once you have stock MM installed, do at least a partial backup with SALT before proceeding to unlock with steadfasterX's UsU method. Make sure you read and understand the OP completely there.
sdembiske said:
First thing is check your kdz version that you have installed - use steadfasterX's SALT program to do this. It will also establish your ARB version (must be less than or equal to 2) - if not, i.e., if greater than 2, UsU is a no-go in your case). It will also let you know your GPT compatibility to show you what custom roms versions you can install.
Once that is ascertained, if you are rooted, re-install your stock LP kdz first (important), then proceed to upgrade to Marshmallow (MM) using LG Bridge first (download from LG site, it will sometimes work when OTA doesn't). If that doesn't work, you'll have to download an MM kdz for your model and carrier and upgrade it with LGUP-NEW. Then, once you have stock MM installed, do at least a partial backup with SALT before proceeding to unlock with steadfasterX's UsU method. Make sure you read and understand the OP completely there.
Click to expand...
Click to collapse
Is the ARB value stored as a variable? I'm guessing its just a variable that gets checked during a KDZ flash. If so, where is the ARB value stored, and why can't we just overwrite it with 0? Has anyone tried this already?
If it's not possible, can't we alter the ARB values of specific KDZ's? For example if your phone has ARB value 3 and you want you want to flash a KDZ with ARB value 1, can you change the ARB value of the KDZ from 1 to 3, so it won't brick?
dharakv said:
Is the ARB value stored as a variable? I'm guessing its just a variable that gets checked during a KDZ flash. If so, where is the ARB value stored, and why can't we just overwrite it with 0? Has anyone tried this already?
If it's not possible, can't we alter the ARB values of specific KDZ's? For example if your phone has ARB value 3 and you want you want to flash a KDZ with ARB value 1, can you change the ARB value of the KDZ from 1 to 3, so it won't brick?
Click to expand...
Click to collapse
Suggest you read the OP in the UsU thread and pay particular attention to REQUIREMENTS #2.
If you really want to hard-brick your device then go ahead -- i.e., you cannot alter the arb value !!!
Hello everyone!
First of all - thanks to steadfasterX for unlocking the LG G4
PLEASE! DON'T TRY ANYTHING BELOW ON YOUR LG G4.
YOU MIGHT BRICK IT PRIOR IT NOT EVEN GOING TO QDLoader ANYMORE.
THE SOLUTIONS ABOVE IS ONLY LIMITED TO MY PARTICULAR MOTHERBOARD,
OR PERHAPS OTHER REFURBISHED MOTHERBOARDS
WHICH ARE F500L's WITH H811 FIRMWARE ON THEM.
Click to expand...
Click to collapse
Purchased the H811 motherboard from Aliexpress as they are pretty cheap now ($ 27). I chose H811, as it allows you to unlock the bootloader without a hassle!
Installed it and it booted up right away and it worked flawlessly except for the fact that the camera's autofocus or manual focus didn't work for some reason.
Then I went to About Phone and, to my surprise, was running an old version of Android 5.1. I decided to update it through the settings, but it refused, saying that the phone was already updated and did not need to be updated. I already had a suspicion because phones that behave this way are usually software modified. SO ... I still flashed the H811 KDZ using LGUP and .. as I thought, the phone did not boot.
After going through the pain of disabling Windows Signature Verification and installing the correct QCOM drivers, opened QFIL, loaded the Mohd Saqib 8992 firehose and XML, and when finished, the phone booted, but with a SecureBoot warning in the top left corner. As soon as it booted into Android, I was greeted with a setup menu, no cellular service, and LG VPN ANR. After going through the setup, I decided to start the camera and got slammed with another ANR. I loaded OpenCamera and that didn't work either. So I knew that this is some kind of a driver conflict or incompatibility.
I took out the motherboard and the place where the model was written was covered with some kind of sticker. (First.jpg). The sticker was so crazy glued on there that I had to use the tip of a soldering iron to soften the glue, and it's a Korean F500L. (Second.jpg).
Loaded mAid, opened SALT, and OMG! ARB of 20! (Third.png) Still, gave it a chance and downloaded F500L20p firmware, edited LG-F500L to LG-H811 using Hex Editor, and it flashed through. Obviously, It ended up in QCOM bootloader mode again. Flashed FireHose through QFIL, it turned on with the same SecureBoot error in the upper left corner. Once booted into Full Korean Android and to my surprise, there were no ANRs. Plugged in my personal sim card and it even got a cellular signal. Called my friend and it worked. The Camera also works flawlessly WITH WORKING AUTOFOCUS.
Connected it to SALT again, this time GPT is unknown. ARB is also unknown. (Fifth.jpg)
This is a miracle. After all this, the phone is still in working order. Not only did the camera regain its autofocus capabilities, but also that the ARB is set to an unbelievable number!
Thank you for reading!
================================================
UPDATE:
I went into Recovery, decided to boot into the bootloader, and it shows that Secure Boot is disabled. I flashed SKYHAWK recovery IMG and it booted! (Sixth.jpg). Flashed H811 Lineage OS and F500 baseband. Booted into LineageOS with everything working including camera, cellular, and wifi. (Seventh.jpg)
Click to expand...
Click to collapse
UPDATE 2:
Lineage OS 16 seems to have poor battery life. Tried to flash the F500L 20p firmware, but LGUP refused to update, claiming that the ARB of the phone is higher than the firmware. Flashed back the H81120r, followed by QFIL and it Booted up. Flashed the F500L 20p firmware again, and now, no ARB messages whatsoever.
Click to expand...
Click to collapse
LG UP Instructions for this particular frank motherboard:
Basically, to flash this motherboard without ARB kicking in, H81120r firmware has to be flashed via LGUP, and firehose through QFIL and android has to be booted. Once booted, the phone can now be flashed with F500L20p only.
Click to expand...
Click to collapse
(Hard Way) How to flash Stock Nougat:
If updating through LGUP gives out a 0x2000 error then the solution is very complicated. First, while on F500L20p, connect the phone to the PC. Open LG Bridge and let it search for updates. Once it found F500L30b, press Update and wait. It will fail. Without closing or doing anything in LG Bridge open LGUP and load in H81120r KDZ and flash. Wait for H811 firmware to load to Setup, then go to Download Mode again and Click on Retry in LG Bridge. Once finished, Flash the firehose through QFIL.
(Easy Way) How to flash Stock Nougat:
Extract .DZ file out of F300L30p KDZ file using WindowsLGFirmwareExtract. Flash .DZ file through LGUP Upgrade Option. For some reason, it works.
=================================================
In case you wonder if flashing Nougat will set the bootloader stack prior to not letting you flash H81120r anymore... not it won't. I tried flashing H81120r followed by F500L20p while being on Nougat Stack and it flashed without a problem.
=================================================
Click to expand...
Click to collapse
==============================================
Conclusion:
So... this is not H811, but it's closest to it since it lets you flash KDZ's, AOSP Roms, TWRPs, custom kernels, and Magisk, all without USU while on ARB 20. It's just that every LGUP and LG Bridge process has to be followed by QFIL.
I have no idea how this thing consumes almost all KDZ's given to it, even the ones with ARB0.
Sold the Phone
This may seem like a weird question, but is there is way to convert back to the T-Mobile firmware? Mostly I would like to avoid having to install the modem manually with every update. If this is no longer the case and there is a permanent modem solution then that's all I would need. I found a lemonade tar.gz for the T-Mobile firmware supposedly, however, I don't know how to make that a installable ROM. The link is a github link here, OnePlus 9 Pro Firmware. I've never swapped off of the carrier firmware and had to manually reinstall the modem with every update before. The most annoying part of that for me would be keeping the bootloader unlocked. That's only a minor issue for me as I play Pokemon Go and unlocked bootloader/root can cause issues with that. I don't generally tweak my phones much anymore. I prefer the non carrier ROM to have more current updates. To recap, is it possible to either go back to T-Mobile ROM or is a permanent modem fix for the conversion?
MSM is the easiest way. Just use the MSM tool for LE2127 and you'll be on your way.
I have a flash-all script that you put in a fastboot flashable stock rom zip, and it'll make it so the radio (modem) persists through OTA's. Just gotta dig around for it and see what I did with it.
Thank you both. If I could get back to T-Mobile firmware then swap back to global again that would be great. I think I may be up the proverbial creek though. In my search I came across what seems like an older thread first and I used the India MSM to flip to global. This unfortunately means the T-Mobile MSM is unable to flash to my phone as it sees it as an India phone. I found the other global MSM, and I am able to see the Target directory and choose O2, however, the MSM fails to download. Param Preload error, device not match image.
I've made peace with not being able to get back to T-Mobile firmware, I may have to research the persistent modem more for a fix that will work with India. Is there a modem install for OOS12 that doesn't brick the phone? I use the ones I have from the T-Mobile files, and they work fine for OOS11, but they immediately brick 12 after install.
Bumping this post to ask again about the modem for Android 12. Also, my Bluetooth audio cuts in and out, it's very crackly. This only started after jumping from the T-Mobile ROM.
Edit: Also the voicemail doesn't show in the Phone app. Voicemail service is listed as "Your Carrier" and I can't do anything with it. There are no options that I can toggle at all.
I was looking at the repo of builds for the 9 Pro. I see there is an Android S for all regions in there. Could that possibly change the region of the firmware to, more or less, not associated anywhere and allow a restore to the T-Mobile firmware?
I'm not entirely sure how, but I did manage to get off of the India firmware and onto the EU firmware. At least from there I should be able to get the persistent modem. Working on that process now.
All right, everything has been running fine on the EU firmware, the only thing I'm still having an issue with is Bluetooth. Not connectivity at all, just on phone calls and in one vehicle for audio. It's incredibly choppy. It didn't used to be an issue, it only started after I left the T-Mobile firmware. Is there something I need to flash for the Bluetooth or a setting I'm missing?