Related
I will answer any question you need. let me know.
my Cell signal is messed up. I have bootloader unlocked phone that is US998. I installed the US99820e_02_0910.kdz from ChazzMatt and then in TWRP Aroma installered the BoomBox V30 from Whiskeyomega. do you know how to reinstall the modem/cellular parts only?
EDIT: I changed back to the KDZ rom/version instead of BoomBox. I guess the question still stands. How do we reinstall only the cell part of the US998 rom into the BoomBox rom?
acters said:
my Cell signal is messed up. I have bootloader unlocked phone that is US998. I installed the US99820e_02_0910.kdz from ChazzMatt and then in TWRP Aroma installered the BoomBox V30 from Whiskeyomega. do you know how to reinstall the modem/cellular parts only?
EDIT: I changed back to the KDZ rom/version instead of BoomBox. I guess the question still stands. How do we reinstall only the cell part of the US998 rom into the BoomBox rom?
Click to expand...
Click to collapse
Does it say no service or does it show signal but no LTE?
acters said:
my Cell signal is messed up. I have bootloader unlocked phone that is US998. I installed the US99820e_02_0910.kdz from ChazzMatt and then in TWRP Aroma installered the BoomBox V30 from Whiskeyomega. do you know how to reinstall the modem/cellular parts only?
EDIT: I changed back to the KDZ rom/version instead of BoomBox. I guess the question still stands. How do we reinstall only the cell part of the US998 rom into the BoomBox rom?
Click to expand...
Click to collapse
Boombox doesnt touch the modem though
acters said:
my Cell signal is messed up. I have bootloader unlocked phone that is US998. I installed the US99820e_02_0910.kdz from ChazzMatt and then in TWRP Aroma installered the BoomBox V30 from Whiskeyomega. do you know how to reinstall the modem/cellular parts only?
EDIT: I changed back to the KDZ rom/version instead of BoomBox. I guess the question still stands. How do we reinstall only the cell part of the US998 rom into the BoomBox rom?
Click to expand...
Click to collapse
You don't say what provider you are with. But whatever it is, on 20E you are fine? It's only when you install Boombox that you can't get a signal?
On most ROMs, you do not need to re-flash modem. But still many developers provide TWRP flashable versions of newer modems so you can update when those are released. I am not aware of any TWRP flashable modems for the V30 yet.
SGCMarkus said:
Boombox doesnt touch the modem though
Click to expand...
Click to collapse
Yeah, I'm confused about that as well. If his phone is working fine on US998 20E, then why is it not on stock-based Boombox ROM?
Dam xda login deleted my whole message and sent me to the front page. Mean. I won't rewrite it but here are the highlights.
TMobile. It's been a week straight of reflashing. I think it's a level 8 error but I don't know what I would mess up on these simple instructions. The messaging apps and phone app crashes. after putting in the apn settings, I got data but very poor. I've recreated some of the main features like dual speaker and sound mixer from whiskyomega and set the dpi to 560 and uninstalled many system apps through titanium backup on this US998 ROM. I'm exhausted on going through LGs tutorial stuff over and over again. Yeah i know what my buttons do, NAVI ya pest. I would definitely love to just flash boombox ROM instead of going through the hassle of this. However right now I'm tired of trying. I'll just wait for stable pie ROMs to come out.
Thank you for reading my long winded story.
Thanks for this thread. I don't need to make new threads for questions now.
Question:
I'm quite jnterested in flashing this kernel
https://forum.xda-developers.com/lg-v30/development/kernel-lunar-kernels-lg-v30-t3804267
for stock ROM (h930). Unfortunately, I've been reading the thread (I think I'm just missibg a few pages in the middle), but there are some things I couldn't find.
1. What are the bugs for stable? In the OP of the threat, the bugs are marked "outdated" so I'm not sure if the issues still persist.
2. Treblelized? I keep seeing this but I don't know if this is necessary. I haven't repartitioned, and I was wondering if i will have to moving forward (for flashing ROMs, kernels, etc). I can't recall seeing this on the bootloader unlock thread so I never got around to doing it (based on experience, repartitioning is dangerous - one mistake and you run the risk of hard brick - so I might skip this if I don't need it).
Again, thank yiu for the thread and for the amswers! Apologies if the questions are noobish. My last phone was a G5 that can't be rooted so I am far from up-to-date on flashing and modding (never had to do that on my g3 and g4 lol). And i didn't want to ask general questions on dev threads...
is there a solution to fix Hardrick lg v30 (msm8998) qdloader 9008. please
Sent from my LGM-V300S using XDA Labs
cascabel said:
Thanks for this thread. I don't need to make new threads for questions now.
Question:
I'm quite jnterested in flashing this kernel
https://forum.xda-developers.com/lg-v30/development/kernel-lunar-kernels-lg-v30-t3804267
for stock ROM (h930). Unfortunately, I've been reading the thread (I think I'm just missibg a few pages in the middle), but there are some things I couldn't find.
1. What are the bugs for stable? In the OP of the threat, the bugs are marked "outdated" so I'm not sure if the issues still persist.
2. Treblelized? I keep seeing this but I don't know if this is necessary. I haven't repartitioned, and I was wondering if i will have to moving forward (for flashing ROMs, kernels, etc). I can't recall seeing this on the bootloader unlock thread so I never got around to doing it (based on experience, repartitioning is dangerous - one mistake and you run the risk of hard brick - so I might skip this if I don't need it).
Again, thank yiu for the thread and for the amswers! Apologies if the questions are noobish. My last phone was a G5 that can't be rooted so I am far from up-to-date on flashing and modding (never had to do that on my g3 and g4 lol). And i didn't want to ask general questions on dev threads...
Click to expand...
Click to collapse
Custom kernel questions should be asked in the kernel thread. You can ask here, but the best people to answer - - including the dev - - are there.
No, you don't need "Treble" or to vendor partition your drive. If that's something you want to tinker with later, feel free. We don't have official Treble support anyways. The Treble stuff is project @SGCMarkus is doing to replicate Treble in our phone. But all ROMs without Treble in the title do not need vendor partition ("Treble") to install. You just need TWRP.
ChazzMatt said:
Custom kernel questions should be asked in the kernel thread. You can ask here, but the best people to answer - - including the dev - - are there.
No, you don't need "Treble" or to partition your drive. If that's something you want to tinker with later, feel free. We don't have official Treble support anyways. The Treble stuff is project @SGCMarkus is doing to replicate Treble in our phone. But all ROMS without Treble in the title do not need vendor partition ("Treble") to install. You just need TWRP.
Click to expand...
Click to collapse
I see. My apologies. I'm not used to asking on dev threads as it was frowned upon on past device subforums (unless you have a log for your issue, questions are for the Q&A threads - I really don't want to bother the devs with a lot of questions unless i can provide logs to help them out). I guess it's qyite different here (still in awe of how helpful everyone's been).
I'll finish readibg the whole thread and ask there if I still have questions. Again, thank you. And i apologize for having a lot of questions.
Edit;
I'll probably leave treble alone for now. I've had bad experiences with repartitioning (hard brick) since one wrong move and there's no going back. Lol.
please delete
On request, to easier find this, im creating this thread
For all the H932 users out there, who also want to use ROMs that dont provide support for it, but only for the H930, heres a little zip for you, which will allow you to fully use H930 ROMs on your H932.
What this zip does:
Replaces the necessary firmware files (list here (H930 tree, because the H932s list is somehow empty... gotta fix that later)) which are the only (important) difference.
This wont change the device fingerprint from H930 to H932 (maybe in a later version, who knows)
This is also ONLY intented for AOSP ROMs (LOS, RR, whatever else we have), do NOT use this on Stock based ROMs
How to use it:
1) Flash H930 ROM on your H932
2) Flash this zip
3) boot the system
This is NOT for H930/US998/and so on users!
XDA:DevDB Information
H932 Firmware zip, Tool/Utility for the LG V30
Contributors
SGCMarkus
Version Information
Status: Stable
Created 2019-08-16
Last Updated 2019-08-16
Thanks! Just added to the Root Sticky post.
Suggestion: all the ROM devs should add prominent link to this thread to their OP (post #1) of their ROM threads. It would only increase their ROM usage, as T-mobile H932 users think they don't have many choices!
ChazzMatt said:
Thanks! Just added to the Root Sticky post.
Suggestion: all the ROM devs should add prominent link to this thread to their OP (post #1) of their ROM threads. It would only increase their ROM usage, as T-mobile H932 users think they don't have many choices!
Click to expand...
Click to collapse
Thanks a lot for the zip Markus ?
Guys please add the link to your ROM pages.
@kherio @BADA 187 @Mrxyzl @luffy1105
@Blackmanta @Ab.Shaheen
Thx for your work!:good:
i'd like to try on stock... but kinda scary
immns said:
i'd like to try on stock... but kinda scary
Click to expand...
Click to collapse
It clearly says don't try on stock. So don't
immns said:
i'd like to try on stock... but kinda scary
Click to expand...
Click to collapse
This is ONLY for AOSP/Lineage custom ROMs, so T-Mobile H932 can boot them. Is the op not clear?
Post #2 screenshot is pretty clear.
Thanks for yours hard work. Have more choices to choose now..,?
Has anyone used on LiquidRemix rom for H930 and installed the rom on Tmo H932? Thanks.
thank you for thread (and link to thread) as it clears alot of confusion.
im still weary of using ROMs that werent "built" with h932 foundation for a number of reasons, but may give a few of the AOSP ROMs a shot if i cant find a decent debloated stock.
letthebeatrock said:
thank you for thread (and link to thread) as it clears alot of confusion.
im still weary of using ROMs that werent "built" with h932 foundation for a number of reasons, but may give a few of the AOSP ROMs a shot if i cant find a decent debloated stock.
Click to expand...
Click to collapse
XenonHD and this zip will work
HueyT said:
XenonHD and this zip will work
Click to expand...
Click to collapse
Tried it. And a bunch of pie based AOSP ROMs on rooted h932. They all boot fine but the modem bootstack doesn't match up. You won't get Wi-Fi on any pie ROM with h932 at the moment
I Tried to Update But Cant Possible.
Any One How to update LG V30 AS998?
Plz Tell Me I am New in Community
waseemrehmat said:
I Tried to Update But Cant Possible.
Any One How to update LG V30 AS998?
Plz Tell Me I am New in Community
Click to expand...
Click to collapse
Why are you posting in this thread? It's for T-mobile H932 and you say you have AS998.
ChazzMatt said:
Why are you posting in this thread? It's for T-mobile H932 and you say you have AS998.
Click to expand...
Click to collapse
So I Want Yo Know How. I Update My AS998
waseemrehmat said:
So I Want Yo Know How. I Update My AS998
Click to expand...
Click to collapse
Well, you need to ask in relevant threads. Or start a new thread in the Questions section. I see you finally posted in Frankenstein, which is helpful for what you need. I answered your question there.
In forums like this, people don't want irrelevant questions clogging their threads. This is a thread for T-Mobile H932 only and they couldn't care less about AS998.
letthebeatrock said:
Tried it. And a bunch of pie based AOSP ROMs on rooted h932. They all boot fine but the modem bootstack doesn't match up. You won't get Wi-Fi on any pie ROM with h932 at the moment
Click to expand...
Click to collapse
Can you clarify what you mean with this? I used RR and this converter and wifi worked fine. Similarly I've used for a long time the Lineage specific H932 build and I also get wifi. However in my region (Norway) I get an "x" on the LTE, HSPDA, 3G (any bands really) signal bars that comes and goes. Sometimes data works - especially when connected to a VPN, but I've had no issue in any other country, just this one and I wonder if the 2 are related. Or am I clutching at straws? I had to give up on my H932 and go back to my old iphone (bluurgh) because I don't know what the issue is and I can't be working with unreliable data.
letthebeatrock said:
Tried it. And a bunch of pie based AOSP ROMs on rooted h932. They all boot fine but the modem bootstack doesn't match up. You won't get Wi-Fi on any pie ROM with h932 at the moment
Click to expand...
Click to collapse
This literally does the same (relevant) changes to the ROM as when you would build H932 ROMs (the only difference are the few firmware files and the device fingerprint (unimportant))... so whatever issue you have, its not related to this
ddevey said:
Can you clarify what you mean with this? I used RR and this converter and wifi worked fine. Similarly I've used for a long time the Lineage specific H932 build and I also get wifi. However in my region (Norway) I get an "x" on the LTE, HSPDA, 3G (any bands really) signal bars that comes and goes. Sometimes data works - especially when connected to a VPN, but I've had no issue in any other country, just this one and I wonder if the 2 are related. Or am I clutching at straws? I had to give up on my H932 and go back to my old iphone (bluurgh) because I don't know what the issue is and I can't be working with unreliable data.
Click to expand...
Click to collapse
SGCMarkus said:
This literally does the same (relevant) changes to the ROM as when you would build H932 ROMs (the only difference are the few firmware files and the device fingerprint (unimportant))... so whatever issue you have, its not related to this
Click to expand...
Click to collapse
I honestly couldnt explain it any further than what I did
HOWEVER.
I decided to flash the LP ROM again, then the H930 to H932 converter, flash Magisk, and THEN the 20s Modem from a another topic and all my WiFi issues were cleared up.
so yes, in my particular case, I had to flash the ROM, and then the Modem in order to get Wi-Fi to work
Updated with the pie blobs from H932 30d. Zip is attached in the OP.
Does the same as for oreo, just with pie blobs and their location, so you shouldnt have any issues.
It looks like the international forum is pretty dead compared to indian, there are no non-miui custom roms at all.
Is it possible to install indian model custom rom on global version? Thanks.
There's a reason for that.
Not too long ago we had one combined forum for ROM development but when Joyeuse was released, (Curtana was released a couple of months earlier), custom ROM rookies who weren't sure what they were doing, were bricking their phones by flashing the wrong device specific tools and/or ROMs.
A retrospective change was made to the forum structure to try and help the rookies and the result was the separation of Indian and Global versions.
A few short weeks later, a smart developer unified the device trees for both versions, (Joyeuse and Curtana), so that ROMs, and tools, could be built that would work on either device without issue. These ROMs are tagged with the code "Miatoll".
So long story short, due to history of the forums, it appears that there is very little development for Joyeuse, but in reality, nearly all Note 9 developers are now using the stable Miatoll tree and there are just as many ROMs available for both the Indian and the Global versions of the Note 9 Pro.
Hope this helps clarify your, (and anyone else that follows), concerns around ROM development for the Global version.
sir_bazz said:
There's a reason for that.
Not too long ago we had one combined forum for ROM development but when Joyeuse was released, (Curtana was released a couple of months earlier), custom ROM rookies who weren't sure what they were doing, were bricking their phones by flashing the wrong device specific tools and/or ROMs.
A retrospective change was made to the forum structure to try and help the rookies and the result was the separation of Indian and Global versions.
A few short weeks later, a smart developer unified the device trees for both versions, (Joyeuse and Curtana), so that ROMs, and tools, could be built that would work on either device without issue. These ROMs are tagged with the code "Miatoll".
So long story short, due to history of the forums, it appears that there is very little development for Joyeuse, but in reality, nearly all Note 9 developers are now using the stable Miatoll tree and there are just as many ROMs available for both the Indian and the Global versions of the Note 9 Pro.
Hope this helps clarify your, (and anyone else that follows), concerns around ROM development for the Global version.
Click to expand...
Click to collapse
Thank you for the detailed answer
I'm kinda confused about the kernels now..In a ROM post, do I simply install the kernel given, even though it's not saying that it's specifically only for Joyeuse?
For example here: https://forum.xda-developers.com/redmi-note-9-pro/development/gsi-t4165873
"2. Download vbmeta from here and flash it in fastboot like this:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_note9s.img (IF YOU DONT DO THIS STEP, VOLTE AND OK GOOGLE WONT WORK!)"
I'm not really sure what is vbmeta, and it also says note9s, so once again just trying to verify if it's ok and I won't brick my phone
msacco4 said:
Thank you for the detailed answer
I'm kinda confused about the kernels now..In a ROM post, do I simply install the kernel given, even though it's not saying that it's specifically only for Joyeuse?
For example here: https://forum.xda-developers.com/redmi-note-9-pro/development/gsi-t4165873
"2. Download vbmeta from here and flash it in fastboot like this:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_note9s.img (IF YOU DONT DO THIS STEP, VOLTE AND OK GOOGLE WONT WORK!)"
I'm not really sure what is vbmeta, and it also says note9s, so once again just trying to verify if it's ok and I won't brick my phone
Click to expand...
Click to collapse
My suggestion would be to forget about GSI's and choose one or the 20 or so ROM's that have been built speficially for our device.
sir_bazz said:
My suggestion would be to forget about GSI's and choose one or the 20 or so ROM's that have been built speficially for our device.
Click to expand...
Click to collapse
By specifically built rom you mean unified rom, or one that specifically states that supports joyeuse?
msacco4 said:
By specifically built rom you mean unified rom, or one that specifically states that supports joyeuse?
Click to expand...
Click to collapse
Either of Miatoll or Joyeuse build will be good.
I'm not a dev, but I believe ROM's built on the Miatoll device tree may even be slightly better than Joyeuse due to the wider take up of development.
Initial topic - https://forum.xda-developers.com/lg-v40/development/android-10-0-0-lineageos-17-0-v40-t3970119
So far I am only doing compilation without testing the result.
Download:
LOS-17.1
Latest build: lineage-17.1-20200304-UNOFFICIAL-judypn
lineage-17.1-20210304-UNOFFICIAL-judypn.zip
drive.google.com
Prev.:lineage-17.1-20201118-UNOFFICIAL-judypn
https://drive.google.com/drive/folders/1QT_yRNtydEZmplZvl5oSq1xiySv53NK9?usp=sharing
LOS-18.0
Latest build: lineage-18.0-20201126-UNOFFICIAL-judypn
https://drive.google.com/drive/folders/17d7f1QdUoljNnU00VRJYC776KhAwIq4R?usp=sharing
Contributors
xenius9, SGCMarkus
Many thanks to SGCMarkus for the sources.
xenius9 said:
Initial topic - https://forum.xda-developers.com/lg-v40/development/android-10-0-0-lineageos-17-0-v40-t3970119
So far I am only doing compilation without testing the result.
Click to expand...
Click to collapse
Is LOS 18.0 "Pre Alpha or Alpha" suitable for daily use?
Haven't noticed exact description what works and what are the current bugs.....
xenius9 said:
Initial topic - https://forum.xda-developers.com/lg-v40/development/android-10-0-0-lineageos-17-0-v40-t3970119
So far I am only doing compilation without testing the result.
Download:
LOS-17.1
Latest build: lineage-17.1-20201118-UNOFFICIAL-judypn
https://drive.google.com/drive/folders/1QT_yRNtydEZmplZvl5oSq1xiySv53NK9?usp=sharing
LOS-18.0
Latest build: lineage-18.0-20201126-UNOFFICIAL-judypn
https://drive.google.com/drive/folders/17d7f1QdUoljNnU00VRJYC776KhAwIq4R?usp=sharing
Contributors
xenius9, SGCMarkus
Many thanks to SGCMarkus for the sources.
Click to expand...
Click to collapse
Do you think most of the bugs will be cleared out by the end of the year? Also, which kdz should I use if I want band 71 support?
camray00 said:
Do you think most of the bugs will be cleared out by the end of the year? Also, which kdz should I use if I want band 71 support?
Click to expand...
Click to collapse
I don't know anything about the bugs, but for b71 2 of the roms have it; US OP Pie (no Q yet) and KR OP which is Korean Open (Q version available) has b71 also.
cheers
AsItLies said:
I don't know anything about the bugs, but for b71 2 of the roms have it; US OP Pie (no Q yet) and KR OP which is Korean Open (Q version available) has b71 also.
cheers
Click to expand...
Click to collapse
I was thinking it might be possible to grab the modem partition from sprint or unlocked pie and write them over before installing this ROM. Would that work, or would it be incompatible?
camray00 said:
I was thinking it might be possible to grab the modem partition from sprint or unlocked pie and write them over before installing this ROM. Would that work, or would it be incompatible?
Click to expand...
Click to collapse
I'm not sure, have not tried that. I've read others suggesting the same thing but don't know if they've had success with it. I'd bet it wouldn't as there are so many threads, in various model phones, about which rom supports which bands. If that problem could be resolved by simply using the modem partition from a diff rom, it happening would almost certainly be common knowledge and many threads with various modem partitions available, but there aren't.
AsItLies said:
I'm not sure, have not tried that. I've read others suggesting the same thing but don't know if they've had success with it. I'd bet it wouldn't as there are so many threads, in various model phones, about which rom supports which bands. If that problem could be resolved by simply using the modem partition from a diff rom, it happening would almost certainly be common knowledge and many threads with various modem partitions available, but there aren't.
Click to expand...
Click to collapse
Ended up trying it and it prevents boot to system and recovery. I replaced all 4. modemst1,modemst2,modem_a,modem_b
I think we'll have to wait for them to make Q for v405qa unlocked.
I used v405ebw with lineage 18. VoLTE and VoWiFi aren't supported, which basically makes Mint Mobile unusable except for data.
camray00 said:
Ended up trying it and it prevents boot to system and recovery. I replaced all 4. modemst1,modemst2,modem_a,modem_b
I think we'll have to wait for them to make Q for v405qa unlocked.
I used v405ebw with lineage 18. VoLTE and VoWiFi aren't supported, which basically makes Mint Mobile unusable except for data.
Click to expand...
Click to collapse
I'd suggest another option, as 405qa Q arrival is ???, use the korean open 30e. That's what I have. One mod makes it quite workable; copy the US Open /OP partition (from Pie) and use it instead of the KR Open partition. Everything works, including vowifi and volte. And it does get b71. There's only 1 other small change needed to get vowifi to work.
It's very solid and haven't had any trouble with it at all. Something to consider.
I just found out that a great deal of work can be done with Cellular Support via the Qualcomm PDC tool.
AsItLies said:
I'd suggest another option, as 405qa Q arrival is ???, use the korean open 30e. That's what I have. One mod makes it quite workable; copy the US Open /OP partition (from Pie) and use it instead of the KR Open partition. Everything works, including vowifi and volte. And it does get b71. There's only 1 other small change needed to get vowifi to work.
It's very solid and haven't had any trouble with it at all. Something to consider.
Click to expand...
Click to collapse
Can you link the Korean open download? Also, what is the small change for VoWiFi?
Yes it's on this link. It's at the top of the list, the KR Open, 30e is the last one in the beginning section.
The other change is minor, have to enter the service menu with the dial code and it's one of the SVC (iirc) fields you have to enable vowifi. I can find it if you decide to do it.
There's a little 'trick' u need to do when cross flashing, to avoid the 'NT_Error' thing when u first boot up. It doesn't cause a problem, it's just annoying. Just after doing a partition DL of the rom, let it boot of course, to finish. Then shut it off, don't touch anything. Then use LG up and do a refurbish with same rom. No more nt-error code thing.
Also, even though the firmware page (above) doesn't indicate it, that rom does have b71. I have a screen shot of the phone using lte discovery connected to b71 on that rom. It's there.
AsItLies said:
Also, even though the firmware page (above) doesn't indicate it, that rom does have b71. I have a screen shot of the phone using lte discovery connected to b71 on that rom. It's there.
Click to expand...
Click to collapse
I'm trying to boot TWRP. When I run
Code:
fastboot boot judypn_TWRP_bootable-metadata.img
it reads out this:
Code:
downloading 'boot.img'...
OKAY [ 0.942s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.946s
This is after flashing the Korean Open version. I'm not sure what to do. I made sure USB Debugging was on and changed the driver to the official LGE one, but no luck.
I tried everything on google. Still no luck.
camray00 said:
I tried everything on google. Still no luck.
Click to expand...
Click to collapse
Hi, so we've hijacked this thread long enough, let's move this over to this thread which is kor open specific.
Sorry about the hijack xenius.
Please help me. My LG v40ua is switched into los-18.0 and recovery is also los-18.0. Now I want to change back to the previous system, but I can't do it without root. Please tell me what to do, thank you
And my phone can't enter FastBoot mode
xenius9 said:
Initial topic - https://forum.xda-developers.com/lg-v40/development/android-10-0-0-lineageos-17-0-v40-t3970119
So far I am only doing compilation without testing the result.
Download:
LOS-17.1
Latest build: lineage-17.1-20201118-UNOFFICIAL-judypn
https://drive.google.com/drive/folders/1QT_yRNtydEZmplZvl5oSq1xiySv53NK9?usp=sharing
LOS-18.0
Latest build: lineage-18.0-20201126-UNOFFICIAL-judypn
https://drive.google.com/drive/folders/17d7f1QdUoljNnU00VRJYC776KhAwIq4R?usp=sharing
Contributors
xenius9, SGCMarkus
Many thanks to SGCMarkus for the sources.
Click to expand...
Click to collapse
Thank you for your work, @xenius9 - спасибо большое. Using lineage-17.1-20201118-UNOFFICIAL-judypn on Sprint LM-V405UA for about a month without problems.
praiseeee said:
Please help me. My LG v40ua is switched into los-18.0 and recovery is also los-18.0. Now I want to change back to the previous system, but I can't do it without root. Please tell me what to do, thank you
And my phone can't enter FastBoot mode
Click to expand...
Click to collapse
You should get fastboot working via 9008 guide (I suggest not to wipe lafs on both slots), then fastboot TWRP.
praiseeee said:
Please help me. My LG v40ua is switched into los-18.0 and recovery is also los-18.0. Now I want to change back to the previous system, but I can't do it without root. Please tell me what to do, thank you
And my phone can't enter FastBoot mode
Click to expand...
Click to collapse
If you install this apk (only on los), it will allow you to switch to the other side and reboot recovery. It's hard coded (I changed the original file) to boot to recovery after you select the other slot. Did it for the exact situation you're experiencing.
cheers
LOS 17.1 updated
xenius9 said:
LOS 17.1 updated
Click to expand...
Click to collapse
Is it stable? Good for daily driver? Thanks!
Hello forum!
I have LG LM-V405QA and would like to have a ROM flashed that removes all Google everything. I have flashed ROMs in the past, but have already spent too much time researching with no results. I am in California, USA.
This is a serious inquiry. Please help.
Thank you.
I'm looking to build AOSP for the Red Magic 8 Pro. Has anyone managed to get the proprietary binaries from Nubia or extract it from the stock firmware?
I have tried searching around for these binaries to no avail. If someone has a download link to share I would really appreciate it. I just want a completely stock android experience and don't mind if not everything isn't working.
Do you really want AOSP or Paranoid Android will do as well? In any case, download OTA here, extract payload.bin and use payload-dumper-go. You can use LineageOS instructions for getting binaries from unpacked .omg files.
aaa.bbb111222 said:
Do you really want AOSP or Paranoid Android will do as well? In any case, download OTA here, extract payload.bin and use payload-dumper-go. You can use LineageOS instructions for getting binaries from unpacked .omg files.
Click to expand...
Click to collapse
Have they already released a ROM for this phone? If not, AOSP builds without most Google trash and I block many of their domains in the hosts file just in case. I did finally find a dump here: https://github.com/RandomPush/nubia_nx729j_dump
Appreciate your help though. I'll post my progress here in case anyone is interested. The android developer documentation says proprietary binaries are usually located in a /vendor partition. Going through the dump now and trying to figure out the bare minimum to get a custom ROM booted.
My guesses are anything Qualcomm related for the SoC. I'm unsure of what baseband/radio chips the phone uses, actually it's been pretty tough to find a good spec sheet on it. Most resources that come up on Google only refer to surface level specs and don't go into much detail on the chips themselves.
No, they haven't, but I've seen people working on it. It would be a bit easier to bring up because PA is CLO-based (not AOSP), so the probability of most stuff working is higher. CLO has some Qualcomm-specific patches. Actually, you can probably build QSSI (like GSI but from CLO) without much difficulties, so this might be the way to go.
I'd recommend that you extract those binaries from OTA anyway as they might be updated in the future. Out of the box you probably won't get working vibration.
With the kernel source released, what's so difficult with building LineageOS and stuff?
SevastianXDA said:
With the kernel source released, what's so difficult with building LineageOS and stuff?
Click to expand...
Click to collapse
We need a good unbricking method just to be on the safe side (personally, I'm not very keen on even trying someone else's build, let alone making my own, simply too much risk). Other than that, a lot of time is needed and there are basically zero good instructions. Once again, LOS isn't the best option for 8g2, would be better to go for Paranoid Android. One can theoretically build QSSI image (basically GSI, but for Snapdragons), might be a good idea for now. Still risky tho
aaa.bbb111222 said:
We need a good unbricking method just to be on the safe side (personally, I'm not very keen on even trying someone else's build, let alone making my own, simply too much risk). Other than that, a lot of time is needed and there are basically zero good instructions. Once again, LOS isn't the best option for 8g2, would be better to go for Paranoid Android. One can theoretically build QSSI image (basically GSI, but for Snapdragons), might be a good idea for now. Still risky tho
Click to expand...
Click to collapse
What are the bricking issues here? Usually even if the ROM is f*cked or just something doesn't work you can always flash back to stock through TWRP.
SevastianXDA said:
What are the bricking issues here? Usually even if the ROM is f*cked or just something doesn't work you can always flash back to stock through TWRP.
Click to expand...
Click to collapse
If only there was a fully working TWRP... Unfortunately, there isn't. Well, kind of. It boots but that's it. And no, sideload simply doesn't work. When I went back to stock on my previous device (1+7 Pro), I had to use MSM Tool. Nothing like that is available for RM8P, ZTE doesn't want to give the tools to us because of bs reasons.
aaa.bbb111222 said:
If only there was a fully working TWRP... Unfortunately, there isn't. Well, kind of. It boots but that's it. And no, sideload simply doesn't work. When I went back to stock on my previous device (1+7 Pro), I had to use MSM Tool. Nothing like that is available for RM8P, ZTE doesn't want to give the tools to us because of bs reasons.
Click to expand...
Click to collapse
Bruuuuhhh, that's stupidd, someone shall reverse engineer the MSM tool to work for the RM8P (sarcasm)
Hmm, as I can see from this post, it seems peeps have managed to actually restore the phone from a full brick..: Post
Edl or its countparts is not a necessity for buiding a custom rom. 1st, a custom rom usually just overwrite the application parts, so in the worst case the user can still restore to factory rom via fastboot commands. 2nd, many manufacturers never release their factory rescue tools (Google, ?) but there are numerous custom roms, even official builds.
Cyanide_zh said:
Edl or its countparts is not a necessity for buiding a custom rom.
Click to expand...
Click to collapse
True, it's more a convenience factor.
Cyanide_zh said:
1st, a custom rom usually just overwrite the application parts, so in the worst case the user can still restore to factory rom via fastboot commands.
Click to expand...
Click to collapse
Or not. In fact, happened to me (Qualcomm crashdump mode or something like that). And if something could go wrong, it will.
Cyanide_zh said:
2nd, many manufacturers never release their factory rescue tools (Google, ?) but there are numerous custom roms, even official builds.
Click to expand...
Click to collapse
Usually those devices have much less ROMs available if any. Just compare 1+9 Pro and 10 Pro.
aaa.bbb111222 said:
less ROMs available if any. Just compare 1+9 Pro
Click to expand...
Click to collapse
Any ROM than the stock would do, just LineageOS would be superb.
SevastianXDA said:
Hmm, as I can see from this post, it seems peeps have managed to actually restore the phone from a full brick..: Post
Click to expand...
Click to collapse
Interesting.. https://romprovider.com/nubia-red-magic-8-pro-plus-firmware-stock-rom/
SevastianXDA said:
Interesting.. https://romprovider.com/nubia-red-magic-8-pro-plus-firmware-stock-rom/
Click to expand...
Click to collapse
sadly, 9008 firmware need pay about 50 USD, But nobody said the package can be used still now.
CrazyMoney said:
sadly, 9008 firmware need pay about 50 USD, But nobody said the package can be used still now.
Click to expand...
Click to collapse
Bruh the custom ROM and modding community is so mid and goofy for the RM8P Literally one of the main things making me go for a Poco F5 instead
Chinese dev made MIUI rom but its only payed with alipay for like 3 dollars. I im waiting when we can pay with paypal to try it looks good.
ibestmoder said:
Chinese dev made MIUI rom but its only payed with alipay for like 3 dollars. I im waiting when we can pay with paypal to try it looks good.
Click to expand...
Click to collapse
Well yeah, but as explained/talked about here, AOSP/LineageOS has to be technically possible
I got the rom maybe extract and check it? Take out alipay security then we can try it
ibestmoder said:
I got the rom maybe extract and check it? Take out alipay security then we can try it
Click to expand...
Click to collapse
Maybe share the ROM file, then we can try finding some way to remove forced payment/crack it (No paid ROMs allowed in XDA forums) and maybe possibly clean it somewhat (Does it even have english as an option?) and we'll finally get ourselves a finally working alternative custom ROM.