Need some help - Optimus One, P500, V General

Hey everybody, been following this forum for a while, but I eventually found the need to register and post. I have a LG Optimus One from Koodo (here in Canada). I was so excited when I heard that LG finally pushed the Gingerbread update. I decided to update and then...yeah.
I was initially thrilled. Everything seemed pretty good. Nice change in colours, felt smoother, all was well. Then I noticed that my battery was dramatically affected after the update. Pre-update, I accidentally left my phone overnight sometimes and was pleasantly surprised to see much of the juice still available. I'm not sure if this is a widespread problem, but I've read that a few other users have experienced the same thing.
So, I feel like I should just go all out and try to flash mik_os CM7 rom. Now for a tech noob like me, just reading the guides/tips is pretty intimidating. I know about the possibility of bricking, so it's putting me off until I know exactly how to execute this. Or is it not possible to flash mik_os CM7 since I upgraded to 2.3.3? I read something about basebands, but I have no idea what that means. Will I have to use the KDZ updater (again, only heard about it, never actually used it) to downgrade and then proceed? I assume I'll also have to root the phone, and have read that there are many ways to do this.
Well, that's the end of my little story. I'm just very interested in flashing the CM7 rom and just want to know how to do it precisely. If anyone can help, it'd be greatly appreciated.

from your position it looks like you'll need to downgrade to froyo to flash mik's CM.. but now AdFad666's new port of CM is available for the new baseband.. so you don't need to downgrade to enjoy CM7..
what you DO need to do is..
Root phone, Install custom recovery,flash rom.
excellent guides for all these are available here itslef.. read well before attempting these.. but not to worry.. follow the instructions to the line and you'll have no problems
http://forum.xda-developers.com/showthread.php?t=1007244

Related

[Q] Best method of flashing CM7 from stock

Hi all,
So I just picked up a Xperia Mini Pro today... pretty solid looking phone, performance is "average" w/ the stock ROM. This is my first Sony android, but I've rooted and flashed CM7 on many HTC and Samsung devices (i run a G2 and SGS myself)
Anyway, after spending the whole week reading up on this phone in XDA, i realize that there's one question that I can't seem to find any good info on.
Basically, I'm never gonna use this phone on stock ROM (that's just silly) and I'm gonna flash to CM7 like my other phones
I'm a bit confused as to which method is the more "proper" way.
What's the recommendation of anyone who has the SK17i/a?
do I use the FlashTool method (http://forum.xda-developers.com/showthread.php?p=10879507#post10879507)
or do I use the method provided in the wiki from the cyanogenmod site? (http://wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Mini_Pro:_Full_Update_Guide)
The only important steps are really: rooting, unlocked BL and install CMW ... flashing CM7 is prob the easiest step of all
I'm comfortable doing either way, both instructions seem pretty straight forward and clear-cut ....but i just wanted to know which one I should be using to make this process a bit smoother for me
I just bought this phone yesterday and love it, but it does seem to be crammed with too much rubbish. this is my first android phone. I've rooted it, but still trying to decide whether to flash to CM7 (i've had iphones before and i'm guessing CM7 is the android version of Custom Firmware) Are there any step by step guides for THIS phone on flashing to CM7 as i'm still learning about android handsets.
hi.. i am also new to SE Xperia Mini.. and i am a former Samsung Galaxy 5 user.. i used to have a a CM7 in my galaxy 5.. and flashing on a samsung phone was easy..
i'm would also want to see a step by step guide on flashing.. thanks..
so, it didn't take long for me to realize that CM7 just doesn't work that great for this particular phone
... Feel free to read up on the known issues (ie: no hardware keyboard support)
Anyhoo...I updated my firmware and flashes hybrom v8...great looking ROM
"there is no spoon"

[Q] Rooting, Flashing, Custom ROM questions from a noob!

Hi everyone,
I am new to the android world having just bought a galaxy s2, so please be gentle. I'm a previous iphone owner and always hated the restrictions apple put on their phones and dictated the way I could use my handset! I've since moved over to android and my first impressions are OMFG, how confusing is all of this!! I'm not techphobic by any means but I am struggling to piece together how the world of android works and I have spent a lot of time reading various things about ROMs, rooting, flashing, kernels etc... but I am getting more and more confused!
I recently bought a Galaxy S2 which is running a custom ICS ROM on it (resurrection remix 1.0) and also has CWM on it. Having looked at the forums i can see that another version in out (1.3 i believe) but i'm very hesitant to try a flash as i dont want to screw my phone.
The way I see it i've got two choices, either try and reset the phone to stock so that warranty etc... remains uneffected and then update to ics through kies when its available or try and install a later version of one the ics ROM's that are availabe. I was wondering to that end if you lovely people coudl give me some guidance.
If I were to reset my phone to stock how do i do this bearing in mind i am confused about
a) what kernels are in the first place and
b) which one i woudl need for my phone and will I need a usb jig for this?
c) -i need to unroot my phone to return it to stock and if so how do i do this
also:
-what is the difference between an insecure and secure kernal
-if i flash my phone to a newer version of ics can i revert back to 1.0 as at the mo apart from the odd app crashing here and there I'm not having any probs with it.
I'm reading about GAPPS and APKs and dont know what the hell these are either but they keep popping up every so often.....basically i'm confused and on the verge of a breakdown!!
Please could somebody help mw with this and massive apologies if i've posted where i shoudnt have.
Thanks in advance
Saf
If you had taken the same time took for typing here to search and read you would have learnt almost everything...
go through these stiky threads
also see my links in singnature.......read as much as possible....no other substitute for reading and learning, nobody will answer you in essays like you typed
http://forum.xda-developers.com/showthread.php?t=1544657
Appreciate what you're saying mate and thank you for taking the time to reply. I have been reading various threads over the last day or so but the problem is when something like this which is quite techinical is completely new territory you dont know where to start. Google throws up page after page of stuff that doesnt make much sense and i've searched on the forums here and read up on quite a bit but again am not sure if i've grasped it.
problem is I didnt install the custom ROM on the phone, i bought it like this and to do anything further with it i dont know if i need to go back to the original owner with more questions or can i just go ahead and start tinkering with it without knowing what software was originally on the phone? (bearing in mind that various posts state that you need certain software which is as close to the original one as possible)
Thanks anyway
Saf
this is the stage which passed by all the noobs including me, dont worry
Your strating treble will only be over when you start flashing a ROM,
cool.
ima go ahead and try and install version 1.3 of resurrestion remix! Wish me luck hehe!!
Good luck,
dont forget to follow the steps mentioned the ROM thread atleast...

