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 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
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.
Hey folks. I'm in need of some help, but need to provide some background info as it seems there might be a few ways to correct this.
Background
I had a recent bad Nandroid mess up a restore process which somehow led to me losing root. I was on XDABBEB's 47A stock rooted ROM for months, then went to try the 3.1.1 ROM recently. I found that I wanted to go back, then BOOM! Bad restore from my data NANDROID. Then I:
Got stuck in a boot loop.
Rebooted into recovery
Saw the LG Recovery
(Stupidly?) chose to wipe cache
Continued to boot from LG Recovery
Went immediately to TWRP
Wiped Data and caches
Rebooted
At this point, I got back into 47A, but obviously without any data. I soon found that, though SuperSU was installed, it wasn't working:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-rot - consult the relevant forums for your device!
Click to expand...
Click to collapse
At this point, I checked Root Checker app and, surely enough, it says I wasn't rooted.
I checked ADB and tried to su from the prompt ($) and
Code:
su: notfound
However, adb reboot recovery brings me to TWRP
I tried TOT'ing on my Windows 10 (x64) machine, but it wasn't working:
PID: FAIL
IMEI: Unknown
[23:59: 0] CrossDL [Unknown] to [VS985].SW ***The text on this line continues, but I can't read it***
00000064
Error: [23:59: 0] CrossDL [Unknown] to [VS985].
Click to expand...
Click to collapse
I'm lucky in that my phone is currently working fine. I'm on 47a with everything working fine ... just not rooted, which I would really like to be.
So, my question is, what should I do next? I know some options that I have, I just don't know what options I should try or in what order I should try them...I understand some of the jargon and background info, but I don't understand the true inner workings of rooting and therefore don't feel comfortable making these choices on my own.
So, to all of you people that are way more intelligent at this than I am...
Should I try restoring my rooted 49A backup from TWRP?
Should I try to flash SU binaries in TWRP?
Should I TOT from my work machine that is Windows 7?
Should I KDZ on Windows 10?
Thanks in advance for your collective help.
This inquiring mind wants to know!
I'm assuming that since you were running XDEBs ROM, then you do NOT have a K model of the phone. In that case, you must flash back to 10B via the TOT method. That way, you can then root with Stump and then install TWRP, flash the correct boot images, and then reflash XDEBs ROM.
Stock 47A is only rootable by Kingroot and there is NO way to install TWRP with pure stock 47A, which is why you must downgrade via the 10B TOT method. It's the boot partition that is incompatible with TWRP and they have not found a way to "bump" it to work with the stock 47/48/49A versions.
iBolski said:
I'm assuming that since you were running XDEBs ROM, then you do NOT have a K model of the phone
Click to expand...
Click to collapse
Correct. xdebbeb's stock 47A on a non-K model
Stock 47A is only rootable by Kingroot and there is NO way to install TWRP with pure stock 47A, which is why you must downgrade via the 10B TOT method.
Click to expand...
Click to collapse
That's why I'm confused a bit about my options. I already HAVE TWRP installed. Is having TWRP not helpful to regain root? This is causing me to feel like I'm in a weird limbo state (of options) with the phone.
It's the boot partition that is incompatible with TWRP and they have not found a way to "bump" it to work with the stock 47/48/49A versions.
Click to expand...
Click to collapse
Since I have TWRP already, does that mean that my boot partition was/is/has been "bumped"?
Sorry for so many questions. I do like making sense of things that I'm told and understanding them.
Since I'm failing on the TOT method at home, is that possibly because of the Windows 10 machine? Should I try Windows 7 on a different machine?
Thanks a lot for the help, iBolski.
my.ads0 said:
Correct. xdebbeb's stock 47A on a non-K model
That's why I'm confused a bit about my options. I already HAVE TWRP installed. Is having TWRP not helpful to regain root? This is causing me to feel like I'm in a weird limbo state (of options) with the phone.
Since I have TWRP already, does that mean that my boot partition was/is/has been "bumped"?
Sorry for so many questions. I do like making sense of things that I'm told and understanding them.
Since I'm failing on the TOT method at home, is that possibly because of the Windows 10 machine? Should I try Windows 7 on a different machine?
Thanks a lot for the help, iBolski.
Click to expand...
Click to collapse
You're best bet is to either flash a full 47A KDZ but you won't be able to root and TWRP will be removed and you won't be able to flash custom ROMs, like XDEBB.
Your other option is to flash to 10B via TOT method, root, reinstall TWRP Then, based on the custom ROM's instructions, you may have to flash 35B bootstack, but you'll be in a position to flash custom ROMs again.
Either flash WILL erase everything on your phone as it's like a factory data reset. Those are your only options unfortunately. TWRP cannot work under 47A as you're finding out. You will be unable to flash root, any custom roms, etc.
iBolski said:
You're best bet is to either flash a full 47A KDZ but you won't be able to root and TWRP will be removed and you won't be able to flash custom ROMs, like XDEBB.
Your other option is to flash to 10B via TOT method, root, reinstall TWRP Then, based on the custom ROM's instructions, you may have to flash 35B bootstack, but you'll be in a position to flash custom ROMs again.
Either flash WILL erase everything on your phone as it's like a factory data reset. Those are your only options unfortunately. TWRP cannot work under 47A as you're finding out. You will be unable to flash root, any custom roms, etc.
Click to expand...
Click to collapse
I just want to make sure that you're aware that I am NOT on pure stock 47A. I'm on xdabbeb_stock_vs98547a.zip from here.
When I flashed back from his 3.1.1 ROM, I flashed to my backup of the above ROM, which had Root. The SYSTEM flash from my nandroid back to his version of 47A worked without incident, but the DATA flash of my nandroid failed, left me in a bootloop, after which I performed the actions outlined in my original post. That squarely left where I am now, with no root, but on his version of 47A (I never had the stock 47A on my device before) with TWRP as my recovery.
In the end, I'm game for trying different things, but ideally, I'd like to try the least invasive method (trying to flash SuperSU in TWRP?; trying to flash my xdabebb 3.1.1 version?) ) before trying any other method or going to the extreme method (TOT'ing). I just am trying to avoid TOT'ing since my phone IS working AND the fact that I would have to do that at work. It would suck to go from a working phone to a broken phone without being able to fix it without knowing that I tried all of the least invasive methods first. I just need guidance from people like you as to what will or won't work in my situation.
The reason for this post is that I wasn't sure that you were aware I wasn't on pure stock 47A, but on xdabebb's version, which maybe you had overlooked and offered me more options? If you were aware of that and everything above is irrelevant, then I'm cool with that. Just tell me so. I just didn't want that fact overlooked.
Thanks again for entertaining my inquisitiveness, iBolski.
Well, trying to install the SuperSU binary zip from TWRP didn't work. That got me flashing blue & red lights. I tried restoring my XDABEBB 49A 3.1.1 install and that didn't help either. Both TOT & KDZ methods are failing on my PC (Windows 10) with both not able to read the phone properly (can't see imei). I will maybe try to uninstall the drivers or just wait until Monday to try my windows 7 machine at work.
Oops.
So I took up the cause again this morning and loaded all of the tools for the KDZ method on another PC. I installed the most up to date LG drivers, rebooted, made the PC recognize my phone in every mode (Download Mode, Bulk Mode [flashing lights], and while in TWRP). The tool still wasn't working properly and not reading my phone's info. Though I had run it a few other times, I had been following instructions and hadn't changed the language to English. The last couple of times, I changed the language to English. This time, when it stopped working (not connecting to LG servers) it offered me the option to retry. I took them up on the offer ... unplugged the phone, pulled the batter, put the battery back in, entered Download mode (volume up + connect USB), reconnected and BAM!!! It did the upgrade!
So I'm back on 10B. Crisis averted.
Thanks once again for putting up with me, iBlonksi.
my.ads0 said:
So I took up the cause again this morning and loaded all of the tools for the KDZ method on another PC. I installed the most up to date LG drivers, rebooted, made the PC recognize my phone in every mode (Download Mode, Bulk Mode [flashing lights], and while in TWRP). The tool still wasn't working properly and not reading my phone's info. Though I had run it a few other times, I had been following instructions and hadn't changed the language to English. The last couple of times, I changed the language to English. This time, when it stopped working (not connecting to LG servers) it offered me the option to retry. I took them up on the offer ... unplugged the phone, pulled the batter, put the battery back in, entered Download mode (volume up + connect USB), reconnected and BAM!!! It did the upgrade!
So I'm back on 10B. Crisis averted.
Thanks once again for putting up with me, iBlonksi.
Click to expand...
Click to collapse
Awesome. I saw your earlier post about being on XDEBB but that didn't matter. You were at a point that flashing back to 10b was your best option to get back to XDEB. That's why I kept saying you needed to flash back to 10B if you wanted to get back on XDEBB because where you were at that point was messed up, so it was just best to flash to 10b clean.
Glad you got it all worked out!
EDIT: no longer need this. It is possible to make your own...
There is a chance that I may not have fried my V10 by shorting the test point, but to test that I need a full Nougat dump (something I can not believe I didn't make from my own phone -- I only have a full MM dump).
If there is someone that has rooted Nougat AND flashed all the Nougat partitions (v30b_update.zip and full_nougat.zip), and is willing to do a full dump, please let me know.
It is preferable if you have access to Linux because you will need to null out some partitions that have private data, and it is much easier to explain how to do it on Linux.
Lastly, this image will be 64gigs uncompressed, but it compresses very well.
Thanks,
-- Brian
Wish I can help, but mine is not rooted..
Hopefully I can bring my phone back to life (one way or another) so I can continue on. I got my board of eBay, but it was more dead than my current board.
runningnak3d said:
Hopefully I can bring my phone back to life (one way or another) so I can continue on. I got my board of eBay, but it was more dead than my current board.
Click to expand...
Click to collapse
That sounds bad. Hopefully someone will upload it.
if i can downgrade it , ill re upgrade to rooted nougat and get a dump but i dont know how to dump and dont have the image for downgrade.
@runningnak3d There's a guy selling one in General. Perhaps you can get a dump off of him?
@runningnak3d I currently have one V10 that I cannot get past the Checking Updates screen in the setup wizard on Nougat (with TWRP) which I am considering performing a KDZ wipe and another that went black screen after I flashed MM (also with TWRP). If I do a KDZ wipe on the first one, I could do a dump for you but I would have to look up how to. You are also welcome to buy the board from the second V10 from me but I'm unsure if you can revive it.
Thanks all, but everything I needed to make my own was staring me in the face.
-- Brian
i will help if i can , but didnt have root yet
@runningnak3d I'm in a need of a Nougat dump for H901, to make a bootable sdcard. Could you share yours or guide how to make one from nougat kdz?
Due to messing the aboot partition (while trying to shut the "big cores" off) the phone does not boot, nor enter download mode. On powering on, it only vibrates. QPST does not work with the phone put into 9008, it returns "target may be unstable". Before that, the phone was rooted, with bootloader unlocked, updated to nougat via the recovery, with the ZIPs.
Any help would be greatly appreciated
Be glad to, and it is easy, but you need dd. If you use Windows, there may be some program that can do something similar, but I haven't used Windows in years. You can always install a very basic Cygwin environment...
* Insert 64gig SD card
* Dump KDZ
* dd if=PrimaryGPTxxxxxx of=/dev/mmcblk0
The xxxxx above is because I can't remember what it gets dumped as, but it will be obvious.
Once you have the partition table on the sdcard, get a list of the partitons:
* gdisk -l /dev/mmblck0
Then proceed to flash the rest of KDZ onto their individual partitions.
For example, I believe that modem was partition 1, so:
* dd if=modemxxxxx of=/dev/mmcblk0p1
Repeat for every partition from the KDZ except system (unless you want to fully boot from the SD card). Also, you can flash recovery with TWRP, and then you can boot from the SD card to recovery and then you only need to flash your aboot partition, so you don't have to use download mode to flash the entire KDZ.
Let me know if you need me to clarify anything.
EDIT: If you do boot to recovery from the SD card, you will need to make sure to flash the correct device. When you go into an adb shell, you will have two mmcblk devices (mmcblk0 and mmcblk1). I don't remember which will be which, so to be safe flash the aboot partition on both...
-- Brian
@runningnak3d Thank you for your reply! I have Ubuntu 17 as a bootable DVD. Does the sdcard have to be formatted in a specific filesystem before doing this? Another question I have, is that the sdcard shows up as dev/sdd for me but it also shows that dev/sdd1 exists on it, so to which should I dd the GPT table to?
I tried to dev/sdd and wrote the rest of KDZ to the partitions, but the phone has not booted (its 64gb sd hc class 10 card). After dd-ing the PrimaryGPT, the terminal mentions that backupGPT is corrupted and that MBR is protective on the sdcard. Also, GParted shows "unknown" for each partition, and modem partition shows up as fat16 one.
Perhaps I should try different nougat KDZ? the phone's sticker under battery says it's H901, so was written in the phone under settings menu (phone also had t-mobile bloatware) and in LGUP when updating to MM, yet the motherboard has VS990 written on it.
My phone said vs990 on the board as well, so that isn't the issue. You need to flash a few partitions from the phone that aren't in the KDZ ... you will have to get someone to dump them for you.
The only place I had them was on an SD card that I have already wiped since I don't have a v10 anymore.
I will have to look in SBL1 to get you a list that you will have to ask for.
They are all just firmware, and contain nothing specific to a users phone, so anyone with a rooted Nougat phone can safely dump them for you.
Please bear with me. I am currently trying to revive my H910 and I order an H918 that I am going to use to help someone with, but I will try to get you the info ASAP.
H901 VS990 board 9008 brick help
@runningnak3d Hey, you seem like an expert at unbricking V10s. I have a H901 that has vs990 motherboard in it. It bricked while I was updating through LG Bridge. I now only have access to qualcomm 9008 mode.
From my understanding, there are 2 ways to solve this. QFIL or booting from dump image through sdcard. The qfil way didn't work for me, since there aren't any compatible .mbn files and xml for VS990 owners. So my only other option is getting to download mode via sdcard method, and I need the dump files for that. If I do what you've told @Mr_pringle, would my phone enter download mode? What exactly would I have to do? Thanks
@N3XTN3XUS What version were you on, and what version did LG Bridge try to update you to?
runningnak3d said:
@N3XTN3XUS What version were you on, and what version did LG Bridge try to update you to?
Click to expand...
Click to collapse
mm to nougat. Do you have the dump img for mm by any chance?
Unfortunately you are going to have to roll your own with the instructions I gave above.
In order to do that, you need to find out what model you should be flashing. I know you said your board said VS990, I am sitting here looking at my dead board, and it says VS990 on it as well, so H901 Nougat *should* have worked for you. I don't have any idea where you should start looking, but you do need to know that before making an SD card or even if you make a perfectly good card, it won't work
-- Brian