help with vs985! - G3 Q&A, Help & Troubleshooting

Full disclosure, I'm 100% new to all of this and I'm having a hard time picking up the lingo. I flashed the 47a kdz onto my g3 and it all went well. Everything is working on the phone except my internet. I have none. After doing some reading I'm assuming it is because I need the 35b bootstack for the modem. I had downloaded the 35b bootstack, unzipped it, and moved the files into my internal storage. I thought this was all I needed to do, but apparently I did something. Can someone help me with how exactly to flash a bootstack, or whatever else I could have done wrong that is causing my internet not to work. Everything is working perfectly. Thank you very much in advance.

You shouldn't have to flash the 35B bootstack, that's for people that use a custom recovery.
You have the latest 47A images (same ones that the 35B bootstack uses, but newer) and there is no reason to downgrade your images.
First try a hard factory reset, if I have to guess that'll fix your issue.
Else redownload and reflash your KDZ (yes, redownload it; some of the images could be messed up and/or the flash might have messed up).
Else, try a new SIM card; sometimes (rarely from what I have seen) this can be the issue so this is a last resort.
PS: When you have a file to flash, it's supposed to be left zipped and done in custom recovery. You will not need to flash though, like previously stated that bootstack is for users that have a custom recovery.

Ariac Konrel said:
You shouldn't have to flash the 35B bootstack, that's for people that use a custom recovery.
You have the latest 47A images (same ones that the 35B bootstack uses, but newer) and there is no reason to downgrade your images.
First try a hard factory reset, if I have to guess that'll fix your issue.
Else redownload and reflash your KDZ (yes, redownload it; some of the images could be messed up and/or the flash might have messed up).
Else, try a new SIM card; sometimes (rarely from what I have seen) this can be the issue so this is a last resort.
PS: When you have a file to flash, it's supposed to be left zipped and done in custom recovery. You will not need to flash though, like previously stated that bootstack is for users that have a custom recovery.
Click to expand...
Click to collapse
I will give it a try! Thanks so much for the help. I'm at work on the wifi, I'll give it a go tomorrow. Should it Make any difference that the phone is being used on straight talk?

I tried a hard reset and still nothing. 3g/4g shows up at the top but the bars showing it's active are non existent, and I have no mobile network. I will try to re download and flash again tomorrow. Thanks again for the help.
Edit: I think I used this http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
I think I may have used the wrong one? But it's the only stock kdz I saw. Unfortunately I'm brand new to all of this ?

Ariac Konrel said:
You shouldn't have to flash the 35B bootstack, that's for people that use a custom recovery.
You have the latest 47A images (same ones that the 35B bootstack uses, but newer) and there is no reason to downgrade your images.
First try a hard factory reset, if I have to guess that'll fix your issue.
Else redownload and reflash your KDZ (yes, redownload it; some of the images could be messed up and/or the flash might have messed up).
Else, try a new SIM card; sometimes (rarely from what I have seen) this can be the issue so this is a last resort.
PS: When you have a file to flash, it's supposed to be left zipped and done in custom recovery. You will not need to flash though, like previously stated that bootstack is for users that have a custom recovery.
Click to expand...
Click to collapse
Tried everything you said, and tried this http://www.mylgphones.com/how-to-flash-android-6-0-m-stock-firmware-on-lg-vs985-using-lg-up-software . I did not try a different sim card yet, as I only have this one, but the internet will still not work.

stevehug said:
I will give it a try! Thanks so much for the help. I'm at work on the wifi, I'll give it a go tomorrow. Should it Make any difference that the phone is being used on straight talk?
Click to expand...
Click to collapse
It may, I think you just have to set your APNs.
This is the Straight Talk APN.
stevehug said:
Tried everything you said, and tried this http://www.mylgphones.com/how-to-flash-android-6-0-m-stock-firmware-on-lg-vs985-using-lg-up-software . I did not try a different sim card yet, as I only have this one, but the internet will still not work.
Click to expand...
Click to collapse
That's a full ROM that is used to be flashed in TWRP (AKA custom recovery).
THIS is the KDZ method I use:
Guide that always works for me here.
VS98547A KDZ download here.
Extract the 7Z file until you just have the KDZ file.
This method will COMPLETELY wipe your phone, pictures, videos, games, apps, etc.
Make backups!

