Ghost touches with custom rom fixed coming back to stock rom... - ZTE Axon 7 Mini Guides, News, & Discussion

Ok, so sorry about that, but the EU g&rbest version has ghost touch that make it unusable (almost impossible to navigate the menu or write the keyboard) with every custom rom.Actually I don't know why, but I finally reinstalled stock EU build B2017GV1.2.0B13 (B13 7.1.1) Kernel 3.10.84 , installed TWRP and rooted with magisk and everything is finally fine...I really hope that Oreo lineage won't have this problem, at the moment AOKP and the lineage can't be used on mine EU B2017G (( looks like I'm the only one with that problem (or almost all the people here has USA or UK version).
P.S.P I hope is the right section, please move it if am I wrong.Thank you

Related

Has Anyone Gotten a Custom ROM onto a BLN-L24 (US Variant)?

I have tried quite a few ROMs, and all ended up going back to stock firmware because they wouldn't boot. I know I have to format data, and some ROMs ask you to change the data partition as f2fs.
Still, I think that there may be no ROMs that currently work for the US variant. One guy said LOS 13 worked, but when I flashed it, it failed. If someone has gotten it to work, can you please post as many steps as you remember on how to get it work?
Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050
RedSkull23 said:
Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050
Click to expand...
Click to collapse
Thanks, but wouldn't there be more issues down the line with a debranded phone? What if I soft-bricked my phone, it seems like it'd be really hard to restore? Has anyone actually ever done this on a BLN-L24?
Hello all,
I too am having issues with flashing roms to this device, US variant (BLN-L24). In my particular case, the rom boots up (EliteRom v7.1) and will actually function. However, wifi does not work, as well as I have no sound whatsoever. Youtube also will not play, nor will any videos, which I'm guessing is tied to whatever issue is with the sound. I have flashed multiple times per the step by step instructions, as well as following the Youtube video, all with the same result over the last few days. At this point, my phone is effectively useless to me, though cellular data does still work, just no calls can be answered. Anyone have any suggestions I might be able to follow? Also, even my TWRP backup that I made before installing the rom will not restore at this point. Any help is appreciated, thanks.
Jessooca said:
You must be missing a step or something, because [Elite ROM][EMUI 5.1] Elite ROM v7.1 for Honor 6X by HassanMirza01 works on the L24 us variant without issues, I have none.
Perhaps go back to stock and start over. I haven't had any issues with his rom and I didn't do anything more than what's needed to root/install twrp and flash the rom per his instructions.
Click to expand...
Click to collapse
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop
i4ybrid said:
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop
Click to expand...
Click to collapse
On one of the attempts that I did for installing, I installed the patch and it put me in a boot loop. Maybe not installing the patch can help you?
I cant get anything to work for the US version. Sure stuff boots but some of it is just broken. On octOS i am unable to use root unless i switch supersu to automatically grant root to apps. I cant get root access by using prompt because nothing pops up. On crdroid i have the same exact issue. Id rather have the prompt than allow any app root access without my knowledge. With ELITE ROM my first boot brings up a home screen with no keyboard. It completely skips any kind of setup screen. I can get the setup screen by flashing a keyboard from an aroma gapps installer but then i lose google services. The US version also seems to be forgotten as for most roms you wont see it anywhere under supported lists.
I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?
code_name_duchess said:
I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?
Click to expand...
Click to collapse
It really sucks that nothing seems to work. Ive tried flashing using multiple recoveries and ive tried all kinds of flashing to fix issues with the ROMS. Nothing helps. If anyone has successfully gotten a ROM fully working on BLN-L24 they need to tell people exactly what they did step by step.
It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.
TurtlePwr82 said:
It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.
Click to expand...
Click to collapse
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing. Most recoverys say Open Kirin Edition when booting. What confuses me is why we need to debrand to get the ROMS to work. If the phone pretty much run on the same hardware then why is L24 having so many issues? Why are the devs not testing on these devices?
BakedOnSomeSour said:
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing
Click to expand...
Click to collapse
Right, that's what I was thinking. For any phone I've ever rom'd, there was always just one twrp that everyone worked from.
Edit: found this while looking through the roll back to stock forum. I don't know if it will help anyone else, but figured I'd put it here as well if it might. All credit for this goes to the original poster johnnyrichter:
johnnyrichter said:
Tried this method after being on LineageOS for a week or two and having poor LTE signal, no MMS, and voicemail issues so I'm trying to go back to stock so I can have a fully functional phone since I rely on it heavily for work. Followed all steps using BLN-L24 B360 firmware. On step 10 I rebooted to update and it went right to "5% Installing Update" and stuck there for 5 mins, then rebooted itself, has been sitting at "honor" boot screen for 14 minutes so I made it reboot to EMUI recovery, wiped/factory reset, rebooted, loaded EMUI afte 2 more minutes. Appears to have worked and hopefully my issues are fixed!
Edit: Signal, mms, and voicemail issues fixed.
Click to expand...
Click to collapse
Hopefully will benefit someone here as well.
When debranding the BLN-L24, and branding it to BLN-L21, are there any issues with the ROMs once they're installed? I imagine the radios, and such are different for the two models??
BakedOnSomeSour said:
Why are the devs not testing on these devices?
Click to expand...
Click to collapse
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?
galapagos said:
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?
Click to expand...
Click to collapse
well, many don't want to give them a phone because most developers here tend to stop work on a ROM and leave people hanging.
I have gotten several ROMs working on L24 variant...
Yes it seems to me any Elite kernel based ROM works or should work on the L24. But /data must be ext4 format. Then even that the ROM works, the fingerprint scanner never allows a complete successful scan. I think because it must be f2fs format for that encryption to work or something. This is the link to those ROMS https://hassanmirza01.blogspot.com/p/custom-roms.html?m=1
On the other hand the LOS based ROMs never work or at least they reboot and the screen is always black or the ROM branding just stays there flashing. This sucks cause I want to run the newest Resurrection ROM but I ask the developer about why I have that problem or how long that ROM takes to boot and I never get an answer. He also just put a new beta AOKP ROM up and it does the same black screen thing too.
I am also suspicious it has to do with the version of TWRP. I think some are capable of formatting f2fs correctly or the encryption or whatever. Point is some of the devs need to be a little more consistent answering questions at a minimum. I know it takes time to fix bugs but give us a little heads up.