[Q] Questions about flashing ICS for a friend

Hello everyone, I'm trying to do a buddy of mine a favor by upgrading his Vibrant to something a lot better (he's on stock) but I'm a bit unclear on a few things. First of all let me get out of the way that I'm a Fascinate (Verizon) owner that recently modded my own phone to run AOKP ICS Milestone 6 with great results, so I figured since he pretty much had the exact same phone I could do it for him. The problem I'm running into is the procedure I used to flash my phone doesn't seem to apply to the Vibrant (or at least what I was searching for) so I just wanted to clear up a few steps before I try to flash his phone.
He's not a very tech savvy guy, so he won't be updating ROMs on the bleeding edge or anything, he just wants his phone to run better so I figure ICZen is the way to go right, considering it's based off of what I'm using now (AOKP M6)? Everything needs to work, so that pretty much rules out any JB right now because of the GPS issues. Okay now onto the specific flashing questions:
1) This thread seems to be the go to thread for flashing the Vibrant, but it hasn't been updated since Dec '11, so would I just follow the same procedure for the newer ICS roms?
2) Here is the guide I used for my Fascinate (see section 4), which has a few extra steps that I notice are lacking for the Vibrant... namely installing cwm4 fixed for cm7 first, then installing THS Build 2, then flash over that with whatever ICS Rom you need.
3) Devil Kernel is what's considered best on my phone running AOKP M6... is that true as well for ICZen?
4) Since the Vibrant never got 2.3, what is the best modem to be using? On the Fascinate the EH03 (GB) stock modem is best, but I'm unsure what the deal is for the Vibrant since they never got an official GB update. Also along the same topic, Verizon has a code you can input that updates your PRL and improves reception... does T-Mobile have such a code or not?
I appreciate any and all input, as I want this to go as smoothly as possible. Thanks
You seem to have a pretty good grasp on what your doing.
From stock, install gingerbread bootloaders then go to recovery via volume rocker down and hold power button, until the logo. Might have to practice it a couple times.
Once in recovery click reinstall packages, might have to do it s couple of times. This installs your update.zip
From here I always perform wipes and flash a custom Froyo ROM. Maybe overkill but, only takes a second and I don't mind.
From here I flashed the latest CM9 nightly and on to Helly Bean.
Do your wipes in between flashes, and you should be fine.
I haven't ever heard about a T-Mobile code for tower updates, I think its automatic.
Well I didn't have to worry about bootloaders on my Fascinate since I was already on GB, so that's a bit new to me... but doing a quick google search I found this guide. Is that an accurate guide to follow? Alright so basically what you're saying is before I root at all I need to do this?
Also like I was saying earlier, he wants everything to work so I think Helly Bean is out of the question because of GPS, right? I was thinking ICZen looks the cleanest, with everything working nicely, and it's based on what I'm currently using on mine.
Can you clarify on why you're flashing a custom froyo rom? I won't mind to do that either, if it has any benefit.
Also, I checked his phone last night and it's on stock 2.2, not 2.1 if that makes any sort of difference. Thanks again
First root and get cwm recovery then flash bootloaders. The vibe never got an official GB, so that's why boot loaders are recommended. The guide you have is fine. Second the GPS on the vibrant has been notoriously hit or miss. I have a captivate, the GPS works great but my vibe couldn't get a lock to save my life.
Now as far as iczen or hellybean, you have to weigh the options:
Iczen is a great ROM and might have a better chance getting a GPS lock. IMO if you can get a lock with ICS you will probably get a lock with JB. But with ICS you have to be concerned with the EU bug. What's that you ask:
There has been an issue with people randomly looking at phone and a message saying encryption unsuccessful press to reset. If you press the button you have basically just locked up your internal SD card. If you don't press you MIGHT be able to recover it. There is a workaround if this happens, to use ext SD only but your friend will not like that.
I'm currently running hellybean on both of my devices and I love it. Like I said, cappy gps works great and my vibrant not so much. If you really want stable go with bionix as toast recommended or one of moped Ryder's ROMs . If you want to be wowed, go with hellybean.
There are some things you can try with it to get a GPS lock. The general consensus is turn on GPS, reboot, wait it out till you get an initial lock. After that locks will be quicker. I hope this helped in some way, if so hit thanks. As far as the guides etc you are good to go.
its peanut butter jelly(bean) time
That did help quite a bit, thank you. I have never even heard of that bug, do you know if that's Vibrant specific or can that happen on any of the others? I have been wanting to try Helly Bean on my Fascinate, but unfortunately my sdcard isn't very stable and I don't trust to flash anything until I can buy a new one. Honestly, I don't even think he cares much about the GPS, my original point was more along the lines of that I wanted to give him as much of a glitch-free experience as possible, so my fault for not being more specific. If Helly Bean is as stable as you're saying, then maybe I'll just do that instead then, especially after you explained that glitch. Also, since I don't have any Helly Bean experience myself, does it offer as much customization as AOKP? I've grown quite fond of all the little tweaks they include
Hellybean is pretty stable. When I did my vibrant I didn't have to use a boot loader I went straight to ICS then jellybean. If you want ICS then you may want to try aokp for his vibe its nice. If you end up trying aokp milestone 6 and have unknown baseband let me know and I'll link you to a linario build that should fix that
Sent from my SGH-T959 using xda app-developers app
I have a complete guide to install ICS ROMs in my signature if you feel so inclined. PM me if you need any of the files or I may just host them on my Dev-Host account. I'll be out most of the day, but I can upload them later on tonight.
When I need to go back to stock and root and flash cwm I use the AIO toolbox. I just put the rom on the internal flash and then use AIO to get cwm on it from the flash custom rom option. Then cancel the file and the phone will reboot into recovery where you install packages twice and should end up in cwm.
The EU bug has hit vibrant and captivates that I know of. It seems rare though, if you think about the number of users compared to the reported number of cases of the EU bug, its a small percentage.Hellybean doesn't have nearly as much customization but it does offer theming and some launcher/lock screen tweaks. You could always use a custom launcher. There are a few other jellybean ROMs you could try. Honestly any way you go will be better than stock!
*I forgot to tell you, you will need to Odin back to stock 2.1!
its peanut butter jelly(bean) time
Yeah.. I don't think root is actually necessary to do any of this. You'll be rooted when the process is complete however. The custom ROMs come with root access.
But to elaborate on Samsgun357's last post, if you are currently on Froyo 2.2 stock, you'll need to Odin back to stock 2.1 prior to starting, because Samsung fixed the bug that allows installation of custom recovery when they released 2.2
It's simple to do, search the forums and you'll find a guide on Odining back to JFD. That's stock Eclair. If I have time in a few I'll locate it for you and post it.
There are YouTube videos about it with links to the files as well. I think djeddie1west posted a good one with links to all files needed, if they are still working links.
Edit: http://forum.xda-developers.com/showthread.php?t=1117990
There's the link for installing GB bootloader.
Also, I am on my phone and haven't tested links, but as long as they work, near the bottom of the post you'll find the files needed to Odin the JFD files.
Eh, I just gave up and told him to go get an iPhone instead, to increase his hipster status.
Or... that's right, I'd rather be dead than own one of those ugly bricks.
You have all been extremely helpful, and I think I have more than enough to go on. I think for now I'll just throw ICZen on his phone since it's based on the rom I'm most familiar with... and when I have more experience with Helly Bean (I finally ordered a new sdcard that's on the way, so I can play with it on my own phone soon enough :good I'll just flash his again. He'll be okay with the risks mentioned so far in this post, and honestly his upgrade is coming up soon so I'm sure I'll be drooling over his S3 when that time comes.
@Woodrube That guide you made to install ICS was exactly what I was looking for, and I wish I had found it earlier so thank you for making such an excellent post.
I'll post back here with the results, thanks for all the help once again