THIS is the KDZ method I use:
[URL="http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140" said:
Guide that always works for me here.[/URL]
VS98547A KDZ download here.
Extract the 7Z file until you just have the KDZ file.
This method will COMPLETELY wipe your phone, pictures, videos, games, apps, etc.
Make backups!
Click to expand...
Click to collapse
I'm following the guide spot on, when I try to flash back to 10b, I get an error and the process won't continue the "upgrade". This is so frustrating, I guess I should have left well enough alone when I got the phone instead of wanting the newest update

Ariac Konrel said:
It may, I think you just have to set your APNs.
This is the Straight Talk APN.
That's a full ROM that is used to be flashed in TWRP (AKA custom recovery).
THIS is the KDZ method I use:
Guide that always works for me here.
VS98547A KDZ download here.
Extract the 7Z file until you just have the KDZ file.
This method will COMPLETELY wipe your phone, pictures, videos, games, apps, etc.
Make backups!
Click to expand...
Click to collapse
I was able to flash back to 35b and my phone is fully functional again, I cannot thank you enough for your help. My wife was ready to kick my butt! haha. Maybe I will try going to 47a now knowing that I can go to 35b and be funtional if it doesn't work. Again, I cannot thank you enough for your kindness and your help, you saved me a large headache!

stevehug said:
I was able to flash back to 35b and my phone is fully functional again, I cannot thank you enough for your help. My wife was ready to kick my butt! haha. Maybe I will try going to 47a now knowing that I can go to 35b and be funtional if it doesn't work. Again, I cannot thank you enough for your kindness and your help, you saved me a large headache!
Click to expand...
Click to collapse
Since this is the Verizon version, my suggestion is go to the Verizon specific forums. And yes, if you took one of the 47a images, that's not an official image. And yes, you must have the 35b modem and bootstack because TWRP will not work with those and the 47a image assumes that's what you have. Usually, it can result in a brick which requires a TOT or KDZ flash to fix.

Related

[Q] No ROMs taking, keep getting no MD5 message, phone close to bricked.

I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
gvazquez82 said:
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
Click to expand...
Click to collapse
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
MrHaPpY66 said:
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
Click to expand...
Click to collapse
First of all thank you for trying to help me, I hope you are having a good Thanks Giving.
I used the thread you linked to, and downloaded the version with out knox. I followed the instructions
transferred ROM and flashed kernel file to SD card
used odin to flash TWRP,
used twrp to flash rom and kernel file.
and it takes the file thankfully, there's only one issue. My phone can't make or receive calls/texts. Is yours able to?
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Next Update
the bootloader I flashed apparently flashed to the external sd card? I flashed another one and it is booting from the internal sd. I had to flash a different modem the one in the bootloader/modem file I flashed from the link above didnt take? I got most everything sorted out, but im getting tired, it has been an all night adventure. its 08:23 est now
sorry for the delay in updating this I had to get some rest.
theramsey3 said:
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Click to expand...
Click to collapse
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
spongdangly said:
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
Click to expand...
Click to collapse
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I will give that a shot, but what's an APN, sorry. And how do I create one, and is it needed for me to do so?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
It should be, I'm working right now so I don't have time to fine the guide on how to inject your IMEI. If I remember correctly it involves using QPST. If you have an old (or any) working Nandroid backup that should fix the problem.
FYI, make sure you don't use the guide for the international S3 as it has different hardware and folder structure/contents.
As for the APN, it should automatically fill itself in since it reads it off the SIM Card (I might be wrong).
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I tried it and it work!!!!!!!!!!!!!!!!!
67 texts just came in. Sir, I thank you oh so kindly. You have made this gloomy rainy day oh so joyous.
No problem. Glad I could help you.
The real credit should go to -Mr.X-, loserskater and anyone else(no disrespect there were alot of files) whose stuff I tried to flash lastnight thank you all in the dev community who contribute.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
gvazquez82 said:
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
Click to expand...
Click to collapse
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
flexfulton said:
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
Click to expand...
Click to collapse
do you know of a good stable kit kat like ROM I could use for the s3? And any speculation as to why the ROMs werent taking for me?

VS986 13B >>ROOTED<< >>DEBLOATED<< System Image & KDZ DOWNLOAD

VS986 13B >>ROOTED<< >>DEBLOATED<< System Image & KDZ DOWNLOAD
EDIT:Thank you everyone for your support in this thread and to those that donated. This thread actually got me the first donations I've ever received just for tinkering around with phone operating systems; super cool. However, I will no longer be actively taking feature requests or looking for/fixing bugs as I have succumbed to the allure of the V10 and have retired my beloved G4 in less than a year of ownership. I must say the V10 is a gorgeous phone and I absolutely love it. I will continue to frequent this thread and answer any questions and offer any help that I can give to help anyone who may need it. My G4 is now on eBay (until Sunday) so if anyone is interested in a MINT condition Verizon G4 with a LOT of extras, PM me and I will give you the link listing as I believe posting it on here violates xda policy. Now time to explore the V10 forums. Cheers all!
_______________________________________________________________
Fellow Big Red G4 owners,
I am providing for everyone a ROOTED BEBLOATED 13B system image for the Verizon G4. I was on 12A rooted and the OTA to 13B failed so I flashed the stock 12A image that I had laying around, took the OTA successfully, pulled a stock 13B image, used the root injection method found in these forums and flashed back. I can confirm this works!! I'm running it on my phone right now. This system image is also slightly debloated. No, I don't have some fancy program that can open the system image files and pick and choose what I want to delete. All I did was boot my phone on the rooted 13B system and use root explorer and root uninstaller to remove a bunch of stuff that wasn't needed. I made a few other changes as well. Once I was satisfied with my debloating I extracted the system image again and am sharing it with you all! Below is a list of the changes I made as well as the download link. WARNING!!!!!!!! I AM NOT RESPONSIBLE FOR ANYTHING YOU DO WITH YOUR PHONE!! I ASSUME YOU KNOW WHAT YOU'RE DOING IF YOU PROCEED!!!!!!
EDIT 1: I put the img file in a highly compressed rar and 7z archive so the you now only have to download a 1.74 GB file instead of a 4GB+ file.
EDIT 2!! It looks like the official 13B KDZ is FINALLY here thanks to @autoprime !!! Get it HERE.
----------------------------------------------------------------------------
The super user binaries are updated. (meaning you wont get prompted to update them on first boot.)
BusyBox has been pre-installed.
AdAway Host file baked in.
Google Chrome browser has been removed and has been replaced with the stock LG Browser!!
The following system apps have been replaced with those from the new LG V10:
SmartNotice (The best difference is that it's somewhat transparent so it looks WAY cooler.)
Calendar
File Manager
Gallery
Music
^^I was able to get odex files for the above V10 system apps so they don't have to be "optimized" on first boot.^^ Even though the Contacts and Home Launcher app are available from the V10, the Contacts app always force closed no matter what I did and the Home Launcher app would randomly pop up with a "Loading Apps..." pop-up box for about a second when you hit the Home button, so I left both those apps out.
All the VZW bloatware apps have been removed, save for visual voicemail, which I like and actually use. In response to a question I received as to why I removed the CallerNameID app, I use Advanced Calling and CallerNameID, as well as a few other Verizon apps, are not compatible with Advanced Calling according to Verizon's web-site. (See attached screenshot.)
The stock, very annoyingly bright red, could-have-been-a-flashlight-app (lol) Verizon boot animation has been deleted and was replaced with a nice, simple and unobtrusive stock android boot animation. White text on black background. Much better.
The DPI has been set to 560 compared to the stock 640. It will go as low as 540 with no FCs but 560 is just about perfect for me. If you don't like this size, use Textdroider app to change the dpi. NOTE: The only stock app I have found that doesn't work with this lower DPI setting is the LG Voice Recorder. It doesn't work on any DPI setting other than 640 (not even 639). However this app is still included in case you wish to revert back to stock 640 DPI and use it.
-----------------------------------------------------------------------
First boot after a factory reset using this image will be really quick as it will only have to optimize 2 or 3 apps instead of 20+. If you don't like anything, such as the DPI, or visual voicemail, etc, you can change whatever you want since you'll be rooted. This is just how I like my phone.
YOU MUST have already taken the 13B OTA and you will need to be un-rooted to take the OTA. If you are on 11A or 12A rooted, the easiest way to un-root is to use the 13B KDZ to reset your phone to factory un-rooted stock. If you use the KDZ method be sure to backup your personal data as flashing a KDZ will wipe all your data.
You can follow the instructions on how to flash the system image HERE. You will more than likely run into problems if you are on 11A or 12A and try to flash this image without having first updated to 13B using one of the methods listed above (OTA or KDZ), so don't even try. I will not be able to help you get out of that predicament.
You can download the image file HERE!! (RAR Archive format)
Same image in 7z archive format HERE due to several users have MD5 mismatches with the RAR archive. (Needs free 7-Zip archiver program to unpack.)
The MD5 of this file (the IMG file; not the archive files) as it sits on my desktop is 1eca2a177f50f4a092bc5ef0939a99a7
Another thing to remember. Once you flash this image, there is no going back to the state your phone was in before (stock, un-rooted) unless you have a backup of your current system image. Meaning, even if you do a reset to factory defaults from the stock G4 recovery after you've flashed this system image, the defaults it will go back to are those of this system image.
IMPORTANT!! Resetting to factory defaults using the stock G4 recovery after you have flashed this image will NOT un-root your phone. You will have to flash a KDZ file to get back to stock un-rooted. There are instructions on how to extract your current system image HERE before you flash my image.
CREDITS
HUGE thanks, kudos and all credit for the LG Browser goes to @xdabbeb. I was never able to find a new version of the LG Browser that would work on the G4. I asked xdabbeb to see if he could get it working for me and he was gracious enough to do so; thank you!! I became hooked on the LG Browser being a long time fan and user of his ROMs for the Verizon G2.
Thanks to @BySezerSimsek for the V10 system apps. His thread with all the apps is HERE.
I do not take credit for any of the methods used in achieving this. All credits for superuser scripts, injection methods, ported V10 apps, etc goes to the appropriate people. You know who you are. I'm not a developer by any means. I'm just a power user who's not afraid to take the plunge and follow instructions from other very respected users who give all of us the tools we need to make our phones what we want them to be. Without these people, we would have very boring phones. lol. This is the least I can do to contribute back to the community who has helped me out in so many ways.
ENJOY!!!!!!!!!!!!
will give it a try in a few. I dont see clear instructions on how to pull my own system .img for back up purposes
Edit: I guess if i look i would find it. HaHA, to early in the morning to be reading XDA!
Anyone tried this yet?
Sent from my VS986 using Tapatalk
I cant get a good download of this? Is anyone else having success?
madmaverickmatt said:
I cant get a good download of this? Is anyone else having success?
Click to expand...
Click to collapse
Nope, keeps failing. No worries. It's fairly new. Give it some time to work the kinks out.
Sent from my VS986 using Tapatalk
13B? When did that come out? I never even got 12A. Stuck on 11A with screen touch problems.
dvgb173 said:
13B? When did that come out? I never even got 12A. Stuck on 11A with screen touch problems.
Click to expand...
Click to collapse
Within the last 24 hours I believe. I just checked for an update this morning via WiFi and got/installed it.
https://www.reddit.com/r/lgg4/comments/3u3nfo/verizon_update_1124_wifi_fix/
I was on 11A and the 422.1MB download took me straight to 13B .
Any pointers for this VS986 + forum newbie on how to root 13B greatly appreciated .....
divineBliss said:
Within the last 24 hours I believe. I just checked for an update this morning via WiFi and got/installed it.
https://www.reddit.com/r/lgg4/comments/3u3nfo/verizon_update_1124_wifi_fix/
I was on 11A and the 422.1MB download took me straight to 13B .
Any pointers for this VS986 + forum newbie on how to root 13B greatly appreciated .....
Click to expand...
Click to collapse
Again, like the 12a rooted image, there is no coming back from this if something goes wrong. Maybe someone could write a short step-by-step for those of us who want to make a personal backup of our system.img, and I really need to go find the instructions to flash the pre-rooted image since that was so long ago now. Really happy to see this though.
ps.- the download worked fine for me.
I second his advice to create a backup of your current system.img. If you don't you will need to factory reset again when you want to install another OTA, that's what happened to me. No matter what I tried, the OTA would not install on my system.img, even after I unrooted etc. I think I also went too far with moving system apps to the SD card and freezing some apps which prevented it from installing.
To install the OTA on a rooted VS986, is it necessary to flash a stock image (kdz), or can we simply unroot via SuperSU?
dvgb173 said:
To install the OTA on a rooted VS986, is it necessary to flash a stock image (kdz), or can we simply unroot via SuperSU?
Click to expand...
Click to collapse
I'm on 11A and I am wondering this as well. Not sure where to go from here....
rfarrah said:
I'm on 11A and I am wondering this as well. Not sure where to go from here....
Click to expand...
Click to collapse
On 11A as well.
I'm pretty fed up with this phone, so when I get home I'm going to kdz 11a stock with LGUP tool, factory reset, take the 13B OTA, back up the stock system image, then inject root and see how that runs.
Then I'll probably flash the debloated image later this weekend.
dvgb173 said:
To install the OTA on a rooted VS986, is it necessary to flash a stock image (kdz), or can we simply unroot via SuperSU?
Click to expand...
Click to collapse
The update will not install if you are rooted. You can try, it will go through the motions and throw an error.
If you KDZ, make sure you use the KDZ of the version you are on. If you are on 12A and flash the 11A KDZ, you will brick your phone.
The proper way to do this is to BACKUP YOUR SYSTEM.IMG BEFORE YOU DO ANY ROOTING so you can just restore your original system image and restore back to out of the box experience.
If you did NOT backup the system image, then I would recommend looking for a STOCK UNROOTED system image of the same level you are currently running. Push the system.img back onto your phone, take the OTA, BACKUP, and push a rooted system image.
dvgb173 said:
On 11A as well.
I'm pretty fed up with this phone, so when I get home I'm going to kdz 11a stock with LGUP tool, factory reset, take the 13B OTA, back up the stock system image, then inject root and see how that runs.
Then I'll probably flash the debloated image later this weekend.
Click to expand...
Click to collapse
My plan, too, but without the debloated image. Backing everything up now....
I don't have the original stock image. Can anyone provide a link to an 11A stock image?
Sys img Bkup command?
Is this the correct code to run a backup on my 12a unrooted stock, using the LG Root.zip?
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=548352 of=/data/media/0/system.img
sefirosu0522 said:
I don't have the original stock image. Can anyone provide a link to an 11A stock image?
Click to expand...
Click to collapse
Here is a link to a kdz:
http://storagecow.eu/index.php?dir=Xda/LG+G4/Verizon+VS986/
rfarrah said:
Here is a link to a kdz:
http://storagecow.eu/index.php?dir=Xda/LG+G4/Verizon+VS986/
Click to expand...
Click to collapse
Thanks. Maybe I mistyped. What I meant is, the stock image we pull off when we first root. I deleted mine. Is KDZ the only way to go or are the two essentially the same?
usr folder
Hello Everyone,
I was wondering if anyone could pull there /system/usr folder from 13 and upload it?
I'd like to tryout the new idc to see if that resolves the last of my touch issues on 11A
Thanks in advance,
~Eugene
player911 said:
<snip>...If you did NOT backup the system image, then I would recommend looking for a STOCK UNROOTED system image of the same level you are currently running. Push the system.img back onto your phone, take the OTA, BACKUP, and push a rooted system image.
Click to expand...
Click to collapse
I don't remember backing up system image as part of the Low Effort Root procedure. I will go check, but if it wasn't in the steps, I didnt do it.
If it was, I should have it somewhere.
I do have the original 11a stock rooted image saved. But that won't do me any good.
How is the system image backup accomplished without root? It is probably in the Inject Root thread.

Flashing a New ROM, Get an Incompatible Baseband Version Error?

Warning: This post is long, and probably full of grammatical errors due to my writing it late at night. a TL;DR is included at the bottom, but to fully understand my problem, I encourage you to read the whole post.
Hello, xdadevelopers community. I really need your help. So, recently I learned how to install custom ROMs myself and the experience has been really informative but also very struggling. To make a rather long story short, I bought a used G3 from my friend, had him root it, put a custom ROM on it, and everything was working fine. Only, that ROM was on Android 5.1.1, which was contemporary to when it was flashed. I wanted 6.0.1, so I went about getting it. I eventually got that up and running with Resurrection Remix, but the battery life was completely awful. Idle is okay, but using the device results in completely intolerable battery life. I asked Reddit what to do, and someone recommend crDroid for it's great battery life. I attempted to install that, and that's where I got the problems discussed in this post.
Post where I got the ROM and GApps from
Specific ROM and GApps I got:
- crdroid-6.0.1-20160118-vs985
- So I go the one for Android 6.0.1, and the most recent one at that, last updated on the 18th of January, for my G3 model the vs985
- for GApps, I selected "ARM", "6.0", and "Stock" from the menu
Could another problem be that the ROM is 6.0.1, and the GApps are 6.0? If so, open GApps version exists of 6.0.1.
Basically, I downloaded the two zip files, the ROM and the GApps. I then formatted my device, wiped it, did a real quick, skip through everything set-up of my current ROM, enabled USB debugging, copied the two zip files (ROM and GApps, both of which were inside a folder I made called ROM) onto my devices internal storage (I don't have an SD Card), and rebooted into recovery. I'm using Team Win Recovery Project (TWRP) v2.8.6.1 if that's helpful at all. Once in recovery, again I wiped the device (using the default wipe function in TWRP, then doing an advanced wipe and specifically selecting cache and Dalvik Cache, just to make sure), and went to flash the ROM, finally. I navigated to the ROM folder it was located it, selected it, and swiped to flash the ROM. I got the following in response:
Installing '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip'
...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Checking for BASEBAND version 35B
ERROR: It appears you are running an unsupported baseband. assert failed: h3.verify_baseband("35B:MPSS.DI.2.0.1.c1.13.4-00005") == "1"
E:Error executing updater binary in zip '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip'
Error flashing zip '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
So basically it failed to flash, apparently because of both an unsupported baseband version and a failure to execute a certain binary. Well, if you know how to fix the executing issue, that'd be great, although that's now what I'm focusing on here. I'm focusing on the baseband, because I believe that may be causing the failure to execute (although, as a newbie, I'm not sure if that's actually true). Apparently it was looking for version 35B, and that's not what I was running. When I set up my current ROM again just to be able to use the device, and checked for the baseband verion, it simply says "Unknown". Also, if you check out that link to the post above, it says:
We're mainly based on CyanogenMod so use custom kernels compatible with them!
Click to expand...
Click to collapse
. Well, I never installed a custom kernel, but I assume my friend did, because when looking at the kernel version on my phone it says:
3.4.0-CM-g74498f7
[email protected] #1
Mon Dec 14 09:48:16 EST 2015
Click to expand...
Click to collapse
.
I'm assuming if it was a non-custom kernel it would just have multiple numbers separated by periods, not have all that info, and it specifically says "CM" in there, so I assume that should work, but am not for certain.
Anyway, back to the baseband. It was looking for a baseband version 35B, which I apparently don't have. I have a few questions about this
1. How are you supposed to know your baseband version if your settings app returns "Unknown"?
2. How are you supposed to know what baseband versions work and what baseband versions don't work on the ROM you plan on flashing prior to doing so? I saw nothing about this from from start to failure to install.
3. If the ROM I intend to flash doesn't support my baseband version, can I install a custom baseband version?
I will admit, I don't even know what a baseband is, and I'm too tired to look it up as I write this.
So that's it. I realize this post is incredibly long but feel like if it was shorter, potentially important information would be nixed. I have a TL;DR below for your convenience, but as I just said, to get all the important information, read everything above, please.
TL;DR:
Tried to install a new ROM
Failed
Failing apparently due to unsuppported baseband version
I can't determine my baseband version b/c my settings app returns "Unknown""
If baseband is unsupported, how do I know which are?
Also apparently "E:Error executing updater binary in zip '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip' " is a thing. Caused by unsupported baseband version or entirely different problem all together?
Also maybe the ROM being 6.0.1 and the openGApps being 6.0 is a problem? If so, no openGApps 6.0.1 exist.
Please read the whole post to get all the detail needed.
NeatAndClean,
Thank you for providing the detailed information in this thread, so let's get to business.
First thing I want to straighten out is that you said your Baseband Version says "Unknown", i think you should check your IMEI information, if your IMEI is "null" then there is another problem to fix first.
If you have tried restoring from a backup after the "Baseband Unkown" issue and the Baseband Version still says "Unknown", then something happened whilst, or after you tried flashing CrDroid. At this moment I am not so knowledgeable about how to fix the Unkown Baseband issue, but it is a well known problem and usually coincides with the IMEI "null" issue. If you still are having that problem, I will try to find out how to fix it.
However, I will provide you with my full answer so this can hopefully get fixed at your preferred pace.
To start out, my questions are:
1. What ROM/Version of that ROM are you running right now? (I assume it is Resurrection Remix 6.0.1?)
2. Do you have a backup before trying to flash CrDroid? If so, I would suggest restoring from your backup to fix your "Settings Unkown" issue.
Once your Baseband "Unknown" problem is fixed, you can continue on to flash CrDroid (This time, it should work). Now I just downloaded the CrDroid zip file, that you used, on my PC. And just from opening it I can already tell that it is deeply based on CyanogenMod, but with some tweaks to make it CrDroid. Reason I mention this is because of this quote:
We're mainly based on CyanogenMod so use custom kernels compatible with them!
Click to expand...
Click to collapse
I'm not super knowledgeable on downloading Custom Kernels, but i do know that your Kernel:
3.4.0-CM-g74498f7
[email protected] #1
Mon Dec 14 09:48:16 EST 2015
Click to expand...
Click to collapse
is (I'm 99%sure) a CyanogenMod Custom Kernel, which comes when you flash a CM ROM.
Mine is:
3.4.0-CM-gc6520f1
[email protected] #1
Click to expand...
Click to collapse
and I'm running CyanogenMod 13, 6.0.1 on my vs985. Point is, you should be all set to flash CrDroid based on your Kernel.
Now, the "Unsupported Baseband" issue when flashing, at least CM based ROMs, is a known error recently. (In the past year I'd say) So the very common way to get around this, without having any issues, is to:
1. Go into your downloaded ROM zip, the zip you wish to flash, in your case it's crdroid-6.0.1-20160118-vs985.zip.
2. Extract the files into a folder (I'd recommend naming the folder the name of the .zip file, for ease in the end)
3. Open the extracted files folder
4. Open "META-INF" ==> "com" ==> "google" ==> "android"
5. Within that "android" folder, open "updater-script" file with Notepad, or a similar text editor.
6. Delete this line of code:
assert(getprop("ro.product.device") == "g3" || getprop("ro.build.product") == "g3" || getprop("ro.product.device") == "vs985" || getprop("ro.build.product") == "vs985" || abort("This package is for device: g3,vs985; this device is " + getprop("ro.product.device") + ".");
assert(g3.verify_baseband("35B:MPSS.DI.2.0.1.C1.13.4-00005") == "1");
Click to expand...
Click to collapse
7. You should be left with "ui_print("Target: lge/g3_vzw....." in your case.
8. Overwrite the edited "updater-script" back to it's directory (the android folder)
9. (Make sure you don't save it as a .txt file, it should still be a "File" (no extension))
10. Now go back to the "crdroid-6.0.1-20160118-vs985" folder after editing and saving "updater-script"
11. Select all the files/folders within, and add them to a .zip archive (Recommended by using WinRar)
12. You should end up with a .zip file visually identical to the original crdroid-6.0.1-20160118-vs985.zip, except this one has the edited "updater-script"
13. The edited one^ is the only one you need now, and is the one you will be flashing
14. Also, if you're curious I have done this many times with CyanogenMod, on vs985, and can assure you nothing bad will come of this... I assume the same is with CrDroid as it is deeply based on CM. (As long as you're "Unknown Baseband" problem has been fixed.
This procedure essentially gets rid of the Baseband/Model Check, ensuring a successful flash. Also as you can see in the code, it checks for the 35B:MPSS.DI.2.0.1.C1.13.4-00005 Baseband/Modem version, I believe "xdabbed" makes a flashable version of the 35B:MPSS.DI.2.0.1.C1.13.4-00005 Modem, which should eliminate the need to edit the updater-script. However, I strongly recommend to do the "updater-script" fix rather than trying to flash a different Baseband, as I have heard flashing a new Baseband can easily brick your phone, and you really do not need to do it.
I have Baseband: MPSS.DI.2.0.1.c1.13-00008, which does not match the "Baseband Check" and my ROM still works like a charm after the updater-script fix.
However, before you flash the edited crdroid-6.0.1-20160118-vs985.zip with your TWRP seperately, with the Marshmallow (6.x) ROMs right now, if you plan on using GApps you need to flash the ROM AND the GApps file at the same time in your custom recovery. Otherwise you will most likely get errors and you will need to re-flash the ROM and GApps.
Also maybe the ROM being 6.0.1 and the openGApps being 6.0 is a problem? If so, no openGApps 6.0.1 exist.
Click to expand...
Click to collapse
To answer this, no it is not a problem, you were correct.
1. The LG G3 is an ARM device
2. GApps only uses the first two digits in the OS version (i.e. 5.0.x or 6.0.x) (<==That "x" variable is the third digit in the OS version, and does not matter in GApps
3. All in all you have the correct version of GApps, no you just need to flash it at the same time as your edited ROM.
The procedure you did to flash the ROM was all good:
Basically, I downloaded the two zip files, the ROM and the GApps. I then formatted my device, wiped it, did a real quick, skip through everything set-up of my current ROM, enabled USB debugging, copied the two zip files (ROM and GApps, both of which were inside a folder I made called ROM) onto my devices internal storage (I don't have an SD Card), and rebooted into recovery. I'm using Team Win Recovery Project (TWRP) v2.8.6.1 if that's helpful at all. Once in recovery, again I wiped the device (using the default wipe function in TWRP, then doing an advanced wipe and specifically selecting cache and Dalvik Cache, just to make sure), and went to flash the ROM, finally
Click to expand...
Click to collapse
This is great, again the reason it didn't work was because of the mismatch in the Baseband Check, which shouldn't persist after following the instructions in the "updater-script" fix.
Anyway, back to the baseband. It was looking for a baseband version 35B, which I apparently don't have. I have a few questions about this
1. How are you supposed to know your baseband version if your settings app returns "Unknown"?
2. How are you supposed to know what baseband versions work and what baseband versions don't work on the ROM you plan on flashing prior to doing so? I saw nothing about this from from start to failure to install.
3. If the ROM I intend to flash doesn't support my baseband version, can I install a custom baseband version?
I will admit, I don't even know what a baseband is, and I'm too tired to look it up as I write this.
Click to expand...
Click to collapse
1. The Baseband Version is not supposed to state "Unknown", as i said in the beginning, this is a problem that happens sometimes, I am not sure why, or exactly how to fix it, but if you do some research I'm sure you will find something, I will also do some research so I can try to help you with that if it is not fixed by a Factory Reset or a Restore from Backup
2. The Baseband Version that a specific ROM calls for will be in that "updater-script" I was talking about, at least that's how it is for CyanogenMod based ROMs. I think your stock Baseband Version will work with any custom ROM, as long as it is a ROM made for your specific phone. That being said, I do think that the latest Baseband Version for your specific phone does improve Network, Cellular and GPS Connectivity, but again I do not recommend venturing there yet, until you have alot of background on it and can do it safely.
3. If the ROM you intend to flash doesn't support your Baseband, chances are the ROM is not made for your phone or you somehow have a Custom Baseband that is not made for your phone. I say that because even though you get that Baseband error when flashing CM based ROM, it is still supported, it's just that you do not have the "latest" Baseband Version I believe.
I do believe I have answered all of your questions, at least I hope so. I'm sorry that some things I could not answer in great detail, but I tried my best so that you could continue on enjoying your device. I also have the VS985 so I'm familiar with the device.
Summary:
1. Before anything try to Restore from Backup to fix the Baseband "Unknown" issue, as fixing this is priority. If that does not work I will try to find a fix online, or you can try to beat me to it.
2. Once that is fixed^ you can carry on with the "updater-script" fix i included.
3. Then flash the edited ROM and your 6.0, ARM OpenGApps at the same time (one right after another, without a Reboot in between)
4. Then you should honestly be all set
5. Your Kernel is all set for CrDroid
6. The GApps you said you downloaded is all good for the CrDroid version you downloaded
7. You could also try to flash back to vs985 stock (10B) this will hopefully give you your Baseband back if you still need it after Restoring from Backup
7. You should get no errors now! Yay. Now you can enjoy a Battery Optimized beautiful Marshmallow ROM
Click to expand...
Click to collapse
Please let me know if you have any confusion, I would be happy to provide you with clarification, screenshots etc.
I've run into a huge issue. My phone is semi-bricked now, and I don't know what to do. I was getting the baseband version error as well, and I removed the lines in the script and then it failed stating "wrong footer". I tried first installing CM, then like a fool, I installed Cyanogen Recovery over TWRP. Cyanogen Recovery can't do anything. But the install failed. I no longer have any version of Android on my phone, I can't install that baseband package with Cyanogen Recovery. Stock ROMs all come back "wrong footer" as well. I can't install anything. I have Fastboot/ADB installed. Please help!
Edit: I'm not sure if Fastboot is actually working. I can't get it to do anything. It just hangs on whatever command I give it, and it continues to hang until I unplug USB, then fails.
I've run into a huge issue. My phone is semi-bricked now, and I don't know what to do. I was getting the baseband version error as well, and I removed the lines in the script and then it failed stating "wrong footer". I tried first installing CM, then like a fool, I installed Cyanogen Recovery over TWRP. Cyanogen Recovery can't do anything. But the install failed. I no longer have any version of Android on my phone, I can't install that baseband package with Cyanogen Recovery. Stock ROMs all come back "wrong footer" as well. I can't install anything. I have Fastboot/ADB installed. Please help!
Click to expand...
Click to collapse
First off, in my response to @NeatAndClean I said to have the Baseband error fixed before proceeding, which is probably what caused your error.
For your Fastboot issue;
1. Make sure you are using the original Slimport cable (over-suggested, I know, just making sure)
2. Try USB 2.0 ports if you got them, if not, give this a shot forum.xda-developers.com/showthread.php?t=2256359
3. Try updating the phone's drivers
4. Otherwise, reinstall fastboot/ADB drivers or SDK Tools
5. Alternatively try this forum.xda-developers.com/showthread.php?p=48915118#post48915118
Assuming you have a VS985, here are stock IMG files:
forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
(If you do not have VS985 just find your Model's stock IMG files)
Here are commands you can use in fastboot once you manage to get it working, which will hopefully bypass your "Wrong Footer" issue. Obviously use your stock IMG files.
I would normally recommend flashing full stock TOT with LGFlashTool, but I'm not sure if it may worsen your Unknown Baseband issue (i.e. You may erase your IMEI if you Factory Reset when you have the Unknown Baseband problem) Here is everything you would need for the TOT Method: forum.xda-developers.com/showthread.php?t=2785089 - Also the old .dll needed for LGFlashTool probably won't work, so search LGUP_8974.dll and use that alongside the TOT instead) <== This should work if nothing else does, however, I don't think it will fix you "Unknown Baseband" but it may... I am not sure.
Finally, if you have ever made a previous backup, and still have it, if you restore from that your Baseband should re-appear and the error should fix itself. (I just figured you tried this already)
I once got the Unknown Baseband and IMEI - null issue, you could try to flash the stock Modem.img file for your phone, and try an IMEI injector program using the IMEI number in the battery compartment (Under the physical battery) But to fix mine I ended up calling the Customer Service and they eventually pushed an update file to my phone. I assume it was a Modem update of some sort, but it was a long time ago so I honestly don't remember.
I wish you good luck, as I know how frustrating these situations are. And keep in mind, I am only trying to help.
Please, to anyone experiencing the "Unknown Baseband Version" issue, focus on that before anything else, as you will most likely worsen your problem the more you do with the issue persisting.
Edit: Sorry, I didn't reach 10 posts yet, so you gotta drag 'n drop the links
Williquah said:
First off, in my response to @NeatAndClean I said to have the Baseband error fixed before proceeding, which is probably what caused your error.
For your Fastboot issue;
1. Make sure you are using the original Slimport cable (over-suggested, I know, just making sure)
2. Try USB 2.0 ports if you got them, if not, give this a shot http://forum.xda-developers.com/showthread.php?t=2256359
3. Try updating the phone's drivers
4. Otherwise, reinstall fastboot/ADB drivers or SDK Tools
5. Alternatively try this http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Assuming you have a VS985, here are stock IMG files:
http://http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
(If you do not have VS985 just find your Model's stock IMG files)
Here are commands you can use in fastboot once you manage to get it working, which will hopefully bypass your "Wrong Footer" issue. Obviously use your stock IMG files.
I would normally recommend flashing full stock TOT with LGFlashTool, but I'm not sure if it may worsen your Unknown Baseband issue (i.e. You may erase your IMEI if you Factory Reset when you have the Unknown Baseband problem) Here is everything you would need for the TOT Method: http://lgflashtool.net/index.php/tot-method/ - Also the old .dll needed for LGFlashTool probably won't work, so search LGUP_8974.dll and use that alongside the TOT instead) <== This should work if nothing else does, however, I don't think it will fix you "Unknown Baseband" but it may... I am not sure.
Finally, if you have ever made a previous backup, and still have it, if you restore from that your Baseband should re-appear and the error should fix itself. (I just figured you tried this already)
I once got the Unknown Baseband and IMEI - null issue, you could try to flash the stock Modem.img file for your phone, and try an IMEI injector program using the IMEI number in the battery compartment (Under the physical battery) But to fix mine I ended up calling the Customer Service and they eventually pushed an update file to my phone. I assume it was a Modem update of some sort, but it was a long time ago so I honestly don't remember.
I wish you good luck, as I know how frustrating these situations are. And keep in mind, I am only trying to help.
Please, to anyone experiencing the "Unknown Baseband Version" issue, focus on that before anything else, as you will most likely worsen your problem the more you do with the issue persisting.
Click to expand...
Click to collapse
Up until this point, I've only had the phone stock with the OTA updates from Verizon. It was updated the day I got the phone, so the baseband must be official, even if not supported by CyanogenMod. I wanna say it's 23B. I tried everything to get fastboot to work. I'm using the original cable that came with the phone "LG Electronics DC1501" plugged directly into a USB 2.0 port on my motherboard. If fastboot doesn't work, I can't flash imgs. An OS doesn't exist. I don't have a versatile recovery (Cyanogen Recovery might as well be stock). You say there's a chance TOT method will erase my IMEI, but you say there is an IMEI injector that can restore it, correct?
At this point, I'm at a loss. I really don't know what else can be done. I'm going to give the TOT method a shot. The website you linked has been suspended, so I'm following the 2015 updated method here: http://forum.xda-developers.com/showthread.php?t=2432476
---------- Post added at 09:09 AM ---------- Previous post was at 08:37 AM ----------
Knux Kitsune said:
Up until this point, I've only had the phone stock with the OTA updates from Verizon. It was updated the day I got the phone, so the baseband must be official, even if not supported by CyanogenMod. I wanna say it's 23B. I tried everything to get fastboot to work. I'm using the original cable that came with the phone "LG Electronics DC1501" plugged directly into a USB 2.0 port on my motherboard. If fastboot doesn't work, I can't flash imgs. An OS doesn't exist. I don't have a versatile recovery (Cyanogen Recovery might as well be stock). You say there's a chance TOT method will erase my IMEI, but you say there is an IMEI injector that can restore it, correct?
At this point, I'm at a loss. I really don't know what else can be done. I'm going to give the TOT method a shot. The website you linked has been suspended, so I'm following the 2015 updated method here: http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
OMG! It worked! My phone's still activated, so no problems with IMEI. I may be coming on kinda strong, but I LOVE YOU! I spent several hours yesterday, and I've been stressing about it ever since. I even put in a repair request with LG...now I can cancel that request. Thank you thank you thank you!
Knux Kitsune said:
OMG! It worked! My phone's still activated, so no problems with IMEI. I may be coming on kinda strong, but I LOVE YOU! I spent several hours yesterday, and I've been stressing about it ever since. I even put in a repair request with LG...now I can cancel that request. Thank you thank you thank you!
Click to expand...
Click to collapse
@Knux Kitsune Haha I'm glad that you finally got it working, I apologize about the problem with the link... I think I messed up all of the links in my response I'll fix those for the future. But again I'm just glad you got it working with no more problems, thanks for being so patient, XDA is like the best forum out there IMO.
Also, just curious, if you don't mind responding.. I was just wondering, did you use the KDZ method from the link you posted? Just want to know so that I know how many solutions there are for problems like these.
Anyway, enjoy your "new" phone lol, and be careful in the future because I know how painful these situations can be!
Glad you got it fixed!
:good::good:
Edit: The LGFlashTool link literally just got it's domain suspended like minutes after I posted it.. quite ironic.
Williquah said:
@Knux Kitsune Haha I'm glad that you finally got it working, I apologize about the problem with the link... I think I messed up all of the links in my response I'll fix those for the future. But again I'm just glad you got it working with no more problems, thanks for being so patient, XDA is like the best forum out there IMO.
Also, just curious, if you don't mind responding.. I was just wondering, did you use the KDZ method from the link you posted? Just want to know so that I know how many solutions there are for problems like these.
Anyway, enjoy your "new" phone lol, and be careful in the future because I know how painful these situations can be!
Glad you got it fixed!
:good::good:
Edit: The LGFlashTool link literally just got it's domain suspended like minutes after I posted it.. quite ironic.
Click to expand...
Click to collapse
I actually downloaded the KDZ, but I used the TOT method. I actually almost did it again, because in KitKat, my connection was very unstable, I did install the 35B baseband from XDABBEB, but that didn't fix the problem. I tried updating the firmware legitimately via LG Upgrade Assistant Utility (Verizon), but it kept giving an error everytime it got to 20%. I found no support online to get past this error, so I looked into stock ROMs and found XDABBEB (again) had built a flashable stock ROM for my phone, identical to what Verizon released last month, but with root access. I flashed TWRP 3.0 with Flashify, then flashed the ROM. The first time I flashed it, the phone showed that the phone service had stopped responding, a dialog box that only comes up once per cycle...super annoying. I managed to get back into Flashify and attempted installing the ROM again. I was actually prepared to do another TOT flash if it still had issues, but the second time wiping and flashing worked. My connection is solid, and I've had no errors (so far). It seems to run faster on Marshmallow than it did on Lollipop. It's pretty much the end result I was going for when I tried upgrading some 35 hours ago.
Update: Apparently, my baseband is fixed now. It did say Unknown before, even after flashing the 35B baseband from XDABBEB (initially anyways, reflashed after wipe just before flashing the ROM), but now it says "VS985-MPSS.DI.2.0.1.c1.13.4-00005-M8974AAAAANPZM-1"....so that's...good?
*Solution*
Knux Kitsune said:
I actually downloaded the KDZ, but I used the TOT method. I actually almost did it again, because in KitKat, my connection was very unstable, I did install the 35B baseband from XDABBEB, but that didn't fix the problem. I tried updating the firmware legitimately via LG Upgrade Assistant Utility (Verizon), but it kept giving an error everytime it got to 20%. I found no support online to get past this error, so I looked into stock ROMs and found XDABBEB (again) had built a flashable stock ROM for my phone, identical to what Verizon released last month, but with root access. I flashed TWRP 3.0 with Flashify, then flashed the ROM. The first time I flashed it, the phone showed that the phone service had stopped responding, a dialog box that only comes up once per cycle...super annoying. I managed to get back into Flashify and attempted installing the ROM again. I was actually prepared to do another TOT flash if it still had issues, but the second time wiping and flashing worked. My connection is solid, and I've had no errors (so far). It seems to run faster on Marshmallow than it did on Lollipop. It's pretty much the end result I was going for when I tried upgrading some 35 hours ago.
Update: Apparently, my baseband is fixed now. It did say Unknown before, even after flashing the 35B baseband from XDABBEB (initially anyways, reflashed after wipe just before flashing the ROM), but now it says "VS985-MPSS.DI.2.0.1.c1.13.4-00005-M8974AAAAANPZM-1"....so that's...good?
Click to expand...
Click to collapse
Awesome, well that's good that you eventually reached your goal. I can't say for sure why your connection was unstable on the Stock Kit Kat, but the 35B baseband is for 35B (5.1.1) Lollipop. The TOT method flashes back Stock Firmware, which is 10B (I believe 4.2.2) - KitKat so you would then need the Stock Modem IMG: (10B Modem File) but you are past that.. which is great. The Phone Service not responding is, I'm sure, a result of the incompatible 35B Modem mixing with 10B (4.2.2) Software Version. That's why flashing XDABBEB's Stock ROM fixed it (at least the second time around), because it includes all the stock IMGs, including the stock Baseband Version (10B).
But I'm so glad that you re-flashed and wiped again, because you have literally managed to return it to complete stock. Your baseband is official, and seems to me.. completely fixed!
Just confused with this:
It seems to run faster on Marshmallow than it did on Lollipop.
Click to expand...
Click to collapse
Are you running Marshmallow now? Or Kit Kat? I think I just lost you at some point haha.
But congrats on fully flipping your situation around! And in fact, because you fixed your Baseband issue, this thread is now completely answered! :good:
The TOT Method does wonders, doesn't it :victory:
Sorry, the stock ROM I used is http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's identical to what Verizon sent out last month except it is rooted, which I don't know why phone providers are so against letting their customers have full access to phones they either own or are leasing. I own this phone. It's paid in full. I want root access... Anyways, yes, it's Marshmallow.
Knux Kitsune said:
Sorry, the stock ROM I used is http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's identical to what Verizon sent out last month except it is rooted, which I don't know why phone providers are so against letting their customers have full access to phones they either own or are leasing. I own this phone. It's paid in full. I want root access... Anyways, yes, it's Marshmallow.
Click to expand...
Click to collapse
Ohhh, I see. I totally agree with you, it really makes no sense... the phone was built a certain way, it was meant to be used like that. Why the providers "nerf" them, I don't know. Even with the FM radio, they disable the receiver on the phones, I assume so that we are forced to stream instead, and they make more money. It's absolute sh**. But yeah, alright well that's cool, I might have to flash that myself actually, Marshmallow is lookin' really nice, as long as the battery life ain't too bad I'm gonna test it out myself!
Excuse me, first i´m sorry for my bad english language. I have same problem the unsupported baseband, but till now i just feel confused. I flash the Resurrection Remix Nougat on twrp and says unsupported baseband error. What should i do first? Flash the new baseband? If it yes, which baseband version is suitable for my device. Im using LG d855 and running android 6. Or i must unlock bootloader before flashing the new ROM? Thankyou, hope anyone will answer my stupid question.
I am using micromax q372 smartphone, had an android 5.0 stock ROM, and now i have installed resurrection remix 5.5.9, and my DEVICE OFFICIALY DOESN'T SUPPORT, and I garbed all of my luck and installed it, and now I have a fully working custom ROM on a unsupported device, the only problem I had was with the data connection, and I sorted it out, now everything is working, .............now I want to install resurrection remix 5.9.X , and my device doesn't is not on the support list, so ....can I do it , without any bugs? .......plz advice me

TWRP: failed to mount \data, \system, \cache

Hey all,
Fairly new to custom roms, so hopefully I'm asking a legit question. My phone is a D855, currently on DU 10.3. I wanted to upgrade to the 10.4, doing a clean install, but I seemingly cannot wipe anything. TWRP (using 3.0.2) will give an error message: failed to mount \[...]. Interestingly, flashify labels the recovery as Stock, so maybe there is a connection.
I have been doing some googling/"xda-ing" and as it seems, going back to stock can help. BUT, for one, I hope that there's an easier way, and also I would like to know what's causing this issue. Maybe it can be avoided somehow? So maybe someone can help me with that?
Cheers.
Just going to add a few more specific questions. As I am rather unexperienced, I don't want just to try things out without a confirmation that it's safe to go:
- TWRP: can I just try and reflash the newest one via flashify? Or maybe recover an old backup and update? Might it solve the issue and is it safe to go?
- If I have to revert back to stock: I'm coming from stock MM -> root -> Dirty Unicorns. Can I revert back to MM directly using that LG up method, or would you rather recommend flashing Lollipop, if I want to root again anyways? There seems to be a plethora of options for flashing stock (MM to MM, MM to LP, LP to MM, ...) and I am not sure which one applies here...
Hey. I had similar problem with my ls990. And tried all means to fix. Twrp was not mounting the system and sometimes internal storage appears as 0mb. It was so frustrating. So i resorted back to stock. But why flashing stock i got hooked at 98% and since then i was not able to do anything. My phone hardbricked.
Ugh, great prospects. :\
Really hope I can sort this out. At least, my phone is running fine so far, so no need to hurry. Glad for any idea!
Dellocatus said:
Ugh, great prospects. :\
Really hope I can sort this out. At least, my phone is running fine so far, so no need to hurry. Glad for any idea!
Click to expand...
Click to collapse
Wait. Let me understand you well. U can boot up phone? U mean the only issue is you not able to flash anything via recovery right?
Oh, forgot to mention explicitly that the phone is still running fine. So yeah - I just cannot wipe and thus cannot flash anything. So for now, I am stuck with the rom I am on, unless I find a solution to the problem.

Trace bootloop after ROM install

Hi guys.
I have tried to take a logcat of my phone when it bootloops upon restarting after install. Here is the code I used:
Code:
adb -d logcat>C:\adb>Bootloop.txt
However, the output file is empty.
My issue is that I can install any stock-based ROM, but not any custom ROMs (CM or AOSP). When I try to install custom ROMs (CM or AOSP) it always bootloops.
So I am trying to trace the phone when it bootloops. My PC does recognise the phone, as I get the message "This device can perform faster if blah, blah, blah".
Is there another way I can trace the boot up process to find out what errors its throwing out?
Thx in advance.
theKramer
I don't know if USB Debugging is turned on my default on custom ROMs - it isn't on stock ROMs, so logcat wouldn't work via ADB until that would be enabled, which if the custom ROM bootloops from the very start, obviously you wouldn't be able to turn it on.
Have you re-wiped Cache, Dalvik/ART and Data? Flash the appropriate Bootstack? Try moving what you want to keep from your internal storage, eject your MicroSD card/keep it ejected and wipe/reformat your internal storage from TWRP. You can always turn the phone off from TWRP after flashing the custom ROM/Bootstack and then eject the card. Last but not least, try flashing the TOT to start fresh, reroot with the Stump app, put TWRP on with TWRP Manager, and flash the custom ROM and Bootstack like that, although if you go back to stock again after that, I recommend flashing the TOT again before doing so, as some people have trouble with signal or mobile data coming from non-stock or international-stock based ROMs.
Edit: Just noticed you're on the D855, so I don't know the TOT situation there - I only know the VS985, but the advice still stands.
roirraW "edor" ehT said:
I don't know if USB Debugging is turned on my default on custom ROMs - it isn't on stock ROMs, so logcat wouldn't work via ADB until that would be enabled, which if the custom ROM bootloops from the very start, obviously you wouldn't be able to turn it on.
Have you re-wiped Cache, Dalvik/ART and Data? Flash the appropriate Bootstack? Try moving what you want to keep from your internal storage, eject your MicroSD card/keep it ejected and wipe/reformat your internal storage from TWRP. You can always turn the phone off from TWRP after flashing the custom ROM/Bootstack and then eject the card. Last but not least, try flashing the TOT to start fresh, reroot with the Stump app, put TWRP on with TWRP Manager, and flash the custom ROM and Bootstack like that, although if you go back to stock again after that, I recommend flashing the TOT again before doing so, as some people have trouble with signal or mobile data coming from non-stock or international-stock based ROMs.
Edit: Just noticed you're on the D855, so I don't know the TOT situation there - I only know the VS985, but the advice still stands.
Click to expand...
Click to collapse
Hi @roirraW "edor" ehT
This is a long ongoing issue. Basically it surfaced after flashing back to stock as I was having random reboots and thought it might be custom ROM related, but after flashing stock I still had the reboot issues, so figured out battery was toast so changed that and reboot issues were resolved.
But since flashing stock MM on my D855, I cannot get any custom ROM (CM/AOSP) to boot on my ROM except Bumped 5.0.1 ROMs.
I can install any stock or stock-based ROM without any issue, however, custom, no go. The funny thing is that I was running custom ROMs on my phone for more than a year without issue. I could throw any custom ROM at it, and where other people might have issues, my phone would always run them flawlessly.
Not anymore
I have flashed stock Lollipop about 7 or 8 times (via LGUP and LG Flash Tool 2014) and stock KK about another 4 times, so I should have blown out any MM remnants at this stage.
The weird thing is that my phone doesnt boot up with stock based KK either (all of them just hang on bootup), but LP or MM is no issue. I am running LIMITLESS ROM v10.2 at the moment (based on v30a). I cannot remember if I tried v10b actually, I did so many of them..
I have rooted from LP each time, and it is always successful (I have used 3 or 4 different rooting methods) and TWRP is successfully bumped each time.
I have tried numerous versions of TWRP (2.6/2.8/3.0/3.0.2).
I have done a full wipes (cache/dalvik/data/system), even including a format data after and still no luck..
The reason I was asking about methods to get some kind of log info during bootup was so I could maybe get some info on why it doesnt boot custom ROMs..
theKramer said:
Hi @roirraW "edor" ehT
Click to expand...
Click to collapse
Hi! Argh. Sounds really frustrating! Bear with me since it sounds like you know what you're doing and again I have the VS985. Among the 100% stock unrooted you flashed, did you only flash KDZs or is there a TOT available and did you try that? The reason I ask is that TOTs flash more partitions than KDZs and can fix problems that KDZs and ROMs can't. I can personally attest to that but once I experienced it and asked an experienced developer, it became clear that's expected, and when I extracted the partitions out of the VS985 10B TOT and compared to the KDZ I indeed noticed one or two more partitions.
Again, don't mind me if I'm telling what you already know. The other thing is the Bootstack situation, although I haven't ever experienced a bootloop due to the wrong Bootstack, only non-working modem or dangerous combo of our Marshmallow sbl1 partition along with the BUMP-vulnerable 12B aboot (bootloader), necessary for TWRP and for root on Marshmallow. Reference this VS985 post if needed http://forum.xda-developers.com/showpost.php?p=63438031&postcount=2. I don't really expect that to be the issue and since you tried from a variety of stock ROM situations, I wouldn't have expected you to have an issue with every combo you tried.
Edit: actually, the remaining item is the MicroSD card. I know it sounds silly but it's happened. Try it without the card and see what happens. While you're at it, try with the SIM ejected too just for the heck of it, won't hurt to try.
Good luck! Hope you figure it out.
roirraW "edor" ehT said:
Hi! Argh. Sounds really frustrating! Bear with me since it sounds like you know what you're doing and again I have the VS985. Among the 100% stock unrooted you flashed, did you only flash KDZs or is there a TOT available and did you try that? The reason I ask is that TOTs flash more partitions than KDZs and can fix problems that KDZs and ROMs can't. I can personally attest to that but once I experienced it and asked an experienced developer, it became clear that's expected, and when I extracted the partitions out of the VS985 10B TOT and compared to the KDZ I indeed noticed one or two more partitions.
Again, don't mind me if I'm telling what you already know. The other thing is the Bootstack situation, although I haven't ever experienced a bootloop due to the wrong Bootstack, only non-working modem or dangerous combo of our Marshmallow sbl1 partition along with the BUMP-vulnerable 12B aboot (bootloader), necessary for TWRP and for root on Marshmallow. Reference this VS985 post if needed http://forum.xda-developers.com/showpost.php?p=63438031&postcount=2. I don't really expect that to be the issue and since you tried from a variety of stock ROM situations, I wouldn't have expected you to have an issue with every combo you tried.
Edit: actually, the remaining item is the MicroSD card. I know it sounds silly but it's happened. Try it without the card and see what happens. While you're at it, try with the SIM ejected too just for the heck of it, won't hurt to try.
Good luck! Hope you figure it out.
Click to expand...
Click to collapse
Hi.
I didnt know that about there being more partitions in TOT vs KDZ files actually..
I have tried flashing without SD card also already.. I haven't tried without sim card, so why not
Is there a specific reason you mentioned flashing v10b, by the way?
theKramer said:
Hi.
I didnt know that about there being more partitions in TOT vs KDZ files actually..
I have tried flashing without SD card also already.. I haven't tried without sim card, so why not
Is there a specific reason you mentioned flashing v10b, by the way?
Click to expand...
Click to collapse
In the case of the VS985, 10B is the first or earliest build we have, and we have a TOT of it, so I was just using it as an example. I've only ever noticed a leak of one TOT per variant of a device at the most, but if you have more than one available I would choose the earliest.
Mostly useless information to you, but the VS985 does have a 10B KDZ, but it's 10B_01, whereas the TOT is 10B_03. 10B_03 was the official release so it can get OTAs, and 10B_01 was a leak so it can't. From what I've seen, the sub-build _## is only available as part of the filename when you get a hold of the KDZ and TOT. 10B for the VS985 is also the easiest to root because we can just use the Stump app with its brute force option. For us, rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B. Both 10B and 12B are still KitKat. 23C and 24B 5.0.1 are rootable via PC/USB/adb script. As far as I remember, 35B 5.1.1 and definitely 46A through 48A 6.0 has no method of permanent root, only KingRoot on 35B through 47A which gives temporary and suspicious root.
roirraW "edor" ehT said:
In the case of the VS985, 10B is the first or earliest build we have, and we have a TOT of it, so I was just using it as an example. I've only ever noticed a leak of one TOT per variant of a device at the most, but if you have more than one available I would choose the earliest.
Mostly useless information to you, but the VS985 does have a 10B KDZ, but it's 10B_01, whereas the TOT is 10B_03. 10B_03 was the official release so it can get OTAs, and 10B_01 was a leak so it can't. From what I've seen, the sub-build _## is only available as part of the filename when you get a hold of the KDZ and TOT. 10B for the VS985 is also the easiest to root because we can just use the Stump app with its brute force option. For us, rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B. Both 10B and 12B are still KitKat. 23C and 24B 5.0.1 are rootable via PC/USB/adb script. As far as I remember, 35B 5.1.1 and definitely 46A through 48A 6.0 has no method of permanent root, only KingRoot on 35B through 47A which gives temporary and suspicious root.
Click to expand...
Click to collapse
So, I haven't actually flashed v10b as I have handed my phone in to a phone repair shop as I have been having a number of hardware issues such as wifi not working, high temperatures at the back of the phone and SIM card detection issues (most likely related to the phone heating up).
However, before I had handed it in to the shop, I flashed a custom kernel (Gabriel stock-based) on the stock ROM I was running at the time, and that reminded me that I have flashed Gabriel kernel on a number of different stock and stock-based ROMs, and if I flashed a stock-based custom kernel, I also got the same bootloop error.
So I was wondering if that might help in any way to pinpoint what is going on with my phone...
theKramer said:
However, before I had handed it in to the shop, I flashed a custom kernel (Gabriel stock-based) on the stock ROM I was running at the time, and that reminded me that I have flashed Gabriel kernel on a number of different stock and stock-based ROMs, and if I flashed a stock-based custom kernel, I also got the same bootloop error.
So I was wondering if that might help in any way to pinpoint what is going on with my phone...
Click to expand...
Click to collapse
I don't think that's specific enough to narrow things down any in this case, but doesn't hurt to note the info! Good luck with your phone!
roirraW "edor" ehT said:
I don't think that's specific enough to narrow things down any in this case, but doesn't hurt to note the info! Good luck with your phone!
Click to expand...
Click to collapse
So my feeling is that there is something up with my boot image, even though my phone is rooted and bumped and TWRP is bumped, there is something my phone doesnt like in AOSP/CM or modified stock-based kernels that is not visible in LG stock.
Is there any tool/script that I can run that would collect info on the boot process...
theKramer said:
So my feeling is that there is something up with my boot image, even though my phone is rooted and bumped and TWRP is bumped, there is something my phone doesnt like in AOSP/CM or modified stock-based kernels that is not visible in LG stock.
Is there any tool/script that I can run that would collect info on the boot process...
Click to expand...
Click to collapse
I'm not very knowledgeable about logs or experienced collecting or looking through them, but maybe collecting a logcat through adb (over USB) while booting would help? You'd have to have USB Debugging turned on, and make sure it stays on across reboots - there's a common issue that is easy to resolve where if USB Debugging doesn't stay on after you reboot, turn it on, plug it into a PC, manually switch the USB connection mode on the phone from MTP and PTP and back to MTP and then disconnect the cable, and it'll stay on then.
roirraW "edor" ehT said:
I'm not very knowledgeable about logs or experienced collecting or looking through them, but maybe collecting a logcat through adb (over USB) while booting would help? You'd have to have USB Debugging turned on, and make sure it stays on across reboots - there's a common issue that is easy to resolve where if USB Debugging doesn't stay on after you reboot, turn it on, plug it into a PC, manually switch the USB connection mode on the phone from MTP and PTP and back to MTP and then disconnect the cable, and it'll stay on then.
Click to expand...
Click to collapse
So, I was suggested the app Liveboot, which was created by Chainfire of SuperSU fame. This app outputs a log to the screen and to a log file on the device of all the calls that are made during bootup (with user selectable level of detail).
Running this app, I did two traces. One with just stock LG and the second after flashing a modified stock kernel..
The stock log is 21KB, the log from when I flashed the modified kernel is 904KB.
Liveboot Stock
Liveboot with kernel
This is not an issue with the modified kernel per se, but with some settings in modified kernels. Any way to pinpoint the offending code/parameter?
This is not directed at you "roirraW "edor" ehT", but to any and all that could help me to figure out what is going on..
theKramer said:
So, I was suggested the app Liveboot, which was created by Chainfire of SuperSU fame. This app outputs a log to the screen and to a log file on the device of all the calls that are made during bootup (with user selectable level of detail).
Click to expand...
Click to collapse
Just wanted to say thanks for a reminder about that app. I had even tested the app when it first came out and I somehow keep forgetting about it.
So I have isolated the issue to some kind of hardware issue.
If I leave my phone turned off for a while with battery out, I can get it to boot custom ROMs. I have tried with 2 different batteries, so its definitely the phone itself. If I reboot the phone once the phone has booted up, then it boot loops again, even if the phone is only booted for a few minutes.
I had to debick my phone a couple of months ago using the short circuit method (due to some stupidity on my part) and it seems that that has fried something in my phone.
Since I brought my phone back to life I have been having issues with Wifi and SD-card slot not working, plus lots of heat and terrible battery life.
I would love to know though what it is in custom ROMs/Kernels that causes my phone to bootloop.
It would be great if I could isolate that somehow.
Anybody have any ideas, by any chance?

Categories

Resources