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.
Related
Hi, first of all, sorry if I mistype anything, as English is not my main language.
I usually try to find my answers in others posts, as I have installed custom ROMs and recoveries on other phones before (Nexus 4, Moto X 2014), but this time I couldn't find anything for my situation.
I recently imported an Axon 7 from Singapore, everything on the box is in Chinese, but when I booted the phone, the version showing on the settings is the A2017G, build number A2017GV1.0.0B10.
I tried to update from the settings to Android Nougat, but it says it is up to date.
Out of curiosity I restarted the phone holding power + vol up and booted the recovery, and it is all in Chinese.
I think the seller probably installed the A2017G Rom.
So now I don't know which guides should I follow to update my phone, I just want to have stock nougat and TWRP for precaution.
Should I just follow this one https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379.
Or this https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165.
Or just download an imagem from here https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547.
I'm currently at work, so I won't be able to try anything right now, but any direction to what to do will be of great help.
And I didn't put my sim card there yet to see if the network works in my country, I'm from Brazil.
the first one.
do steps a then b.
dont do the c steps.
then reflash stock recovery, update to nougat, with stock rom, then reboot the phone in edl and reflash twrp 3.1 with axon-tool.
you will have stock with twrp
thanks for the reply.
I will try as soon as I can.
:good:
pelelademadera said:
the first one.
do steps a then b.
dont do the c steps.
then reflash stock recovery, update to nougat, with stock rom, then reboot the phone in edl and reflash twrp 3.1 with axon-tool.
you will have stock with twrp
Click to expand...
Click to collapse
Hello,
is this procedure good also to have stock nougat rooted firmware?
andr123a said:
Hello,
is this procedure good also to have stock nougat rooted firmware?
Click to expand...
Click to collapse
Yes sr.
You must unlock in b11 or older.
Then upgrade to b04, you must reflash stock recovery from edl or twrp. After that upgrade.
Then go back to edl and reflash twrp.
Note that for first unlock you have to flash the signed buggy twrp, and after unlock, you must flash 3.1 to have a working twrp.
andr123a said:
Hello,
is this procedure good also to have stock nougat rooted firmware?
Click to expand...
Click to collapse
Enviado desde mi ZTE A2017G mediante Tapatalk
only one that worked for me...
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Thank you for your answers but...I discovered that the phone is already updated to 7.1.1 b04....(I bought it yesterday)
A colleague of mine advised me to use kingoroot app....has anyone ever tried it?
Inviato dal mio SM-P905 utilizzando Tapatalk
How do I know which bootloader do I have? I'm currently running build B35.
Can someone direct me to a thread how to flash universal bootloader and modem?
If I use bkores flash toolkit, it said you have to flash universal bootloader, modem along with Rom and Gapps but in which order?
If using twrp for future flash do I need to flash universal bootloader and modem every time I switch ROM?
I'm not an expert but here's what I understand.
1. You don't have to worry which version you have unless you're flashing a custom ROM, usually for Nougat you want the B15 and for Oreo you want the B35.
2.Universal Bootloader>Modem>ROM>GApps>Magisk/SuperSU
3.You only need to flash it once if you're switching ROMs with the same android version.
Nicz14 said:
I'm not an expert but here's what I understand.
1. You don't have to worry which version you have unless you're flashing a custom ROM, usually for Nougat you want the B15 and for Oreo you want the B35.
2.Universal Bootloader>Modem>ROM>GApps>Magisk/SuperSU
3.You only need to flash it once if you're switching ROMs with the same android version.
Click to expand...
Click to collapse
Thank you for the reply.
I'm on Android 7.1.1 with build B35.
I want to flash a custom ROM.
vic_singh said:
Thank you for the reply.
I'm on Android 7.1.1 with build B35.
I want to flash a custom ROM.
Click to expand...
Click to collapse
If you haven't you need to unlock your bootloader before you can start flashing custom ROM. You can find a guide on how to do it here.
I already tried to downgrade from Pie to Los 14.1.
But RIL does not work after Installation. So I probably missed something.
I think i need N Firmware first, right?
So how to downgrade correctly?
Thanks in advance!
Depends on the firmware you were prior to flashing pie. You can fastboot flash according to that. Or just get a TWRP flashable stock build of nougat.
Grab the latest nougat from this thread:
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
The versions that use the aroma installer will make sure that you retain your IMEI by fixing your persist permissions.
Hello everyone
Yesterday I got a steal deal for a brand new lgv20 in just 100$ but it's Puerto Rico model H910PR "CLARO" and it's stuck on December 2016 Update Android 7.0.
I tried to Ota update but it shows device is already on latest update.
Then I tried LG Bridge and it shows also same device is on latest OS.
I SAW MANY POSTS THAT ANDROID OREO IS OUT FOR V20 FOR A WHILE BUT COULDN'T FIND THE OREO KDZ ANYWHERE.
PLEASE SOMEONE SHOW ME SOMETHING HERE I AM GETTING FRUSTRATED. :crying:
Hello, I have the same phone, there is no Oreo update for us (in fact there's no update at all) unless you're willing to root.
if you're willing to root then just keep a dump of your partitions then root it using H910 root method and flash Oreo H910.
Any H910 rom works perfectly on our phone.
Messaibi said:
Hello, I have the same phone, there is no Oreo update for us (in fact there's no update at all) unless you're willing to root.
if you're willing to root then just keep a dump of your partitions then root it using H910 root method and flash Oreo H910.
Any H910 rom works perfectly on our phone.
Click to expand...
Click to collapse
Thanks for reply
You mentioned H910 oreo works perfectly on 910pr so my question is all the radios works ?
I mean wifi/sim card/gps/mobile data everything works?
If everything works perfectly i would love to try it ASAP .
Are you running oreo N910 on your N910pr currently and which method you use to root ?
Do i have to flash N910 KDZ on my N910PR or i have to flash Custom rom from Twrp ?
Sorry for many questions i asked i just want to. Make sure before going any further.
Tia
Trex888 said:
Thanks for reply
You mentioned H910 oreo works perfectly on 910pr so my question is all the radios works ?
I mean wifi/sim card/gps/mobile data everything works?
If everything works perfectly i would love to try it ASAP .
Are you running oreo N910 on your N910pr currently and which method you use to root ?
Do i have to flash N910 KDZ on my N910PR or i have to flash Custom rom from Twrp ?
Sorry for many questions i asked i just want to. Make sure before going any further.
Tia
Click to expand...
Click to collapse
Everything works fine, if it somehow doesn't, just flash your Modem, Modemst1 and Modemst2 from your partition dump and everything will work again, that's why you always keep backup.
I used this https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 root method
Then I flashed Alpha ROM Oreo H910 (a debloated version of the stock rom) through TWRP.
Messaibi said:
Everything works fine, if it somehow doesn't, just flash your Modem, Modemst1 and Modemst2 from your partition dump and everything will work again, that's why you always keep backup.
I used this https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 root method
Then I flashed Alpha ROM Oreo H910 (a debloated version of the stock rom) through TWRP.
Click to expand...
Click to collapse
Thanks for the tip tho. I am having problem with modem. now that I saw this post I solved it.
but now that there's LOS16, can I flash stock Nougat modem on LOS16 in order to get network to work?
H910PR - How to root & install any ROM! (all lineage ROMs verified)
Hey guys! :D I've been struggling over the weekend to get my H910PR rooted w/ a custom ROM installed. I kept getting kernel panics saying 'modem crashed' but was finally able to figure it out. Step 1 - Root / TWRP I followed these steps...
forum.xda-developers.com
So I really want to install a custom rom and I know I need to unlock the boot loader and flash it with twrp. But I been reading around here and it seems unlocking the bootloader on Oreo is not possible and the only way to do that is to downgrade to nougat... except I don’t really know how to do this on my device since as previously stated, the boot loader is not unlocked and I don’t know where the stock rom for nougat is even available to download from, or any necessary tools to download to be able to do this (I’m a complete noob). Some info of my device: A2017u, Oreo, B20
Help would be appreciated, thank you
I think you may need to go back to Marshmallow to unlock bootloader and install TWRP but I'm not on an A2017U so won't try to advise you.
I did revert my own A2017G from latest Oreo back to Nougat ok. Since gone back to Oreo. It seems to work when stock but once you meddle with it that's when all the problems start.
RobboW said:
I think you may need to go back to Marshmallow to unlock bootloader and install TWRP but I'm not on an A2017U so won't try to advise you.
I did revert my own A2017G from latest Oreo back to Nougat ok. Since gone back to Oreo. It seems to work when stock but once you meddle with it that's when all the problems start.
Click to expand...
Click to collapse
//////