[Q] Which ROM?

Years ago a friend installed CM7 on my Atrix and now it's pretty unstable. I would like to reinstall the ROM fresh. The question is, which ROM should I install. (He didn't backup before installing CM7)
I'm thinking it would be nice to go back to an official ROM but, there is CM10.1. I'm leary of going back to CM because the 10.1 ROM is not official and it doesn't seem there will be much improvements for CM on an Atrix 4G.
I'm leery of going to an official ROM because I see all the banter of bricking it with Gingerbread.
Suggestions?
Atrixor said:
Years ago a friend installed CM7 on my Atrix and now it's pretty unstable. I would like to reinstall the ROM fresh. The question is, which ROM should I install. (He didn't backup before installing CM7)
I'm thinking it would be nice to go back to an official ROM but, there is CM10.1. I'm leary of going back to CM because the 10.1 ROM is not official and it doesn't seem there will be much improvements for CM on an Atrix 4G.
I'm leery of going to an official ROM because I see all the banter of bricking it with Gingerbread.
Suggestions?
Click to expand...
Click to collapse
The real question is what version of android do you want to run? CM7/7.2 is the only official CM ROM. CM10.1 is not official b/c of the kernel issues, which is still being worked. Does it really matter if a ROM is official or not? No. "Doesn't seem there will be much improvements for CM on an Atrix 4G."? Really? I'm not even going to post the link, I'm just going to say go google android version history and see what CM9, 10, and 10.1 have that CM7 does not have, and then restate that noob statement. Seriously, you have no idea what you are talking about.
Multiple users, including myself, have unlocked, rooted, restored to stock, many times over the past 3 yrs. In addition, there are guides readily available to help you through the process of preparing your device for custom ROMs. So the concern of bricking is a non issue unless you don't know what you're doing. Banter of bricking it only exists if you flash the incorrect sbf. Its not that hard. Sit down, read guides, ask questions as needed.
Let me be the first to admit that I am a noob and have no idea what I'm doing because this is my first foray into the world of smart phones (we all have to learn somewhere).
I went ahead and put CM10.1 on there and after adding the fixed gapp package it seems to be working fine.
Does anyone have a working link to a gingerbread ROM that works for an AT&T Atrix 4G? The links on this tread are dead: http://forum.xda-developers.com/showthread.php?t=1163342

Unstable WiFi on LG V30

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!!

Categories

Resources