I have been dealing with this problem for about three weeks now, and nowhere have I been able to find a workable solution to the problem. I've gone the route of wiping cache, dalvik, system and data, let the phone boot to "No OS" then attempt the flash, but so far I have just wasted time and achieved no viable ends from these various means.
Is there anyone who actually know what the problem is with this? The device is a rooted LG G3 VS985. I'm running TRWP v2.8.6.0. I would really like to get to the root of this problem (slight pun intended) so that I can get back to upgrading my ROMs as BlissRom releases them.
MoparOso said:
I have been dealing with this problem for about three weeks now, and nowhere have I been able to find a workable solution to the problem. I've gone the route of wiping cache, dalvik, system and data, let the phone boot to "No OS" then attempt the flash, but so far I have just wasted time and achieved no viable ends from these various means.
Is there anyone who actually know what the problem is with this? The device is a rooted LG G3 VS985. I'm running TRWP v2.8.6.0. I would really like to get to the root of this problem (slight pun intended) so that I can get back to upgrading my ROMs as BlissRom releases them.
Click to expand...
Click to collapse
Most likely you are failing a baseband check that CM based ROMs started doing a few weeks ago. Flash this modem before you try and flash the ROM: https://www.androidfilehost.com/?fid=95916177934553732
It should flash after that. If not, please post a screenshot of your recovery screen(vol down + power at the same time) so we can see the error.
And here's a link to our modems: http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4
If you don't like the 23c modem you can flash whichever one you want after you get your ROM flashed.
startswithPendswithOOH said:
Most likely you are failing a baseband check that CM based ROMs started doing a few weeks ago. Flash this modem before you try and flash the ROM: https://www.androidfilehost.com/?fid=95916177934553732
It should flash after that. If not, please post a screenshot of your recovery screen(vol down + power at the same time) so we can see the error.
And here's a link to our modems: http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4
If you don't like the 23c modem you can flash whichever one you want after you get your ROM flashed.
Click to expand...
Click to collapse
Thank you so much for an intelligent and more important workable solution to my problem. I used your modem, version 23C. It worked great. I can't thank you enough.
startswithPendswithOOH said:
Most likely you are failing a baseband check that CM based ROMs started doing a few weeks ago. Flash this modem before you try and flash the ROM: https://www.androidfilehost.com/?fid=95916177934553732
It should flash after that. If not, please post a screenshot of your recovery screen(vol down + power at the same time) so we can see the error.
And here's a link to our modems: http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4
If you don't like the 23c modem you can flash whichever one you want after you get your ROM flashed.
Click to expand...
Click to collapse
This also worked for me, 23c modem prior to rom and all is well. Thank you!
startswithPendswithOOH said:
Most likely you are failing a baseband check that CM based ROMs started doing a few weeks ago. Flash this modem before you try and flash the ROM: https://www.androidfilehost.com/?fid=95916177934553732
It should flash after that. If not, please post a screenshot of your recovery screen(vol down + power at the same time) so we can see the error.
And here's a link to our modems: http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4
If you don't like the 23c modem you can flash whichever one you want after you get your ROM flashed.
Click to expand...
Click to collapse
Hi all, incredibly noon here. I faced the same error but it's still present after I flashed the modem. Anyone can help? I tried to screencap but I don't think it worked in recovery mode.
help
having same problem after trying to install cm13 on lg g3 verzon tryed flashing modem 23c still no luck please help
lazy445 said:
having same problem after trying to install cm13 on lg g3 verzon tryed flashing modem 23c still no luck please help
Click to expand...
Click to collapse
You probably need the 35b modem to get past the baseband check. But the 35b modem alone may have some issues if you don't flash the whole bootstack with it. So flash this 35b bootstack 1st( https://www.androidfilehost.com/?fid=24052804347843993 ), then flash the ROM & MM gapps.
OR - if you really like the 23c or 24b modem and don't want to use the 35b, you can flash just the 35b modem( http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4) to get past the check, flash the ROM, and then flash whatever modem you prefer. I use the 24b modem/boostack on MM ROMs and it works fine...not sure about 23c.
startswithPendswithOOH said:
You probably need the 35b modem to get past the baseband check. But the 35b modem alone may have some issues if you don't flash the whole bootstack with it. So flash this 35b bootstack 1st( https://www.androidfilehost.com/?fid=24052804347843993 ), then flash the ROM & MM gapps.
OR - if you really like the 23c or 24b modem and don't want to use the 35b, you can flash just the 35b modem( http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4) to get past the check, flash the ROM, and then flash whatever modem you prefer. I use the 24b modem/boostack on MM ROMs and it works fine...not sure about 23c.
Click to expand...
Click to collapse
I got it to work with 35b but don't have data? Any sugestions
lazy445 said:
I got it to work with 35b but don't have data? Any sugestions
Click to expand...
Click to collapse
K...that's a bummer. I'm not on cm13 rt now...I'm on candy6(which is very nice BTW) so if there is a ROM issue that is causing the no data - I would have no idea about it. Best to check the CM threads and see if anyone else has the issue. It could be something simple like changing your apns or whatever normally causes data issues...or maybe you just got a bad build.
But if you think it's a radio issue - did you flash the whole 35b bootstack, or just the modem? If just the modem then try flashing the 35b bootstack as well - or just downgrade your modem to 24b.
If you flashed the 35b bootstack and want to downgrade to 24b you'll need to downgrade the entire bootstack and not just the modem because it will probably give you issues. For ex, as an experiment, I just flashed Temasek cm13 with 35b bootstack and have data working (if you want to try that build instead... http://forum.xda-developers.com/ver...aseks-unofficial-build-lollipop-5-01-t2965501 ) & the 24b boostack also worked normally as well. But if I mix bootstacks and modems(35b bootstack with 24b modem, & vice versa) the phone won't boot past the LG splash screen. You can find the 24b bootstack here if you need it(and read post #2 if you want to know more about bootstacks)... http://forum.xda-developers.com/verizon-lg-g3/development/xdabbeb-s-vs980-2-0-0-t3231279
Personally I find the whole bootstack thing annoying and don't see any significant benefit from using the newer modem which is why I stick with using the 24b modem/bootstack, flash the 35b modem to pass the initial check if I need to, and flash the 24b modem and reboot. It just makes life easier when restoring my nandroid backups. But that's just me & to each his own
startswithPendswithOOH said:
You probably need the 35b modem to get past the baseband check. But the 35b modem alone may have some issues if you don't flash the whole bootstack with it. So flash this 35b bootstack 1st( https://www.androidfilehost.com/?fid=24052804347843993 ), then flash the ROM & MM gapps.
OR - if you really like the 23c or 24b modem and don't want to use the 35b, you can flash just the 35b modem( http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4) to get past the check, flash the ROM, and then flash whatever modem you prefer. I use the 24b modem/boostack on MM ROMs and it works fine...not sure about 23c.
Click to expand...
Click to collapse
startswithPendswithOOH said:
K...that's a bummer. I'm not on cm13 rt now...I'm on candy6(which is very nice BTW) so if there is a ROM issue that is causing the no data - I would have no idea about it. Best to check the CM threads and see if anyone else has the issue. It could be something simple like changing your apns or whatever normally causes data issues...or maybe you just got a bad build.
But if you think it's a radio issue - did you flash the whole 35b bootstack, or just the modem? If just the modem then try flashing the 35b bootstack as well - or just downgrade your modem to 24b.
If you flashed the 35b bootstack and want to downgrade to 24b you'll need to downgrade the entire bootstack and not just the modem because it will probably give you issues. For ex, as an experiment, I just flashed Temasek cm13 with 35b bootstack and have data working (if you want to try that build instead... http://forum.xda-developers.com/ver...aseks-unofficial-build-lollipop-5-01-t2965501 ) & the 24b boostack also worked normally as well. But if I mix bootstacks and modems(35b bootstack with 24b modem, & vice versa) the phone won't boot past the LG splash screen. You can find the 24b bootstack here if you need it(and read post #2 if you want to know more about bootstacks)... http://forum.xda-developers.com/verizon-lg-g3/development/xdabbeb-s-vs980-2-0-0-t3231279
Personally I find the whole bootstack thing annoying and don't see any significant benefit from using the newer modem which is why I stick with using the 24b modem/bootstack, flash the 35b modem to pass the initial check if I need to, and flash the 24b modem and reboot. It just makes life easier when restoring my nandroid backups. But that's just me & to each his own
Click to expand...
Click to collapse
Do you think the 24b boot stack will fix data. If so can you link that. Also if you find apn fixed for cm13 lg g3 data
lazy445 said:
Do you think the 24b boot stack will fix data. If so can you link that. Also if you find apn fixed for cm13 lg g3 data
Click to expand...
Click to collapse
It is already linked in the last post...xdabbebs vs985 thread has 35b, 24b, and 12b bootstack links.
And I don't use cm13(too many bugs) so I'm not familiar, but if you Google Verizon APN settings you'll find what you need.
MoparOso said:
I have been dealing with this problem for about three weeks now, and nowhere have I been able to find a workable solution to the problem. I've gone the route of wiping cache, dalvik, system and data, let the phone boot to "No OS" then attempt the flash, but so far I have just wasted time and achieved no viable ends from these various means.
Is there anyone who actually know what the problem is with this? The device is a rooted LG G3 VS985. I'm running TRWP v2.8.6.0. I would really like to get to the root of this problem (slight pun intended) so that I can get back to upgrading my ROMs as BlissRom releases them.
Click to expand...
Click to collapse
I have LG G3 D858HK (D858HK20e-HKG-XX) and I'm having the same problem when trying to flash Android 6.0 ROM to my phone with TWRP Recovery, anyone knows what's this and how to fix it, please HELP!!!
Dear i have the same problem, my cell fone is LG g3 vs985, it was running on stock Rom 4.4.2 kitkat, then i tried to upgrade it, i managed to upgrade it on Fulmics 6.5, i used it fot month, but it seems that its a bit slow, i checked out for other Custom Roms, LineageOS or Ressurection Remix 7.0 are my choices, but unfortunatly, i could not manage to flash them, i had to downgrade my fone to stock using TOT method, then i installed recovery n root it, as it is required to flash a custom ROm but i get error while flashing n now i m Operationg system less plz some one help....
Sent from my HUAWEI ALE-L21 using XDA Labs
---------- Post added at 12:02 PM ---------- Previous post was at 11:59 AM ----------
ASGH93 said:
I have LG G3 D858HK (D858HK20e-HKG-XX) and I'm having the same problem when trying to flash Android 6.0 ROM to my phone with TWRP Recovery, anyone knows what's this and how to fix it, please HELP!!!
Click to expand...
Click to collapse
Dear i think u must try to flash Fulmics.7.0, its the only ROM which i found to flash with no hurdle, try it its also ful of almost extra features
Sent from my HUAWEI ALE-L21 using XDA Labs
Hey there, I just flashed 35b bootstack on lg g3 vs98510B on stock ROM 4.4.2 just check what impact does it put, I dont see any change on system about page, but I see Sim & data go on & of like its creating some problem with sim, rest is working fine. What do u say shud I it a try n flash cm based MM or N&N ROM. Will it work.
Sent from my HUAWEI ALE-L21 using XDA Labs
Related
Hey guys, I i see that JasmineROM has some instructions on updated using an Installrom.sh file or something, when I updated to 23B (SkyDragon 3.0.0 to be exact) I just KDZ'd back to 10c, rooted and flashed a bump'd TWRP and than flashed the SkyDragon 3.0.0 full on top and everything seems to work. I have since tried a few different roms and am now on SlimLP, but I want to know if this is an ok way to upgrade? Is there any reason to use the JasmineROM's creator (I forget his name, sorry) update method with the installrom.sh over this method?
The InstallROM.sh method was for JasmineROM v5.0. 6.0 is just a normal flashable zip. Just flash it from TWRP, doesn't matter what you're on currently.
roirraW "edor" ehT said:
The InstallROM.sh method was for JasmineROM v5.0. 6.0 is just a normal flashable zip. Just flash it from TWRP, doesn't matter what you're on currently.
Click to expand...
Click to collapse
Okay, just to be sure, if I'm on stock 10c but rooted and twrp'd than I can just flash the jasmine ROM 6.0 and everything is good?
r3xx3r said:
Okay, just to be sure, if I'm on stock 10c but rooted and twrp'd than I can just flash the jasmine ROM 6.0 and everything is good?
Click to expand...
Click to collapse
i havent been following this closely, but i didnt think you would be able to flash up ever without installing the base first.
unless something changed, you would need to install the 5.0 base first, then you could flash 6.0, but you should verify, there may have been new developments i wasnt privy to.
r3xx3r said:
Okay, just to be sure, if I'm on stock 10c but rooted and twrp'd than I can just flash the jasmine ROM 6.0 and everything is good?
Click to expand...
Click to collapse
Yes. Honest. Triply sure. @hsbadr is additionally very complete and accurate in his instructions for flashing his ROMs, along with caveats if there were any, which there are none for 6.0.
bweN diorD said:
i havent been following this closely, but i didnt think you would be able to flash up ever without installing the base first.
unless something changed, you would need to install the 5.0 base first, then you could flash 6.0, but you should verify, there may have been new developments i wasnt privy to.
Click to expand...
Click to collapse
6.0 is the new base (of 23C). 5.0 of course, was 23B. 6.0 includes every single .img file from 100% complete stock 23C except it also has the 12B aboot.img and bump'd 23C kernel instead of the originals (for 23C) of those. The 6.0 zip includes all of said .img files and then additionally includes the file/folder structure necessary to modify them to mold them into what becomes debloated and tweaked JasmineROM 6.0.
This is why I was able to simply take the .img files out of his 6.0 zip and use them with his installROM.sh script from 5.0 in order to install complete 100% stock (system) 23C in an all-in-one working manner through TWRP's Terminal Command option in the Advanced menu since I like to debloat and tweak my own way. I manually flashed SuperSU.zip since obviously the stock .img files don't include root, and since I don't use anything from the 6.0 zip except the .img files, and it's the additional files in his 6.0 zip which do all the debloating and tweaking.
Sorry for repeating myself.
It's really great the way he's done it since anyone can (assuming having a reasonably up to date TWRP) get 23C installed.
Personally, I think Verizon is just having fun with us at this point.
roirraW "edor" ehT said:
Yes. Honest. Triply sure. @hsbadr is additionally very complete and accurate in his instructions for flashing his ROMs, along with caveats if there were any, which there are none for 6.0.
6.0 is the new base (of 23C). 5.0 of course, was 23B. 6.0 includes every single .img file from 100% complete stock 23C except it also has the 12B aboot.img and bump'd 23C kernel instead of the originals (for 23C) of those. The 6.0 zip includes all of said .img files and then additionally includes the file/folder structure necessary to modify them to mold them into what becomes debloated and tweaked JasmineROM 6.0.
This is why I was able to simply take the .img files out of his 6.0 zip and use them with his installROM.sh script from 5.0 in order to install complete 100% stock (system) 23C in an all-in-one working manner through TWRP's Terminal Command option in the Advanced menu since I like to debloat and tweak my own way. I manually flashed SuperSU.zip since obviously the stock .img files don't include root, and since I don't use anything from the 6.0 zip except the .img files, and it's the additional files in his 6.0 zip which do all the debloating and tweaking.
Sorry for repeating myself.
It's really great the way he's done it since anyone can (assuming having a reasonably up to date TWRP) get 23C installed.
Personally, I think Verizon is just having fun with us at this point.
Click to expand...
Click to collapse
thanks for explaining.
one question though, where did the unrooted system file come from?
root is required to pull the system, therefore its rooted by default.
just curious,
thanks
Thank you guys for the great explanations. I am still getting used to the G3. My old Galaxy S4 from T-mo was very different. I have another question now. If I want to run an AOSP rom, like SlimLP, would anything be different if I flashed JasmineROM 6.0 than SlimLP?? Do the basebands or anything like that change from 23b to 23c and would they stick between roms??
bweN diorD said:
thanks for explaining.
one question though, where did the unrooted system file come from?
root is required to pull the system, therefore its rooted by default.
just curious,
thanks
Click to expand...
Click to collapse
Anytime! I've wondered the same thing. I definitely didn't have SuperSU in my app drawer before I rebooted to TWRP and flashed SuperSU.zip. I meant to do that anyway but it's just as well I find out for sure that SuperSU wasn't installed. Perhaps the system.img is technically rooted but the SuperSU app was moved from system to data before pulling the image. So binaries, etc are still in the system.img but without the SuperSU app it's effectively not rooted.
But if that were the case, I could've merely installed SuperSU from the Play Store. I didn't try that so I won't know if that's the case until I have time to play with the phone more.
@HolyAngel, can you confirm if this is how the system.img by itself for 23A/B/C doesn't "appear" rooted?
If we had the KDZ, of course, then it would be a different story since we can extract the totally pure system.img as of course you already know (just saying for other reader's benefit).
r3xx3r said:
Thank you guys for the great explanations. I am still getting used to the G3. My old Galaxy S4 from T-mo was very different. I have another question now. If I want to run an AOSP rom, like SlimLP, would anything be different if I flashed JasmineROM 6.0 than SlimLP?? Do the basebands or anything like that change from 23b to 23c and would they stick between roms??
Click to expand...
Click to collapse
You're welcome! I understand. Came from the S3 and S2 before this myself. At least KDZ is reminiscent of Odin, although it sure was easier to get custom recovery and root installed with being able to flash custom recovery from Odin. I've wondered about building KDZ packages of custom recoveries, although it'd have to flash the 12B aboot.img and a bump'd kernel, too. Since we can extract KDZs, hopefully we can create them, too. Don't know how hard it is to get LG Mobile Tool 2014 to flash custom KDZs, though, or for the phone to accept them.
Sorry I digressed. So far, AOSP/CM ROMs need 12B's modem, they won't work with 23A/B/C's modems. You can get the 12B modem from @bweN diorD 's sticky thread in the General section.
So far all 23A/B/C ROMs flash the appropriate modem. Just backup the modem when you do nandroid backups.
Sent from my VK810 4G
roirraW "edor" ehT said:
Anytime! I've wondered the same thing. I definitely didn't have SuperSU in my app drawer before I rebooted to TWRP and flashed SuperSU.zip. I meant to do that anyway but it's just as well I find out for sure that SuperSU wasn't installed. Perhaps the system.img is technically rooted but the SuperSU app was moved from system to data before pulling the image. So binaries, etc are still in the system.img but without the SuperSU app it's effectively not rooted.
But if that were the case, I could've merely installed SuperSU from the Play Store. I didn't try that so I won't know if that's the case until I have time to play with the phone more.
@HolyAngel, can you confirm if this is how the system.img by itself for 23A/B/C doesn't "appear" rooted?
If we had the KDZ, of course, then it would be a different story since we can extract the totally pure system.img as of course you already know (just saying for other reader's benefit).
You're welcome! I understand. Came from the S3 and S2 before this myself. At least KDZ is reminiscent of Odin, although it sure was easier to get custom recovery and root installed with being able to flash custom recovery from Odin. I've wondered about building KDZ packages of custom recoveries, although it'd have to flash the 12B aboot.img and a bump'd kernel, too. Since we can extract KDZs, hopefully we can create them, too. Don't know how hard it is to get LG Mobile Tool 2014 to flash custom KDZs, though, or for the phone to accept them.
Sorry I digressed. So far, AOSP/CM ROMs need 12B's modem, they won't work with 23A/B/C's modems. You can get the 12B modem from @bweN diorD 's sticky thread in the General section.
So far all 23A/B/C ROMs flash the appropriate modem. Just backup the modem when you do nandroid backups.
Sent from my VK810 4G
Click to expand...
Click to collapse
Yea, most likely the su app wasn't system, and you just need to re-install it.
I really need some help. Please please help. I have my LG G3 VS985 and it was on stock verizon firmware. I had lollipop and android 5.1.1. I rooted it using Kingroot and it was working fine. I used an app called Autorec and i tried flashing twrp using it and all it did was make my phone not turn on. It keeps vibrating and i really need your help or anyone. I'm very worried.
I have this same exact problem... anyone have a solution?
I haven't looked in @bender_007 's autorec thread in a while but last I looked he didn't provide a version for 35B, only 23C and 24B.
Even if the screen stays black, go through the motions of putting the phone in Download mode. Does your phone show up in Windows' Device Manager in the modem section? If so, flash the 10B TOT using the .DLL that's extracted from the 35B KDZ to start fresh. Re-root with the Stump app and use TWRP Manager from the Play Store to put TWRP back on.
Rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B. For what it's worth, I stick to stock but modified/heavily debloated Verizon/LG ROMs.
Always flash the 10B TOT to root and to put TWRP on, it just saves a lot of headache. Kingroot installs a bunch of stuff behind the scenes (not just apps), so it's very shady. @xdabbeb experienced just how much Kingroot modifies the ROM under the hood.
roirraW "edor" ehT said:
I haven't looked in @bender_007 's autorec thread in a while but last I looked he didn't provide a version for 35B, only 23C and 24B.
Even if the screen stays black, go through the motions of putting the phone in Download mode. Does your phone show up in Windows' Device Manager in the modem section? If so, flash the 10B TOT using the .DLL that's extracted from the 35B KDZ to start fresh. Re-root with the Stump app and use TWRP Manager from the Play Store to put TWRP back on.
Rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B. For what it's worth, I stick to stock but modified/heavily debloated Verizon/LG ROMs.
Always flash the 10B TOT to root and to put TWRP on, it just saves a lot of headache. Kingroot installs a bunch of stuff behind the scenes (not just apps), so it's very shady. @xdabbeb experienced just how much Kingroot modifies the ROM under the hood.
Click to expand...
Click to collapse
I was completely stupid and have soft bricked my phone tonight.
I had a small issue with xdabbeb's 47A and went to restore a prior nandroid. Now the phone turns on, (I can hear it) but the screen is black. I'm sure it's a bootstack 35B issue.
I'm in a panic and am having trouble finding all the correct files to TOT or KDZ back and fix my phone.
Can you please walk me through the steps?
I feel so stupid and this couldn't have happened at a worse time.
Specter597 said:
I was completely stupid and have soft bricked my phone tonight.
I had a small issue with xdabbeb's 47A and went to restore a prior nandroid. Now the phone turns on, (I can hear it) but the screen is black. I'm sure it's a bootstack 35B issue.
I'm in a panic and am having trouble finding all the correct files to TOT or KDZ back and fix my phone.
Can you please walk me through the steps?
I feel so stupid and this couldn't have happened at a worse time.
Click to expand...
Click to collapse
For KDZ, @annoyingduck 's stickied return to stock thread in the General section.
For TOT, just Google for:
Code:
TOT method
and just use the VS985 TOT and .DLL. The method is the same on all LG devices, just use the VS985 files instead of whatever the directions you find specify. You can still get the 10B TOT and the .DLL that's necessary at my Android File Host section which is linked to from the bottom of the first post of the return to stock thread I referenced. There's also a link to his thread in my signature below.
As you found out, when restoring TWRP back ups or flashing a new ROM, always flash the corresponding appropriate Bootstack after the restore or flash. 12B Bootstack for KitKat, 24B Bootstack for Lollipop 5.0.x and 35B Bootstack for Lollipop 5.1.x and Marshmallow 6.0.
roirraW "edor" ehT said:
For KDZ, @annoyingduck 's stickied return to stock thread in the General section.
For TOT, just Google for:
Code:
TOT method
and just use the VS985 TOT and .DLL. The method is the same on all LG devices, just use the VS985 files instead of whatever the directions you find specify. You can still get the 10B TOT and the .DLL that's necessary at my Android File Host section which is linked to from the bottom of the first post of the return to stock thread I referenced. There's also a link to his thread in my signature below.
As you found out, when restoring TWRP back ups or flashing a new ROM, always flash the corresponding appropriate Bootstack after the restore or flash. 12B Bootstack for KitKat, 24B Bootstack for Lollipop 5.0.x and 35B Bootstack for Lollipop 5.1.x and Marshmallow 6.0.
Click to expand...
Click to collapse
Yes, I see the link in your sig now. Thanks for responding. The 10b download is not working from that link but 12b KDZ is downloading. Should that be a problem? I can still bump and stump 12b right? Also I think 12b was what shipped with my phone.
Specter597 said:
Yes, I see the link in your sig now. Thanks for responding. The 10b download is not working from that link but 12b KDZ is downloading. Should that be a problem? I can still bump and stump 12b right? Also I think 12b was what shipped with my phone.
Click to expand...
Click to collapse
You're welcome!
You're looking at the direct links to those KDZs, right, like the following?
-VS98510b_01.kdz: -Thanks to @autoprime
-Mirror for VS98510b_01.kdz (10b): md5: d228ba692ef0c4704cba0b00fad8b8c
-VS98512b_00.kdz: -Thanks to @hokiealumnus for the AFH hosting
-Mirror for VS98512b_00.kdz (12b): md5: e8280b279d327b96689579a9eca22a3e
Click to expand...
Click to collapse
I have an Android File Host link below those that points to a folder that has all the KDZs and TOTs in one place. 10B, whether TOT or KDZ, is recommended because you can root 10B the easiest - by using the Stump app found on XDA. You can't use Stump after 10B, or at least definitely not on 12B (not 100% positive about 11C that came between). Put TWRP on after rooting with TWRP Manager from the Play Store. Installing TWRP is possible that easily on 12B if you root it using a different method. Putting TWRP on becomes more complicated after 12B, FYI.
What your phone came with doesn't affect things.
Even though your screen may stay blank, if you go through the motions of putting it in Download mode, then it will be in Download mode. Pull the battery first then put it in Download mode using the original USB cable that came with the phone, connected preferably to a USB 2.0 port that comes directly off of your PC motherboard - not through a USB hub. You can check it by looking in Windows' Device Manager to see if the "LGE..." device is listed under the Modem section.
The symptom you're having is common and isn't actually caused by a Bootstack, but by a lack of one, or probably more accurately, a catastrophic mix of conflicting partitions caused by, in this case, having one Bootstack on the device - probably 35B, and then restoring a backup that might've included only some of the partitions necessary for the Bootstack. TWRP backups don't back up the entire Bootstack, so you end up with some partitions from one, and other partitions from another, and they don't play well together.
JasmineROM and SkyDragon in particular play havok, so even if you dirty flashed either ROM after restoring a TWRP backup of either, if you had the 35B Bootstack flashed previously and didn't flash any Bootstack after dirty flashing either ROM, you'd have a mix of 24B and 35B partitions because even though the latest versions of both of those ROMs are based on 35B, they include part of the 24B Bootstack, but not even the whole thing at that. The reason they did that is because they couldn't figure out how to get the 35B modem working, and it wasn't until @xdabbeb packaged the proper Bootstacks we needed that it was realized that the 35B sbl1 - which those two ROMs don't include any kind of sbl1 partition - is necessary for the modem to work with it, so they included some 24B partitions because that modem worked fine with the older sbl1 which was still on the device from the last time the phone was flashed to stock unrooted.
We have a similar situation with 47A except in this case, besides needing the 47A sbl1 for the 47A modem to work, the 47A sbl1, in combination with the 12B aboot (bootloader) causes a QHSUSB_BULK 9008 mode type of brick, which requires different instructions for recovering than the normal KDZ or TOT methods, although it does use the TOT as part of the recovery, and then you flash the entire TOT method afterwards.
Sorry if this is TL;DR.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
roirraW "edor" ehT said:
You're welcome!
You're looking at the direct links to those KDZs, right, like the following?
I have an Android File Host link below those that points to a folder that has all the KDZs and TOTs in one place.
Click to expand...
Click to collapse
I followed to your Android Host link and was getting errors on primary DL and mirrors for 10b KDZ and 10b TOT. That is why I started DLing the 12b
10B, whether TOT or KDZ, is recommended because you can root 10B the easiest - by using the Stump app found on XDA. You can't use Stump after 10B, or at least definitely not on 12B (not 100% positive about 11C that came between). Put TWRP on after rooting with TWRP Manager from the Play Store. Installing TWRP is possible that easily on 12B if you root it using a different method. Putting TWRP on becomes more complicated after 12B, FYI.
Click to expand...
Click to collapse
I think the most recent version of Stump could brute force 12b. I never TOT'd back to 10b when I bought my phone so it may have worked a year or so ago. But I will try downloading 10b KDZ and 10b TOT/.DLL in a few minutes and see if the Android Host File DL's are working again.
Is there any problem with KDZ'ing now and TOT'ing later? I understand the limitation on KDZ and Updates. But KDZ doesn't prevent a future TOT does it?
About the TL;DR - I read it. You describe EXACTLY what I did. I was on Jasmine 9.1; I successfully installed 47A but TWRP borked my MMS/SMS backups so I thought, "I'll restore my TWRP nandroid AND (because I thought I was clever) I'll dirty flash the ROM and Update over the Nandroid so that the partitions are correct!"
... and here we are.:crying:
Specter597 said:
I followed to your Android Host link and was getting errors on primary DL and mirrors for 10b KDZ and 10b TOT. That is why I started DLing the 12b
I think the most recent version of Stump could brute force 12b. I never TOT'd back to 10b when I bought my phone so it may have worked a year or so ago. But I will try downloading 10b KDZ and 10b TOT/.DLL in a few minutes and see if the Android Host File DL's are working again.
Is there any problem with KDZ'ing now and TOT'ing later? I understand the limitation on KDZ and Updates. But KDZ doesn't prevent a future TOT does it?
About the TL;DR - I read it. You describe EXACTLY what I did. I was on Jasmine 9.1; I successfully installed 47A but TWRP borked my MMS/SMS backups so I thought, "I'll restore my TWRP nandroid AND (because I thought I was clever) I'll dirty flash the ROM and Update over the Nandroid so that the partitions are correct!"
... and here we are.:crying:
Click to expand...
Click to collapse
Weird, I just checked and all the servers aren't working for me either. I might have to put all the files up somewhere else as a backup. AFH is so convenient though since developers can upload via FTP.
No, Stump won't work on 12B. You have to brute force on 10B, but it just won't work on 12B. A new root method had to be found, and they're available, some scripts in some threads in the non-Verizon G3 General section, but it requires a connection to the computer and USB Debugging mode and is less reliable than Stump.
I'll upload the 10B stuff and the .DLL elsewhere and I'll let you know if/when it's up - might take a while to upload though.
No, you can always TOT - just TOTing from stock unrooted 35B and higher requires the .DLL I have a copy of (it's extracted from the 35B KDZ). There was an older .DLL that worked fine coming from 24B and lower, but the new .DLL should work for coming from both new and old builds. And as I think you're saying you already know, if you're on stock unrooted 35B or higher you can only flash the 35B or higher KDZs, which is one of the reasons it's always suggested nowadays to flash the 10B TOT in order to root and put TWRP on.
Whether TOTing or KDZing, if you're rooted and have flashed any of @xdabbeb 's Bootstacks, then you should be able to flash the TOT with either the old or new .DLL, and you can flash any KDZ.
roirraW "edor" ehT said:
Weird, I just checked and all the servers aren't working for me either. I might have to put all the files up somewhere else as a backup. AFH is so convenient though since developers can upload via FTP.
No, Stump won't work on 12B. You have to brute force on 10B, but it just won't work on 12B. A new root method had to be found, and they're available, some scripts in some threads in the non-Verizon G3 General section, but it requires a connection to the computer and USB Debugging mode and is less reliable than Stump.
I'll upload the 10B stuff and the .DLL elsewhere and I'll let you know if/when it's up - might take a while to upload though.
No, you can always TOT - just TOTing from stock unrooted 35B and higher requires the .DLL I have a copy of (it's extracted from the 35B KDZ). There was an older .DLL that worked fine coming from 24B and lower, but the new .DLL should work for coming from both new and old builds. And as I think you're saying you already know, if you're on stock unrooted 35B or higher you can only flash the 35B or higher KDZs, which is one of the reasons it's always suggested nowadays to flash the 10B TOT in order to root and put TWRP on.
Whether TOTing or KDZing, if you're rooted and have flashed any of @xdabbeb 's Bootstacks, then you should be able to flash the TOT with either the old or new .DLL, and you can flash any KDZ.
Click to expand...
Click to collapse
Thank you, thank you. I DID manage to download the special 10b .DLL from your Android Host File location. I think I've found the 10b_3 TOT on a different site and I'll try using it with your DLL - but if I doesn't work I'll try getting yours as well when you tell me its working.
Specter597 said:
Thank you, thank you. I DID manage to download the special 10b .DLL from your Android Host File location. I think I've found the 10b_3 TOT on a different site and I'll try using it with your DLL - but if I doesn't work I'll try getting yours as well when you tell me its working.
Click to expand...
Click to collapse
You're welcome. That's good. I'm uploading the TOT and KDZ elsewhere but looks like it'll take three or more hours to finish.
Good luck!
---------- Post added at 10:03 AM ---------- Previous post was at 09:27 AM ----------
@Specter597 I had put in a ticket to Android File Host and it appears the problem was caused by me. They told me there were illegal characters in the filename and said he'd contact the uploader, not realizing the uploader was me, so he didn't mention which characters are illegal - I asked so hopefully he'll reply soon and I don't have to experiment to find the right combination.
For what it's worth, thanks for helping me to find out there was a problem with some of my filenames on AFH. Doh me!
Edit 2: Turns out it was the comma I had put in the filename. I removed the comma from that one and the 10B KDZ and now they download fine. Sigh!
This time I was successfully able to start the 10b TOT download from your AHF.
Thank you so much.
I'm going to take the time and download YOUR file out of sheer paranoia, even though the other file has finished.
Specter597 said:
This time I was successfully able to start the 10b TOT download from your AHF.
Thank you so much.
I'm going to take the time and download YOUR file out of sheer paranoia, even though the other file has finished.
Click to expand...
Click to collapse
If the MD5 hash of the TOT you had downloaded is F22CD79F6C4924A0FE4429A8C4BABE9A, then it's the same as the TOT I have inside the 7-Zip archive you're currently downloading. That's the easiest and quickest way of checking to see if you have the right thing.
I've gotten everything installed and setup, but for whatever reason Windows 7 is not showing the LGE Modem at all in COM Ports.
Do you think I should just try different Phone drivers?
Edit: Maybe I have the drivers right now.
Edit 2: The Drivers' installation seem to be spotty.
Sometimes The LGE Android MTP Device install Fails
Sometimes the LGE Mobile for VZW USB Modem fails.
But I'm having a hell of a time figuring out if I'm in Download Mode or not.
How long, @roirraW "edor" ehT after I plug in the USB cable should I continue to hold "Up"?
Specter597 said:
I've gotten everything installed and setup, but for whatever reason Windows 7 is not showing the LGE Modem at all in COM Ports.
Do you think I should just try different Phone drivers?
Edit: Maybe I have the drivers right now.
But I'm having a hell of a time figuring out if I'm in Download Mode or not.
How long, @roirraW "edor" ehT after I plug in the USB cable should I continue to hold "Up"?
Click to expand...
Click to collapse
You would only have to hold the Up volume button for at the very most 10 seconds, and that's probably extreme. If the Modem and Port sections list the LGE device now, you can be reasonably sure it's in Download mode. For TOT, change the port of the LGE device that's in the Port section (not Modem section) to 41.
I always use the latest drivers either from LG's or Verizon's website. 4.0.4 was the latest last I looked. I always reboot the PC (with the phone disconnected) after installing drivers. I don't bother updating the drivers to the latest if I already have working ones installed. With new drivers, it can take Windows up to 10 minutes to actually finish loading the drivers the first time you plug a new device into a new/different USB port. That's the way all USB devices work. In other words, if you plug the phone into port "A" in Download mode and you wait anywhere from seconds to minutes until it loads the drivers, and then unplug it and replug it into port "B", then it'll load the driver again. If you switch back to "A" it won't have to load the driver again, though.
They'll all load them from the same driver installation you did once.
Are you using the original USB cable that came with the phone? Letting the phone sit while plugged in, and not moving it around? Sometimes just rebooting the PC or trying different USB 2.0 ports help. In the end, sometimes trying a different PC helps.
Update: Success.
Successfully TOT'd back to 10b.
I decided (after installing/reinstalling the drivers 6 times) that even though it had said that some of the drivers failed to install, I would just say "F* it." Try it anyway. Despite the Windows installer saying that two elements of the DL Mode Driver package didn't install - it worked anyway. The other part that got me was that after clicking the Yellow arrow you have to unplug/plug the phone back in. What a way to spend 12 hours of my life.
Thanks for all your support @roirraW "edor" ehT
Now I just have to decide if I want to bother rooting again, install xdabbeb's 47A or just play it safe ...
Specter597 said:
Update: Success.
Successfully TOT'd back to 10b.
I decided after installing/reinstalling the drivers 6 times, that even though it had said that some of the drivers failed to install, I would just F* it. Try it anyway. The part that got me was that after clicking the Yellow arrow you have to unplug/plug the phone back in.
Thanks for all your support @roirraW "edor" ehT
Now I just have to decide if I want to bother rooting again or just play it safe ...
Click to expand...
Click to collapse
Great! You're welcome! Glad things didn't get worse from installing drivers so many times. F* it. Root it, it's so easy. Just always remember to flash the right Bootstack after flashing any ROM, even if you think you're already on the right Bootstack - doesn't matter, just flash it, there's no reason not to. You know you can't stand it without the features you get from rooting!
Hope you didn't lose anything you don't mind losing.
roirraW "edor" ehT said:
Great! You're welcome! Glad things didn't get worse from installing drivers so many times. F* it. Root it, it's so easy. Just always remember to flash the right Bootstack after flashing any ROM, even if you think you're already on the right Bootstack - doesn't matter, just flash it, there's no reason not to. You know you can't stand it without the features you get from rooting!
Hope you didn't lose anything you don't mind losing.
Click to expand...
Click to collapse
No. I don't think there was anything that I don't have backed up. (I'm a nut about cloud/sdcard/etc.) Just some SMS/MMS. Maybe a save'd game. Who cares! I still have a phone!! :laugh:
But I'm definitely deleting those Jasmine 9.1 backups. I don't even want to risk that again. Aside from Skydragon/JasmineROM are there any of the other ROM's floating in the DEV forum that will Bork my phone this badly?
And after I Root and TWRP is there any reason I can't go straight from 10b to xdabbeb's 47A?
Specter597 said:
No. I don't think there was anything that I don't have backed up. (I'm a nut about cloud/sdcard/etc.) Just some SMS/MMS. Maybe a save'd game. Who cares! I still have a phone!! :laugh:
But I'm definitely deleting those Jasmine 9.1 backups. I don't even want to risk that again. Aside from Skydragon/JasmineROM are there any of the other ROM's floating in the DEV forum that will Bork my phone this badly?
And after I Root and TWRP is there any reason I can't go straight from 10b to xdabbeb's 47A?
Click to expand...
Click to collapse
Yes you can go straight to 47A from 10B, I've done it a few times before with no problems. Also you can try out xdabbeb's 2.0 which is lollipop not marshmallow. Very slimmed down, not a whole lot of grill to it, but very smooth and reliable. I keep going back and forth between the two myself.
Sent from my g3 using XDA Labs
Specter597 said:
But I'm definitely deleting those Jasmine 9.1 backups. I don't even want to risk that again. Aside from Skydragon/JasmineROM are there any of the other ROM's floating in the DEV forum that will Bork my phone this badly?
Click to expand...
Click to collapse
Not that I'm aware of. And either ROM is just fine as long as you flash the Bootstack after, and you should do that no matter what TWRP backup or ROM you flash.
Everytime i upgrade to an international marshmallow rom i lose 4g signal and becuz of it i get "cell stanby" draining my battery heavily. I tried flashing all the basebands and bootstacks even backedup my efs from an older rom or marshmallow rom on verizon becuz my data works perfect on verizon roms. The right apns looks to be in tact. I just really want this to work becuz this is the lg g5 rom im on. (Fulmics 5.0) i can also still text and call. Just no 4g and bars.
MonstaSaleens said:
Everytime i upgrade to an international marshmallow rom i lose 4g signal and becuz of it i get "cell stanby" draining my battery heavily. I tried flashing all the basebands and bootstacks even backedup my efs from an older rom or marshmallow rom on verizon becuz my data works perfect on verizon roms. The right apns looks to be in tact. I just really want this to work becuz this is the lg g5 rom im on. (Fulmics 5.0) i can also still text and call. Just no 4g and bars.
Click to expand...
Click to collapse
If it's not specifically for the VS985, I wouldn't flash it. You'll have to either fully TOT or KDZ flash it back to fix all your partitions just to be on the safe side.
You should never flash a non-VS985 ROM on the VS985. If you do, you're taking a risk to brick it.
If this was for the VS985, then my apologies, but you didn't specify which ROM it was and I'm assuming since you're postin ghere in the Verizon G3 forums, you have the VS985 G3 and not some other variety.
iBolski said:
If it's not specifically for the VS985, I wouldn't flash it. You'll have to either fully TOT or KDZ flash it back to fix all your partitions just to be on the safe side.
You should never flash a non-VS985 ROM on the VS985. If you do, you're taking a risk to brick it.
If this was for the VS985, then my apologies, but you didn't specify which ROM it was and I'm assuming since you're postin ghere in the Verizon G3 forums, you have the VS985 G3 and not some other variety.
Click to expand...
Click to collapse
Yes it is for verizon, its fulmicsROM 5.0 i chose vs985 in aroma. Other verizon users are saying thier data works without even touching apns. Mine worked in the bigginning but after a couple hours it just did what it did in the pics and havnt worked since.
MonstaSaleens said:
Yes it is for verizon, its fulmicsROM 5.0 i chose vs985 in aroma. Other verizon users are saying thier data works without even touching apns. Mine worked in the bigginning but after a couple hours it just did what it did in the pics and havnt worked since.
Click to expand...
Click to collapse
When you flashed this ROM, what boot partition to you flash from? I did find one in the generic G3 Development forum so I'm assuming the following link is where you probably found it:
http://forum.xda-developers.com/lg-g3/development/rom-fulmics-rom-1-0-tweaks-ota-v20u-t3232340
You might have flashed it with the wrong boot and modem partition. I believe 12B is the last one that works with the current version of TWRP that is bumped for the VS985. Anything above that will not work as they haven't released a new bumped TWRP for the more recent OTAs.
I would find one of the revert back to stock threads, flash it back to a version such as 10B (via TOT or KDZ) and see if your LTE signal comes back. If so, then you should be able to root from there, flash TWRP and then hopefully flash the fulmicsROM at that point and it should hopefully work. If it doesn't work on 10B, then it sounds like your LTE antenna may be going bad.
Otherwise, I'm not sure what is going on.
Hope that helps!
I have same problem. Seems vs985 is updated to 47a witch there is no bumped boot loader for 47a. That may be our problem.
Sent from my VS985 4G using XDA-Developers mobile app
iBolski said:
When you flashed this ROM, what boot partition to you flash from? I did find one in the generic G3 Development forum so I'm assuming the following link is where you probably found it:
http://forum.xda-developers.com/lg-g3/development/rom-fulmics-rom-1-0-tweaks-ota-v20u-t3232340
You might have flashed it with the wrong boot and modem partition. I believe 12B is the last one that works with the current version of TWRP that is bumped for the VS985. Anything above that will not work as they haven't released a new bumped TWRP for the more recent OTAs.
I would find one of the revert back to stock threads, flash it back to a version such as 10B (via TOT or KDZ) and see if your LTE signal comes back. If so, then you should be able to root from there, flash TWRP and then hopefully flash the fulmicsROM at that point and it should hopefully work. If it doesn't work on 10B, then it sounds like your LTE antenna may be going bad.
Otherwise, I'm not sure what is going on.
Hope that helps!
Click to expand...
Click to collapse
Theres nothing wrong with my data when i flash any verizon rom. So when i go back to it it works perfectly. But when i go to any marshmallow rom for multiple variants my data seems it cant connect. Ive tried the kdz method like 3 times and flashed from there but it didnt work. Im not sure about what you mean by what boot partition i flashed from
MonstaSaleens said:
Theres nothing wrong with my data when i flash any verizon rom. So when i go back to it it works perfectly. But when i go to any marshmallow rom for multiple variants my data seems it cant connect. Ive tried the kdz method like 3 times and flashed from there but it didnt work. Im not sure about what you mean by what boot partition i flashed from
Click to expand...
Click to collapse
Depending on the version of Android you used KDZ'd from, that determines what your modem and boot partition are set up as. In order to flash any Marshmallow ROM, you cannot be on the current 72A boot and modem partitions. They do not work with TWRP for the G3. So based on what you've told me, where your LTE signal is fine on stock, that to me suggests one of two things:
You're flashing the custom ROM with an incorrect modem and/or boot partition (later than 10B)
The ROM itself is bad
So, you have to KDZ or TOT back to 10b and flash your ROM from there. I'm assuming that's what you've done, but I wanted to make sure.
The directions in that thread do not give the specifics for the VS985 version.
Here are directions on downgrading to 10B properly so that you can flash custom ROMs properly:
http://forum.xda-developers.com/verizon-lg-g3/general/lg-g3-downgrade-to-10b-t3354834
Here's another thread on doing the same:
http://forum.xda-developers.com/verizon-lg-g3/general/lg-g3-downgrade-to-10b-t3354834
@iBolski From what I read in the Fulmics v5.0 thread, the 12B bootstack is the one that's necessary to have data working on Verizon (for most people). The OP said he tried all the bootstacks though so no idea there.
roirraW "edor" ehT said:
@iBolski From what I read in the Fulmics v5.0 thread, the 12B bootstack is the one that's necessary to have data working on Verizon (for most people). The OP said he tried all the bootstacks though so no idea there.
Click to expand...
Click to collapse
@roirraW "edor" ehT Thanks! I must have missed that somewhere in the thread.
@MonstaSaleens, there's your answer. Make sure you TOT or KDZ back to 12B (I would flash the entire thing). @roirraW "edor" ehT has links in his sig that can point you to all the correct images and instructions you need. The first two links in his sig are what you want.
iBolski said:
@roirraW "edor" ehT Thanks! I must have missed that somewhere in the thread.
@MonstaSaleens, there's your answer. Make sure you TOT or KDZ back to 12B (I would flash the entire thing). @roirraW "edor" ehT has links in his sig that can point you to all the correct images and instructions you need. The first two links in his sig are what you want.
Click to expand...
Click to collapse
Ive done this multiple times before. I even formated internal storage. Went bakc down to 12b used stump root to root and still no data on fulmics. Ive been had problems with the data on roms that are for all varients and are marshmallow. It just doesnt like my phone. But hey, data is doing the same thing on my brothers g3 when he flashed this rom cuz he wanted the new g5 ui too.
roirraW "edor" ehT said:
@iBolski From what I read in the Fulmics v5.0 thread, the 12B bootstack is the one that's necessary to have data working on Verizon (for most people). The OP said he tried all the bootstacks though so no idea there.
Click to expand...
Click to collapse
Do we have any flashable marshmallow radios yet?
MonstaSaleens said:
Do we have any flashable marshmallow radios yet?
Click to expand...
Click to collapse
Short answer: No.
There's technical reasons why we can't use the 46A and 47A modems, at least if you want to be able to use TWRP. There's nothing to stop you from flashing the modem extracted out of the 47A KDZ, but you won't have a signal or data with the modem alone. The 46A and 47A modem require the 46A or 47A sbl1 partition.
Putting the 46A or 47A sbl1 on the phone when you already have working TWRP will cause a QHSUSB_BULK 9008 mode brick because those sbl1 really don't like the 12B (or older) bootloader, and the 12B (or 11C or 10B) bootloader is required to get into TWRP.
So...you can have either:
1. TWRP along with the 12B bootloader, but only up to 35B sbl1 and modem.
Or
2. The Marshmallow bootloader, sbl1 and modem.
I haven't tried or tested getting rid of TWRP and re-upgrading the bootloader, sbl1 and modem, but that should in theory work, at least on stock 46A and 47A ROMs - don't know about international or CM13 ROMs.
So yesterday i was using my phone as usual and then all of sudden it turned off and rebooted. Well after it turned on i tried to turn on WiFi it would not turn on at all. I thought rebooting would help but no luck. Then apps would not open. Especially SuperSu. I reset my phone using the 47A kdz because for some reason 10b tot would not work. The wifi still wont turn on. Any Help?PLZ
That's odd however when flashing ROMs and KDZs don't help trying the TOT is a must. Several months ago I had a weird problem that stayed with me no matter what ROM or KDZ I flashed. After I flashed the 10B TOT, everything's been fine since. TOTs flash more partitions than KDZs.
When you tried the TOT method, if using the original .DLL that was provided to use with the VS985 doesn't work, try the .DLL that's extracted from the 35B KDZ. I have it on Android File Host - you can find a link to my section at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section, or the first link in my signature below to get to his thread. You shouldn't have had to use the newer .DLL as far as I'm aware since you were rooted and presumably using @xdabbeb 's 35B Bootstack, which contains downgraded partitions that allow flashing older KDZs (not just 35B and newer ones) and the TOT without the newer .DLL.
Even if neither .DLL worked before, try the new one now that you flashed the KDZ.
Also, when you flashed the KDZ, did you use the CSE or Normal option? If you didn't do CSE, then try a Factory Reset. If it's some errant user/system data that's causing the WIFI problem, then only using the CSE option or Factory Reset can help. Flashing the TOT also wipes all data. Move everything you want to keep from internal storage since that'll be wiped too.
roirraW "edor" ehT said:
That's odd however when flashing ROMs and KDZs don't help trying the TOT is a must. Several months ago I had a weird problem that stayed with me no matter what ROM or KDZ I flashed. After I flashed the 10B TOT, everything's been fine since. TOTs flash more partitions than KDZs.
When you tried the TOT method, if using the original .DLL that was provided to use with the VS985 doesn't work, try the .DLL that's extracted from the 35B KDZ. I have it on Android File Host - you can find a link to my section at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section, or the first link in my signature below to get to his thread. You shouldn't have had to use the newer .DLL as far as I'm aware since you were rooted and presumably using @xdabbeb 's 35B Bootstack, which contains downgraded partitions that allow flashing older KDZs (not just 35B and newer ones) and the TOT without the newer .DLL.
Even if neither .DLL worked before, try the new one now that you flashed the KDZ.
Also, when you flashed the KDZ, did you use the CSE or Normal option? If you didn't do CSE, then try a Factory Reset. If it's some errant user/system data that's causing the WIFI problem, then only using the CSE option or Factory Reset can help. Flashing the TOT also wipes all data. Move everything you want to keep from internal storage since that'll be wiped too.
Click to expand...
Click to collapse
well i kept on trying @LASERWOLF452's method "LG G3 downgrade to 10B, root and how to use TWRP with custom roms (update 6-5-2016)" but had no luck and on the flash tool i would either get the errors " Model information check fail" "fail to get mini os check" "fail to get complete status check"
and then it would just stay in a bootloop. And i used CSE flash
JustAnotherUser69245 said:
well i kept on trying @LASERWOLF452's method "LG G3 downgrade to 10B, root and how to use TWRP with custom roms (update 6-5-2016)" but had no luck and on the flash tool i would either get the errors " Model information check fail" "fail to get mini os check" "fail to get complete status check"
and then it would just stay in a bootloop. And i used CSE flash
Click to expand...
Click to collapse
Using the original USB cable? Try rebooting the PC? Using a USB 2.0 (not 3.0) port that comes directly off the motherboard, not through a hub? You're not actually clicking the Windows software's button to check the phone model info, right? If you are, don't do that.
Does your phone show up in Windows' Device Manager in the Modem section?
roirraW "edor" ehT said:
Using the original USB cable? Try rebooting the PC? Using a USB 2.0 (not 3.0) port that comes directly off the motherboard, not through a hub? You're not actually clicking the Windows software's button to check the phone model info, right? If you are, don't do that.
Does your phone show up in Windows' Device Manager in the Modem section?
Click to expand...
Click to collapse
it shows up like this.
http://imgur.com/SN5MEiT
was i supposed to download this dll. https://www.androidfilehost.com/?fid=24421527759885198 and then try the tot. Because if i did, it didnt work still.
JustAnotherUser69245 said:
it shows up like this.
Click to expand...
Click to collapse
Yep, that's right.
was i supposed to download this dll. and then try the tot. Because if i did, it didnt work still.
Click to expand...
Click to collapse
From stock unrooted 35B or higher, you use that .DLL with the TOT method. From earlier than 35B, or when you're on 35B and higher but rooted and using the custom Bootstacks that @xdabbeb provides, then you should be able to use the original .DLL but the newer one should work too.
Sometimes using a different PC helps. Since you didn't answer the questions I asked I assume the answer to all of them is affirmative when appropriate and negative when not. Is that correct? Since flashing the KDZ worked I would presume that however you did it should work for TOT too, just as long as like I said, you're not clicking the program button to read the phone info. That often leads to program crashes.
For the TOT method, are you changing the port of the correct device that's in the Port (not Modem) section of the Device Manager to port 41? For that matter, is it showing up under the Port section? I always forget until I'm actually doing the TOT method - KDZ uses the one in the Modem section, TOT uses the one in the Port section.
roirraW "edor" ehT said:
Yep, that's right.
From stock unrooted 35B or higher, you use that .DLL with the TOT method. From earlier than 35B, or when you're on 35B and higher but rooted and using the custom Bootstacks that @xdabbeb provides, then you should be able to use the original .DLL but the newer one should work too.
Sometimes using a different PC helps. Since you didn't answer the questions I asked I assume the answer to all of them is affirmative when appropriate and negative when not. Is that correct? Since flashing the KDZ worked I would presume that however you did it should work for TOT too, just as long as like I said, you're not clicking the program button to read the phone info. That often leads to program crashes.
For the TOT method, are you changing the port of the correct device that's in the Port (not Modem) section of the Device Manager to port 41? For that matter, is it showing up under the Port section? I always forget until I'm actually doing the TOT method - KDZ uses the one in the Modem section, TOT uses the one in the Port section.
Click to expand...
Click to collapse
i am on 47a unrooted using the KDZ method
yes thats correct and yes i do change the port number not the modem for the TOT method
I acquired an lg g3 on 24b. I figured I would make it as a spare incase I lost or damaged my original and use it to test newer versions like marshmallow or nouget.
Here's what I did
1. I I restored factory image using lg flash tool .tot version back to 10b
2. stump rooted it.
3. installed earliey twrp from 2014 with flashify
4. installed twrp 3.0.0
5. did a twrp back up including EFS
6. restored my jasmine9.1 -35b image to it. with EFS checked
7. Noticed my modem/baseband version was "Unknown"
I was going to flash the 35b modem but before that I had some questions.
Questions.
1. what exactly is EFS? ( am asking because I included it when I went from 10b to jasmine9.1 35b I need to know if that's something you dont flash from one phone to another)
2. if I flash my modem file to 35b wil I be able to flip flop back and forth and upwith modem files.?
3. how high can I go with revsions keeping twrp and modem/baseband without have to restore original with .tot if I want to get back to 35b.
I know enough to be dangerous so I'm asking cause I don't know enough! lol
thanks.
EFS is or includes your IMEI. If your 35B backup was from another phone, you don't want to restore EFS from your old phone. Restore your EFS from your 24B backup. You don't normally want to restore your EFS every time you restore a TWRP Backup. I personally do a TWRP back up of just my EFS and save it to Google Drive since sometimes flashing a TOT, KDZ or ROM will wipe the IMEI and without having an EFS backup handy, it's a bigger pain to restore using proprietory Windows software.
Just in case you don't know, never flash a Bootstack BEFORE flashing either JasmineROM 9.x or SkyDragon 6.x. After flashing either ROM, either flash the 24B or 35B Bootstack from @xdabbeb 's VS985 v2.0 ROM thread in the Development (non-original) section. Don't just flash the modem.
If you flash the 35B Bootstack you can certainly flash the 24B Bootstack later if you wish. The Bootstacks contain more than just the modems, but they include the modem too. The modem sometimes requires a newer sbl1 partition which is included, which is why you should flash the entire Bootstack and not just the modem, because the Bootstacks contain the appropriate sbl1. Not having the correct modem/sbl1 combination (for instance, 35B modem but 24B sbl1, or when using an older completely incompatible modem/sbl1 with a newer stock ROM) *might* cause the Settings / About / Status menu to show no IMEI too, but it shows back up after flashing the entire correct Bootstack.
The 35B Bootstack is the highest you can flash no matter what ROM you use on 35B or higher (46A or 47A). I'm not clear on what you were asking "how high can I go with revsions keeping twrp and modem/baseband without have to restore original with .tot if I want to get back to 35b" so if that doesn't answer that, please reword that question. You can flash @xdabbeb 's stock 47A (pre-rooted) firmware if you want to be on the 47A ROM; albeit you still have to use the 35B Bootstack.
I'm glad I saved the EFS from 24b now. (just incase I sell the phone I will restore it... doubt I will though but it's good to have. I don't mind flashing EFS to the second phone cause I will only use one at any given time with my sim card. I flashed xdabeb bootstack-35bmodem file already but I used the orignal not the non-orginal... so I guess I'm lucky cause it works. Thanks. I can't wait to try marshmallow! I got some reading ahead of me cause I want to get all the features I prefer working on marshmallow
like
xposed
wifi tethering with native app.
g3 tweak box (auto call recording feature is nice when your wife says "no I diddn't say that" lol
rp201 said:
I flashed xdabeb bootstack-35bmodem file already but I used the orignal not the non-orginal...
Click to expand...
Click to collapse
There's only one @xdabbeb VS985 v2.0 thread - in the regular Development section (what I call non-original), not the Original Development section. That's what I meant.