Database Users

[Q] Is it worth 330$ to switch from Oneplus One to Axon7?

Hello,
I can buy Axon7 on Aliexpress for around 330USD. Currently I'm using OPO and it is running just fine. I've got a few questions to you guys:
1. Are custom ROMs stable ( no bugs, battery drains, camera and sound is working like on stock )?
2. How far is Stock ROM from AOSP (recents, QS, settings) ?
3. Would you switch if you had OPO ?
4. Are there any news of update to Android O being planned ?
Thanks for the replies!

If you want front facing speakers, yes. If you like the huge amount of roms available for bacon, stay with that. I was on the opo and if it was not for the speakers on the a7 I would switch back.

There are still enough roms available, just not like for op5. Roms are stable

FunkyRasta said:
Hello,
I can buy Axon7 on Aliexpress for around 330USD. Currently I'm using OPO and it is running just fine. I've got a few questions to you guys:
1. Are custom ROMs stable ( no bugs, battery drains, camera and sound is working like on stock )?
2. How far is Stock ROM from AOSP (recents, QS, settings) ?
3. Would you switch if you had OPO ?
4. Are there any news of update to Android O being planned ?
Thanks for the replies!
Click to expand...
Click to collapse
Most ROMs are somewhat stable, but all of them have a couple of bugs like mic broken until you turn on and off the loudspeaker (you can fix that with macrodroid). And the stock ROM works better than the custom ROMs no doubt. But I found out that (if you care more about MP3 music than FLAC lossless) V4A is better on custom ROMs than stock. and you can get more than 7 hours SOT on custom ROMs if done right (normally people get 5 on the stock ROM)
The stock ROM is totally different than AOSP. The stock launcher has no dock just like Apple stuff but it also comes with an alternative with dock. The icons are crappy though. If you install Lawnchair from XDA you get a launcher better than Pixel and stock icons for almost all of the apps. Recents is just like AOSP but with a Clear all button and a lock to avoid you closing the app by swiping or via the button. pretty handy!
Now, I had something weird happen to me: When I got my Moto G 2 I used the stock ROM for like 3 days and switched to customs. I never even thought about going back to stock for all the poor phone's life (like 1.5 years). now with this one, I try a couple of ROMs for a month or two, get bored and return to stock. Always happens. Many people say the same, that they started liking the stock ROM even though it strays from AOSP a lot. But it has its fair share of good things, like auto power-on some minutes before your alarm goes off, scheduled on and off, a Dolby Atmos QS tile... It's not bad because it doesn't look like AOSP. not at all.
Besides, MiFavor 5.0 was released for the Chinese and it looks very good!
The phone has hardware keys but the Chinese version hasn't, hence the on screen keys on the screenshot.
Update to O: No news yet, though if it comes, expect the first 2 or 3 builds to be riddled with bugs. ZTE's devs barely know how to use a keyboard. Up to B04 Nougat they broke the Play store then fixed it, broke exFAT for SD cards, then fixed it... People made petitions (basically spamming "We want Android O" on a petition thread on the German forums) but nobody said anything close to a confirmation.
Would I switch from a OnePlus One? 2K AMOLED screen, SD820, speakers better than Samsung's $800 phones come with, QC3.0, for 330 dollars? definitely
The screenshots I attached are from the Chinese MiFavor 5.0 because that's what I'm using right now. You can install it via TWRP if you want.
one thing though: If you can get an A2017U (US version) instead of an A2017 (Chinese Aliexpress version) you're gonna thank me. The U version has so much more development than the G or Chinese... Even people say that sound is better on it. It costs 330 dollars on the US too.
This phone is easy to brick, be REALLY careful and read everything twice before doing stuff or you can end up with a DFU brick which is the most hardcore brick of them all.

