I recently installed lineageOS 18.1 on my Oneplus 8 (t-mobile) and everything worked just fine. Only problem I had was a slightly reduced signal strength and noticed I was often roaming with LOS while at work so I ended up using msm-tools to go back to stock and check a few things with the stock firmware near my work and noticed I was just always roaming out there so lineage was working just fine after all (OOS just didn't have the R above my signal like LOS). But when I tried reinstalling any other custom rom it now fails to write the modem or something. I get no errors until it boots up lineage and then suddenly CrashDumps after a minute or so. I have no sim detection or wifi. The msm tool will always bring me back to a fully functional stock image that works just fine but I cant get any custom rom working now. Has anybody else seen this issue before? I get no error reports other than modem failed to load on CrashDump. Followed the same instructions on lineageOS site and ran same exact files as before. I have tried running older versions of msm tools and still the same result. Same with crDroid. I tried installing through both TWRP and LineageRecovery.
Ok I think I figured it out. In case anyone else stumbles on this issue.. using the manual firmware upgrade on lineage site.. https://wiki.lineageos.org/devices/instantnoodle/fw_update fixed the problem. Just need to extract a payload from an official update from T-Mobile and flash every driver again.
Related
Does anyone know what changed regarding wifi in Android 8 or MIUI 10?
I was happily using LOS 14 for a while (after having officially unlocked my bootloader at some point in the past, but became curios and wanted to try out the new MIUI 10. While I could not find anything official, I did find this chinese dev ROM (I DO NOT RECOMMEND YOU FLASH THIS). I flashed it, wasn't that impressed and then decided to try LOS 15 based on Android 8.
That was a bit too unstable for me, so I tried reverting back to LOS 14.
I did so using a backup I made to my pc (I did `adb backup` while in TWRP and selected every partition I think). After booting into LOS14, things seemed to crash an awful lot.
At this point I realized wifi wasn't working. It showed a MAC Address of 02:00:00 I think, but no networks were found. I tried restoring my phone using MiFlash normally. I then tried restoring it using Qualcomm's download mode. Older MIUI versions would not boot anymore (although I did manage to boot an old version of TWRP made for the pre-Nougat bootloader). I tried LOS14 again, and attempted using fastboot to erase various partitions (such as the bluetooth and modem partition, and then manually flashed the image again. Still no wifi.
Does anyone know what could have happened? My bootloader is still unlocked, and even downgrading the device to an old version of MIUI using Qualcomm mode did not make it work again? How come LOS15 and MIUI 10 are able to use wifi without problems?
tl;dr WiFi stopped working on any rom other then Lineage OS 15 or MIUI 10.
This is a new GSI thread i found. It includes MIUI, OOS, HOS, ZenUI, and One UI. Now let us test this gsi and discuss our experience.
Here is the link:
https://forum.xda-developers.com/pr...vice-development/pie-erfan-gsi-ports-t3906486
I had some crazy problems. I flashed OOS. everything seemed fine. Boot took some time but ok. Eventually booted. Everything seemed to be working, even the fingerprint! After some time it just started to reboot again and again. Tried going back to stock rom with twrp: failed. Tried fastboot: failed. Even edl didnt work. Everytime i tried flashing it came up with a different error. I kept trying and after like 10 tries it finally worked. Got real worried there
What i want to say is: Be careful. As always you might run into some trouble.
Yes!! I saw this thread too and it seems to be very interesting
atengo said:
I had some crazy problems. I flashed OOS. everything seemed fine. Boot took some time but ok. Eventually booted. Everything seemed to be working, even the fingerprint! After some time it just started to reboot again and again. Tried going back to stock rom with twrp: failed. Tried fastboot: failed. Even edl didnt work. Everytime i tried flashing it came up with a different error. I kept trying and after like 10 tries it finally worked. Got real worried there
What i want to say is: Be careful. As always you might run into some trouble.
Click to expand...
Click to collapse
I tried OOS with 9.6.4.0 vendor it booted but im bugged in the notch cut out and i think its very unstable. Also the wifi isnt working but i havent tried installing custom kernel. What did vendor did you tried?
I was bored looks like we have a version out there but i havent tried it yet it has step by step pretty much but you will have to unroot go back to latest stock i think first then flash if anyone checks it out lemme know
https://www.getdroidtips.com/android-10-moto-g7-power/
the github is here https://github.com/phhusson/treble_experimentations/releases/tag/v210
AOSP 10.0 v210
Dev is phhusson <<-----all credit would be to this gentleman i just happened across it while i was surfing, and saw 10 was out for the plus.
toxinburn said:
the github is here https://github.com/phhusson/treble_experimentations/releases/tag/v210
AOSP 10.0 v210
Dev is phhusson <<-----all credit would be to this gentleman i just happened across it while i was surfing, and saw 10 was out for the plus.
Click to expand...
Click to collapse
I tried the android 10 system image on my moto g7 power. I tried wiping system and installing the system image in twrp.
Phone kept bootlooping. Ended up trying to restore my backup via twrp but data would not restore,and I ended up in a twrp bootloop. Eventually I somehow hardbricked the device. Luckily I was able to find a blankflash to restore the phone to fastboot and I used rsdlite to reflash fw. Maybe I should have wiped everything, not just sytem, but I'm not willing to risk trying again.
skalnas said:
I tried the android 10 system image on my moto g7 power. I tried wiping system and installing the system image in twrp.
Phone kept bootlooping. Ended up trying to restore my backup via twrp but data would not restore,and I ended up in a twrp bootloop. Eventually I somehow hardbricked the device. Luckily I was able to find a blankflash to restore the phone to fastboot and I used rsdlite to reflash fw. Maybe I should have wiped everything, not just sytem, but I'm not willing to risk trying again.
Click to expand...
Click to collapse
Same to me with the difference I wiped all. But I don't pretend to be a guru of the phone's firmwares so it might be I did it wrong.
Maybe it's not a good section for this thread, it's more like Q&A.
It's possible to flash Android 10 GSI, but it wasn't ready for a daily driver.
What was working:
-booting
-screen
-audio
-connecting to 4G network
what wasn't:
-connecting to wifi
-receiving SMS on 4G network
I did not test rest of it.
Just wait a little while longer. The official stock upgrade will be released and Android 10 custom ROMs will be developed.
robson_89 said:
Maybe it's not a good section for this thread, it's more like Q&A.
It's possible to flash Android 10 GSI, but it wasn't ready for a daily driver.
What was working:
-booting
-screen
-audio
-connecting to 4G network
what wasn't:
-connecting to wifi
-receiving SMS on 4G network
I did not test rest of it.
Click to expand...
Click to collapse
ut
Here are some notes about Android 10 gsi and Moto G7 power from the main developer. I believe there's a flashable wifi zip PHH made as a fix for the wifi somewhere on this page: https://github.com/phhusson/treble_experimentations/wiki/Moto-G7-Power
Yes, I've seen it.
I don't have telegram account nor do I wish to create any, so WiFi patch is not for me.
Besides, it's only applicable when your WiFi works with static IP but not with dhcp.
Mine wasn't working at all.
*SOLVED: see reply*
The ROM I used before was LineageOS [10.0] and used a custom ROM with Android 9 before that. Needed to unlock my phone, and couldn't do that on Lineage, and had troubles flashing firmware with Odin, so I ended up using FrankensteinS6. The Stock kernel seems to let me input the NCK, and unlock the phone. So that's luckily finally over.
For about 4 days now I've been formatting phone and trying again and again. FrankensteinS6 works, some other 6.0/7.0 ROMs work. But LineageOS now enters a bootloop, and Pixel Experience (9.0 and 10.0) and Evolution X 10.0 don't detect the SIM. The ones that don't detect SIM also show no IMEI, which was worrying at first because I though I lost a partition.
Possibly related, the ROM of Pixel Experience Android 10.0 for G920W8 will not install because (paraphrasing) "This device is zeroflte, this file is for zerofltecan, zeroflte***, zeroflte***" claiming that my phone isn't one of those models. I got this S6 from Bell Canada, and I still have even the sticker that says it is a G920W8, not G920F. However, the Pixel Experience ROM for G920F flashes fine (sans the main problem).
I don't know the exact LineageOS ROM I used before, but I've tried all of their 10.0 releases, tried redownloading, and I get the bootloop every time. I see some info online of flashing modem firmware, but... I don't even know where to start with that. As I mentioned at the start, Odin is crapping out. I couldn't flash firmware with it, because it would reject the phone right after I started flashing. Anything I could do within TWRP would be great. I moved it back to FrankensteinS6 for my sanity, I started doing this Sunday and I'm starting to repeat steps over and over hoping that it just solves itself.
I tried to keep this straightforward, and I'm sure I did a bad job. I can extrapolate on what I have attempted. Please tell me what I have to do to get an android 10 ROM working on this old beauty again.
I do not have all the solutions. As per my tests with my SM-G920W8. I have managed to find ROMS and try them out. I have only seen Nougat 7.0 ROMS to work almost flawlessly. NOT 7.1.2, important, 7.0 only.
I have also tested some Pie and v10 ROMS like Pixel Experience. The ROMS boot nicely but since I do not use a SIM card to call as I use SIP phone numbers and require WiFi. But that left asside, I came upon serious camera issues no matter what I try. Up to now, SamStock ROM is pretty much the best Stock ROM I found but I always need to run the Magisk UNINSTALLER before re-installing the latest Magisk version..
As for Kernels, well, Anything that is oriented with Lineage OS, I've had camera issues even with Nougat v7.0. So basically, the only ROMS I found good, as of today, for now, are stock ROMS v7.0. But, to do your tests, Even if you have a 920F ROM, you can download a 920W8 kernel as long as you download a kernel which supports your installed Android version. Also make sure to download the proper Stock or AOSP kernel (AOSP for LineageOS). There's not many but there's a few ones that work properly.
Another option is to download an AOSP ROM that works for W8 phones, unzip the file and grab the boot file inside corresponding to the W8 or T-Mobile version. You simply unzip your real ROM you want top install, replace the boot file for the one you got and rezip it. This made my phone boot properly for some F version ROMS but again, not without issues. That's why, I really suggest v7.0 Srock ROMS. I hope this helps you a bit. Again, you can have your own tests and other users may have other answers, but this is based off over 30 bootloops in my case of trying to mod a ROM for the W8 model. It's not easy to find a good one for Canada, I admit!!!
I flashed TWRP years ago, and I found out that I had a G920F version flashed. I don't know why Lineage allowed me to use SIM before, but rectifying this issue seems to made the SIM work in newer versions.
I don't know what the S6's predisposition to having crashing cameras is, but I have avoided this in the past by using custom camera apps, like Open Camera. This has saved me every time.
As for the boot loops... I think another thing that helped is that "format data" doesn't wipe the OS. When you are in recovery, having issues with bootloops in various ROMs, try advanced wipe, and wipe the system. It didn't fix right away, but the time I got Pixel Experience 10 up and running that was the trick.
I've had a strange issue with my LG V20 ever since I got in last year and installed LineageOS 18.1 after rooting my H990 on LG firmware 10d (H990ds10d_00_OPEN_AU_DS_OP_1216.kdz) with DirtySanta and installing TWRP. Whenever I left the range of my Wi-Fi network, I would cause the System UI to become unresponsive while doing certain tasks - Unlocking, going to Settings -> Wi-Fi, expanding the Wi-Fi quick toggle in notifications, and probably a few more things.
This doesn't happen on the aforementioned stock firmware, nor on 10g AU 0117 stock firmware either.
For a while, I dealt with it by simply not using Wi-Fi. This sucked because I couldn't access computers over LAN, mobile data was slower, and it also had a data cap that I had to be wary of.
However, I decided I wanted to fix it.
I saw some recommendations involving installing every Lineage version since 14.1 sequentially until the latest. This didn't make sense to me, as clean flashing shouldn't leave any remnants behind, but dirty flashing that many versions went against everything I'd ever heard of regarding custom ROMs.
I also heard that it could be a modem firmware issue. Since I started on the last version of the stock OS for my region vulnerable to DirtySanta I thought surely not.
I later found out about KDZWriter, and used that to install the latest Nougat version of the stock rom available (also mentioned above). After installing that, I tried installing the latest LOS on top, which constantly informed me that com.android.media had stopped, I still had the LG sounds and wallpapers, and I didn't go through the initial setup - A sign of a dirty flash. I was still crashing in the same way too.
I formatted my data partition in TWRP (the "type yes to confirm" way), and tried again. Same crashes.
I've been awake for a little too long trying to fix this, but :
What I believe ended up working was backing up my /efs and /firmware partitions in TWRP while on rooted 10g firmware, dirty flashing LOS on top, formatting data as before, then flashing my /firmware backup in TWRP.
I'm hoping for this thread to document this issue as well as the fixes that worked for people. I saw tidbits of information spread out everywhere, so I'd like a central repository for it.
I hope this caffeine-induced writeup will help someone else with the same or similar issues.
If I have any more experiences with it, I'll do my best to write them down. Please share your experiences too!