Heyo! Just recently rooted my H931 by following first the Frankenstein guide, then the WTF guide.
Anyways, I've tried both RR and LOS roms on the phone, and both end up being a bootloop. LGUP says its recognized as a US998, thanks to the frankenstein guide, so I figured Id have been able to use those kinds of custom roms.
So, has anyone with an AT&T lg v30 (h931) had any success with AOSP or LOS roms? If not, do we have any idea what causes the bootloops?
Truvaldak said:
Heyo! Just recently rooted my H931 by following first the Frankenstein guide, then the WTF guide.
Anyways, I've tried both RR and LOS roms on the phone, and both end up being a bootloop. LGUP says its recognized as a US998, thanks to the frankenstein guide, so I figured Id have been able to use those kinds of custom roms.
So, has anyone with an AT&T lg v30 (h931) had any success with AOSP or LOS roms? If not, do we have any idea what causes the bootloops?
Click to expand...
Click to collapse
what error show in twrp? (i.e los rom is vendor mount error for some devices)
and dirty flash or clean flash
TxanMoe said:
what error show in twrp? (i.e los rom is vendor mount error for some devices)
and dirty flash or clean flash
Click to expand...
Click to collapse
The problem is well known. Its just bootlooping....
Idk why yet, logs dont really show anything, atleast i dont see it
I'm not sure the Los rom I used needed a vendor repartition, because I was given no errors when flashing.
I'm terms of clean/dirty, for both roms I did a clean flash I think. Factory reset and wipe through twrp, then flash.
So, I think, and I'm probably wrong, that what's causing these bootloops is in the kernel. I don't have any logs to back this up, but I flashed the Lunar Kernel you can find here on this site, and my phone would boot up, then instantly shut back off. Not the same as a bootloop, but it just makes me think that whatever custom kernel is being used for AOSP or Los rooms has some sort of incompatibility with the H931
Maybe they're two entirely unrelated issues though.
Truvaldak said:
So, I think, and I'm probably wrong, that what's causing these bootloops is in the kernel. I don't have any logs to back this up, but I flashed the Lunar Kernel you can find here on this site, and my phone would boot up, then instantly shut back off. Not the same as a bootloop, but it just makes me think that whatever custom kernel is being used for AOSP or Los rooms has some sort of incompatibility with the H931
Maybe they're two entirely unrelated issues though.
Click to expand...
Click to collapse
I remember reading in a other thread that the kernel performs a firmware check against the devices ID before booting and that our att Franken phones still say they are a different phone somewhere. I believe it's just an aosp/Los thing because LG probably doesn't check the device type when installed as they perform the version control at the install level (ie. there are different kernels for different models rather than all using the same one)
MetaMaverick said:
I remember reading in a other thread that the kernel performs a firmware check against the devices ID before booting and that our att Franken phones still say they are a different phone somewhere. I believe it's just an aosp/Los thing because LG probably doesn't check the device type when installed as they perform the version control at the install level (ie. there are different kernels for different models rather than all using the same one)
Click to expand...
Click to collapse
If anything, we could try to develop an aosp/Los kernel specifically for the att franken phones, and test that out.. it's probably no walk in the park to do so, though. I have no experience doing that kind of stuff either, so I'm not much help.
I was browsing forum posts for custom roms, and it seems some people have had luck flashing a custom room over 20a us998 stock firmware, versus 20b. I'm going to try this out on the H931, see if that works
Truvaldak said:
I was browsing forum posts for custom roms, and it seems some people have had luck flashing a custom room over 20a us998 stock firmware, versus 20b. I'm going to try this out on the H931, see if that works
Click to expand...
Click to collapse
You probably shouldn't install US998 KDZ onto European H931, if that is what you are suggesting.
ChazzMatt said:
You probably shouldn't install US998 KDZ onto European H931, if that is what you are suggesting.
Click to expand...
Click to collapse
Nah, At&t h931. After flashing 20a, and then flashing an aosp room (dotos), it still bootloops. In other words, no luck.
Truvaldak said:
Nah, At&t h931. After flashing 20a, and then flashing an aosp room (dotos), it still bootloops. In other words, no luck.
Click to expand...
Click to collapse
Thanks for trying this, i was just about to do this. I can only boot successful on stock roms.
Truvaldak said:
Nah, At&t h931. After flashing 20a, and then flashing an aosp room (dotos), it still bootloops. In other words, no luck.
Click to expand...
Click to collapse
Sorry, long day. I was thinking H930 even though I was reading and typing H931.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Sorry, long day. I was thinking H930 even though I was reading and typing H931.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
No problem!
Who-Lep said:
Thanks for trying this, i was just about to do this. I can only boot successful on stock roms.
Click to expand...
Click to collapse
No problem. Was really a shot in the dark. Anyone welcome to try it as well, see if results vary.
Truvaldak said:
So, I think, and I'm probably wrong, that what's causing these bootloops is in the kernel. I don't have any logs to back this up, but I flashed the Lunar Kernel you can find here on this site, and my phone would boot up, then instantly shut back off. Not the same as a bootloop, but it just makes me think that whatever custom kernel is being used for AOSP or Los rooms has some sort of incompatibility with the H931
Maybe they're two entirely unrelated issues though.
Click to expand...
Click to collapse
What was the order of flashing when you flashed the kernel? The v20 had an issue similar and i had to flash the rom then kernel + gapps & root then reboot.
Who-Lep said:
What was the order of flashing when you flashed the kernel? The v20 had an issue similar and i had to flash the rom then kernel + gapps & root then reboot.
Click to expand...
Click to collapse
I flashed the kernel over the stock firmware (like it was meant to be)
Truvaldak said:
Nah, At&t h931. After flashing 20a, and then flashing an aosp room (dotos), it still bootloops. In other words, no luck.
Click to expand...
Click to collapse
Did you flash a 20a rom or used the 20a kdz with lgup?
Who-Lep said:
Did you flash a 20a rom or used the 20a kdz with lgup?
Click to expand...
Click to collapse
I only tried lgup.
Has anyone figured out how to flash custom ROM's on the h931 yet?
Big_Bad_Beast said:
Has anyone figured out how to flash custom ROM's on the h931 yet?
Click to expand...
Click to collapse
Yes, there's a guide
https://forum.xda-developers.com/lg-v30/how-to/running-h930-aosp-rom-us998-converted-t3889320
helppppppppp!!!!!
Truvaldak said:
Heyo! Just recently rooted my H931 by following first the Frankenstein guide, then the WTF guide.
Anyways, I've tried both RR and LOS roms on the phone, and both end up being a bootloop. LGUP says its recognized as a US998, thanks to the frankenstein guide, so I figured Id have been able to use those kinds of custom roms.
So, has anyone with an AT&T lg v30 (h931) had any success with AOSP or LOS roms? If not, do we have any idea what causes the bootloops?
Click to expand...
Click to collapse
hey dude plsss help me to root my lh h931 i tried 1000 times and my phone won't reboot into fastboot mode... pls help
Related
I've observed that quite a few people with the model number E988 have been having trouble in the modding(?) process. Mostly from due to unlocking and flashing a custom recovery via FreeGee (no offense intended to the maker of FreeGee)
So out of curiosity, before I have to unecessarily attempt the dreadful Recovery process again, have any of you guys managed to flash a custom ROM on your E988? If so, how?
(sorry mods if this is in the wrong forum).
I have flashed and used almost all the roms available in the original dev section.......no problems what so ever...... only one rom was problematic....... that is the PA port........ though not mandatory, keep the modem zip handy.......
Sent from my LG-E988 using xda app-developers app
Install cwm and disable lg security via freegee...and install rom without flashing modem is ok...working..only change apn..
But you can't back to stock rom without flashing kdz..
Once you reboot you can install rom via cwm but can not enter stock rom...
Sent from my LG-E988 using xda app-developers app
BauhausPen said:
I've observed that quite a few people with the model number E988 have been having trouble in the modding(?) process. Mostly from due to unlocking and flashing a custom recovery via FreeGee (no offense intended to the maker of FreeGee)
So out of curiosity, before I have to unecessarily attempt the dreadful Recovery process again, have any of you guys managed to flash a custom ROM on your E988? If so, how?
(sorry mods if this is in the wrong forum).
Click to expand...
Click to collapse
I concur especially the 10.2 cm rom (not the at&t version one) the one for e98X devices... always gives me error
any idea how to go back to stock rom ? I get various errors by lg flash tool ... device not detected mid way through or low battery error !!!
BauhausPen said:
I've observed that quite a few people with the model number E988 have been having trouble in the modding(?) process. Mostly from due to unlocking and flashing a custom recovery via FreeGee (no offense intended to the maker of FreeGee)
So out of curiosity, before I have to unecessarily attempt the dreadful Recovery process again, have any of you guys managed to flash a custom ROM on your E988? If so, how?
(sorry mods if this is in the wrong forum).
Click to expand...
Click to collapse
Looks like freegee does not work anymore. E986 or E988. Alternatives? Thanks.
demax123 said:
Looks like freegee does not work anymore. E986 or E988. Alternatives? Thanks.
Click to expand...
Click to collapse
FreeGee works fine on E988. I own one (Indian variant) and I can vouch for it. All you have to do is select "No" on the disable LG security option. CWM will get installed just fine. And since the FreeGee recovery is lokified, you are good to go for any rom including 4.3 ones. Like I said in my previous reply, I have used almost all the roms available in the Original DEV section. Only the PA port causes issues with the signal reception. Rest all work fine. If you are facing problems, be specific and I will try to help.....
bhoyonkor said:
FreeGee works fine on E988. I own one (Indian variant) and I can vouch for it. All you have to do is select "No" on the disable LG security option. CWM will get installed just fine. And since the FreeGee recovery is lokified, you are good to go for any rom including 4.3 ones. Like I said in my previous reply, I have used almost all the roms available in the Original DEV section. Only the PA port causes issues with the signal reception. Rest all work fine. If you are facing problems, be specific and I will try to help.....
Click to expand...
Click to collapse
I own G Pro e988 and want to flash Cyanogenmod 11.
Can you describe the steps of using the FreeGee app? And what stock firmware should I use with the freegee app. Should I flash stock Jellybean, root and the install FreeGee?
For know I am on stock kitkat (e98820c_twn_XX) and freegee don't work.
Thank you!
Is there a way to downgrade the bootloader without flashing an entire kdz?
I tried fastboot flash and dd an aboot.img extracted from a 4.4 kdz but I still get secure boot error.
Does anyone know if using the 4.4 bootloader on the F460 (NOT f400) will work with bumped images like the other models?
Also is it possible to download old kdz files from LG servers? Its almost impossible to find old F460 kdz, the few I found I'm not entirely confident in their integrity.
Is aboot.img the only image you tried to manually flash? There is also a boot.img you could also try flashing.
eradicator006 said:
Is aboot.img the only image you tried to manually flash? There is also a boot.img you could also try flashing.
Click to expand...
Click to collapse
I thought boot.img is just the kernel? I flashed a bumped version of the stock boot I pulled from my phone. That's working fine hasn't broken anything.
Is a non stock boot.img necessary just to install recovery?
You're right, boot.img is the kernel. Ignore what I said previously.
You could use the app autorec to "unlock" your bootloader. It essentially does the same thing you are trying to do; downgrade the bootloader.
eradicator006 said:
You're right, boot.img is the kernel. Ignore what I said previously.
You could use the app autorec to "unlock" your bootloader. It essentially does the same thing you are trying to do; downgrade the bootloader.
Click to expand...
Click to collapse
I wish. There is virtually no support for the F460 from anyone. I'm trying to port stuff to it and I already have test builds ready but I can't even run them. I followed the assumed method of autorec manually but it doesn't seem to work. I'm probably missing a few small but important details.
MeetShawn said:
I wish. There is virtually no support for the F460 from anyone. I'm trying to port stuff to it and I already have test builds ready but I can't even run them. I followed the assumed method of autorec manually but it doesn't seem to work. I'm probably missing a few small but important details.
Click to expand...
Click to collapse
rom
autorec f460
you're welcome
bender_007 said:
rom
autorec f460
you're welcome
Click to expand...
Click to collapse
!!!!!!!!!!!!!!!!!!!!!!!! AWESOME !!!!!!!!!!!!!!!!!!!!!!!!!
If this is new I feel like it deserves a thread, I think a lot of F460 owners gave up a while ago.
Now to see if that CM build that I spent so much time on works...
MeetShawn said:
!!!!!!!!!!!!!!!!!!!!!!!! AWESOME !!!!!!!!!!!!!!!!!!!!!!!!!
If this is new I feel like it deserves a thread, I think a lot of F460 owners gave up a while ago.
Now to see if that CM build that I spent so much time on works...
Click to expand...
Click to collapse
Don't forget to bump the kernel
Poslano sa mog LG-D855 koristeći Tapatalk
bender_007 said:
Don't forget to bump the kernel
Poslano sa mog LG-D855 koristeći Tapatalk
Click to expand...
Click to collapse
I forked the g3 repo and I think their mkbootimg includes bump. I should probably make a separate thread for troubleshooting this...
My g3 keeps restarting again and again , i have tried all the methods to resolve it like changing battery, reflashed rom many times, custom rom etc but the issue is still their i need help urgently.
reaper-soul said:
My g3 keeps restarting again and again , i have tried all the methods to resolve it like changing battery, reflashed rom many times, custom rom etc but the issue is still their i need help urgently.
Click to expand...
Click to collapse
What rom are you on? Stock? if yo which version? Have you tried flashing your stock, latest v30 rom?
i tried custom rom(resurrection remix), stock lollipop and stock marshmallow.Model is d855
reaper-soul said:
i tried custom rom(resurrection remix), stock lollipop and stock marshmallow.Model is d855
Click to expand...
Click to collapse
I got the same issue, but my phone doesn't bootloop with the latest stock rom for my IMEI (v30e), it does with everything else. Which version of the stock marshmallow did you try?
Teemoo said:
I got the same issue, but my phone doesn't bootloop with the latest stock rom for my IMEI (v30e), it does with everything else. Which version of the stock marshmallow did you try?
Click to expand...
Click to collapse
I tried global version i.e. 30b and according to my imei its same.
reaper-soul said:
I tried global version i.e. 30b and according to my imei its same.
Click to expand...
Click to collapse
Just to make it clear, you flashed your latest stock rom with LGUP right, because is changes all the partitions not just /system.
Teemoo said:
Just to make it clear, you flashed your latest stock rom with LGUP right, because is changes all the partitions not just /system.
Click to expand...
Click to collapse
yes i followed back to stock steps . used kdz file and lg flash tool.
I always followed these steps but nothing wrong happened but this time my phone is facing bootloop despite of new original battery checked on other g3 which worked fine.
I have been trying to get an answer for quite a while and no one has replied so I'm going to make my own thread.
I have a Samsung Galaxy S9(SM-G960F) 64GB, Running 8.0 Oreo and the current build number I am on is G960FXXU2BRGA_G960FOXM2BRGA_BTU.
My issue is that I cannot flash any custom ROMs onto my phone without it getting stuck on the "S9 secured by knox" splashscreen on boot. It does not bootloop or anything it just stays on that screen.
I have heard many things about the fact that BRE5 vendor is needed to flash custom ROMs but I cannot find anything anywhere on how I get this vendor.
Can somebody please help me?
Thanks
Milkyskittle said:
I have been trying to get an answer for quite a while and no one has replied so I'm going to make my own thread.
I have a Samsung Galaxy S9(SM-G960F) 64GB, Running 8.0 Oreo and the current build number I am on is G960FXXU2BRGA_G960FOXM2BRGA_BTU.
My issue is that I cannot flash any custom ROMs onto my phone without it getting stuck on the "S9 secured by knox" splashscreen on boot. It does not bootloop or anything it just stays on that screen.
I have heard many things about the fact that BRE5 vendor is needed to flash custom ROMs but I cannot find anything anywhere on how I get this vendor.
Can somebody please help me?
Thanks
Click to expand...
Click to collapse
Not sure what your specific issues is....but latest flashable vendor files are on this site. Plus....look for Soldier9312 development Discussions in Cross Device Devolpment here on S9 Forums.
http://www.soldier9312.de/#firmware
BRH4 is latest BTW...
Docmjldds said:
Not sure what your specific issues is....but latest flashable vendor files are on this site. Plus....look for Soldier9312 development Discussions in Cross Device Devolpment here on S9 Forums.
http://www.soldier9312.de/#firmware
BRH4 is latest BTW...
Click to expand...
Click to collapse
So if I installed BRH4 that would allow me to flash ROMs? At the moment I can only assume its the build that I'm on that is stopping me from doing so
Docmjldds said:
Not sure what your specific issues is....but latest flashable vendor files are on this site. Plus....look for Soldier9312 development Discussions in Cross Device Devolpment here on S9 Forums.
http://www.soldier9312.de/#firmware
BRH4 is latest BTW...
Click to expand...
Click to collapse
I just flashed the BH4 software and it chucked my phone in a bootloop...
Milkyskittle said:
I just flashed the BH4 software and it chucked my phone in a bootloop...
Click to expand...
Click to collapse
You are not giving much info. Start over. If you updated firmware, then you need to flash a ROM that is also using latest firmware. Just flashing a firmware update is not going to fix anything. Don't know what else to tell you. From your first post, you were on BRGA. I'm guessing latest firmware not compatible with your current ROM.
When my setups for whatever reason are in a really bad state, I do the following:
From TWRP recovery, I use the format tab and answer YES to the Format process. I then go back and under advance wipe, click on all the caches, data, system, and even internal storage. You can try without wiping Internal storage, but if you were coming from total stock, then I would also wipe that. Now flash a ROM and you should be fine. Not here to tout any one ROM. I have used a slew of them and again, not here to promote any single ROM as "the best".
Docmjldds said:
You are not giving much info. Start over. If you updated firmware, then you need to flash a ROM that is also using latest firmware. Just flashing a firmware update is not going to fix anything. Don't know what else to tell you. From your first post, you were on BRGA. I'm guessing latest firmware not compatible with your current ROM.
When my setups for whatever reason are in a really bad state, I do the following:
From TWRP recovery, I use the format tab and answer YES to the Format process. I then go back and under advance wipe, click on all the caches, data, system, and even internal storage. You can try without wiping Internal storage, but if you were coming from total stock, then I would also wipe that. Now flash a ROM and you should be fine. Not here to tout any one ROM. I have used a slew of them and again, not here to promote any single ROM as "the best".
Click to expand...
Click to collapse
So I'm now back on the stock firmware that I was originally on which is BRGA. Whenever I flash a rom I always format data just to be safe but I tried flashing RR and dotsOS and the BH4 rom that the other member suggested and none of them worked. I downloaded the stock firmware from sammobile it's the UK one
Milkyskittle said:
So I'm now back on the stock firmware that I was originally on which is BRGA. Whenever I flash a rom I always format data just to be safe but I tried flashing RR and dotsOS and the BH4 rom that the other member suggested and none of them worked. I downloaded the stock firmware from sammobile it's the UK one
Click to expand...
Click to collapse
AOSP ROMs IMHO have issues. Use a Samsung based ROM, and generally no issues. Your choice. I do NOT push any one ROM. I currently am on TGP...The Galaxy Project you can look up in Cross Device Development.
Docmjldds said:
AOSP ROMs IMHO have issues. Use a Samsung based ROM, and generally no issues. Your choice. I do NOT push any one ROM. I currently am on TGP...The Galaxy Project you can look up in Cross Device Development.
Click to expand...
Click to collapse
Ok I will have a look. Thank you for your help
Milkyskittle said:
Ok I will have a look. Thank you for your help
Click to expand...
Click to collapse
Welcome
im not saying im gonna root my a22 yet but is anyone gonna port twrp or nah
when you try to write twrp, you may need to unlock bootloader first. and i have the problem with param file, because it's compressed by lz4 with another methods. can't open it with 7zip anymore.
do you have it?
same. i thought i'd be able to flash a custom ROM but I'm stuck with my device not listed on TWRP
nptoonix said:
same. i thought i'd be able to flash a custom ROM but I'm stuck with my device not listed on TWRP
Click to expand...
Click to collapse
Yea but this is a device that's like 3 months old
Will this work? (https://odinforum.com/discussion/7/how-to-flash-custom-rom-on-samsung-devices-using-odin)
nptoonix said:
Will this work? (https://odinforum.com/discussion/7/how-to-flash-custom-rom-on-samsung-devices-using-odin)
Click to expand...
Click to collapse
Well firstly it's done on a old version of odin with the old layout of firmware files, which won't work. And if it did work there's a high chance there's no custom roms for A22.
BlueTower said:
Well firstly it's done on a old version of odin with the old layout of firmware files, which won't work. And if it did work there's a high chance there's no custom roms for A22.
Click to expand...
Click to collapse
Thank you for the response I'll wait then