First of all sorry for posting thread here in dev sector, but here audience is bigger.
I want to ask devs. Why do you make model-specific mods? Eg AndroidNow supports only D855 and the CM vs LiquidSmooth too.. And many other roms....
What about "korean" series F400SKL or others? It is possible to make multi-variants via AROMA as it did Cloudy.
So answer to me - Is it so hard for developers to bring their ROMS for more people?
P.S. As i know, the difference in models is only in kernel and modem, so why not?
I think once the bump tool is released today, this won't be a big problem.
Because people cant follow simple instructions!
17akota said:
I think once the bump tool is released today, this won't be a big problem.
Click to expand...
Click to collapse
I read the post and don't understand this completely. Does it say that you can use every LG G3 rom on every G3 model?
I believe as long as the kernel matches your device, you should be fine. You might run into problems flashing a Verizon ROM on an AT&T phone though with service and stuff though.
Okay despite you saying that you know that this post was not supposed to be in here doesn't excuse it from being in this sub-forum. Q&A would've been much better since you're asking a question and believe me when the amount of audience in here is just as same in there.
17akota said:
I believe as long as the kernel matches your device, you should be fine. You might run into problems flashing a Verizon ROM on an AT&T phone though with service and stuff though.
Click to expand...
Click to collapse
Ok, lets take G3 Android Development section.
S3V3N is a developer of AndroidNow. This ROM is stock-based, and it has awesome features, but the only model it support is D855, so it can't be installed on F400SKL or other model with different kernels and basebands. My question is - Why it support only one model? Why cant developer add AROMA and push there more kernels for more variants of G3 as it did Cloudyfa in his CloudyG3?
And there more ROMS with support of only D855 (which is G3 modification for Europe) For Example CM and LiquidSmooth
As for me, i have bought G3 when in day it was released, and that model is F400S. I think there many people who like custom ROMs but the are not able to try CM on our device because of no support
Kniazkoff said:
Ok, lets take G3 Android Development section.
S3V3N is a developer of AndroidNow. This ROM is stock-based, and it has awesome features, but the only model it support is D855, so it can't be installed on F400SKL or other model with different kernels and basebands. My question is - Why it support only one model? Why cant developer add AROMA and push there more kernels for more variants of G3 as it did Cloudyfa in his CloudyG3?
And there more ROMS with support of only D855 (which is G3 modification for Europe) For Example CM and LiquidSmooth
As for me, i have bought G3 when in day it was released, and that model is F400S. I think there many people who like custom ROMs but the are not able to try CM on our device because of no support
Click to expand...
Click to collapse
I think its because pepole without a contract are most likely to buy the D855 variant...
you cant expect a developer to maintain a rom for every variant out there, you can however learn and explore how to get it working for your variant and build it from source.
Jagdish84 said:
I think its because pepole without a contract are most likely to buy the D855 variant...
you cant expect a developer to maintain a rom for every variant out there, you can however learn and explore how to get it working for your variant and build it from source.
Click to expand...
Click to collapse
What contract are you talking about? I bought F400S in Russian LG official retailer. It was unlocked from factory. The box was sealed.
Yeap i can learn how, but i wont to become dev again, and most of people with G3 dont want to develop roms, they want to use CM or others..
I have no idea how @Cloudyfa did his patch to make his ROM work for all variants. He also helped the MIUI dev get that working on all the variants as well. Also this Bump thing is all new to me too. I'm not sure how it all works.
I have the D850 and I flashed AndroidNow when it first came out. It worked fine on my device minus a problem with in-call audio which was not a kernel problem. I believe it was a RIL problem, but whatever the problem was, Cloudyfa made that patch in his ROM to work on all variants.
I'm no dev but I've been around and maybe someday would like to get into ROM developing. I had fun theming the Galaxy SIII back in the day.
17akota said:
I have no idea how @Cloudyfa did his patch to make his ROM work for all variants. He also helped the MIUI dev get that working on all the variants as well. Also this Bump thing is all new to me too. I'm not sure how it all works.
I have the D850 and I flashed AndroidNow when it first came out. It worked fine on my device minus a problem with in-call audio which was not a kernel problem. I believe it was a RIL problem, but whatever the problem was, Cloudyfa made that patch in his ROM to work on all variants.
I'm no dev but I've been around and maybe someday would like to get into ROM developing. I had fun theming the Galaxy SIII back in the day.
Click to expand...
Click to collapse
It is not a patch. He made AROMA zip with switchable models. choosing a model will install specify kernel, modify build.prop and add some files into /lib /etc (they configure gps region, bluetooth country settings,lte gsm and wcdma bands)
Kniazkoff said:
It is not a patch. He made AROMA zip with switchable models. choosing a model will install specify kernel, modify build.prop and add some files into /lib /etc (they configure gps region, bluetooth country settings,lte gsm and wcdma bands)
Click to expand...
Click to collapse
So he got every variants kernel and managed to Bump them all so they can be flashed?
Kniazkoff said:
What contract are you talking about? I bought F400S in Russian LG official retailer. It was unlocked from factory. The box was sealed.
Yeap i can learn how, but i wont to become dev again, and most of people with G3 dont want to develop roms, they want to use CM or others..
Click to expand...
Click to collapse
I didnt say you got it under contract, I meant that the most common variant is D855 and that's why chances are that if you're a Dev you got that variant(unless you're from the US and got it under contract from one of the carriers) ... Plus, you say most people don't want to develop for the G3 but you expect development to pick up for all variants, if you gonna demand something to fit your needs you better be ready to assist.
Sent from my caseless LG G3, because I believe in myself
It's simple. You usually develop ROMs for the device that you have. Easier to debug issues for a device that you have rather than ask someone else to do so.
If you're frustrated by the lack of development for your device, PM a dev that develops ROMs for D855, ask him politely if it's possible for him to do so for your variant, and offer to maintain & debug the issues with your device. Sorry to say this but the way you're asking here in this thread comes across as rude and demanding.
Jagdish84 said:
I didnt say you got it under contract, I meant that the most common variant is D855 and that's why chances are that if you're a Dev you got that variant(unless you're from the US and got it under contract from one of the carriers) ... Plus, you say most people don't want to develop for the G3 but you expect development to pick up for all variants, if you gonna demand something to fit your needs you better be ready to assist.
Sent from my caseless LG G3, because I believe in myself
Click to expand...
Click to collapse
F400 is the first variant of G3. It was released 2 months earlier than D855.( or mb 1 month idk) so why European version received CM and other thing earlier? I cant imagine that there are no devs who bought G3 at start, i mean F400
if4ct0r said:
It's simple. You usually develop ROMs for the device that you have. Easier to debug issues for a device that you have rather than ask someone else to do so.
If you're frustrated by the lack of development for your device, PM a dev that develops ROMs for D855, ask him politely if it's possible for him to do so for your variant, and offer to maintain & debug the issues with your device. Sorry to say this but the way you're asking here in this thread comes across as rude and demanding.
Click to expand...
Click to collapse
Just search in CM AndroidNow and other for hotword "F400" and u will see that users asked for it long time ago
Asking for it does not entitle you to get it. That is not how XDA works. The devs do what they do for free, for the community, in their free time or as a hobby. It should not turn into something that they *have* to do or be difficult to maintain.
Like I said, PM a dev asking for pointers on how to port stuff for your variant or ask them if they can do so, offer help. Don't post a thread demanding & questioning them.
17akota said:
So he got every variants kernel and managed to Bump them all so they can be flashed?
Click to expand...
Click to collapse
Stock kernels do not need bump, cloudy uses stock kernels.
If anything the devs do enough by just making the ROM
It'd be cool for someone to make a porting guide. Or even better a stock installer script or an aroma installer that automatically detects the model and flashes the appropriate kernel etc. I'd take on the challenge but I'm not too confident in my skills on this stuff. First step would be diff the stock roms and compare the changes
Kniazkoff said:
It is not a patch. He made AROMA zip with switchable models. choosing a model will install specify kernel, modify build.prop and add some files into /lib /etc (they configure gps region, bluetooth country settings,lte gsm and wcdma bands)
Click to expand...
Click to collapse
Okay so if I may ask you. I have a Tmo G3 which is unlocked. I'm running Cloudyfa rom. I have at&t service. In his aroma installer there's an option for both at&t and Tmo. I chose Tmo and can't seem to get the LTE icons to show. Would I be able to flash the at&t option instead in order to get the LTE icon and not damage the phone? Sorry for the long drawn out question.
Thanks for you help.
Bert
Related
http://forum.xda-developers.com/lg-g3/general/leak-lollipop-5-0-android-l-d85519h00-t2934345
Excuse any nooby moves on my part. I am just very excited!
I want to see this ported for the d851 i keep going on xda just to see if anyone has ported this please any dev who sees this im willing to donate for the port thank you ... Peace and love from NYC ...
Patiently waiting...our bootloader is unlocked already we have the best G3 model for flashing. Really looking forward to this.
^what he said... Can't wait for it to be ported to d851.
jerseykat1 said:
^what he said... Can't wait for it to be ported to d851.
Click to expand...
Click to collapse
What is the difference between models? Is it a ton of work for the devs to port it over?
I wish I had time to learn this stuff...
I don't know how difficult it is to do, but I can't imagine it's very easy or it would be done already.
Can't wait for this to be ported...loving my AOSP at the moment though!
Port! Port! Port! Port!
I want! I want! (wish I knew dev work)
Sent from my LG-D851 using XDA Free mobile app
Porting it shouldn't require extensive testing since the release to hardware for d855 is almost identicle to ours but the kernel has to play well otherwise we will have to wait for t-mobiles official release. The real question is how easy will it be to reroot.
At this point I don't care about root, I just want Stock Lollipop on my T-mobile LG G3.
Still no lollipop
talltubatom said:
What is the difference between models? Is it a ton of work for the devs to port it over?
Click to expand...
Click to collapse
d855 is international or europe model . Spec-wise I believe they are identical.
shaido7 said:
d855 is international or europe model . Spec-wise I believe they are identical.
Click to expand...
Click to collapse
update notification tonight on tmo lg g3, but looked like same smaller file from beginning of december, 230mb where the 5.0 update is almost 600mb, maybe someone loaded wrong file into push and I get real one tomorrow
amlaria said:
update notification tonight on tmo lg g3, but looked like same smaller file from beginning of december, 230mb where the 5.0 update is almost 600mb, maybe someone loaded wrong file into push and I get real one tomorrow
Click to expand...
Click to collapse
I got the same thing the other day, but I'm still on M.
Daimugen said:
I got the same thing the other day, but I'm still on M.
Click to expand...
Click to collapse
DONT DO IT!! It breaks root and thats about all it does.
I started noticing that every time I would update to the latest version then root my D851 I would almost immediately recieve an update from Tmo. It's something built into their version of the firmware, maybe in the ever intrusive Tmo bloatware (My account etc), but it seems they can detect root and thats all these updates are for. To break your root access.
I ended up getting sick of it, installing TWRP and flashing the Unofficial CM12 build. No real problems with it so far.
Rasumgal said:
DONT DO IT!! It breaks root and thats about all it does.
I started noticing that every time I would update to the latest version then root my D851 I would almost immediately recieve an update from Tmo. It's something built into their version of the firmware, maybe in the ever intrusive Tmo bloatware (My account etc), but it seems they can detect root and thats all these updates are for. To break your root access.
I ended up getting sick of it, installing TWRP and flashing the Unofficial CM12 build. No real problems with it so far.
Click to expand...
Click to collapse
The next update I'll do will either be stock lollipop or CM12 official.
I heard someone say that" Its like that can detect you have root" I know for a fact that T-Mobile can detect that you have root.. Hell they told me over the phone that my phone is rooted. Only thing they didnt tell me was my OS version. which changes from time to time.. and yes its LP. not the stock LP that we should be getting soon. I also checked into
when will we get LP on T-Mobile and they told me, between April and Summer time.. it was supposed to be release already but some problems delayed it.
Dont forget that when Google releases the LP then LG has to get with all major Carriers and agree what goes into and what doesnt go into.. and then it gets tested by carrier for they told me 2 weeks before the OK is givin over to Carrier (T-Mobile) . Then LG wil Roll out the releases..
Me Personaly, I wont update to stock LP till I know there is a ROOT method that works.. I just want my wifi calling back. which only T-Mobile has.. so thats why I want the T-Mobile LP.. But till Root is working with stock T-Mobile LP. I will just wait......... I run ACIP 5.02 and Resurrection Remix 5.02 with MultiROM..
Rasumgal said:
DONT DO IT!! It breaks root and thats about all it does.
I started noticing that every time I would update to the latest version then root my D851 I would almost immediately recieve an update from Tmo. It's something built into their version of the firmware, maybe in the ever intrusive Tmo bloatware (My account etc), but it seems they can detect root and thats all these updates are for. To break your root access.
I ended up getting sick of it, installing TWRP and flashing the Unofficial CM12 build. No real problems with it so far.
Click to expand...
Click to collapse
It's built in my account via diagnostics to ensure that's what is causing the problems or not during troubleshooting. And no, we do not push out updates to break root. That's not our priority. We dgaf what you do with your phone, but if it's rooted it just voids warranty, that's all.
cpackar said:
It's built in my account via diagnostics to ensure that's what is causing the problems or not during troubleshooting. And no, we do not push out updates to break root. That's not our priority. We dgaf what you do with your phone, but if it's rooted it just voids warranty, that's all.
Click to expand...
Click to collapse
also, from various sources, you can't Jump! while rooted
I'm about to buy the international version of LG G4. And wondering if anyone has had any success with installing Xposed with no issues.
Also would appreciate if anyone can please direct me for the most safe steps to root the G4
Thanks in advance :good:
i got bootloop with xposed.
there is good rooting guides if you look in g4 threads.
Sent from my unlocked and rooted LG-H815
Too bad :crying:
I'm kinda obsessed using xposed & GravityBox, extremely looking forward to get xposed work on LG G4
If anyone knows the trick, please keep us posted .. and I will .. :good:
From what I recall back when I was running GravityBox on my Nexus devices, it is only supported on Nexus and AOSP-based roms. Pretty sure even if we get Xposed working on the G4, you won't be able to use GravityBox on the stock LG ROM.
je55ter said:
From what I recall back when I was running GravityBox on my Nexus devices, it is only supported on Nexus and AOSP-based roms. Pretty sure even if we get Xposed working on the G4, you won't be able to use GravityBox on the stock LG ROM.
Click to expand...
Click to collapse
Not sure if it would matter as far as this case goes, but I was able to run GravityBox on my Galaxy Note Edge (which was on a modified stock TW rom, so no AOSP-Base), Not sure why it would run on TW and not UX.....but then again, who knows....I guess the whole point is moot if we can not find a way to even get Xposed running in the first place.
masze said:
i got bootloop with xposed.
there is good rooting guides if you look in g4 threads.
Sent from my unlocked and rooted LG-H815
Click to expand...
Click to collapse
Thanks for your reply. I was reading almost all threads about rooting the G4, however, haven't yet found anything about rooting version H818. Please let me know if you have any idea about a successful rooting method for H818.
Thanks in advance ,, :good:
There's good news....and
Moe560 said:
Thanks for your reply. I was reading almost all threads about rooting the G4, however, haven't yet found anything about rooting version H818. Please let me know if you have any idea about a successful rooting method for H818.
Thanks in advance ,, :good:
Click to expand...
Click to collapse
As you know, you must unlock your boot loader before you can root your G4. Mine is the international or EU model H815 unlocked and rooted back in May. Take heart. It is easy. Key points are: a visit to the LG support site. Then can make your way to the Developer section and register to receive the bootloader unlock code. LG will try three times to dissuade you but will in the end email you the code. Once done the process is "irreversible" and will always show bootloader ulocked (on the boot screen). LG say they have listened to customers (a dig at Sammy and the i-sheep) and have started to roll out the unlock code globally. Yours may be listed already, if not it soon will be. It's been a month now so register / monitor the site. Once you unlock, you'll find step by step method of rooting your G4 here on xda. I posted one myself but thread was closed as there is one there already. Your next query will probably be a lean deodexed ROM or to install Xposed. Sadly, no news on either of those for the G4. Hopefully a bright spark will crack those soon.
Farrys said:
As you know, you must unlock your boot loader before you can root your G4. Mine is the international or EU model H815 unlocked and rooted back in May. Take heart. It is easy. Key points are: a visit to the LG support site. Then can make your way to the Developer section and register to receive the bootloader unlock code. LG will try three times to dissuade you but will in the end email you the code. Once done the process is "irreversible" and will always show bootloader ulocked (on the boot screen). LG say they have listened to customers (a dig at Sammy and the i-sheep) and have started to roll out the unlock code globally. Yours may be listed already, if not it soon will be. It's been a month now so register / monitor the site. Once you unlock, you'll find step by step method of rooting your G4 here on xda. I posted one myself but thread was closed as there is one there already. Your next query will probably be a lean deodexed ROM or to install Xposed. Sadly, no news on either of those for the G4. Hopefully a bright spark will crack those soon.
Click to expand...
Click to collapse
Thanks for the reply @Farrys still only H815 eu is supported for unlocking http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
We'll wait ..
Farrys said:
As you know, you must unlock your boot loader before you can root your G4. Mine is the international or EU model H815 unlocked and rooted back in May. Take heart. It is easy. Key points are: a visit to the LG support site. Then can make your way to the Developer section and register to receive the bootloader unlock code. LG will try three times to dissuade you but will in the end email you the code. Once done the process is "irreversible" and will always show bootloader ulocked (on the boot screen). LG say they have listened to customers (a dig at Sammy and the i-sheep) and have started to roll out the unlock code globally. Yours may be listed already, if not it soon will be. It's been a month now so register / monitor the site. Once you unlock, you'll find step by step method of rooting your G4 here on xda. I posted one myself but thread was closed as there is one there already. Your next query will probably be a lean deodexed ROM or to install Xposed. Sadly, no news on either of those for the G4. Hopefully a bright spark will crack those soon.
Click to expand...
Click to collapse
That's not accurate, you don't need to unlock the bootloader to root the device. There is root available for most variants in the dev section and none of them save the 815EU and H811 (TMo) variant have an unlocked bootloader available. The H815 you have to get unlocked via the LG support site as you mentioned and the H811 is unlocked by default from TMo.
je55ter said:
From what I recall back when I was running GravityBox on my Nexus devices, it is only supported on Nexus and AOSP-based roms. Pretty sure even if we get Xposed working on the G4, you won't be able to use GravityBox on the stock LG ROM.
Click to expand...
Click to collapse
On the G3 we had a module called G3 Tweaksbox which did a lot of the same things as GravityBox, and more, specifically designed for the G3. We can hope the same happens with the G4!
Long live XPOSED and G3 (G4) Tweaksbox!
I love lg stock roms but love to have more control of the kernel and was hoping we could get a bounty to get a great kernel dev like dorimanx or if you guys have any other great devs in mind...G4 is a great device and I'm more than willing to donate if anyone is interested...Thanks!
There is already an early stock custom kernal available. dev is working on the Cyanogenmod Rom also.
http://forum.xda-developers.com/g4/orig-development/h815-tornadorx-r1-t3179317
IIIIkoolaidIIII said:
There is already an early stock custom kernal available. dev is working on the Cyanogenmod Rom also.
http://forum.xda-developers.com/g4/orig-development/h815-tornadorx-r1-t3179317
Click to expand...
Click to collapse
I have h811 T-Mobile...nothing in the works yet afaik...hoping to find a dev to build for all unlocked models and who is willing to add support for devices that get unlock/workaround down the line
jamesd1085 said:
I have h811 T-Mobile...nothing in the works yet afaik...hoping to find a dev to build for all unlocked models and who is willing to add support for devices that get unlock/workaround down the line
Click to expand...
Click to collapse
Fair enough, I didn't know you had the H811. Though I'm sure Mythops234 will be more than willing to look at other devices once CyanogenMod is into at least a beta state. Why not send him a PM.
IIIIkoolaidIIII said:
Fair enough, I didn't know you had the H811. Though I'm sure Mythops234 will be more than willing to look at other devices once CyanogenMod is into at least a beta state. Why not send him a PM.
Click to expand...
Click to collapse
I might talk to him once cm stabilty comes...they are busy enough without me asking more of them
When I get home from Saudi Arabia I can put together a nice stock custom kernel. It was on my list of things to do, but I have been hung up on getting a deodexed rom base going. Its proving to be a major pain in the ass. 64 bit isn't being very cooperative and coupled with the weird mounts and other generally weird crap with this phone afaik everyone working on traditional zip flashable roms are running into the same issues. I suppose I can put that on the back burner and make a kernel... I wont be home for another week or 2 though.
Thread closed.
This thread is omnidirectional, please make it linear.
OP if you would like to start a new thread, please be more specific in your title and then in the OP of your thread.
Hello XDA, I have been working on an Aosp-ish nougat rom for our beloved trltetmo. It has nearly no features yet, since it's an AOSP ROM. I'm a Nexus dev, and just recently started working on the trltetmo because I bought one. I had a marshmallow rom and kernel(but tend not to release stuff to anyone to avoid drama and the eta requests).
Downloads: https://www.androidfilehost.com/?a=show&w=files&flid=111459
I have uploaded my work to GitHub: http://github.com/TrlteNougat
For now until I get my gpu back, you have to flash this kernel for MM bootloader support: https://www.androidfilehost.com/?fid=529152257862667083
Known issues:
- Camera is wonky. It's going to be difficult to fix
- The phone acts like it's a dual sim phone, no usability is sacrificed, it just shows two APN settings and the carrier on Dialer
Features:
None yet, it's AOSPish
What is being worked on:
Bluetooth
Call audio (mixer_path issues)
The kernel source is up: https://github.com/TrlteNougat/kernel_samsung_trlte/commits/n7.0
Manifest located here: https://github.com/TrlteNougat/manifest
Nice! Subscribed.
Test build
https://www.androidfilehost.com/?fid=24723757092306996
This one doesn't reboot randomly. Still has ril and Bluetooth errors. Sound doesn't work. Camera does.
I m not dev. But great to see work on 7 ...cheers to all devs...hoping for a stable one soon thx again
I'm keeping my eye on this thank you
Sent from my SM-N910T using Tapatalk
Ril is now partially working. I can send and receive texts. Calls cause a soft reboot, but shouldn't be hard to fix. Still no data connection yet, but that'll be fixed soon enough. Wifi connects but doesn't access internet for some reason. I haven't looked into that any.
Because why not
improper bootloader and in some cases modem can cause Wi-Fi to behave similar to how you have described. I'm not a TMO user but I think there should be several versions newer than OK2
if you have any desire to return to 5.1.1 or keep the option open to do it in the future, you may want to steer clear of the newest 2 or so bootloaders as they may prohibit further downgrading. if TMO is anything like Sprint, anything PE2 and older should still permit downgrades. newer versions I have not tested or seen any info on the topic.
[QRCODE][/QRCODE]ok I did a quick check and you are in fact on a 5.1.1 modem. I don't know if you've updated your bootloader but I get the feeling you would know if you have or not lol
all TMO MM firmware is newer than the Sprint firmwares (PB5, PC1, PD1, PE1, PE2) that I know to not prohibit downgrades, so you're on your own there.
if you believe the test builds to be compatible with the Sprint model, I'd be happy to help test as time allows for it
Sterist said:
[QRCODE][/QRCODE]ok I did a quick check and you are in fact on a 5.1.1 modem. I don't know if you've updated your bootloader but I get the feeling you would know if you have or not lol
all TMO MM firmware is newer than the Sprint firmwares (PB5, PC1, PD1, PE1, PE2) that I know to not prohibit downgrades, so you're on your own there.
if you believe the test builds to be compatible with the Sprint model, I'd be happy to help test as time allows for it
Click to expand...
Click to collapse
910T can be downgradable to DOK2 but not below that (unless you use work around and flash 910T2 firmware, which will allow you to go to 4.4.4 BL , and still can come back to latest) but thats a different story, regardless of that , however , you can anytime switch among DOK2 to PE3 to PG2 in any order. I think android N for 910T should be tested on EPG2 and not on DOK2 , atleast should give it a try on EPG2. I think the dev @USA-RedDragon , already must have tried all bootloaders and basebands , i m just replying to above posts.
Manan79 said:
910T can be downgradable to DOK2 but not below that (unless you use work around and flash 910T2 firmware, which will allow you to go to 4.4.4 BL , and still can come back to latest) but thats a different story, regardless of that , however , you can anytime switch among DOK2 to PE3 to PG2 in any order. I think android N for 910T should be tested on EPG2 and not on DOK2 , atleast should give it a try on EPG2. I think the dev @USA-RedDragon , already must have tried all bootloaders and basebands , i m just replying to above posts.
Click to expand...
Click to collapse
I tried EPE3 on mm but got too frustrated with the issues. So I've been weary to try it again. But you do have a point that I should try with newer bl/modem combos. I've got a mm rom compatible with epe3, so I might as well flash that. The Odin files are on my desktop staring me down
Side note, the logs point to something bring wrong wkth the code and not a bl/modem -> rom compatibility. But I could be wrong. Never hurts to try
USA-RedDragon said:
I tried EPE3 on mm but got too frustrated with the issues. So I've been weary to try it again. But you do have a point that I should try with newer bl/modem combos. I've got a mm rom compatible with epe3, so I might as well flash that. The Odin files are on my desktop staring me down
Click to expand...
Click to collapse
to make it easier ,why dont you just flash EPG2 BL and CP using odin (as opposed to entire MM rom) .and see if it fixes any of the issues with current N build.
Manan79 said:
to make it easier ,why dont you just flash EPG2 BL and CP using odin (as opposed to entire MM rom) .and see if it fixes any of the issues with current N build.
Click to expand...
Click to collapse
I'll do that. Progress is still ongoing with all this. But this week I've been busy with an Android Dev's biggest bane: a full-time job ?
USA-RedDragon said:
Side note, the logs point to something bring wrong wkth the code and not a bl/modem -> rom compatibility. But I could be wrong. Never hurts to try
Click to expand...
Click to collapse
sure ,i do understand that I do want to ask , how about xda devs who work for CM14 unofficial? i dont see much active devs on this thread, i would have thought all the note 4 devs who worked on CM13 unofficial would jump on this to help you out
Manan79 said:
sure ,i do understand that I do want to ask , how about xda devs who work for CM14 unofficial? i dont see much active devs on this thread, i would have thought all the note 4 devs who worked on CM13 unofficial would jump on this to help you out
Click to expand...
Click to collapse
Eh. I have other devs at my disposal. Most don't use XDA, and I tend to not either, but this(like any major version bump on a Samsung) is a big endeavor, so I made the thread for people to jump in if they wanted
USA-RedDragon said:
Eh. I have other devs at my disposal. Most don't use XDA, and I tend to not either, but this(like any major version bump on a Samsung) is a big endeavor, so I made the thread for people to jump in if they wanted
Click to expand...
Click to collapse
got it thx, let me know if you want me to test 910T builds, however i do need sim to be working for incoming/outgoing calls , cant live without that rest all i can test.
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