Choose an username... said:
Most ROMs are somewhat stable, but all of them have a couple of bugs like mic broken until you turn on and off the loudspeaker (you can fix that with macrodroid). And the stock ROM works better than the custom ROMs no doubt. But I found out that (if you care more about MP3 music than FLAC lossless) V4A is better on custom ROMs than stock. and you can get more than 7 hours SOT on custom ROMs if done right (normally people get 5 on the stock ROM)
The stock ROM is totally different than AOSP. The stock launcher has no dock just like Apple stuff but it also comes with an alternative with dock. The icons are crappy though. If you install Lawnchair from XDA you get a launcher better than Pixel and stock icons for almost all of the apps. Recents is just like AOSP but with a Clear all button and a lock to avoid you closing the app by swiping or via the button. pretty handy!
Now, I had something weird happen to me: When I got my Moto G 2 I used the stock ROM for like 3 days and switched to customs. I never even thought about going back to stock for all the poor phone's life (like 1.5 years). now with this one, I try a couple of ROMs for a month or two, get bored and return to stock. Always happens. Many people say the same, that they started liking the stock ROM even though it strays from AOSP a lot. But it has its fair share of good things, like auto power-on some minutes before your alarm goes off, scheduled on and off, a Dolby Atmos QS tile... It's not bad because it doesn't look like AOSP. not at all.
Besides, MiFavor 5.0 was released for the Chinese and it looks very good!
The phone has hardware keys but the Chinese version hasn't, hence the on screen keys on the screenshot.
Update to O: No news yet, though if it comes, expect the first 2 or 3 builds to be riddled with bugs. ZTE's devs barely know how to use a keyboard. Up to B04 Nougat they broke the Play store then fixed it, broke exFAT for SD cards, then fixed it... People made petitions (basically spamming "We want Android O" on a petition thread on the German forums) but nobody said anything close to a confirmation.
Would I switch from a OnePlus One? 2K AMOLED screen, SD820, speakers better than Samsung's $800 phones come with, QC3.0, for 330 dollars? definitely
The screenshots I attached are from the Chinese MiFavor 5.0 because that's what I'm using right now. You can install it via TWRP if you want.
one thing though: If you can get an A2017U (US version) instead of an A2017 (Chinese Aliexpress version) you're gonna thank me. The U version has so much more development than the G or Chinese... Even people say that sound is better on it. It costs 330 dollars on the US too.
This phone is easy to brick, be REALLY careful and read everything twice before doing stuff or you can end up with a DFU brick which is the most hardcore brick of them all.
Click to expand...
Click to collapse
Wow, that's why I love XDA, thank you for this very helpful reply !
So on official LOS for example microphone during call doesn't work until I toggle loudspeaker ? That's is... Weird . So even if you are running custom ROMs you are coming back to stock because of bugs and features :/
I noticed on videos that launcher and icons sucks. Can I just install nova launcher on stock and use it without any problem ?
About Chinese and American versions. The ROMs doesn't work on all version, the a2017, U and G ? I did some reading and I know there are different bootstacks and stuff but I though the custom ROMs are compatible with all regions.
Is this brick recoverable ? Is there a flashtool that will always rescue me ?
Thanks again !

Yes you can flash nova launcher. It is an app! There is a flashtool for flashing and recovering from soft/hard bricks. The phone just rocks...