[ROMS] Treble ROMs GSI working in Nokia 7 plus ( All models )

Install at your own risk
Remember to install Custom ROMS you need to have the bootloader unlocked
LIST ( Tested and working )
Resurrection Remix
https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
AOSP
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
All Treble GSI ROMs ( Untested )
You need chose A-A/B ROMs in that page
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
How to Flash GSI Treble ROMs guide
https://forum.xda-developers.com/nokia-7-plus/how-to/how-to-flash-generic-imagegsi-nokia-7-t3802590
Hey man, how did you unlock your bootloader? Can you post some screenshots of the roms working on our device?
sublimeace said:
Hey man, how did you unlock your bootloader? Can you post some screenshots of the roms working on our device?
Click to expand...
Click to collapse
Sure
@orbirix: Is there anyway to go back to stock after using this? The official rollback doesn't work on top of stock rom on july update because the rollback firmware is older. And, I can't even dump my current system because I can't get magisk patched (or even stock boot.img) to boot.
I am really willing to test out these but the lack of a working stock firmware file is stopping me. Any ideas, friend?
Broadcasted from Zeta Reticuli
Treble ROM screenshots
sublimeace said:
Hey man, how did you unlock your bootloader? Can you post some screenshots of the roms working on our device?
Click to expand...
Click to collapse
You can find some screenshots by clicking here. And you'll know how to unlock the bootloader too
Gravemind2015 said:
@orbirix: Is there anyway to go back to stock after using this? The official rollback doesn't work on top of stock rom on july update because the rollback firmware is older. And, I can't even dump my current system because I can't get magisk patched (or even stock boot.img) to boot.
I am really willing to test out these but the lack of a working stock firmware file is stopping me. Any ideas, friend?
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Hopefully nokia can update the rollback firmware. This is why i prefer custom recovery, we can take a nandroid backup just in case something goes wrong. Nokia needs to let us unlock bootloader. I miss magisk as well lol.
Hey guys I'm kinda on the fence with buying this phone, love the built but I really love to have custom rom and messing with options, but the forum seems plain so anyone have any idea if this phone will have custom som support in the future or because it's android one so there won't be any rom?
This is the only thing that holds me from buying this phone tbh because I love all other things.
Ethan140310 said:
Hey guys I'm kinda on the fence with buying this phone, love the built but I really love to have custom rom and messing with options, but the forum seems plain so anyone have any idea if this phone will have custom som support in the future or because it's android one so there won't be any rom?
This is the only thing that holds me from buying this phone tbh because I love all other things.
Click to expand...
Click to collapse
I would stay away from the N7P if installing custom roms is a must. Even if there is an easy way to unlock the bootloader and root, I doubt the developer community will be interested in this phone.
@orbirixx: Has anybody tried installing Nokia Camera (available in play store) on these? Thanks
Almost all GSI working fine in Nokia 7 Plus now. Except voLTE. All are almsot stable and daily driver. Tested all Android 9 Pie based GSI and everything works except voLTE. You can install Nokia camera but Portrait and 2x Zoom does not work.
Rajeev said:
Almost all GSI working fine in Nokia 7 Plus now. Except voLTE. All are almsot stable and daily driver. Tested all Android 9 Pie based GSI and everything works except voLTE. You can install Nokia camera but Portrait and 2x Zoom does not work.
Click to expand...
Click to collapse
You must have the bootloader unlocked to flash it, am I right?
Rubens95 said:
You must have the bootloader unlocked to flash it, am I right?
Click to expand...
Click to collapse
Absolutely
Any idea how to resolve problem with WiFi on P customs?
Hi all, I have Nokia 7 Plus TA-1055 (single SIM italian edition), unlocked bootloader, installed and tried many GSI ROMs but, in the compatible ones, phone app has many problems:
- a phone call is impossible to hear (low low volume on both speakers)
- a strange behavior: when I start a call, this one closes soon before first ring, but the phone of the recipient ringing and he can answer the call!! In order to get it working (for me), I must start many calls, until the recipient puts my first call on hold and answers my second call
Obviously this is a bad problem, because I want to use Nokia as my first phone
death_jax said:
Hi all, I have Nokia 7 Plus TA-1055 (single SIM italian edition), unlocked bootloader, installed and tried many GSI ROMs but, in the compatible ones, phone app has many problems:
- a phone call is impossible to hear (low low volume on both speakers)
- a strange behavior: when I start a call, this one closes soon before first ring, but the phone of the recipient ringing and he can answer the call!! In order to get it working (for me), I must start many calls, until the recipient puts my first call on hold and answers my second call
Obviously this is a bad problem, because I want to use Nokia as my first phone
Click to expand...
Click to collapse
I experienced the exact same behaviour. Even if the recipient picks up the call, that phone cannot hear anything but when they hang up, I get a notification that usually comes after a call (days remaining in data plan etc.) in my 7 plus TA-1046.
That was back a few weeks ago, the Havoc (maybe) and PixelExperience has been updated along with AEX and it's working for other TA-1046 so far. VoLTE seems to have been fixed for at least one carrier (not mine) by sideloading a specific ims.apk
Maybe try one of those new GSIs ?
Broadcasted from Zeta Reticuli

