Hi all, I'm enjoying reading lots in this forum in order to learn how to unleash my S3. One massive thank you to all who make this community such a great and rich resource. Thanks!
After reading a bunch, I took the XDA plunge. Here's what I've recently done (maybe this will help someone who's considering taking the plunge too. I was surprised at how easy everything was). I rooted my i9300 by flashing CF-AutoRoot via Odin. I then downloaded GooManager from the Market. It installed an open recovery script for me, TWRP. Next, I rebooted to TWRP recovery mode and did a backup and then a factory reset. I flashed temasek's build (v20) of Android 4.3/10.2 with the latest gapps zip (20130813). Then came the moment of truth. I was nervous when my phone took a bit longer to boot. The sweet Cyanogenmod logo just kept swirling. Finally, it booted and I was in love.
I have just a few questions about my phone now.
First, is the TWRP backup I did adequate to get me out of serious trouble if something goes wrong flashing updates? The backup ended up being over 2gb!
Secondly, have I done anything to the kernel? If not, should I?
Thirdly, have I done all that rooting and custom roms have to offer? Do I now just update my rom when new builds come out and continue enjoying my phone? If so, that's great. Just wondering what if anything I could do next, apart from trying other custom roms.
Lastly, what's the proper way to get help troubleshooting glitches/bug with the custom rom I'm using since I'm not yet able to post in its development forum thread? For example, my bluetooth won't turn off and in some apps the screen flickers or doesn't seem to render the window properly.
Thanks in advance.
oceo said:
Hi all, I'm enjoying reading lots in this forum in order to learn how to unleash my S3. One massive thank you to all who make this community such a great and rich resource. Thanks!
After reading a bunch, I took the XDA plunge. Here's what I've recently done (maybe this well help someone who's considering taking the plunge too). I rooted my i9300 by flashing CF-AutoRoot via Odin. I then downloaded GooManager from the Market. It installed an open recovery script for me, TWRP. Next, I rebooted to TWRP recovery mode and did a backup and then a factory reset. I flashed temasek's build (v20) of Android 4.3/10.2 with the latest gapps zip (20130813). Then came the moment of truth. I was nervous when my phone took a bit longer to boot. The sweet Cyanogenmod logo just kept swirling. Finally, it booted and I was in love.
I have just a few questions about my phone now.
First, is the TWRP backup I did adequate to get me out of serious trouble if something goes wrong flashing updates? The backup ended up being over 2gb!
Secondly, have I done anything to the kernel? If not, should I?
Thirdly, have I done all that rooting and custom roms have to offer? Do I now just update my rom when new builds come out and continue enjoying my phone? If so, that's great. Just wondering what if anything I could do next, apart from trying other custom roms.
Lastly, what's the proper way to get help troubleshooting glitches/bug with the custom rom I'm using since I'm not yet able to post in its development forum thread? For example, my bluetooth won't turn off and in some apps the screen flickers or doesn't seem to render the window properly.
Thanks in advance.
Click to expand...
Click to collapse
1. A backup is always adequate on almost all situations and that size is acceptable since most of my backups are around 1.41 gb but I recommend that you also backup your efs since it's one of the most important things to backup on our devices. More info here: http://forum.xda-developers.com/showthread.php?t=1308546
2. As far as I know any cyanogenmod based firmware installs it's own custom kernel however this is highly reversible as soon as you flash a stock firmware again.
3. Well the possibility of having a rooted phone are endless. In xda you'll find vast amount of tweaks, roms, kernels etc that you can flash on your device. Even I still keep on flashing things (with precautions of course) whenever i find something interesting.
4. Until you can post that thread just keep posting your question here in the Q & A but search the topic you have in mind first since it's most likely been asked before, just to keep the forum clean as much as possible.
oceo said:
Hi all, I'm enjoying reading lots in this forum in order to learn how to unleash my S3. One massive thank you to all who make this community such a great and rich resource. Thanks!
After reading a bunch, I took the XDA plunge. Here's what I've recently done (maybe this will help someone who's considering taking the plunge too. I was surprised at how easy everything was). I
I have just a few questions about my phone now.
First, is the TWRP backup I did adequate to get me out of serious trouble if something goes wrong flashing updates? The backup ended up being over 2gb!
No its not It has note backed up EFS .
Secondly, have I done anything to the kernel? If not, should I?
Your choice .
Thirdly, have I done all that rooting and custom roms have to offer? Do I now just update my rom when new builds come out and continue enjoying my phone? If so, that's great. Just wondering what if anything I could do next, apart from trying other custom roms.
Your choice as to try other roms or mods .
Lastly, what's the proper way to get help troubleshooting glitches/bug with the custom rom I'm using since I'm not yet able to post in its development forum thread? For example, my bluetooth won't turn off and in some apps the screen flickers or doesn't seem to render the window properly.
Some roms have a Q&A thread or discussion thread . Usually problems are posted in the rom thread .
Click to expand...
Click to collapse
Thanks for the replies. I booted into recovery and used TWRP to do an EFS backup. Super easy.
I've been trying to wrap my head around rooting and/or installing CM11 on my SGS2 i9100g for a couple of days. The main problem is that whatever is out there (and in these threads) are confusing for someone just starting.
For example, "First time installing CyanogenMod 11 to your Galaxy SII G" (which means probably this is someone like me, still running stock unrooted, and possibly doesn't have a clue)
- Make sure you're running a proper working ClockworkMod-Recovery (not asking to use the kernel, but flash it and use the CWM in it to flash CM)
- Boot into Recovery
- Flash CM11.0 zip from internal SDCard
- Flash GApps zip from internal SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Click to expand...
Click to collapse
I have close to no idea what this all means. I've tried the CM Installer - not available for i9100g. I tried looking up how to backup my nandroid, just in case: CWR and TWRP - but neither have recoveries for i9100g. I've been trying to maybe even be risky and just install CM11, but I'm even having trouble with that. I've tried looking up stuff on Google, only to learn that i9100g is totally different than i9100.
Can someone point me in the right direction, please?
Tried the official guide yet?
oroboros74 said:
I've been trying to wrap my head around rooting and/or installing CM11 on my SGS2 i9100g for a couple of days. The main problem is that whatever is out there (and in these threads) are confusing for someone just starting.
For example, "First time installing CyanogenMod 11 to your Galaxy SII G" (which means probably this is someone like me, still running stock unrooted, and possibly doesn't have a clue)
I have close to no idea what this all means. I've tried the CM Installer - not available for i9100g. I tried looking up how to backup my nandroid, just in case: CWR and TWRP - but neither have recoveries for i9100g. I've been trying to maybe even be risky and just install CM11, but I'm even having trouble with that. I've tried looking up stuff on Google, only to learn that i9100g is totally different than i9100.
Can someone point me in the right direction, please?
Click to expand...
Click to collapse
Have you tried following the official guide from the cyanogenmod team How to install CyanogenMod on the I9100g?? I was a first time newbie like you when i installed 10.1.3 on my S2, but after some trying i got it to work with this guide. The guide is specially made for newbies so every step is explained and if you don't understand something google usually has the answer. If you still need help just say so and I'll do my best to help
Yeah, actually I have. Got stuck with Heimdall Suite, and just now trying to get ClockworkMod Recovery running.
CWM for i9100g
SgtDubKing said:
If you still need help just say so and I'll do my best to help
Click to expand...
Click to collapse
CWM doesn't have a version for the i9100g, so I'm not sure what I need to do there. If you have any suggestions that would be great.
oroboros74 said:
CWM doesn't have a version for the i9100g, so I'm not sure what I need to do there. If you have any suggestions that would be great.
Click to expand...
Click to collapse
Like I said just follow the guide from the CM team, everything is there! Since I'm new on here I suddenly can't post outside links but just look at the tutorial I posted before and then look at th 2. point. Afterwards just follow the official CM tutorial step by step and nothing can go wrong!
Thanks for this. Actually I'm still having problems, specifically getting a status error 7 described here (but please reply here if you have any insights).
This is getting to be a commonly asked question these days... and tbh a little reading/searching WOULD have answered it for you....
The version of CWM you are trying to flash CM11 with is wrong......
KitKat based roms need CWM 6.0.4.5 or newer......
The CWM I used to flash to KK was 6.0.4.7 and was linked to in the thread where I got the ROM......
So as I said, a little reading would have answered this for you.....
My wife says I'm a phone geek....She's probably right
keithross39 said:
This is getting to be a commonly asked question these days... and tbh a little reading/searching WOULD have answered it for you....
The version of CWM you are trying to flash CM11 with is wrong......
KitKat based roms need CWM 6.0.4.5 or newer......
The CWM I used to flash to KK was 6.0.4.7 and was linked to in the thread where I got the ROM......
So as I said, a little reading would have answered this for you.....
Click to expand...
Click to collapse
You're absolutely right about reading, but the problem is the information is never all in one place!
That is why I wanted to create a thread like this on: where an absolute beginner might find all the relevant and up to date information in one place rather than having to weed through pages of threads, downloading wrong CWM versions or whatever just to find out it's the wrong version.
In my case, first I learned that I even needed CWM. Ok, (and not to mention figuring out what it is). Then I try to find the version I find compatible with my device. Ok. Then I read somewhere to use Odin to flash it. Done. Then somewhere I else I read not to use Odin, and to flash it via recovery. So I have to figure out how to do that next. Only after some 5-6 more steps do I learn from someone like yourself that the version I'm trying to use is wrong. All the relevant information is so fragmented online, hence the necessity to make things easier for absolute beginners (which would also avoid questions and answers like the ones in this thread).
I don't think the problem for a lot of beginners is not reading, but not knowing where to find what they're supposed to read. I hope you see my point...
oroboros74 said:
I don't think the problem for a lot of beginners is not reading, but not knowing where to find what they're supposed to read
Click to expand...
Click to collapse
Sorry, but you're wrong. That is absolutely the problem for 99% of people who come here. They can't be bothered searching/reading & learning 'under their own steam' (so they understand things in their own way, rather than be fed a bunch of steps by someone else they don't understand). People seem to have this attitude that modding your phone without learning first is easy & risk free. It isn't. I've seen thousands of people on here like this end up with busted (permanently/requiring a lot of money to fix in many cases) phones over the past 2.5 yrs. And these people then cry they don't have a working phone. And it's almost always their own fault.
We already have countless guides/stickies/etc on here made by people with the idea that others will refer to these rather than post the same questions over & over & over. These are easily found with a minimum of effort. Just as the answers to random questions not necessarily covered in detail in these threads are easily found with a minimum of effort. Unique questions stopped being asked here a few months after this phone was released, every question that gets asked here has already been asked & answered many many times.
And guess what ?
People still post the same questions over & over & over. Why ? Because they're either lazy & 'want it now' (as opposed to taking the time to learn for themselves) or because they're unable to do something as basic as an effective internet search.
BTW, I'm not necessarily saying you're one of these people, I'm just telling you how things are around here based on my experiences, and I'd be very surprised if anyone who has been here for any reasonable amount of time offers an opposing view with regard to this.
So...By all means, create your 'thread like this one: where an absolute beginner might find all the relevant and up to date information in one place', but understand we already have dozens and dozens of these, and yours will end up like the rest; ignored by 99% of people who come here.
MistahBungle said:
So...By all means, create your 'thread like this one: where an absolute beginner might find all the relevant and up to date information in one place', but understand we already have dozens and dozens of these, and yours will end up like the rest; ignored by 99% of people who come here.
Click to expand...
Click to collapse
So, for the most part I started off with not even a clear idea of what the difference between rooting and flashing a ROM was, and I was able to finally install CM11 - but it took me days with dozens of various errors and such. But I did it.
I'm a firm believer of documenting for myself and if useful also for others, so I have written a small beginner's guide... written by a successful (?) beginner.
The only problem is I'd love for someone who's not a beginner to look it over to make sure it is in fact 100% correct before I post it - If there are errors, I don't want others to rely on that information. If I post it here, would you think you'd be able to give your input?
Of course Put it up.
Hi All,
Had my Verizon G3 for a bit now and everything was grand.... pre-lollipop. Post-Lollipop I've been stuck with the no notifications while on WiFi bug and for someone who spends literally 98% of my time on either my home or work WiFi this has simply become untenable for me. I'd like to root and go to, preferably, a Lollipop ROM that is not plagued by the same issues, or if I have to go back to KitKat then a ROM based on that (or perhaps there is a non-rooted solution here?).
All these things said, I've done the root/custom ROM thing back in the days of my Droid Incredible and honestly found it quite off putting to have to constantly keep up to date with ROM updates / Kernel updates / Radio updates, etc. and a lot of those even requiring wiping the phone.
My question to you fine folks is, has the game changed a bit to be a bit more friendly to like a kind of all-in-one here is your ROM/everything package, install it and get going type deal? Or is that still a pipe dream?
I appreciate that there are some steps involved prior to the installing of the ROM and I'm not opposed to those at all, I'm more worried about the nightmarish endless cycle of updates that require wipes / resets / etc. in order to fix the myriad of bugs that used to pop their heads up. I simply just want a ROM to get me through the next year or so until I can move along - and *gasp* allow me to get updates while on WiFi while having the core of the phone still functional.
Perhaps my concerns are those of days past, so please forgive my ignorance.
Any info on the topic and possible ROMs to look into (I was looking at Resurrection Remix) would be much appreciated.
Thanks! :good:
scrdy said:
Hi All,
Had my Verizon G3 for a bit now and everything was grand.... pre-lollipop. Post-Lollipop I've been stuck with the no notifications while on WiFi bug and for someone who spends literally 98% of my time on either my home or work WiFi this has simply become untenable for me. I'd like to root and go to, preferably, a Lollipop ROM that is not plagued by the same issues, or if I have to go back to KitKat then a ROM based on that (or perhaps there is a non-rooted solution here?).
All these things said, I've done the root/custom ROM thing back in the days of my Droid Incredible and honestly found it quite off putting to have to constantly keep up to date with ROM updates / Kernel updates / Radio updates, etc. and a lot of those even requiring wiping the phone.
My question to you fine folks is, has the game changed a bit to be a bit more friendly to like a kind of all-in-one here is your ROM/everything package, install it and get going type deal? Or is that still a pipe dream?
I appreciate that there are some steps involved prior to the installing of the ROM and I'm not opposed to those at all, I'm more worried about the nightmarish endless cycle of updates that require wipes / resets / etc. in order to fix the myriad of bugs that used to pop their heads up. I simply just want a ROM to get me through the next year or so until I can move along - and *gasp* allow me to get updates while on WiFi while having the core of the phone still functional.
Perhaps my concerns are those of days past, so please forgive my ignorance.
Any info on the topic and possible ROMs to look into (I was looking at Resurrection Remix) would be much appreciated.
Thanks! :good:
Click to expand...
Click to collapse
At this point, most any ROM you install will require updating. There are really no ROMs that are completely trouble free.
That said, running stock rooted may be your best choice. Rooting stock will allow you the option to block OTA updates. With root you will also be able to remove any pesky apps you do not require from LG.
Thanks for your insight. Perhaps I'll look at rooting and running a stock KitKat based ROM. If you could possibly point me in the direction of finding stock KitKat ROMs to flash to it would be much appreciated.
(sorry for posting in the wrong forum the first time)
Thanks
Jasmine 4.0 is a good 4.4 ROM. It can be found in the 7.0 thread. Just look in the first few posts. Sky dragon is also good.
Don't most roms have OTA's built in anymore? I had roms on my S4 and never had to worry, I would update and be fine, 0 wipes updating roms (Unless I was changing roms completely) and even then I have everything back up regularly so there is no hassle getting it all back.
Illogi.xbone said:
Don't most roms have OTA's built in anymore? I had roms on my S4 and never had to worry, I would update and be fine, 0 wipes updating roms (Unless I was changing roms completely) and even then I have everything back up regularly so there is no hassle getting it all back.
Click to expand...
Click to collapse
I know some of the custom CM12 and CM12.1-based ROMs I've tried have a potentially working OTA method built into the ROM. For various reasons they're not all necessarily implemented just yet, though - probably because there's just too many constant updates to the source code to make OTAs realistic.
roirraW "edor" ehT said:
I know some of the custom CM12 and CM12.1-based ROMs I've tried have a potentially working OTA method built into the ROM. For various reasons they're not all necessarily implemented just yet, though - probably because there's just too many constant updates to the source code to make OTAs realistic.
Click to expand...
Click to collapse
Very true. I do know though that CM does have OTAs. I think another part is that most CM 12 and 12.1 based roms don't change the source for the update. So you won't get any since it is no longer a CM rom and it isn't looking for the one you are using.
Stay off the nightly train and you won't have to update much at all. A dirty flash every couple of months, topped with some Gapps. I get notifications on wifi all the time. Only stock ROM tries to force you to update anyway.
Hi,
so I am having issues with the Wifi on my, recently acquired, LG V30.
I have got a strange model, L-01K, from Japanese provider DOCOMO.
I have unrooted / flashed .. currently running Havoc 3.11 on Android 10.
The wifi often loses connection/signal and in order to restore requires a complete device reboot.
Looking for some help.
Regards,
H.
haevaristo said:
Hi,
so I am having issues with the Wifi on my, recently acquired, LG V30.
I have got a strange model, L-01K, from Japanese provider DOCOMO.
I have unrooted / flashed .. currently running Havoc 3.11 on Android 10.
The wifi often loses connection/signal and in order to restore requires a complete device reboot.
Looking for some help.
Regards,
H.
Click to expand...
Click to collapse
Check your network stability? Don't use Havoc?
ldeveraux said:
Check your network stability? Don't use Havoc?
Click to expand...
Click to collapse
Is this a joke ?
Not really a joke... did the phone work fine on a stock ROM? You never told us what you came from.
How did you get to Havoc 10? As far as I've seen, Pie ROMs often have issues after install... I can't imagine 10-roms to be any better. Did you try any of the fixes mentioned in the ROM threads instead of just asking here? Sounds like it's probably ROM specific...
Well, is it my first custom, so I have no past experience and I don't know if this is specific to the ROM or the firmware drivers, or etc... hence I am asking around here for some support.
I assumed it was clear where I cam from, I came from stock. I only had the phone stock for a short period so I do not know if it was better or not before flashing. The phone was trully horrible with all the Japanese software crap on it.
I think I saw somewhere that this phone is known to have crappy drivers from LG.
haevaristo said:
Well, is it my first custom, so I have no past experience and I don't know if this is specific to the ROM or the firmware drivers, or etc... hence I am asking around here for some support.
I assumed it was clear where I cam from, I came from stock. I only had the phone stock for a short period so I do not know if it was better or not before flashing. The phone was trully horrible with all the Japanese software crap on it.
I think I saw somewhere that this phone is known to have crappy drivers from LG.
Click to expand...
Click to collapse
You also don't have a model number I've ever seen before, nor is it mentioned in the WTF thread. We have no clue what you installed here or how you did it, so I would suggest flashing one of the stock ROMs through TWRP if that's your bag. The Havoc ROM used in this forum is v3.9, again don't know how you got 3.11
Perhaps its not 3.11 ... I got it from the V30 Telegram group ... the zip file is "Havoc-OS-v3.11-20201128-joan-Unofficial.zip", I cannot seem to find the running software version, so I dont know how to check ... I am also trying to get some help there but I thought it wouldn't hurt to ask here as well.
are you rooted and or unlocked bootloader?
Also I've never heard of there being an issue with WIFI on this device.
Yes. TWRP installed as well
You say you came from stock, but WHAT stock? Oreo? Pie? US998? Something else? All this matters. You can't just slap a ROM on without having the rest of the stuff prepared on this phone.
As others mentioned, the model number doesn't make sense to us, so it could be some weird stock ROM that is not compatible with Havoc (or other custom ROMs). Even for many of these, you need to start with a known stock ROM, so that the proper blobs (binaries) are present as well as the partition layout in the phone. As you don't seem to know what it was (eg US998 is preferred) then I'd recommend you start there and then move forward. This means Frankensteining to US998, then moving forward.
Of course, given your weird model number, this may not be advised either... but if you want to try that's where I'd start.
OK.
So, phone came with stock Docomo android 8. Dont know too many details as I didnt kept it long.
Then I had some discussions on telegram group, where people advised me to unroot the phone, and install TWRP. It was mostly same as described in the thread for the LGv30 here in the forums.
I had to install a pre 2018 ROM version, using samsungs tools.
I don't recall anymore all the details order i did things from this on, I followed the steps as advised ... but I had to flash a V300 to H930 ROM. I also remember that an important step in the flashing process was not to flash modem, xbl and xbl2. So I did skip those.
Then initially I rooted Revolution Remix android 9.0, from stock android 10.0 ... by mistake, then I reverted back and I installed Havox android 10.0 instead.
The stock filename was "H93020d_00_OPEN_EU_OP_0326.kdz" and "V300_to_H93031a_converter.zip".
Edit: perhaps it wasnt Android 8 but rather 9 as someone corrected, this phone did not shipped with android 8. As mentioned, I did not keep the phone stock for long as it was literally unsuable with all the Japanese software, so I have not paid too much attention.
haevaristo said:
OK.
So, phone came with stock Docomo android 8. Dont know too many details as I didnt kept it long.
Then I had some discussions on telegram group, where people advised me to unroot the phone, and install TWRP. It was mostly same as described in the thread for the LGv30 here in the forums.
I had to install a pre 2018 ROM version, using samsungs tools.
I don't recall anymore all the details order i did things from this on, I followed the steps as advised ... but I had to flash a V300 to H930 ROM. I also remember that an important step in the flashing process was not to flash modem, xbl and xbl2. So I did skip those.
Then initially I rooted Revolution Remix android 9.0, from stock android 10.0 ... by mistake, then I reverted back and I installed Havox android 10.0 instead.
The stock filename was "H93020d_00_OPEN_EU_OP_0326.kdz" and "V300_to_H93031a_converter.zip".
Click to expand...
Click to collapse
You're ostensibly trying to combine 2 tutorials and forums to fix your problem. My guess is that flashing all those random ROMs, unrooting to install TWRP (?!?!), and using a Samsung tool definitely were not the right move. I'd advise against doing anything else unless @ChazzMatt gives his blessing, but he's away for a bit. Either that or ask for your Telegram friends to fix what they broke.
Also, wtf is docomo? The V30 did not come stock with Android 8.
ldeveraux said:
You're ostensibly trying to combine 2 tutorials and forums to fix your problem. My guess is that flashing all those random ROMs, unrooting to install TWRP (?!?!), and using a Samsung tool definitely were not the right move. I'd advise against doing anything else unless @ChazzMatt gives his blessing, but he's away for a bit. Either that or ask for your Telegram friends to fix what they broke.
Also, wtf is docomo? The V30 did not come stock with Android 8.
Click to expand...
Click to collapse
If you had read my earlier posts, I explain who is docomo and why I have such a weird model.
They are not my 'Telegram friends' but a community of people who use the LG V30. From what I gather it seems several of them are very active in ROMs, fixes and also part of the XDA forums here. They continue trying to help me however I though it would not hurt to also ask here in parallel ... it is also far easier for someone who later may face the same issues, to benefit from the solution if they can find this thread. Perhaps it was a mistake, this reminds me why I dont really miss much using forums ...
Using the LG tool was definitely the right move as written everywhere in the forums here and advised by anyone you ask to directly. As a first step, you need to break the encryption/security on the phone and you can only do that by reverting to an older version, preJuly 2018, where a known exploit exists. And guess what, until you root the phone, you can only do that by using a tool developed by LG.
And yes, I am definitely trying to combine several tutorials as there simply is no single tutorial or source of information.There are also no instructions, or even knowledge, for my model on the forums, and since the information is vague, outdated or incomplete on the different threads, you simply have no choice other than combining it. I followed the instructions as advised by my 'Telegram friends' considering it was clear I had to Frankenstein to something anyhow and the information they gave me, It all made sense, when compared to the forums information and according to the rationalle that they gave. So I took the risk. It worked without me bricking my phone, so I consider that a success.
It was definitely not 'random ROMs', if you go into the XDA section on LGv30 it is clearly explained why you need each of those and how. Its only the specifics, and versions, for my case that is not clear.
Seriously dude, you obviously have not enough knowledge nor interest in helping, .. so why don't you do me a favor, ignore this thread and go spend your time somewhere else and let others who can actually help reply... thanks, seriously!
Oh OK, no problem. Hope you and the other user who bothered replying twice can fix your cockup. With the 0 Likes and 2 weeks on XDA, I'm sure you'll solve it immediately.
... another really helpfull post, you really never disappoint ...
You really need to be far more clear in what you are doing or did. Don't blame the other users for your mistakes, nor should you complain to them when they're trying to help you with limited info. If you want help, you need to give a LOT more info. And you did, indeed, flash multiple different custom ROMs, which is a recipe for trouble.
Your terminology is also confusing, as you keep saying "unroot" and then install TWRP. You need to unlock the bootloader to install TWRP, maybe that's what you mean. Unrooting is a very different operation. You need to be precise in what you are asking for help with, otherwise you'll get bad info from anyone. Know the terms and use them properly, otherwise we can't help you... bad info will always lead to trouble.
Bottom line, as far as I know, there's only one way to do this right on the V30, which we can only assume you have. If you want to proceed, then you need to focus on one process and not try to mix with every other person's idea of what's right. Chazz has been great on this, and has provided detailed info... follow that.
Again, I won't tell you to do this because I don't want you to blame me if you brick the phone. So, if you want to proceed, you do so at your own risk. That said, I would start by getting to US998 stock ROM via KDZ. Follow the Frankenstein thread hereon XDA to see how to get there first. Once there, check to see that the phone operates properly - it should. If it doesn't then stop jumping around and fix that first.
Once all is good on that stock ROM, follow the WTF thread to install TWRP again (KDZ will remove it), with the version mentioned there (there may be newer versions, but you need to stick to what's detailed there to prevent problems, as those are the ones that are tested and known to work). Once you get that done, again, make sure the phone is working properly... then you can consider going to a custom ROM.
If you decide to move ahead, then you need to read the requirements of the custom ROM carefully. Most PIE ROMs, for example, require the PIE blobs, so you need to get to a stock PIE ROM as prescribed before going to a custom ROM. I don't know what the specifics are for 10-ROMs, so you'll have to see what's possible and how it's done based on that ROM's thread.
Well, I am not blaming anyone for my mistakes nor am I complaining to anyone trying to help me, you've been really helpful so far, not only giving ideas on what could be done but as well trying to teach and correct me, and I haven't complained about it.
However, the other guy is literally just patronizing.
Even for me who is new to this, I can clearly see by his comments that he doesn't know what he is talking about, this device in particular, and he even didn't bother to read Chad's thread to try and understand the typical, normal, process.
Just feel free to read again everything that I posted and everything that he posted, 'helping' me, its all registered above.
As for your points you are right, I am trying my best to understand all the details, but as you can notice I have literally just registered here in the forums and this is in fact my first attempt at customizing an android phone ROM.
I have initially, wrongly assumed, that the information I provided was enough and I expected this to be a more common issue that someone with experience could quickly point me to the problem or what I did wrong. And yes, my terminology is wrong, nothing I can do about that at the moment. The posts and information are literally full of jargon, abreviations, code names and sometimes spread over multiple replies or even different threads, this is not for the faint of heart and anyone new will always struggle to understand it all, no matter how smart they are, ... I am literally doing my best to try and catch up as quickly as possible.
So, wherever you read 'unroot' earlier, just replace with "unlock bootloader". As far as I understood it, and as I recall all the things that I have done, I have literally followed the process outlined in Chad's post here in XDA ... I have however frankensteined using the V300 to H930 patch, also according to instructions outlined here (I'm not sure at this moment, if that is also a post by Chad) as per the advice I received in the Telegram group. BTW, I have looked into the telegram group and Chad is also part of it, though he has not been active in the past days, so its not just a random group of people as pointed out earlier.
Anyway .. as far as I was explained, this device requires you to first flash A9 before going straight to A10, otherwise there are some 'blobs' issues with it, i dont really understand the details. During the process of discussion in the chat group, there was some miss understanding and I ended up going straight to A10 and then I installed LineageOS. Later when we noticed this, I tried to correct this by then going back again to A9 and then A10 and then finally I installed Havoc instead of going back to LOS.
So there was some mix up there, and I mentioned this not to blame anyone but just because I thought this could potentially be a source of the problems I am facing and a hint at the potential solution.
Thank you for your suggestion, I am literally half way in the process of sort of doing what you suggest. I am now back to stock A9 and see if the WiFi behaves better. I did flashed stock via TWRP, not KDZ. So I did not went all the back as you suggest. If this proves unsuccessful I might do that.
Not that he/she/they needs my defense, but ldeveraux is a senior member (more-so than me) and has tons of knowledge on this device, in my experience. That's all I want to say about that.
So it sounds like the problem was jumping to A10 from A9. Also, using instructions from one ROM to end up jumping to another. Each ROM has its needs/requirements, so you can't really do that. Also, at least on this phone, going between Android levels is somewhat tricky, so you can't just jump around from what I've read.
Yes, there can be some jargon and such. Chazz's thread (post 193) explains most, if not all, of that, but if you're missing something I strongly recommend reading MUCH more, rather than just moving forward. It is a very long thread, but it's very important you read through ALL of it, and understand it before moving forward. Then read it again. Don't read it on a phone/device - use a computer because browsers and apps have a bad habit of truncating the message. These are Chazz's recommendations as well, for good reason (and also at the top of this thread). I did a TON of reading before I did my phone unlocking/rooting, and with that thread alone, so I have read it MANY times myself (well, at least the older revision when I did my hacking) and I didn't have to ask questions... so I know the answers can be found.
US998 is the best "foundation" to start with for various reasons. Fact is, US998 should work on pretty much any carrier to start with, so it's a great foundation for that reason too. That's why I suggest starting there to be sure you have a good, working basis.
I have read that if you go to A9 or A10, going to another version may require going all the way back to Nougat first. You may need to do that now, if you want to get back to a stable US998 to begin with. The Pie/10 threads probably have info on this... I haven't read them up myself as I don't want to bother. I have stuck with Oreo because it does everything you need anyway... I see no advantage to Pie or 10. I believe Chazz has also stayed on Oreo for this reason.
Senior or no senior, he should just not patronize people. He has clearly the option to ignore if he doesn't feel like helping .. I have even politely asked him to do so ... but instead he decided to come back and patronize further ...
I rest my case...
OK. So, I am still in the process of finalizing everything, but I think it is safe to say that for the L-01K models, the US998 is the safe way to go.
Make a backup of your modem partition, then do the Frankenstein to US998 then once you are done, you can restore you original modem partition and everything should work fine!!