Related
I have read so many threads about Nougat that I have gotten myself a bit confused, I think.
I am running an XT1644 in the US on the Verizon network. My device has an unlocked bootlader and is running stock software, albeit rooted (i like adaway), build number MNPJ24.139-48.
I am quite interested in trying out some of the Nougat-based ROMS, and each of them suggest flashing the soak test first. As I read the threads for the soak test, they seem to suggest that they are all for India or variants other than mine.
At the risk of making myself out to be an idiot, I'd like some clarification/confirmation as to how I can get the correct soak test for my variant. I have no issue with following directions, however, the sheer amount of directions and variations for this model just make me want to be extra cautious before flashing.
Thanks
Don't do it. The soak test was not for our models and it can have issues like missing IEMI or WiFi. Verizon being CDMA as opposed to GSM, you can get in even worse problems.
Ah, and once you flash the N bootloader, you can't go back to the MM one. Reverting to MM will be incomplete and with possible issues. Some people report success, some lost their radio.
You have the stock firmware, there are also available .49 and .64 versions. I have rooted too my G4 Plus and didn't receive the OTA updates anymore.
SoNic67 said:
Don't do it. The soak test was not for our models and it can have issues like missing IEMI or WiFi. Verizon being CDMA as opposed to GSM, you can get in even worse problems.
Ah, and once you flash the N bootloader, you can't go back to the MM one. Reverting to MM will be incomplete and with possible issues. Some people report success, some lost their radio.
You have the stock firmware, there are also available .49 and .64 versions. I have rooted too my G4 Plus and didn't receive the OTA updates anymore.
Click to expand...
Click to collapse
Thank you. This is what I was thinking, but the "tinkering" side of me was itching and I needed the voice of reason to help solidify the decision to wait
The .64 update for the MM works fine on my phone, but I am on ATT network (GSM) so... Idk for Verizon.
myk.robinson said:
Thank you. This is what I was thinking, but the "tinkering" side of me was itching and I needed the voice of reason to help solidify the decision to wait
Click to expand...
Click to collapse
I have the XT1644 on T-Mobile and I'm using a 7.1 ROM. But I never updated my bootloader from MM I just flashed CM 14 and everything still works. The only minor issue I've come across is that it will only allow me to set 1 fingerprint. However, it says every fingerprint fails but I'm still able to use them to unlock the device. So it's apparently just a weird bug. My advice, make a good backup and try either beanstalk 7.1, Xperience 7.1 {my current ROM} Or really any of the others. I've flashed all of them and haven't had any issues. And now there's dual boot so you can always keep one MM ROM and one N ROM on your phone.
---------- Post added at 02:32 AM ---------- Previous post was at 02:30 AM ----------
I have the XT1644 on T-Mobile and I'm using a 7.1 ROM. But I never updated my bootloader from MM I just flashed CM 14 and everything still works. The only minor issue I've come across is that it will only allow me to set 1 fingerprint. However, it says every fingerprint fails but I'm still able to use them to unlock the device. So it's apparently just a weird bug. My advice, make a good backup and try either beanstalk 7.1, Xperience 7.1 {my current ROM} Or really any of the others. I've flashed all of them and haven't had any issues. And now there's dual boot so you can always keep one MM ROM and one N ROM on your phone.
hi folks!
I am pretty confused now. I am looking to get the V20 H990DS, but i am more confused now after reading here. My questions:
1. Is Bootloader unlock possible?
2. Can i install TWRP?
3. Can i root?
4. There is LOS official i know, but is the problem with 2. screen now fixed / going to be fixed?
Seems so good of a device, but i am insecure about it now after reading here. My old Mi4/Cancro is one of the best supported phones out there, so i dont expect it to be the same with V20, but i need working LOS with Root and working 2. screen (or the outlook on it working in the future) to be confident in buying it.
I hope you forgive me my nood questions,
Greetings
With sadly no replys, let me add what i know now:
1. + 2. + 3. Still no easy way in sight AFAIK. EDIT: To be clear: There IS a way, Dirty Santa, but the instructions are somewhat too complicated to be confident with trying. Have had rooted Phones with custom ROMs since over 5 years and never again a stock device, but i dont dare it. The 300€ i payed are much to much to have spend it on a bricked device. Will try to find more dirty Santa noob friendly explanations and post them here. EDIT2: For those who DO dare it, here the thread: https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296
4. Second screen still a problem, nothing new heard for quite a long time.
Anyone with knowledge to add or correct, please help! Stock ROM is not as bad as i thought, but without Root, Android is not fully usable for me.
thank you pro for this thread
very useful for me.
Stele88 said:
With sadly no replys, let me add what i know now:
1. + 2. + 3. Still no easy way in sight AFAIK. EDIT: To be clear: There IS a way, Dirty Santa, but the instructions are somewhat too complicated to be confident with trying. Have had rooted Phones with custom ROMs since over 5 years and never again a stock device, but i dont dare it. The 300€ i payed are much to much to have spend it on a bricked device. Will try to find more dirty Santa noob friendly explanations and post them here. EDIT2: For those who DO dare it, here the thread: https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296
4. Second screen still a problem, nothing new heard for quite a long time.
Anyone with knowledge to add or correct, please help! Stock ROM is not as bad as i thought, but without Root, Android is not fully usable for me.
Click to expand...
Click to collapse
i dont get about your complain. you said already using phone with root for 5 years so i guess you've been here on xda for a while. if you really want a phone which support custom rom go with phone which support unlock bootloader like HTC, Oneplus, or even xiaomy. its not that hard finding them on XDA. 300euro for briked devices? well, if you read v20 section carefully you knew most people here bought this devices for the camera, audio, and other things like removable battery, etc. i never found someone who bricked their devices while rooting here, even if they do we already had flasher tools like LG up which already tested fully working by some members. and whats the problem with second screen? its working for whatever it made for. are you expecting to watch movie on those 2.1 inch display? i had lg v20 h990ds rooted with magisk and had no problem so far. bought some apps like grenify and titanium backup for debloated and my phone rocking solid for abouth 2 month. if you cant wait for LOS just bought lenovo zuk2 or oneplus 3t on the same price range.
No problem doing 1+2+3 with DirtySanta exploit/procedure. It's not as complicated or dangerous as it might seem from the instructions. I thought I had soft-bricked my phone twice after rebooting normally with the old kernel instead of straight to TWRP to update the kernel first, but it was easy to re-flash the 10d factory firmware file I had and start over again without any issues both times.
Basic summary of procedure:
1. Flash factory firmware version earlier than 31 December 2016 (only needed if installed firmware version is after 1 January 2017).
2. Do DirtySanta exploit to unlock bootloader and install TWRP and root.
3. Use kdzwriter to update phone's system/modem/cust partitions to latest firmware version without overwriting unlocked bootloader/TWRP, reinstall root (SuperSU or Magisk) from TWRP.
4. Disable automatic OTA updates so that any future firmwares won't automatically install and overwrite bootloader/recovery and remove root and set ARB 1. If that ever happens then TWRP/root will probably be gone forever.
provided you follow the instructions carefully, it's safe to root with DirtySanta.
xoose said:
No problem doing 1+2+3 with DirtySanta exploit/procedure. It's not as complicated or dangerous as it might seem from the instructions. I thought I had soft-bricked my phone twice after rebooting normally with the old kernel instead of straight to TWRP to update the kernel first, but it was easy to re-flash the 10d factory firmware file I had and start over again without any issues both times.
Basic summary of procedure:
1. Flash factory firmware version earlier than 31 December 2016 (only needed if installed firmware version is after 1 January 2017).
2. Do DirtySanta exploit to unlock bootloader and install TWRP and root.
3. Use kdzwriter to update phone's system/modem/cust partitions to latest firmware version without overwriting unlocked bootloader/TWRP, reinstall root (SuperSU or Magisk) from TWRP.
4. Disable automatic OTA updates so that any future firmwares won't automatically install and overwrite bootloader/recovery and remove root and set ARB 1. If that ever happens then TWRP/root will probably be gone forever.
Click to expand...
Click to collapse
Using the steps on #3, would it be safe to say that we can update the device to oreo and still keep root?
nurse_chuck said:
Using the steps on #3, would it be safe to say that we can update the device to oreo and still keep root?
Click to expand...
Click to collapse
No, right now if you update you'll lose root as the engineering aboot isn't compatible with Oreo and you have possibly non working data, invalid sim issues etc
Sent from my LG-H910 using XDA Labs
cnjax said:
No, right now if you update you'll lose root as the engineering aboot isn't compatible with Oreo and you have possibly non working data, invalid sim issues etc
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Too bad. Your earlier post actually got me excited. Hehe. Anyway, hopefully someones starts working on rooting the oreo firmware.
The short answer? @Stele88
Yes. To all of it.
The long answer starts with the Dirty Santa root process. Believe me, I was daunted by it as well, but as long as you follow it (or the noob version of the guide you can find by searching around the same section the original guide is in) and take your time, you'll be okay. It's what I did and I'm now where I am today.
I'll address a couple things since I have the same device as you. If you want to get your device working properly on LineageOS/ResurrectionRemix (LOS with more customisation) then it's a long process.
1. Start by following the bootloader unlock process for Dirty Santa. Depending on what firmware your device gets shipped with, you may need to downgrade to (in the case of the H990DS) the v10c firmware. Once done, then you can Dirty Santa the bootloader and get it unlocked.
2. Once that's done and you're rooted with the initial TWRP from the thread installed, you'll want to look into KDZWriter. It's a program by the same emdroidle who did the Dirty Santa process for us that allows you to update your STOCK system software to newer versions and keep root. You can use it for example with the H990DS firmware KDZ files and go from rooted 10c -> rooted 10f -> rooted 10xx -> etc. until you're on the latest available 7.0 KDZ for the H990DS. This will be the longest part of your process, but it ensures that everything is up to date before going to AOSP/Lineage/Resurrection, specifically the modem partition. I recommend using the TWN region of firmwares if you're just going to convert to a custom ROM anyway, but any region will work fine (the only real difference is that, for example, the Australia region of firmwares comes with more bloat than the TWN region).
2b. You can also use KDZWriter from an updated TWRP you can get in the thread by Phoenix591, his latest TWRP versions have KDZWriter built-in so you don't have to run it off the computer, you can do it all with the kdz files in recovery.
3. Yes, you can root using the Dirty Santa method on v10c kdz firmware. I recommend Magisk for root over SuperSU.
4. There's no official LineageOS that is as up to date as the unofficial ones, and there's no official ones with second screen enabled full stop. That being said, the unoffcial LineageOS 15.1 by x86cpu has been my rock solid daily driver for about 2 months now and I've never had any issues that stop me from using it. The same can be said for ResurrectionRemix 6.2 by Blaises. To use either of these, you will need the updated TWRP from Phoenix591.
4. Second-screen enabled builds of LineageOS and ResurrectionRemix do exist, and in this case ResurrectionRemix is (as of this post) more up-to-date than the LineageOS 15.1 second screen version. If you find yourself needing additional features that aren't in the stock kernels for those ROMs (such as KCAL configuration to help with burn in, among other things), then I maintain the second-screen version of the Gamma Kernel by Omar-Avelar. People are successfully using this with second-screen ROMs and have full functionality. You can purchase the app BoredSigns from the play-store to add additional functions to the second-screen.
As I said at the start, it is a long process, but a very worthwhile one. The jump from stock to custom-ROMs is absolutely incredible. Again, in short, yes. You can get everything you want.
Just do your searching around the forums for the processes I outlined above, ask any questions you have, pre-download your kdz firmwares from HERE and any software you need, and just take your time. It's maybe a couple hours to get setup with a rooted stock system that's up-to-date, and maybe another hour or so to go from stock to Lineage/Resurrection.
P.S: If all goes well with the Dirty Santa process, but you get screen distortion after rebooting when flashing the TWRP from Dirty Santa, just pull the battery instead of rebooting.
Good luck, good searching, and remember to not be afraid to ask questions in the relevant threads.
---------- Post added at 04:50 AM ---------- Previous post was at 04:49 AM ----------
nurse_chuck said:
Too bad. Your earlier post actually got me excited. Hehe. Anyway, hopefully someones starts working on rooting the oreo firmware.
Click to expand...
Click to collapse
It's highly doubtful this will happen, but one can hope. Right now the best way to get Oreo is through a custom ROM, purely because of how security is implemented by LG in the stock Oreo ROMs.
iDefalt said:
It's highly doubtful this will happen, but one can hope. Right now the best way to get Oreo is through a custom ROM, purely because of how security is implemented by LG in the stock Oreo ROMs.
Click to expand...
Click to collapse
Actually it is possible runningnak3d has already said awhile ago he has a process to root stock oreo he's just not releasing it yet so LG can't patch it before the Oreo roll out is complete
Sent from my LG-H910 using XDA Labs
I'm having Moto g5 plus Indian variant xt1686. I have installed a custom ROM Resurrection remix and I'm currently running it.I want to get back to stock rom. I went through many existing threads only to get myself confused. I want you guys to help me get back to stock ROM so that I can get OTA updates.
1. I have working volte and IMEI till now. I didn't take back-up of persist or efs as I was lacking knowledge. Can I take back-up of those now for going back to stock. If yes then suggest how?
2. I don't remember my build number from which I unlocked my bootloader. Should I lock the bootloader again to get OTA? If not then please suggest any way to get back to stock whether Oreo or nougat (get updates to Oreo then).
kash664 said:
I'm having Moto g5 plus Indian variant xt1686. I have installed a custom ROM Resurrection remix and I'm currently running it.I want to get back to stock rom. I went through many existing threads only to get myself confused. I want you guys to help me get back to stock ROM so that I can get OTA updates.
1. I have working volte and IMEI till now. I didn't take back-up of persist or efs as I was lacking knowledge. Can I take back-up of those now for going back to stock. If yes then suggest how?
2. I don't remember my build number from which I unlocked my bootloader. Should I lock the bootloader again to get OTA? If not then please suggest any way to get back to stock whether Oreo or nougat (get updates to Oreo then).
Click to expand...
Click to collapse
From what I believe, you should definitely backup your EFS and Persist right now while it's all good.
If you don't remember your last stock build number, it is safe to use the latest build for your region.
Once you flash a fastboot ROM and everything's good to go, there's absolutely no need to relock bootloader as the script in the OTA only checks for system modifications and if it finds any on your phone, the OTA will not be applied and the update will eventually fail. To ensure that you are able to apply OTAs without any hassle, I recommend you don't do ANY system modifications like root or camera mods or similar. Stick with the core OS and you'll be good to go.
You can alternatively use TWRP flashable ROMs by @NZedPred, they're like a newbie-proof solution to getting to stock ROM from virtually any ROM without losing any functionality as they only flash the OS part of the ROM and rarely do any changes to the HW functionality of the ROM like Radios and Sensors. If all else fails, you can always flash a TWRP flashable stock and be ready to go.
Or
You could simply download the Oreo fastboot ROM with the August security patch which is available at the moment but isn't the latest one as the latest October security patch rolled out to RETIN devices just a few days ago so I doubt that the full fastboot ROM would be available this early. But then again, if you flash the Oreo August patch, you can take the OTA to October patch and be just fine.
Note:
But a bit of advice, if you're planning to go back to Nougat using a Nougat fastboot ROM, I'd highly recommend the TWRP flashable as one can mess stuff up while trying to downgrade using a fastboot ROM as Moto phones have problems downgrading. It's all about these two partitions called "gpt" and "bootloader" which when not paying attention to while flashing can cause a hard-brick.
A safer approach would be to skip these two partitions while using a fastboot ROM to downgrade but I'd be honest and would suggest you to wait to be sure this would work as I myself haven't tried this while downgrading from one Android version to another as Oreo bought with itself some Modem and a few other changes in partitions as compared to Nougat.
If I were you, I would wait for some to confirm the part in the "Note" just to be absolutely sure that it'd work.
Thanks for the response
Thanks for your response.
I'll be going with your suggestion and flash the twrp flashable oreo.
psychopac said:
From what I believe, you should definitely backup your EFS and Persist right now while it's all good.
If you don't remember your last stock build number, it is safe to use the latest build for your region.
Once you flash a fastboot ROM and everything's good to go, there's absolutely no need to relock bootloader as the script in the OTA only checks for system modifications and if it finds any on your phone, the OTA will not be applied and the update will eventually fail. To ensure that you are able to apply OTAs without any hassle, I recommend you don't do ANY system modifications like root or camera mods or similar. Stick with the core OS and you'll be good to go.
You can alternatively use TWRP flashable ROMs by @NZedPred, they're like a newbie-proof solution to getting to stock ROM from virtually any ROM without losing any functionality as they only flash the OS part of the ROM and rarely do any changes to the HW functionality of the ROM like Radios and Sensors. If all else fails, you can always flash a TWRP flashable stock and be ready to go.
Or
You could simply download the Oreo fastboot ROM with the August security patch which is available at the moment but isn't the latest one as the latest October security patch rolled out to RETIN devices just a few days ago so I doubt that the full fastboot ROM would be available this early. But then again, if you flash the Oreo August patch, you can take the OTA to October patch and be just fine.
Note:
But a bit of advice, if you're planning to go back to Nougat using a Nougat fastboot ROM, I'd highly recommend the TWRP flashable as one can mess stuff up while trying to downgrade using a fastboot ROM as Moto phones have problems downgrading. It's all about these two partitions called "gpt" and "bootloader" which when not paying attention to while flashing can cause a hard-brick.
A safer approach would be to skip these two partitions while using a fastboot ROM to downgrade but I'd be honest and would suggest you to wait to be sure this would work as I myself haven't tried this while downgrading from one Android version to another as Oreo bought with itself some Modem and a few other changes in partitions as compared to Nougat.
If I were you, I would wait for some to confirm the part in the "Note" just to be absolutely sure that it'd work.
Click to expand...
Click to collapse
Thanks for your response.
I'll be going with your suggestion and flash the twrp flashable oreo.
kash664 said:
Thanks for your response.
I'll be going with your suggestion and flash the twrp flashable oreo.
Click to expand...
Click to collapse
Make sure to follow the flashing instructions mentioned by the thread OP properly
psychopac said:
Make sure to follow the flashing instructions mentioned by the thread OP properly
Click to expand...
Click to collapse
Yes. Hope everything turns out fine
kash664 said:
I'm having Moto g5 plus Indian variant xt1686. I have installed a custom ROM Resurrection remix and I'm currently running it.I want to get back to stock rom. I went through many existing threads only to get myself confused. I want you guys to help me get back to stock ROM so that I can get OTA updates.
1. I have working volte and IMEI till now. I didn't take back-up of persist or efs as I was lacking knowledge. Can I take back-up of those now for going back to stock. If yes then suggest how?
2. I don't remember my build number from which I unlocked my bootloader. Should I lock the bootloader again to get OTA? If not then please suggest any way to get back to stock whether Oreo or nougat (get updates to Oreo then).
Click to expand...
Click to collapse
I hope i can help !!
vishalrickz said:
I hope i can help !!
Click to expand...
Click to collapse
Sure sir
Hello LG fans,
There is an old thread with a similar title, but since it is inactive I started this one. For certain reasons I got this G4 phone only few days ago. The model number on the box and under-battery tag as well as in settings showed F500 (just F500 without any suffix S, L, or K). It came with Android 5.1, and everything was working well. Online search showed that F500X phones can be officially updated to Nougat 7.0, but the phone OTA update said no update was available.
As per LG website, I installed LG Bridge to get the updates. It identified the phone as F500K and found two updates. First it installed 6.0 Marshmallow and then 7.0 Nougat software version F500K30c. Also the model no changed to F500K in settings. I think this probably means it is is a refurbished phone
The Installation was successful, but it installed a Korea Telecom version with some Korean stuff. I uninstalled or disabled all the Korean bloat I could without root, but there are still a few things remaining, and some Korean language here and there.
In general, I’m quite satisfied with the phone. The only thing I wish to get rid of is the KT Wifi manager app which is all in Korean, and I don’t know what it does or which settings to select. It is a system app, and I can’t uninstall or disable it, but my wifi and data networks seem to be working fine, so no complaints. I’ve seen several people here and elsewhere complaining about network issues, boot loops and bricks, but so far I haven’t experienced any. I hope it stays this way :fingers-crossed:
I was wondering about the other variants F500S and F500L, do they also have Korean bloat and is it more or less than F500K? I have read somewhere that these three firmware variants can be interchangeably installed. Is this the case, and if so, is it advisable to install another variant? I have been reading about this phone, but this is my first time to use an LG phones, and I have no experience with their software and tools, so any help, ideas or suggestions will be highly appreciated.
Thanks
Gold Mix said:
Hello LG fans,
There is an old thread with a similar title, but since it is inactive I started this one. For certain reasons I got this G4 phone only few days ago. The model number on the box and under-battery tag as well as in settings showed F500 (just F500 without any suffix S, L, or K). It came with Android 5.1, and everything was working well. Online search showed that F500X phones can be officially updated to Nougat 7.0, but the phone OTA update said no update was available.
As per LG website, I installed LG Bridge to get the updates. It identified the phone as F500K and found two updates. First it installed 6.0 Marshmallow and then 7.0 Nougat software version F500K30c. Also the model no changed to F500K in settings. I think this probably means it is is a refurbished phone
The Installation was successful, but it installed a Korea Telecom version with some Korean stuff. I uninstalled or disabled all the Korean bloat I could without root, but there are still a few things remaining, and some Korean language here and there.
In general, I’m quite satisfied with the phone. The only thing I wish to get rid of is the KT Wifi manager app which is all in Korean, and I don’t know what it does or which settings to select. It is a system app, and I can’t uninstall or disable it, but my wifi and data networks seem to be working fine, so no complaints. I’ve seen several people here and elsewhere complaining about network issues, boot loops and bricks, but so far I haven’t experienced any. I hope it stays this way :fingers-crossed:
I was wondering about the other variants F500S and F500L, do they also have Korean bloat and is it more or less than F500K? I have read somewhere that these three firmware variants can be interchangeably installed. Is this the case, and if so, is it advisable to install another variant? I have been reading about this phone, but this is my first time to use an LG phones, and I have no experience with their software and tools, so any help, ideas or suggestions will be highly appreciated.
Thanks
Click to expand...
Click to collapse
You could
downgrade to MM,
backup with SALT (CRUCIAL important),
unlock by UsU ,
extract with SALT: system ,modem and boot partitions from a f500 kdz,
root and debloat or (if you like to) install a custom ROM
Check the UsU and SALT threads (you can find both in my signature)
Sent from my OnePlus 6T using XDA Labs
steadfasterX said:
You could
downgrade to MM,
backup with SALT (CRUCIAL important),
unlock by UsU ,
extract with SALT: system ,modem and boot partitions from a f500 kdz,
root and debloat or (if you like to) install a custom ROM
Check the UsU and SALT threads (you can find both in my signature)
Sent from my OnePlus 6T using XDA Labs
Click to expand...
Click to collapse
Thank you @steadfasterX for your reply,
It's quite an honor the Guru himself was the first to reply to my post. I have seen many of your posts and replies in the forum before, and now looked at some of the stuff in your signature. Pretty impressive work. I definitely need to spend some time learning about them particularly SALT and FWUL, as I have also started learning and using Linux lately. How come FWUL is not shown on distrowatch?
For the time being, I was thinking to stick to stock Nougat 7.0 as it's a fairly recent OS, and the phone is fine even with the remaining little Korean stuff. My main dissatisfaction really is with the mysterious kt wifi manager app which is all in Korean and has some settings which I don't know what they are. If just replacing the current Nougat 7.0 with another variant S or L is actually possible, and these variants don't have a similar app, this would be great.
I have been searching for information about these S/L/K firmware variant differences but couldn't find much. I hope other S & L phone owners could tell us about their phones. The only thing I could find so far is that each is for a different carrier in Korea, and that they can be interchangeably installed as per a Reddit post. I don't know how reliable this information is!
From a purely technical perspective for G4 F500 , is it possible to flash another F500 variant using LGUP, or is this something that shouldn't be done? I have seen many people getting in trouble for flashing wrong firmware. If this is safe to do, do I need to do any preparation work like downgrading to MM first, and should this be done as an upgrade or a refurbish? For what it's worth, my ARB value is 0.
Thanks
steadfasterX said:
You could
downgrade to MM,
backup with SALT (CRUCIAL important),
unlock by UsU ,
extract with SALT: system ,modem and boot partitions from a f500 kdz,
root and debloat or (if you like to) install a custom ROM
Click to expand...
Click to collapse
Hi Sfx,
1. to downgrade to MM... use uppercut, right? I'm using latest 20u for F500l is OK for UsU?
2. after backing up with SALT, can I revert back anytime after unlock and with new custom ROM?
3. after rooting, do I install twrp and load custom ROM? and can I extract 30b Nougat's modem from KDZ to use with the custom ROM?
thanks so much in advance for answering...:angel:
Gold Mix said:
How come FWUL is not shown on distrowatch?
Click to expand...
Click to collapse
Because they are ignorant and/or just arrogant enough to ignore my requests. I even offered to pay advertisements as this should be (according to their website) a way to get listed instant. but nothing. Even not on the waiting list..
Gold Mix said:
From a purely technical perspective for G4 F500 , is it possible to flash another F500 variant using LGUP, or is this something that shouldn't be done?
I have seen many people getting in trouble for flashing wrong firmware. If this is safe to do, do I need to do any preparation work like downgrading to MM first, and should this be done as an upgrade or a refurbish?
For what it's worth, my ARB value is 0.
Click to expand...
Click to collapse
ok so one thing first. the most important one: Ensure you keep your ARB at 0. This is crucial important. So never ever flash anything (including QFIL restore files!!!) where you are not 10000% sure it wouldn't increase your ARB.
If you are about to flash a KDZ then check that file with SALT first (simply press extract and it will display the ARB). If you flash anything else.. well ensure that the files offered have that information listed and hope and pray its not wrong (e.g. there are QFIL files around which are labeled for a ARB 0 model but contain ARB2 files..). Never heard about a wrong labeled KDZ file but who knows.
The second important thing is (maybe its even the first): before doing anything, do a full backup with SALT (basic is fine) and (!!) move that to a secure place! (I saw so many ppl who lost their backup through several ways).
So when going on through the UsU process you will have 2 SALT backups: the one before downgrading to MM and another one after you downgraded to MM (tbh the more important one). If you can keep them both.
so about flashing other variants: yes it IS technically possible to even flash e.g. h815 ROMs to a F500 and so converting it that way! but never try that with h811 KDZs or others..
anyways yea you could flash other F500 variants without fear (just carrier bloat is different) as long as you follow the above advises.
cooledi said:
Hi Sfx,
1. to downgrade to MM... use uppercut, right? I'm using latest 20u for F500l is OK for UsU?
2. after backing up with SALT, can I revert back anytime after unlock and with new custom ROM?
3. after rooting, do I install twrp and load custom ROM? and can I extract 30b Nougat's modem from KDZ to use with the custom ROM?
thanks so much in advance for answering...:angel:
Click to expand...
Click to collapse
1. I dunno the latest MM F500 version but "20u" sounds good. Can't help in the downgrade process but there are plenty of guides here in the G4 forums.
2. dunno that you mean here.. but if you wanna know if you can stay on STOCK after UsU'ing yea sure. flashing UsU does not require to go for a custom ROM. It just gives you the freedom to do so.
3. if you follow the UsU guide you will have TWRP already and that's the place where you install a custom ROM if you like. Sure extract the 30b modem and flash it in fastboot should work fine (after UsU).
.-
steadfasterX said:
..
1. I dunno the latest MM F500 version but "20u" sounds good. Can't help in the downgrade process but there are plenty of guides here in the G4 forums.
2. dunno that you mean here.. but if you wanna know if you can stay on STOCK after UsU'ing yea sure. flashing UsU does not require to go for a custom ROM. It just gives you the freedom to do so.
3. if you follow the UsU guide you will have TWRP already and that's the place where you install a custom ROM if you like. Sure extract the 30b modem and flash it in fastboot should work fine (after UsU).
.-
Click to expand...
Click to collapse
Thanks sfx, I'm now on MM and ready to get SALTed I want to flash AEX v6.7 But there are two offerings H811 and H815, and my F500L in SALT say GPT compatibility is H811 /ARB0, so do I flash H811 version of AEX?? If so, is there a H811_UsU_baseband_flash-in-twrp I need to flash as well? thz
cooledi said:
Thanks sfx, I'm now on MM and ready to get SALTed I want to flash AEX v6.7 But there are two offerings H811 and H815, and my F500L in SALT say GPT compatibility is H811 /ARB0, so do I flash H811 version of AEX?? If so, is there a H811_UsU_baseband_flash-in-twrp I need to flash as well? thz
Click to expand...
Click to collapse
if you would flash h811 on yours you will increase your ARB so do NOT flash that.
Use a h815 based ROM even when SALT compat shows different. your partition layout is somehow weird..
for non-UsU ROMs flash the f500(!!) baseband package once
.-
steadfasterX said:
You could
downgrade to MM,
backup with SALT (CRUCIAL important),
unlock by UsU ,
->> extract with SALT: system ,modem and " boot partitions from a f500 kdz, "
root and debloat or (if you like to) install a custom ROM
Sent from my OnePlus 6T using XDA Labs
Click to expand...
Click to collapse
If I wanna go back to stock, what boot partitions should I extract from the f500 kdz image?
so namely I need to flash;
system.img
modem.img
do I need modemst1 & modemst2.img? what else do I need to flash?
thx!
cooledi said:
If I wanna go back to stock, what boot partitions should I extract from the f500 kdz image?
so namely I need to flash;
system.img
modem.img
do I need modemst1 & modemst2.img? what else do I need to flash?
thx!
Click to expand...
Click to collapse
system, boot, modem
nothing else
Pls i had f500s please can someone help withbsome detail process of rooting this phone.i am currently on stock rom android 5.1.its my first time usong lg g4 .i used sumsang and i had no problems around sumsung but lg g4 is a whole new level. I dont understand the UsU terms and SALT.pls help i need root pls.
please i need you help.
Pls i had f500s .i am currently on stock rom android 5.1.its my first time using lg g4 .i used sumsang and i had no problems around sumsung but lg g4 is a whole new level. I dont understand the UsU terms and SALT.pls help i need root pls
Good day everyone. I have a T-Mobile branded 6T - well 2 of them actually, a daily driver, and a game phone. The daily driver needs to be udpated, so I can update the game phone first to make sure it will work before moving to the daily driver. Problem is, I'm rooted with magisk, TWRP as recovery, so OTA doesn't work, and apparently hiding magisk with "keep TWRP" module doesn't work, because OTA is still not loading properly, so I would like to re-flash the whole thing if necessary so it's up to date. I've read many things about this, but I can't seem to find something that fits my situation and makes me comfortable doing it, so thought I'd ask here. What would be the safest method to upgrade to the latest OxygenOS?
* I'm familiar with flashing and rooting this device, so don't care if I lose that
* Losing data would suck, but willing to do so if the procedure is easier that way
* My phones are branded, willing to switch to global if easier
I just want the darn things updated since they're close to a year out of date with upgrades and patches. Please direct me to the best procedure for my current situation, and thank you.
Well OnePlus isn't making any more updates for it. If you want it to be updated I suggest using one of the newer custom roms.
Right, I knew it would not be updated to the absolute latest I just need it to be updated to the point where my carrier will stop telling me that I could lose service. So for now I decided to take the global route. I unbranded the phone with the patch kit found in a thread here, and then used the OnePlus updater app which brought me as current as it could which I believe is November 2021. It's Android 11 and that will do me for the time being. Thank you for the response. I will probably look for other ROMs later