SIM Unlocked G920W8, 9.0 and 10.0 ROMs no longer detect SIM.

*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.

Got a bootloop to TWRP after downloading latest update from Arrow OS and installing it

Dear all,
Hope you are doing great, I was downloading and installing automatic updates just fine and the other week got a notification about a new update of over 1.4 gbs and the automatic installer was not possible to do and requested me to download it and installing it manually. I downloaded the Rar and everything was going smooth and when I enter TWRP I installed at first shoot without doing any wipe or clear cache or data.
All was installed and it told me to restart the phone, I did that and vroom a vibrating sound happen and got me back to the main screen of Poco and then to TWRP and show me 3 workarounds to clear data and cache and the last resort do a clean flash rom.
I had to end with the last option since I was unable to install the update. What could be gone wrong here? I am back at stock now and I am very sad that this fricking update break all the custom firmware and got me bootlooped
I look for your inputs and maybe I can try again.
Thank you!
You must install Android 11 firmware for newer versions of Arrow as it has switched to OSS vendor.
I was on arrow os 11 so Android 11 was on there, the issue was when I was installing the new update from surija I believe si called the developer.
Do you guys have an idea what did I did wrong? Should You recommend staying vainilla stock miui 12 with root privileges or arrow 11?
Thank you!
I was able to flash the latest version update but I am having a System UI is not responding and got WIFI broken so if anyone is installing this update be careful, does anyone installed the last arrow OS update?
I am currently having issues with the last update, I think I will stick with no updates on the firmware
Sorry I am posting multiple updates on my thread, but I tested it and definetly the last update from Surya break the OS when you login you do not have WIFI and is showing the error I mentioned UI system unresponsive. I installed the version from April from Arrow OS and all works like a charm.
So if anyone reads this be careful with latest release from Surya 5/14 version
Yes, i can confirm. The version I used initially was from april 30. The update from may caused bootloop. I'll be turning off updates when I restore it with miflash.
The main reason I went with arrow is that it is selinux enforcing and supports safety net. But this really makes me think..
@SebixWolf The problem may have been that you flashed arrowos from the wrong miui version. I just miflashed back to the original regional version, flashed twrp again and flashed the R firmware. See https://forum.xda-developers.com/t/...ng-flashing-custom-rom.4274891/#post-85002889

Le Eco Le2(x526) No network after a dirty flash of ROM HELP!!!

I have a Le Eco Le2(x526) which is the Indian variant 3GB/32GB codename-s2
I have successfully flashed TWRP recovery installed many custom ROMs
like Pixel experience, Remix OS, Lineage OS, Arrow OS
it was working fine after one day I flashed a new ROM Revenge OS I dirty flashed it
as it was said we can dirty flash the ROM
Later did I realized I did a mistake device was working perfectly fine for like a week
But it suddenly it started losing network time to time after 3 days it wasn't recognizing any network/sim
It was my fault I didn't take any backup of the stock ROM and its files
Later I clean flashed its stock ROM thinking it would work but it didn't I later checked in TWRP there were no network files all the defaults files were not there
this device has been with me for 5 years still works like a beast only problem is it doesn't show network
I need to fix it PLEASE HELP
I am currently on Redmi Note 6 pro I hate MIUI
I want to use Le 2 and make it my current device

Categories

Resources