LG G3 stuck at splash screen after kernel / modem update - G3 Q&A, Help & Troubleshooting

I am in the process of upgrading my LG G3 (Verizon) phone from stock Android 4.4.2, baseband 10B to Cyanogenmod 12.1. I rooted my phone successfully and installed TWRP. I got an baseband not supported failure when I attempted to install Cm 12.1. So, I downloaded baseband and kernel file 12. This was successful. However, when I tried to install CM again, it failed. I noticed that it was still a baseband issue and that the script was looking for an even higher baseband version. Again, I downloaded the kernel and modem zips. This time for baseband 35B. It seemed to flash successfully, but after reboot, it's stuck at LG splash screen.
I would appreciate some assistance.
Thank you in advance

Related

[Q] Baseband version?

I am currently running model SM-N9005, Android Version 4.4.2 with Baseband version of N900TUVUBNI7.
i AM RUNNING BoBCatROM with leanKernel. I have tried using different kernels to go with this ROM but none of them seems to be working, phone gets stuck on boot up screen. I want to have the ability to run different kernels with this ROM, do i have to upgrade my baseband or do i have to do something else?
I am open to any suggestions that you guys have for me.
Thank you.
try fresh install http://forum.xda-developers.com/showthread.php?t=2768867 ne6 update

VS985 - CM13 - LTE not working

Hi guys,
What happened :
I am using VS985 and have been using cyanogenmod(updating to latest nightlies - CM13) from the last few months .
Few days ago i couldn't update to latest nightly because of unknown baseband version. So i, stupidly enough, flashed 24B modem. And was able to update to latest nightly but LTE no longer worked. I figured i need to flash 35B modem. So i ended up flashing bootstack from xdabebb from this link
No luck with LTE reception.
What have i tried till now:
I've tried doing clean installs. Also tried flashing an older 12.1 CM version. Have tried to change preferred netwrok through *#*#4636*#*# . Rebooting , flashing stuff again and again.
Checked APN setting and everything.
End Result:
LTE is not working. Have i messed up the radio?. Do i need to KDZ back to stock and then flash CM again?. Please help
Solved!
Writing this for anyone who might encounter the same problem.
I flashed kdz stock 10B, root and flashed TWRP and flashed CM13 again.
Everything is new and fine again
LTE working and everything.
How did you do that
ranaAz said:
Solved!
Writing this for anyone who might encounter the same problem.
I flashed kdz stock 10B, root and flashed TWRP and flashed CM13 again.
Everything is new and fine again
LTE working and everything.
Click to expand...
Click to collapse
How did you flash CM13 from stock 10B, i couldn't do it, i had a baseband error, i need at least 24B, how do you do that?

installing revolution HD w/ twrp?

hi guys - so i tried to install the revolution rom on my recently unlocked m9 and it'd only boot to the bootloader or download.
i found some threads back from 2012 that said twrp wouldn't install the rev rom, but suspect it's out of date - it seemed to work fine.
is there some magic here? i tried to flash my firmware to the version matching the rom (3.35.401.12) and got a code 10 failure in adb. my current firmware is 3.10.605.7. doesn't flashing the rom update the firmware too? or do i need to successfully flash the rom prior?
should i use a different recovery? twrp launched the rev aroma installer and all seemed to go perfectly smoothly... no problems came up until reboot brought me right back to bootloader.
the aroma install says it might boot loop a couple times, but i booted to bootloader 5+ times before giving up and going back to a deodexed stock vzw rom.
any help is greatly appreciated - i'm hoping to get up to marshmallow before calling it good enough and moving on.
Flashing the rom doesnt update the firmware. S-on makes sure of that.
You must be on the base firmware for the rom to take. You need the vzw marshmallow ota update before you can flash a marshmallow based rom.
Sent from my HTC One M9 using Tapatalk

Baseband unknown after TWRP flash to 35B baseband (Kit Kat 4.4.2)(Verizon)

Hey guys I have a Verizon G3 that I rooted when I first purchased. Stayed with Android 4.4.2 till now. I flashed the 35B baseband with TWRP without signature verification and now phone shows my baseband version as unknown. My next step is to try the new Dirty Unicorn Marshmallow ROM. Mostly I'd like to know if this is a problem and if it will screw with the new ROM installation. I'll walk you through the steps I have taken.
1. Installed busybox(Stericson) via the app store. Installed busybox
2. Installed TWRP 3.0 via TWRP Manager from the app store
3. Created ROM backup via TWRP
4. Tried flashing Dirty Unicorn 6 ROM but got an error saying I had an "unsupported baseband version." After some research I realized I needed an updated baseband
5. Flashed the 35B baseband via TWRP without signature verification. Baseband now shows "unknown"
Is this a problem? Do I need to fix this before attempting to flash Dirty Unicorn at this time? From my understanding my G3 didn't require being "Bump'd" first.

is this what a soft brick is?

Okay so have a I747 AT&T Galaxy S3. Had CM13 running fine on NE4 baseband. Decided to upgrade baseband and flashed NJ1 then NJ2, rebooted and everything was fine.
Well then I decided to check out a different ROM, and tried installing these via recovery and then I get stuck on that AT&T splash screen:
d2att_I747UCUFNJ2.zip (didn't work) so then d2att_I747UCUFNJ2_Deodex_Rooted_KnoxFree_Debloated.zip
I thought I was able to install those since I just upgraded my baseband, but my phone did not like it!
I also noticed that in download mode, in red there was a "warranty bit: 1", not sure if that's relevant?
So I can still get into download and recovery, but any restoring CM13 from backups or return to stock results in a bootloop. How can I get CM13 back?
Can I flash back to stock with Odin and start over to fix this? Is this the file I should use?= I747UCDLK3_I747ATTDLK3_ATT.zip or this one?= I747UCUEMJB.zip
Or will those brick my device since I'm quite certain I'm on NJ2 firmware?
OR should i try reinstalling a certain CM version with certain gapps?
What can I do? I'm really freaking out here, everything I have is on 2fa! Please help!
Was the bootloader updated when the baseband was updated?
turns out im just an idiot and installed the wrong gapps.

Categories

Resources