Q&A for [ROM] VS980 39A Lollipop
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] VS980 39A Lollipop. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
NalNalas said:
Here's a fix for the LED being constantly on
1. Disable notification light
2. Reboot
done
Click to expand...
Click to collapse
That works but kills the front one too.
I flashed the rom, bootstack, and supsersu (in that order) and I get a kernel crash when booting.
"kernel panic - not syncing L2 master port error detected"
Any ideas?
zone117x said:
I flashed the rom, bootstack, and supsersu (in that order) and I get a kernel crash when booting.
"kernel panic - not syncing L2 master port error detected"
Any ideas?
Click to expand...
Click to collapse
Flash bootstack, then rom n supersu.
MicroMod777 said:
Flash bootstack, then rom n supersu.
Click to expand...
Click to collapse
Alright I did that but its been on the Verizon boot animation for over 20 minutes now. Is something still wrong?
Do I have to have anything installed that wasn't mentioned in the post?
Thanks
zone117x said:
Alright I did that but its been on the Verizon boot animation for over 20 minutes now. Is something still wrong?
Do I have to have anything installed that wasn't mentioned in the post?
Thanks
Click to expand...
Click to collapse
U full wipe?
Am I missing it or is knock code still not here? Is it in the manual ota method or neither? Any ways thanks for the Rom because grola was starting to mess up.
So, I'm on the forced OTA 39A and everything is running great, I also just rooted it using this method here http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
Anyway to install TWRP onto this yet? I did a stupid thing and installed AutoRec and flashed recovery just to try it, and it worked fine. Until I rebooted out of recovery, then I got the dreaded LG Security Error. So I had to restore back to 27A and go back to 39A.
LetsHaveSomeAndroidFun said:
So, I'm on the forced OTA 39A and everything is running great, I also just rooted it using this method here http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
Anyway to install TWRP onto this yet? I did a stupid thing and installed AutoRec and flashed recovery just to try it, and it worked fine. Until I rebooted out of recovery, then I got the dreaded LG Security Error. So I had to restore back to 27A and go back to 39A.
Click to expand...
Click to collapse
This is a bit of a guess, so proceed at your own risk, but could you use AutoRec to install recovery, then once in recovery, flash the 39A bootstack from this thread, which also contains a bumped TWRP? I'm thinking the patched kernel that AutoRec installs is what's breaking things
Don't do this. Doesn't work
detonation said:
This is a bit of a guess, so proceed at your own risk, but could you use AutoRec to install recovery, then once in recovery, flash the 39A bootstack from this thread, which also contains a bumped TWRP? I'm thinking the patched kernel that AutoRec installs is what's breaking things
Click to expand...
Click to collapse
Well, I just spent the last few hours re-setting up my device again, but I'll try it. Might as well, if it doesn't work I'll just re-do everything again lol. I wish I would of known that the bootstack for 39A was available, I would of tried it then but oh well. Will let you know how it goes.
---------- Post added at 10:18 AM ---------- Previous post was at 10:05 AM ----------
Nope, just tried it. After installing the recovery then the bootstack I restart and I get secure booting error boot certification verify and the only thing I can do is get back into recovery, so no good.
LetsHaveSomeAndroidFun said:
Well, I just spent the last few hours re-setting up my device again, but I'll try it. Might as well, if it doesn't work I'll just re-do everything again lol. I wish I would of known that the bootstack for 39A was available, I would of tried it then but oh well. Will let you know how it goes.
---------- Post added at 10:18 AM ---------- Previous post was at 10:05 AM ----------
Nope, just tried it. After installing the recovery then the bootstack I restart and I get secure booting error boot certification verify and the only thing I can do is get back into recovery, so no good.
Click to expand...
Click to collapse
Well thanks for being the guinea pig at least. In retrospect, AutoRec loki's your boot.img, but those bootstack zips don't include a bumped boot.img (since they are rom specific I think) so you get the security error still. I'll leave this up to the experts from now on
detonation said:
Well thanks for being the guinea pig at least. In retrospect, AutoRec loki's your boot.img, but those bootstack zips don't include a bumped boot.img (since they are rom specific I think) so you get the security error still. I'll leave this up to the experts from now on
Click to expand...
Click to collapse
You're welcome, not a problem! I see, I have all the partitions of this ROM including boot.img, maybe if I name it update.zip and flash it via TWRP I can get it to boot? I think I'll try it...It's worth a shot.
LetsHaveSomeAndroidFun said:
You're welcome, not a problem! I see, I have all the partitions of this ROM including boot.img, maybe if I name it update.zip and flash it via TWRP I can get it to boot? I think I'll try it...It's worth a shot.
Click to expand...
Click to collapse
All else fails, and you still want to be the closest to stock 39a with root and recovery, I suppose you could just wipe, flash the 27A bootstack, flash this 39A ROM, then flash the 39A bootstack (should't need to KDZ or anything assuming you're still able to get into TWRP). According to this post the differences in this rom and stock are the basically the components that we couldn't pull before root was available, but now they're availabe and in that bootstack zip - once again, no guarantees though, I think I'll try to be patient and wait for the devs to release something
detonation said:
All else fails, and you still want to be the closest to stock 39a with root and recovery, I suppose you could just wipe, flash the 27A bootstack, flash this 39A ROM, then flash the 39A bootstack (should't need to KDZ or anything assuming you're still able to get into TWRP). According to this post the differences in this rom and stock are the basically the components that we couldn't pull before root was available, but now they're availabe and in that bootstack zip - once again, no guarantees though, I think I'll try to be patient and wait for the devs to release something
Click to expand...
Click to collapse
You can't install the recovery because you need the 4.4 aboot. You can adb the the 27A aboot.img through a terminal on your pc or on your phone, then adb blastagator's recovery, and you will be able to have recovery. I'm running twrp no problems right now.
EDIT:
Need a bumped boot.img too. I was bootlooping until I applied one.
bouchigo said:
You can't install the recovery because you need the 4.4 aboot. You can adb the the 27A aboot.img through a terminal on your pc or on your phone, then adb blastagator's recovery, and you will be able to have recovery. I'm running twrp no problems right now.
EDIT:
Need a bumped boot.img too. I was bootlooping until I applied one.
Click to expand...
Click to collapse
Thanks for this.
So I need to be on rooted 39A and then adb flash aboot.img and then adb flash recovery? And any help for a bumped boot.img? I've only had my LG G2 about 2 weeks. Thank you.
bouchigo said:
You can't install the recovery because you need the 4.4 aboot. You can adb the the 27A aboot.img through a terminal on your pc or on your phone, then adb blastagator's recovery, and you will be able to have recovery. I'm running twrp no problems right now.
EDIT:
Need a bumped boot.img too. I was bootlooping until I applied one.
Click to expand...
Click to collapse
Where did you get the bumped boot.img from? Also, all the bootloader files in the resource thread are bins, not imgs, does that matter?
To get to stock rooted 39A with TWRP, it sounds like the process is:
-manually apply 39A OTA
-root using new exploit
-push 27A (or 28A) aboot
-push bumped 39A boot.img
-push TWRP
LetsHaveSomeAndroidFun said:
Thanks for this.
So I need to be on rooted 39A and then adb flash aboot.img and then adb flash recovery? And any help for a bumped boot.img? I've only had my LG G2 about 2 weeks. Thank you.
Click to expand...
Click to collapse
Yes. See below.
detonation said:
Where did you get the bumped boot.img from? Also, all the bootloader files in the resource thread are bins, not imgs, does that matter?
To get to stock rooted 39A with TWRP, it sounds like the process is:
-manually apply 39A OTA
-root using new exploit
-push 27A (or 28A) aboot
-push bumped 39A boot.img
-push TWRP
Click to expand...
Click to collapse
Yeah, either 27A or 28A (confirmed by xdabbeb) should work. I bumped the 39A boot image myself (not hard to do, the info. is readily available on how to do it).
Just change the .bin to .img.
Here is the boot image (adb push it, not a flash file): http://www.mediafire.com/download/pele8oikzesdn39/bumped_boot-image.zip
MD5Sum (of zip file): 6b1f793cdf00db3ef52d1fd08f7b3af2
MD5Sum (of boot.img itself): b4254d5aebe30ad4f1d5e924f45e9bff
bouchigo said:
Yes. See below.
Yeah, either 27A or 28A (confirmed by xdabbeb) should work. I bumped the 39A boot image myself (not hard to do, the info. is readily available on how to do it).
Just change the .bin to img.
Here is the boot image (adb push it, not a flash file): http://www.mediafire.com/download/pele8oikzesdn39/bumped_boot-image.zip
MD5Sum (of zip file): 6b1f793cdf00db3ef52d1fd08f7b3af2
MD5Sum (of boot.img itself): b4254d5aebe30ad4f1d5e924f45e9bff
Click to expand...
Click to collapse
If it's not too much trouble, could you give me some step by step instructions? I am trying to push the aboot.img but it's saying device not found, when it is etc..Thank you.
LetsHaveSomeAndroidFun said:
If it's not too much trouble, could you give me some step by step instructions? I am trying to push the aboot.img but it's saying device not found, when it is etc..Thank you.
Click to expand...
Click to collapse
Download this file; inside are the instructions that I wrote up, and links to the files on how to do it: http://www.mediafire.com/download/h7544eak22lp2c9/Install_TWRP_Recovery_on_vs980_LP_39A.zip
bouchigo said:
Download this file; inside are the instruction that I wrote up, and links to the files on how to do it: http://www.mediafire.com/download/h7544eak22lp2c9/Install_TWRP_Recovery_on_vs980_LP_39A.zip
Click to expand...
Click to collapse
Thank you so much, this worked perfectly!
Related
I have downloaded a TWRP 2.7 flashable zip. The official instructions on the TWRP site talk about using a .img file, but they don't have a 2.7 img for vs980.
Many threads mention some images are Lokified, others are not, I'm not sure how to install.
This is a new G2 with 12B that I'm going to root with IORoot 25, how can I get TWRP installed on it as well, preferably in same adb session?
Thanks
Is this the right way?
flash older 2.6.3.2 img using Flashify
reboot into recovery
flash 2.7 zip
Is there a faster way to do this?
Can someone please help?
ECrispy said:
Can someone please help?
Click to expand...
Click to collapse
Root with ioroot
Flashify has its own download section, I would download the .IMG file in the app, just to make sure you have the correct one.
Follow directions in flashify.
I just did this with cwm and it worked, it might have the latest twrp to flash in the app.
ECrispy said:
Can someone please help?
Click to expand...
Click to collapse
If you just want the easiest method, do this:
Extract twrp.lok from this thread. (first download twrp.zip...the .lok file is in there) Rename the extension to img. Flash that with flashify. Then flash this in recovery. You should now be on twrp 2.7 loki'd for 12b. :good:
Credit for that procedure goes to JRJ442...i just explained his steps from here.
xemnas18 said:
If you just want the easiest method, do this:
Extract twrp.lok from this thread. (first download twrp.zip...the .lok file is in there) Rename the extension to img. Flash that with flashify. Then flash this in recovery. You should now be on twrp 2.7 loki'd for 12b. :good:
Credit for that procedure goes to JRJ442...i just explained his steps from here.
Click to expand...
Click to collapse
+1 This works perfectly.
xemnas18 said:
If you just want the easiest method, do this:
Extract twrp.lok from this thread. (first download twrp.zip...the .lok file is in there) Rename the extension to img. Flash that with flashify. Then flash this in recovery. You should now be on twrp 2.7 loki'd for 12b. :good:
Credit for that procedure goes to JRJ442...i just explained his steps from here.
Click to expand...
Click to collapse
Will this method work if I already have TWRP 2.6.3.3? My goal is: get to TWRP 2.7 but tried to go into TWRP and flash the "openrecovery-twrp-2.7.0.0-vs980.zip", it tells me I can't because it can't find "/tmp/loki.sh" (couldn't capture exact message). Currently I'm on 12B.
thanks
glhelinski said:
Will this method work if I already have TWRP 2.6.3.3? My goal is: get to TWRP 2.7 but tried to go into TWRP and flash the "openrecovery-twrp-2.7.0.0-vs980.zip", it tells me I can't because it can't find "/tmp/loki.sh" (couldn't capture exact message). Currently I'm on 12B.
thanks
Click to expand...
Click to collapse
Yeah the official that you tried doesn't have the correct Loki patch for 12B. Thats why it throws that message. All the ones I made for VS980 are patched to work on 11A or 12B. Just click on "This" a few posts up. That goes to my Dropbox. The zip is Stock-TWRP2.7-VS980. Just flash in recovery, then reboot recovery and it'll be 2.7
Or if you have Flashify you can download and install 2.7 through that.
These one click tools worked for me. I went from 12b + stock recovery to twrp 2.7 with just a few clicks. I used it yesterday. Thread http://forum.xda-developers.com/showthread.php?t=2713954
Sent from my VS980 4G using XDA Premium 4 mobile app
JRJ442 said:
Yeah the official that you tried doesn't have the correct Loki patch for 12B. Thats why it throws that message. All the ones I made for VS980 are patched to work on 11A or 12B. Just click on "This" a few posts up. That goes to my Dropbox. The zip is Stock-TWRP2.7-VS980. Just flash in recovery, then reboot recovery and it'll be 2.7
Or if you have Flashify you can download and install 2.7 through that.
Click to expand...
Click to collapse
thanks. worked as expected.
thanks for sharing
Sent from my LG-VS980 using XDA Free mobile app
I successfully rooted my lg g2 on 26a with stump, but I'm wondering as how i can get twrp installed without bricking. Will the VS980 Autorec work with 26a? or is there any other solution please help me out. BTW i just got my phone back from LG so i don't want to brick again and have to send it in lol. Thanks in adcanve!
uraks said:
I successfully rooted my lg g2 on 26a with stump, but I'm wondering as how i can get twrp installed without bricking. Will the VS980 Autorec work with 26a? or is there any other solution please help me out. BTW i just got my phone back from LG so i don't want to brick again and have to send it in lol. Thanks in adcanve!
Click to expand...
Click to collapse
Not sure about autorec (never used it) but I know Freedom Tool works (used it twice):
http://forum.xda-developers.com/showthread.php?t=2713954
Have any questions, don't hesitate to ask!
uraks said:
I successfully rooted my lg g2 on 26a with stump, but I'm wondering as how i can get twrp installed without bricking. Will the VS980 Autorec work with 26a? or is there any other solution please help me out. BTW i just got my phone back from LG so i don't want to brick again and have to send it in lol. Thanks in adcanve!
Click to expand...
Click to collapse
Yes, AutoRec will work just fine. I've used it plenty of times on 26A.
bouchigo said:
Yes, AutoRec will work just fine. I've used it plenty of times on 26A.
Click to expand...
Click to collapse
But in my case the AutoREC can't flash those 24A, 24A, 12A/B ... in zip format ... all ERROR can't read ZIP file....
You got any idea where I could get the working VS98026A Stock ROM?
THank in advance
mKHMER
mkhmer said:
But in my case the AutoREC can't flash those 24A, 24A, 12A/B ... in zip format ... all ERROR can't read ZIP file....
You got any idea where I could get the working VS98026A Stock ROM?
THank in advance
mKHMER
Click to expand...
Click to collapse
Autorec doesn't use a zip, it just does the behind the scene things needed to flash TWRP then flashes it. Can you clarify what you're trying to do?
mjones73 said:
Autorec doesn't use a zip, it just does the behind the scene things needed to flash TWRP then flashes it. Can you clarify what you're trying to do?
Click to expand...
Click to collapse
As far as I could see that latest AUTORec.apk installation is now included with TWRP already. After rooted my phone, installed AUTOREC, grant root and flashing customer recovery image straight aways, I could flash some ZIP file but not those ROM such VS98011A, VS98024A, VS98026A, etc all return FAIL - Can't Read Zip file. But I from AutoREC recovery menu, I could install Spirit ROM.zip and others.
Why only those stock ROM in zip format are FAIL to be flashed from within AUTOREC/TWRP ????
mkhmer said:
As far as I could see that latest AUTORec.apk installation is now included with TWRP already. After rooted my phone, installed AUTOREC, grant root and flashing customer recovery image straight aways, I could flash some ZIP file but not those ROM such VS98011A, VS98024A, VS98026A, etc all return FAIL - Can't Read Zip file. But I from AutoREC recovery menu, I could install Spirit ROM.zip and others.
Why only those stock ROM in zip format are FAIL to be flashed from within AUTOREC/TWRP ????
Click to expand...
Click to collapse
Autorec flashes TWRP, that's it, once in recovery you're just using TWRP. You can delete Autorec from your phone after you're done flashing TWRP. Anyway, you can't install stock releases via TWRP unless a dev modifies one to be flashed. Care to point to one of the zip's you're trying to flash?
bouchigo said:
Yes, AutoRec will work just fine. I've used it plenty of times on 26A.
Click to expand...
Click to collapse
Where you able to flash the latest 2.8.1.0 Twrp zip after using AutoRec?
droidrev71 said:
Where you able to flash the latest 2.8.1.0 Twrp zip after using AutoRec?
Click to expand...
Click to collapse
If I recall correctly, AutoRec doesn't have the most up-to-date recovery built-in. I just flashed the latest afterward.
bouchigo said:
Yes, AutoRec will work just fine. I've used it plenty of times on 26A.
Click to expand...
Click to collapse
bouchigo said:
If I recall correctly, AutoRec doesn't have the most up-to-date recovery built-in. I just flashed the latest afterward.
Click to expand...
Click to collapse
Correct, AutoRec comes with 2.7.0.0. I tried upgrading Twrp by flashing the latest Twrp zip and it failed. I guess it's just my device. I looked for the 2.8.1.0. Img file but couldn't find it.
droidrev71 said:
Correct, AutoRec comes with 2.7.0.0. I tried upgrading Twrp by flashing the latest Twrp zip and it failed. I guess it's just my device. I looked for the 2.8.1.0. Img file but couldn't find it.
Click to expand...
Click to collapse
Extract the one from the 26A bootstack, it's already lokied.
bouchigo said:
Extract the one from the 26A bootstack, it's already lokied.
Click to expand...
Click to collapse
Thanks but that's not the most current. 2.8.0.1 is in the bootstack.. i don't get why the 2.8.1.0 zip fails when I flash.. I guess I might have to try the bumped one.
hey guys
i had a working lg g2 vzw running xdabbeb's 2.5 rom
i wanted to upgrade to his vs982.5 v1.1 but i was running 26a so i decided to flash 27a bootstack
however, I BRICKED!
everytime i boot, i get this http://imgur.com/NwrZIyg,vLAACcX
and when I boot into download mode, i get this! http://imgur.com/NwrZIyg,vLAACcX
so if i cant get into download mode, I can't use the KDZ method with lg flash tool, correct?
any guidance would be great
thanks!
Nblufire12 said:
hey guys
i had a working lg g2 vzw running xdabbeb's 2.5 rom
i wanted to upgrade to his vs982.5 v1.1 but i was running 26a so i decided to flash 27a bootstack
however, I BRICKED!
everytime i boot, i get this http://imgur.com/NwrZIyg,vLAACcX
and when I boot into download mode, i get this! http://imgur.com/NwrZIyg,vLAACcX
so if i cant get into download mode, I can't use the KDZ method with lg flash tool, correct?
any guidance would be great
thanks!
Click to expand...
Click to collapse
You're not bricked, you just flashed an older 27A bootstack, or some other bootstack that wipes your laf partition...this means download mode will not work.
Go to xdabbeb's resources page, and download the 27A bootstack from there, and flash it in twrp; this will give you download mode back: http://forum.xda-developers.com/ver...s980-resources-bootstacks-unofficial-t3050777
You should still have twrp on your phone - if you don't know how to enter recovery with key presses, you will need to do some reading on how to do it.
bouchigo said:
You're not bricked, you just flashed an older 27A bootstack, or some other bootstack that wipes your laf partition...this means download mode will not work.
Go to xdabbeb's resources page, and download the 27A bootstack from there, and flash it in twrp; this will give you download mode back: http://forum.xda-developers.com/ver...s980-resources-bootstacks-unofficial-t3050777
You should still have twrp on your phone - if you don't know how to enter recovery with key presses, you will need to do some reading on how to do it.
Click to expand...
Click to collapse
EDIT
IM IN RECOVERY!! But everything else is dead. how do i transfer the .zip to flash if all i can do is get into recovery?
thanks
Nblufire12 said:
EDIT
IM IN RECOVERY!! But everything else is dead. how do i transfer the .zip to flash if all i can do is get into recovery?
thanks
Click to expand...
Click to collapse
There are many ways, you're going to have to research. I'm mobile right now, so I can't really help right now. If you're on blastagator's twrp 2.8.5.1 you can enable MTP in recovery, and transfer it that way.
Sent from my VS980 4G using Tapatalk
bouchigo said:
There are many ways, you're going to have to research. I'm mobile right now, so I can't really help right now. If you're on blastagator's twrp 2.8.5.1 you can enable MTP in recovery, and transfer it that way.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
you did enough... i fixed it! so awesome. i was about to restore via ubuntu it would have taken all night
thankyou!!!!
So I forgot to backup my stock kernel before flashing franco R23. Can I just extract the boot.img from the update.zip? I'm on LMY47M. Thanks!
chrisbo4 said:
So I forgot to backup my stock kernel before flashing franco R23. Can I just extract the boot.img from the update.zip? I'm on LMY47M. Thanks!
Click to expand...
Click to collapse
yes, assuming that's the build your are running.
flash using fastboot:
fastboot flash boot boot.img
you'll have to root again after, if desired.
PhilDX said:
yes, assuming that's the build your are running.
flash using fastboot:
fastboot flash boot boot.img
you'll have to root again after, if desired.
Click to expand...
Click to collapse
Thanks! I'll give that a try.
It depends what you mean bybuodste.zip. if you mean OTA then no but you can normally get it from the factory images but there isn't one for M so you'll need to find the rooted ROM.zip and extract it from there.
rootSU said:
It depends what you mean bybuodste.zip. if you mean OTA then no but you can normally get it from the factory images but there isn't one for M so you'll need to find the rooted ROM.zip and extract it from there.
Click to expand...
Click to collapse
^^^ this guy is right, I read the OP too quickly and missed the part about update.zip, I just assumed that we were talking about factory images.
I don't think the boot.img changed after D (including E, M and I), but a little digging around should verify that.
factory images are here:
https://developers.google.com/android/nexus/images
whatever you do, do not attempt to relock your boot loader (should you want to for some reason) until everything is working properly.
PhilDX said:
I don't think the boot.img changed after D (including E, M and I), but a little digging around should verify that.
Click to expand...
Click to collapse
Good point.
Could download the OTA files and run an md5sum on all the boot patches. If they match in each, they're patching kernel identically and the factory image version for any 5.1 would be appropriate.
Download
v3.2.1-0
Sauce: Github
Fixed /system mounting issues
let me know if you have any issues and I will do what I can to fix them.
Credit: @Josh1x for having the h870 device tree put together for me to clone and update. I will fix the original author on my master branch as soon as I get some time
Thank you!
Works like a charm. No issues here, thanks bro.
---------- Post added at 02:27 PM ---------- Previous post was at 01:42 PM ----------
Also this recovery also fixes the error messages apon flashing mods and what not
How can we apply it if no fastboot commands work
Trippyy Doee said:
How can we apply it if no fastboot commands work
Click to expand...
Click to collapse
Follow the steps exactly in this guide https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518 afterwards flash the image provided here in recovery
MudaTrucka said:
Follow the steps exactly in this guide https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518 afterwards flash the image provided here in recovery
Click to expand...
Click to collapse
So this is all we've been waiting for ?! Finally can haz root ? ?
MudaTrucka said:
Follow the steps exactly in this guide https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518 afterwards flash the image provided here in recovery
Click to expand...
Click to collapse
when i go into recovery mode all i get is no command. what should i do?
purplekushDGK said:
when i go into recovery mode all i get is no command. what should i do?
Click to expand...
Click to collapse
I think you might have to reflash recovery but idk I'm not the best with this
MudaTrucka said:
I think you might have to reflash recovery but idk I'm not the best with this
Click to expand...
Click to collapse
Opemilekan's method actually worked, had to flash supersu then used flashify to flash h872 twrp. thanks for the response man
purplekushDGK said:
Opemilekan's method actually worked, had to flash supersu then used flashify to flash h872 twrp. thanks for the response man
Click to expand...
Click to collapse
No problem, I thought I'd at least try to help
@KAsp3rd W00T -- glad to see that you built this.
The new version of the lafsploit will be out later today, and with it you can use any recovery your want. It handles all the hash verifications internally. It is about as automated as I can make it.
It will be:
./flash-h918-laf.py # Flashes the h918 laf without the need of LG UP, so no brick risks if people aren't paying attention
./root-h872.sh <recovery.img> # If specified, it will use the recovery.img passed, if not, then it will use this version which will be included in the repo
./post-root.sh # This takes care of all the final steps.
So three commands, and that is it. If I could force a reboot back into download mode, it would be one command, but a reboot into download mode is required between each command..
-- Brian
MudaTrucka said:
No problem, I thought I'd at least try to help
Click to expand...
Click to collapse
Can you tell me this method? I cannot get this image to stick, it always reverts back to H870, meaning I cannot flash anything custom (guess I could run Remix H870-would that work?)
agmyers76259 said:
Can you tell me this method? I cannot get this image to stick, it always reverts back to H870, meaning I cannot flash anything custom (guess I could run Remix H870-would that work?)
Click to expand...
Click to collapse
Flash the image to recovery, use the steps in the root thread to get it to stick and make sure you're actually booting into recovery and not laf
runningnak3d said:
@KAsp3rd W00T -- glad to see that you built this.
The new version of the lafsploit will be out later today, and with it you can use any recovery your want. It handles all the hash verifications internally. It is about as automated as I can make it.
It will be:
./flash-h918-laf.py # Flashes the h918 laf without the need of LG UP, so no brick risks if people aren't paying attention
./root-h872.sh <recovery.img> # If specified, it will use the recovery.img passed, if not, then it will use this version which will be included in the repo
./post-root.sh # This takes care of all the final steps.
So three commands, and that is it. If I could force a reboot back into download mode, it would be one command, but a reboot into download mode is required between each command..
-- Brian
Click to expand...
Click to collapse
Any idea when this might be ready good sir? I am not in a good place right now with my G6, could really use these commands---stuck in TWRP and can boot a rom, but somehow didnt follow your Step 3 in the Root guide, and my misc.img didnt get moved over, thus I have a rom that cannot connect to Wifi due to lack of MAC--this update would be huge, as I would go back to stock and restart this mess.
TIA
That won't help you now. Hopefully you still have the backup of your misc partition that was made in step 2. If so, boot to TWRP, and run:
adb push misc.img /sdcard/
adb shell dd if=/sdcard/misc.img of=/dev/block/bootdevice/by-name/misc
-- Brian
how do you flash the update
how do you flash the update? its not a option in the system app
purplekushDGK said:
Opemilekan's method actually worked, had to flash supersu then used flashify to flash h872 twrp. thanks for the response man
Click to expand...
Click to collapse
I used flashify and was promted for a decryption password upon booting recovery. Am I doing something wrong?
(Note that I can still access storage on the original download mode twrp, but not on this one)
Like everyone else I'm also confused as to how I can get the h872 recovery to work without breaking anything since I have the h870 recovery on laf
Stupid question I think, but I get a "Traceback (most recent call last):" after entering ./partitions.py --restoremisc twrp-3.2.1-0-h870.img .
Is there a specific place to put the TWRP ing file ? I think when I run the command its not finding the img.
MudaTrucka said:
Follow the steps exactly in this guide https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518 afterwards flash the image provided here in recovery
Click to expand...
Click to collapse
Hey so I already followed this tut last week and have been on root but having issues that this recovery fixes, how can I flash to this TWRP?