FunkyRasta said:
Wow, that's why I love XDA, thank you for this very helpful reply !
So on official LOS for example microphone during call doesn't work until I toggle loudspeaker ? That's is... Weird . So even if you are running custom ROMs you are coming back to stock because of bugs and features :/
I noticed on videos that launcher and icons sucks. Can I just install nova launcher on stock and use it without any problem ?
About Chinese and American versions. The ROMs doesn't work on all version, the a2017, U and G ? I did some reading and I know there are different bootstacks and stuff but I though the custom ROMs are compatible with all regions.
Is this brick recoverable ? Is there a flashtool that will always rescue me ?
Thanks again !
Click to expand...
Click to collapse
It's more complicated than that.
First of all: The modes on this phone are (were):
-EDL (Looks like it's completely off, it's not. You can flash special folder packages with MiFlash when you are in this mode)
-Bootloader mode (Fastboot. On A2017G and U they got rid of it. You can get it back by flashing a zip through TWRP, but if you update the stock ROM officially you'll lose it and will have to flash it again)
-Recovery. You can use axon7toolkit to unlock and install this. One-click tool like the one on Nexus 6 thread.
After you flash the Universal bootloader (for custom ROMs), your TWRP will get overwritten with an older one. Just keep a 3.1.1-0 img file and flash it in this crappy TWRP with Install -> Install image
-FTM. Seems that you get ADB when you are in this mode. Handy when you brick it horribly (no recovery) and can't access EDL. You just issue adb reboot edl and you should get to edl.
And last: DFU mode. Be REALLY careful with EVERYTHING, for example if you flash a system zip and TWRP says that you have no system installed, restore a backup, DON'T reboot! I had a DFU brick once and the two ways to recover from a DFU brick (No EDL, no fastboot, no recovery, very rarely FTM) are to discharge the phone completely and try to get into FTM, or take the phone apart and do the 4th category brick repair manual. I did the latter
But as of now no brick is unrecoverable. With A2017G's and U's you get a pretty overkill warranty, and you can return it claiming that it stopped working all of a sudden for example.
About the launcher: yeah, you can install whatever you like. I use Lawnchair.
And the ROM's work on all 3 phones, but it's the kernels that don't. Kernels work on the G and U on custom ROMs, but there is only one kernel that works for the U on stock, and none for the G. On the G the camera breaks on stock when you use a custom kernel. That's why I recommend you to get a U even if it's a little bit more expensive.
Is there a tool that will always save you from a brick? well there are many, but they will help you like 90% of the time. axon7tool is used to flash stuff to recovery or boot from EDL (you can flash TWRP for ex.), axon7toolkit can do some basic fastboot stuff, and MiFlash is the most useful, cause you can flash a full system directly from EDL and leave your phone in a functional state.So if, say, your digitizer breaks and you are on a custom ROM (and have an A2017G or A2017U, which have warranty) you can simply flash a working system and send it to fix.
If ZTE finds out that the phone has been tampered with (unlocked, opened, etc) they will charge you $80 but they'll fix it. If the phone doesn't even boot and it's a G they'll change it free of charge because of European laws
one more thing: you'll hate the quick settings thingy on stock. Try MiFavor 5.0 if you decide to stay stock, it's a Chinese ROM but with a bunch of work it can get pretty nice. I sent you a couple of screenies there

RUNNERX said:
If you want front facing speakers, yes. If you like the huge amount of roms available for bacon, stay with that. I was on the opo and if it was not for the speakers on the a7 I would switch back.
Click to expand...
Click to collapse
I would go for it because the newer LTE modems are so much better than any of the SD820 especially how poor both the Axon 7 and OP3 signals are compared to the SD821 and SD835. It is night and day in terms of connectivity. Performance wise it's also worth it.

You don't need to flash Nova launcher, I am with the Stock rom and use Nova as it. Just install it and use it as default launcher.
Envoyé de mon ZTE A2017G en utilisant Tapatalk

Moving to LineageOS worth it (and possible) from Cloudy G2.2?

I've been running Cloudy G2.2 for a year an a half. It's given the phone enough legs to mostly make it through 2017. However, about every other week I have to restore my latest backup when Bluetooth stops working because it saw too many devices. This wouldn't be terrible if it wasn't for Authy refusing to sync my newer 2-Factor auth accounts. I think I've convinced myself that the G6 (US997) is my next phone, but now is a silly time to buy as the price should drop like a rock as the next wave of flagships come out.
I'm hoping to make it another couple months and was wondering anyone's experiences moving from Cloudy G2.2 (or other ROMs) to the latest lineage? From what I've read, it's very stable. However, I'm on Kit Kat bootloader, so it doesn't seem like this will be a straightforward process. I was hoping to get some experiences from people who made the same move before starting.
I currently have:
LG G2 D800
Root using stumproot (I think, it's been a while) with supersu installed
TWRP 2.7.0.0 installed by autorec
Cloudy G2.2 KOT49I

So, after some research, I set off to install LineageOS. In hindsight, this might have been a bad idea since it specifically only mentions the D802 in the title. However, it listed links for D800 builds, though they were crossed out.
I updated TWRP to this version by Blastagator and that was painless. I then wiped the phone, made a fresh backup and flashed the latest nightly of LineageOS, and the latest GApps (Mini) for 7.1. That was disappointing since I got the quick "LG logo" followed by a blank screen, that I later found was mentioned in the same Lineage post. Should've read farther.
I think the issue is that I'm on the wrong bootloader. I thought I was on KitKat which the post requires, but in order to enter recovery, I have to press enter three times (rather than using volume buttons to navigate), which indicates I'm on JellyBean bootloader.
So, this is the scary step that I was hoping to avoid. My big fear is that I run Linux on my desktop, so I can't use the LG Flash Tool. As long as I can keep a working recovery, I have backups, so I'm fairly safe. Following the Blastagator bootloader post, I'm not really sure how you go back and forth between bootloaders so easily as it suggests. Is that really as simple as loading the zip file on the phone and installing it in TWRP?
Is there a safer way to handle this?

From my experience, it is that easy. Simply install the zip file and you have loaded a new boot loader. Also, I was in the same boat as you with Cloudy rom and moved to Nougat with crDroid. However it's not stable and I am considering looking for something else more stable but fast like crDroid.

ernie young said:
I was in the same boat as you with Cloudy rom and moved to Nougat with crDroid
Click to expand...
Click to collapse
When you updated your bootloader, were you still able to run the Cloudy ROM before you switched to crDroid? Once I flash the KitKat bootloader, am I only able to use the Nougat ROMs? My big concern is that there might be something a bit off with my bootloader, so I won't be able to get back to TWRP.
I think there's something a bit off with my bootloader as is, because about a year ago I flashed back to stock Jellybean, and took all the OTA updates. However, when the phone tried to take the KitKat update, it softbricked, and could only be recovered using the LG Update Tool, which I don't have access to anymore. Because of this, I'm a little worried that just dropping on the Blastagator KitKat bootloader may have some atypical issues.

i m using it for a while. u know, on Los you won't be able to use lg features such as qslide, qmemo, plug&pop, knockcode etc. Only worth it if you want your phone to look a little bit fresher and lighter or you need a newer android version for some reason. Else, don't take the risk if you can't use flashtool. You can consider installing another kitkat rom. There are lots and they are nice :]

S YILDIRIM said:
or you need a newer android version for some reason.
Click to expand...
Click to collapse
My primary issue is that KitKat (or whatever Cloudy G2.2 is?) has the old Android bluetooth bug where once it sees too many devices, it stops connecting to anything. I have to make sure to turn off my phone if I go somewhere like an airport, and have been having to restore my clean Cloudy backup about once a month. It's getting pretty frustrating. On the other hand, I'm hoping to upgrade to an LG G6 (US997) in a month or two when the V30 release pushes down on prices. So, if it's a case of potentially hard-bricking my G2 at the worst possible time, I should hold off flashing.

I think you need hybrid bootstack for android 7.

WORF84 said:
I think you need hybrid bootstack for android 7.
Click to expand...
Click to collapse
That makes sense, but will I not be able to use my Cloudy 2.2 backup after that? It says that the hybrid bootstack will only boot CM 12.1, CM13, and LP stock roms.

superlou23 said:
That makes sense, but will I not be able to use my Cloudy 2.2 backup after that? It says that the hybrid bootstack will only boot CM 12.1, CM13, and LP stock roms.
Click to expand...
Click to collapse
These questions if this works with that or that are easier to answer for yourself by reading what goes with what.
Just Google LG G2 bootstack and you can probably find the ones you need for any available rom.
I use hybrid on Marshmallow 6.0.1 but I tried Nougat 7.1.2 too, it works.

Want to find a fix to all custom ROM's bootlooping on my SM-J320FN (did not bootloop before)

Want to find a fix to all custom ROM's bootlooping on my SM-J320FN (did not bootloop before)
[
or alternatevly, i was wondering if modifying a some samsung galaxy SM-J320[something] nougat rom, to work on SM-J320FN would be possible (it has only android5.1.1 (lollipop) stock rom as far as im aware and i have searched quite a lot).
]
The thing is, i have the SM-J320FN (twrp and rooted) and for a while i ran various custom roms (based on nougat) on it with no problems. But then about a year ago it bootlooped on resurrection remix (which i had ran with not many problems for 1/2year). Then every custom rom (i tried RR, DotOS, ViperOS and more) began to give me a bootloop, only flashing the stock rom booted.
I wiped and formated everything i could, tried same country stock rom that i had originally and a different country one (thinking maybe the custom roms were not happy with something inside the stock rom that it was flashed after, but logically it does not seem even possible, as before flashing the custom one, the old one is wiped), but custom rom's just did not boot anymore. I could not log the boot either because it had boot animation but nothing showed in adb, i guess it did not get so far that it could connect with adb.
I suspect this may be caused by my camera not working (some hardware part most likely got damaged), because i think wiping my phone completely and flashing stock rom with Odin should restore every software part on the phone thus it would have to be something with hardware that's causing custom roms to bootloop, how else could the problem persist (i obviously might be wrong).
I don't remember when exactly the camera stopped working but i know for a fact that i had a custom rom at the same time, and it did not bootloop (for some time at least) and im also curious why this has not ever stopped the stock rom from booting if it is the case.
So basically what i wish i could do are two things. Firstly find what makes the stock roms able to boot correctly opposed to the custom ones. And secondly implement this to a similar models higher version rom or a custom rom (Nougat). Come to think of this, it seems a useful step to look how did the people that made these Nougat based rom's for SM-J320FN modify the rom so that it could run on it, the source code is open after all.
Why i want to have a higher android version on my phone? Because my countrys corona close contact detection app supports only 6.0 or higher and my banking app recently notified me that they will soon end support for my android version too (this is the real pusher for me as i use it very frequently and there is not really an alternative). And it would be nice to have some other apps too, that not compatible with Lollipop.
And yes, i know, just buying a newer phone would solve all my problems But im a minimalistic (and without money) person. The fact that i own a phone that is still working (or fixable) stops me mentally from buying a new one. Also as one would guess, i like tinkering with this kind of stuff (i study CS currently) and building a rom myself for my phone sounds like a cool and challenging project, as i have not done anything like this before (maybe this will help me: [guide]how to build/modify roms for samsung devices [7.0/6.0.1/maybe more]).
Anyways, i kinda got carried away with this post. But for now im tired and have to sleep so i'll just post this and will come back later to read this over, fix some mistakes (not a native english speaker) and add things i maybe missed.
If anyone read this through, im impressed and if you have the knowledge/time to answer then i Thank You in advance!

i need help i tried to install re dreaux but my phone bootloop on touch wiz custom rom so how can i fix that

Last call...

I went ahead and got my unlock code today. But before I go for a custom ROM...
I noticed twrp had a few more releases...nothing new for the A/B slotted G7 I assume?
Let's say I don't need or want backups...is there ANY path to a stable root with Magisk??
I'd soo much rather have a Magisk root vs. a custom rom. Is there any hope?
I'm seeing so many contradictions of what I know or think I know...I'm pretty confused tbo.
Tia...

Twrp for 11?

Hey guys,
Anyone have any info when either unofficial or official twrp is coming for Android 11? I made the mistake of upgrading to 11 from 10 then tried flashing twrp which bricked my phone ( I fixed it, no biggie ). I just really want to flash a custom ROM and I can't find any other custom recovery that will do that and side loading twrp also gives a crashdump error. Unless anyone knows how to downgrade to 10, the the furthest downgrade I've achieved is 11.0.0, once I hit 10.x.x I get either a black screen or crash dump.
It's a lot there, I know. Much appreciated everyone.
Edit: reading more on this forum, I think I found a way to flash a custom ROM on Android 11.. I guess you can side load roms? So I guess I'm going to give that a try. I'm so old school, like back in 2011.

I had the same problem. Im using the Lineage recovery atm an idk why tbh. I think i used it for rooting and for now im only using magisk modules to obtain some featurers.
Sideloading roms is a thing but man i miss those old HTC Hero., HTC Desire times. Last years i was using a P30 pro without root and im so happy to have root again.
Anyway read carefully and have fun. I would love some answers from your experience here.

Do0ks said:
I just really want to flash a custom ROM
Click to expand...
Click to collapse
Most custom roms include all the files needed to flash the entire rom from a batch file. CrDroid for sure, but also Lineage. I'm sure there are more. My issue is not flashing, it's that all important nand backup from TWRP I miss the most. Switching roms is a lot more tedious when you have to re-install everything to revert back to your old setup.

Twrp for 8 and 8 pro may not happen ever, encryption is the problem

TWRP doesn't look promising considering the time that has passed since 8 launch...