Hi, I have d802 with stock Lollipop 30B firmware.
After wanting to go back to CyanogenMod 12, I cant get stable cellular signal anymore. It looks like it's toggling airplane mode on and off every ~5 sec.
Tried wiping, restoring previous nandroid, a clean install, other ROMs... same thing, cellular network is stable only on stock ROM.
Is there any way to fi it? Has the 30B update updated the modem/baseband so it isn't compatible anymore? Will flashing stock KK revert all updates partitions and firmwares on the phone?I have a fully working stock ROM, but I use custom ROMs for like forever, and this LG UI is for me ugly and limited...
dj_chapz said:
Hi, I have d802 with stock Lollipop 30B firmware.
After wanting to go back to CyanogenMod 12, I cant get stable cellular signal anymore. It looks like it's toggling airplane mode on and off every ~5 sec.
Tried wiping, restoring previous nandroid, a clean install, other ROMs... same thing, cellular network is stable only on stock ROM.
Is there any way to fi it? Has the 30B update updated the modem/baseband so it isn't compatible anymore? Will flashing stock KK revert all updates partitions and firmwares on the phone?I have a fully working stock ROM, but I use custom ROMs for like forever, and this LG UI is for me ugly and limited...
Click to expand...
Click to collapse
Question does not belong in this Forum.
Ask in Q & A.
TDSJR said:
Question does not belong in this Forum.
Ask in Q & A.
Click to expand...
Click to collapse
Sorry, my bad
Flash KK Baseband because Stock Lollipop change it.
L0nelyE4rth said:
Flash KK Baseband because Stock Lollipop change it.
Click to expand...
Click to collapse
Flashed, got cellular again! :good:
Hello dear XDA-Community,
Until now, I kept with Audax Rom 1.2 (based on firmware OH3) with its delivered Audax kernel, but now I wanted to upgrade to OJ5.
Everything went fine with Audax Rom 2.0 (OJ5) - custom kernel from Arter was working as well. I still messed up something though.
I read that the OJ5 firmware/bootloader blocks the flash of any custom recovery. I was a bit too risky and updated my recovery to a newer PhilZ version anyways after I flashed the new bootloader and modem. Now my phone won't boot up anymore. Doesn't matter what I'm trying.
Audax Rom 2.0 (OJ5) with and without custom kernel doesn't boot up. It will only bring me to the stock Samsung bootlogo. But it keeps there.. for an endless amount of time.
I think that I messed up because I still wanted to update my recovery - even after I upgraded to the OJ5 bootloader + firmware + modem.
I wanted to go back to AOH3 now.. and I downloaded the AOH3 stock firmware. Unfortunately it fails to flash in Odin. It literally stops at "cm.bin" and shows "FAIL!".
Is there any way how I can fix my phone again?
I really really need your help, guys. :/
Greetings
Prim
Edit: That's fixed. I can boot now. I installed stock OJ5 firmware.
Apparently there is no way to do a downgrade from AOJ5 to AOH3.
I downloaded the AOJ5 stock firmware and installed it. Everything works fine now.
But due to the fact that it's completely stock, my battery life is horrible (30% loss of battery over 6 hours screen being off.) :crying:
Is there any method to install a custom recovery and kernel after I updated to AOJ5?
A lot of people run AOJ5 with a custom recovery. But my phone is based on the newest bootloader, which now doesn't allow me to install any custom recovery. I really hope there is some workaround for this. I am really not happy with stock AOJ5, as it was supposed to fix the battery drain, but it drains even more than AOH3 :/
Greetings
Prim
Primrose Jy said:
Apparently there is no way to do a downgrade from AOJ5 to AOH3.
I downloaded the AOJ5 stock firmware and installed it. Everything works fine now.
But due to the fact that it's completely stock, my battery life is horrible (30% loss of battery over 6 hours screen being off.) :crying:
Is there any method to install a custom recovery and kernel after I updated to AOJ5?
A lot of people run AOJ5 with a custom recovery. But my phone is based on the newest bootloader, which now doesn't allow me to install any custom recovery. I really hope there is some workaround for this. I am really not happy with stock AOJ5, as it was supposed to fix the battery drain, but it drains even more than AOH3 :/
Greetings
Prim
Click to expand...
Click to collapse
Development options/ OEM Enable and that is all
Oh my actual god. It works. I am now running OJ5 together with the newest modem, custom recovery, custom kernel and ROM.
Thanks a lot, sir. :fingers-crossed:
I am on 6.0 Marshmallow due to Moto X Pure not being updated. I am running stock. I really want to be able to see the emojis that my friends send me. If i root and flash Nougat Emojis? will that prevent me from getting the Nougat update via OTA?
driver969 said:
I am on 6.0 Marshmallow due to Moto X Pure not being updated. I am running stock. I really want to be able to see the emojis that my friends send me. If i root and flash Nougat Emojis? will that prevent me from getting the Nougat update via OTA?
Click to expand...
Click to collapse
Don't get your hopes up for nougat ota anyways...? But jokes aside you can root with magisk and still be able to take an OTA, but I dont know if it's risky, someone correct me if I'm wrong, but i was looking at this thread.
https://forum.xda-developers.com/apps/magisk/ota-updates-magisk-t3476091/page1
Since magisk is systemless, you can get the ota, and from what I get you can flash it with flashfure, but that's over my head, you'll have to do your own reading on that I don't know if you use any apps which use safety net right now(pokemon go, Android pay, Netflix, etc...) But if you head over to the magisk forums the latest stable version is v12 but it doesn't pass safety net. If safety net is necessary for your needs you'll have to flash the latest beta, and then flash away with the nougat emojis!!!
Hope this helps, let me know if you have any questions, and I think after taking an ota you'd have to reflash magisk to gain root again but you'd still have the emojis without root anyways.
Edit : as I wrote that last line it occurred to me...you only need an unclocked bootloader and a custom recovery like TWRP to flash zips! Check some guides on how to unlock the bootloader and flash twrp. So you wouldn't even need root as you don't need to touch the system partition. I hope the above info is useful info anyways, but for the emojis, head over to the TWRP site and check the Downloads for Clark, flash twrp, and then flash the emojis!
Hey there,
I am currently running LineageOS (Oreo) and I have to say I am pretty dissapointed about it.
The Phone is rooted and unlocked.
Most of the reallly usefull stuf the OP5 has doesn't work on LineageOS. The Hardware Profile Slider is useless, no Screen-Off Gestures, the Stock OOS Camera App is buggy...etc
So my question is:
Is there a way to stay on regular Stock OOS and receive all OTAs but keep staying rooted?
And if so will I be able to stay rooted after an update? I read that one way would be to have TWRP installed and "manually flash" updates under 1GB.
Thanks a lot guys!
You can receive OTA with magisk passing SafetyNet but you need to re-root after every update, i think software will advise you before update that had find the root :good:
Hello
I've been struggling with this issue for weeks now. I have literally tried everything.
I have a A2017G with the universal B32 oreo bootstack from NFound. I've tried clean AEX and Resurrection Remix. Various builds. I have wiped system, data, cache, internal before trying to flash another rom. I have tried using different packages of GAPPS 8.1 ARM64 (Nano, Pico, Aroma). I've tried formatting data to f2fs and ext4. I've tried with and without supersu and Magisk.
My NFC module is not broken, I put it on B09 stock and it worked perfectly fine. It could read my NFC card. But as soon as I install either AEX or Resurrection Remix it just stays grayed out. But my NFC service keeps running for some reason and drains my battery. I seem to be the only person having this as well, not a single person running the same builds has these issues.
I ended up giving up and just deleted the NFC.apk from /system/data to fully disable NFC so it would stop draining my battery.
I'd really appreciate some help if any of you has a solution for this. I used to use my NFC all the time for payments.
I would try reflashing the stock ROM, then install TWRP and try those custom ROMs again. I recently had an issue where NFC and Android Beam wouldn't turn on. So I flashed a B19 EDL package with MiFlash, OTA updated to B32, then installed TWRP and AOSP Extended Oreo. NFC works again. I have an A2017U.
AnonVendetta said:
I would try reflashing the stock ROM, then install TWRP and try those custom ROMs again. I recently had an issue where NFC and Android Beam wouldn't turn on. So I flashed a B19 EDL package with MiFlash, OTA updated to B32, then installed TWRP and AOSP Extended Oreo. NFC works again. I have an A2017U.
Click to expand...
Click to collapse
Do you reflash a different bootstack or do you just keep the stock one?
g0dzstar said:
Do you reflash a different bootstack or do you just keep the stock one?
Click to expand...
Click to collapse
You can't keep the stock bootstack lol, use the one that the ROM recommends. Univ bootloader + X modem for Nougat, univ B32 bootstack for Oreo
Choose an username... said:
You can't keep the stock bootstack lol, use the one that the ROM recommends. Univ bootloader + X modem for Nougat, univ B32 bootstack for Oreo
Click to expand...
Click to collapse
He wasn't very specific xD. I've already tried a lot so I wouldn't be surprised if this would fix it. But I will try going back to stock and OTA'ing to B32 and try again.
AnonVendetta said:
I would try reflashing the stock ROM, then install TWRP and try those custom ROMs again. I recently had an issue where NFC and Android Beam wouldn't turn on. So I flashed a B19 EDL package with MiFlash, OTA updated to B32, then installed TWRP and AOSP Extended Oreo. NFC works again. I have an A2017U.
Click to expand...
Click to collapse
This solution actually worked. Thank you very much!
AnonVendetta said:
I would try reflashing the stock ROM, then install TWRP and try those custom ROMs again. I recently had an issue where NFC and Android Beam wouldn't turn on. So I flashed a B19 EDL package with MiFlash, OTA updated to B32, then installed TWRP and AOSP Extended Oreo. NFC works again. I have an A2017U.
Click to expand...
Click to collapse
Hi, is it possible to provide me the files for a A2017G. I have the same problem with a RR Oreo ROM.
cybertronicx said:
Hi, is it possible to provide me the files for a A2017G. I have the same problem with a RR Oreo ROM.
Click to expand...
Click to collapse
You can get them yourself ? no need to be babysitted for everything. Go to the EDL Tool thread (google "edl tool") and download an A2017G file, and install it with EDL Tool
@cybertronicx: Sorry but no, I have an A2017U, not G, so there is no reason I would keep the G firmware files hanging around. I wouldnt be able to flash them anyway. The B19 EDL I downloaded is from a thread by @jcadduono, and he specifically states that the files he provides are for U only, and also warns not to try them on other variants.
AnonVendetta said:
@cybertronicx: Sorry but no, I have an A2017U, not G, so there is no reason I would keep the G firmware files hanging around. I wouldnt be able to flash them anyway. The B19 EDL I downloaded is from a thread by @jcadduono, and he specifically states that the files he provides are for U only, and also warns not to try them on other variants.
Click to expand...
Click to collapse
That's BS though. Flashing the corresponding modem and TWRP just after flashing the edl rom makes it usable on other variants.
Let's keep the thread simple though
@Choose an username...: Flashing a G firmware on a U model in EDL mode would really work? I had no idea, I thought it would hardbrick the phone for sure. On most other Android devices, flashing another firmware, even from a different variant of the same device, will result in bricking. But the A2017U has the best official and community support vs A2017G and A2017 (China).
AnonVendetta said:
@Choose an username...: Flashing a G firmware on a U model in EDL mode would really work? I had no idea, I thought it would hardbrick the phone for sure. On most other Android devices, flashing another firmware, even from a different variant of the same device, will result in bricking. But the A2017U has the best official and community support vs A2017G and A2017 (China).
Click to expand...
Click to collapse
I'm writing off of an U ROM on a G. Of course it can be made. There are a bunch of guides around the forum, that tell you how to do this.
The thing is, all of these phones are ailsa_ii. I know you are talking about variants as in thea/titan for the Moto G2, but in those cases they had 4g on the thea and 3g on the titan for example. In this case the phones only vary in the modem used. If you flash the U ROM as-is, it will probably boot, but you won't have cell signal at all.