yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
[MENTION=5564873]WesTD[/MENTION], I'm using this on an A2017G. you gave me a pretty good scare: if the internal storage is encrypted, the phone just turns off and flashes orange three times just like a DFU brick. After getting into TWRP it asked for a password, so I had to format data, but in turn i lost my internal storage stuff. It would be nice if you added a disclaimer...

Another thing, I can't seem to be able to make Google stuff work. I unfroze them and they didn't work, then flashed openGApps, nothing, tried that app you linked but don't understand what to do with it (it's all in Chinese :eek: ) Can you help me a little?
[ZTE Axon 7 Guides, News, & Discussion] WesTD:
First of all, I'm sorry for the inconvenience you've experienced. I am using U model and never get like these problems. I tried on my friend's G model and it worked well on him too.

So I did not feel the need to add a disclaimer but i'm adding now first post.

Steps on OP are enough to use this ROM on device properly. Just you need to download Play Store or other Google stuff which you use from apkmirror or somewhere else.
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
Not mad or anything, I just wanted you to know that encrypted internal storage + this ROM isn't a good combination

I still can't make google apps work. I uninstalled all of the Google apps, then installed the apkmirror ones (services 440, framework, play store) then used the Chinese google app, pressed on Go, it did something, the 4 apps appeared as green, rebooted just in case, and still the play store doesn't even open

I also have the double vibration bug on almost everything (hard keys, on screen keys, lots of buttons) and I recall that's from the kernel. I don't even know if there's a custom kernel for the A2017...

Edit: Whatever I'll try B06 from the other post
[ZTE Axon 7 Guides, News, & Discussion] supergear:
Not for me.

---------- Post added at 08:41 AM ---------- Previous post was at 08:38 AM ----------

To get this ROM to work on my 2017U I had to install a custom kernel. Hybrid one I forget its name. I used the play store in the link and waited awhile for it to upgrade itself
[ZTE Axon 7 Guides, News, & Discussion] wedelltd:
he asks me after as android password on the first boot, what can i do?
[ZTE Axon 7 Guides, News, & Discussion] WesTD:
Try to format data
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
makes little sense to use this ROM after B06 came out...

The good thing is that if you have it installed you can simply go to TWRP and flash the B06 zip by ronks and nothing else, and it works. Since you have already installed the bootstack and everything it's the only thing you have to do

Also if anyone needs to install Gapps and they don't work, I shared an app on the B06 thread like the one on the OP of this thread, but that one was the only one that worked. jus saying
[ZTE Axon 7 Guides, News, & Discussion] wedelltd:
Got it

factory reset and format

Thanks
[ZTE Axon 7 Guides, News, & Discussion] JvDsN:
Is that rom is good ? what is the diference ?
[ZTE Axon 7 Guides, News, & Discussion] omariscal1019:
still cant get it to work on u version
[ZTE Axon 7 Guides, News, & Discussion] KwesiJnr:
Can you mention exactly what the problem is? I used not to get it to work, too. Everything flashes, but can't boot. Now it works, so elaborate and I may be able to help.
[ZTE Axon 7 Guides, News, & Discussion] omariscal1019:
I started fresh. Flash b19 edl mode. After i setup phone. Then flashed twrp 3.1.1.0. Then followed instructions flash b15 bootstack from first post then proceed to restore like the instructions say and it never booted.

I also tried after i updated to b25 and still no boot.! Maybe its the twrp version which version are you?
[ZTE Axon 7 Guides, News, & Discussion] WesTD:
Here is another ROM. Try this one.

https://forum.turkdevs.com/konu/mifavor-5-0-b08-zte-axon-7-rdx-rom.13660/
[ZTE Axon 7 Guides, News, & Discussion] KwesiJnr:
Yes, it used to be the same with me. This is what worked for me.

From B25,

1. Booted to TWRP, wiped only System (to keep my apps and data intact), Dalvik & Cache.

2. Flashed the B15 bootstack fix, then did the System+Boot restore with the attached package.

3. With system mounted read-only, flashed Magisk for root, then flashed opengapps also to get Play Store and some core Google apps working right off the bat (later unfreeze when the phone boots).

After all these steps, the phone didn't boot and went straight into EDL mode (red LED flashes 2 times)

So I proceeded to flash the A2017U_B19-NOUGAT_TWRP_EDL from this thread with MiFlash.

Once it was done flashing with the green "Success" message, I long-pressed the power button to exit EDL mode and it worked. The phone booted and I'm now on MiFavor5.
[ZTE Axon 7 Guides, News, & Discussion] omariscal1019:
:good::good::good::good::good::good:

finally.... i did ur steps it would boot to zte screen only then reboot... after i realized it maybe kernel related so then flashed that hybrid kernel going round and it booted thanks i appreciate alot.
[ZTE Axon 7 Guides, News, & Discussion] KwesiJnr:
You're welcome, bro. :svetius:
[ZTE Axon 7 Guides, News, & Discussion] WizeMan:
Is there any difference from the OP guide I should follow for an A2017G ?
[ZTE Axon 7 Guides, News, & Discussion] marcus.linkenbach:
No, I did it the same way. The only thing I faced was that I couldn't get root. After installing supersu or magisk it wouldn't start. Stopped continuing booting at the colored axon screen.
[ZTE Axon 7 Guides, News, & Discussion] MahathirMohamad_:
When I wanted to restore the ROM, it only showed System only. It didn't show Boot but it still manage to run the ROM. During the setup process, it couldn't search for any wifi. Is there a fix to it? And the Camera app keeps crashing. Will flash back to Lineage till this problem resolves. I love the UI.
[ZTE Axon 7 Guides, News, & Discussion] WesTD:
https://forum.turkdevs.com/konu/mifavor-5-0-b08-zte-axon-7-rdx-rom.13660/#post-153277

use this guide if you couldn't boot this one.
[ZTE Axon 7 Guides, News, & Discussion] WizeMan:
Also had this issue. You must reflash a compatible TWRP image for the Axon 7. If you see the TWRP version you have now, it probably is 3.0N-1 or something like that. Flash 3.1 image from within TWRP, reboot into recovery and you will see the boot partition.

Generally speaking, the ui changes are good, but not as good to come into that trouble. Battery usage is ridiculously bad and still Mi Favor needs lots of improvements to be my daily driver (e.g. support for notification badges on all apps etc).
[ZTE Axon 7 Guides, News, & Discussion] kerim9967:
Yes working.

try this

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[ZTE Axon 7 Guides, News, & Discussion] joeanca:
Hey [MENTION=5564873]WesTD[/MENTION], thank you for your contribution.

The second link you provided through google drive isn't working. Any way you may update both main links in the main post for the newest versions? I have a U version and want to make sure I do this right.

Thank you very much!
[ZTE Axon 7 Guides, News, & Discussion] WesTD:
You can try this guide.

https://xdaforums.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
[ZTE Axon 7 Guides, News, & Discussion] renatop:
Does this break my warranty?
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
Lol

Unlocking your phone "voids" your warranty. so yeah. but you can go back to stock completely and relock (VERY dangerous, will brick your phone if not everything is stock!) and ZTE will not even notice.
[ZTE Axon 7 Guides, News, & Discussion] raystef66:
Same here.

Testing the new B13 MF5 with bootstack B15. All ok and booting.

But when flashing SU or Magisk, no boot. Stopping @ tile screen...

Anyone have a solution for this ?

Much appreciated :good:
[ZTE Axon 7 Guides, News, & Discussion] Predatorhaze:
mifavor 5.0 is so ugly..nonono
[ZTE Axon 7 Guides, News, & Discussion] joaste:
May not be relevant now, but try the universal bootloader.
[ZTE Axon 7 Guides, News, & Discussion] raystef66:
Hehe indeed joaste :o

That was before i made my own MF5.0. I figured it out then.

As you said B15 Universal can do no harm on the contrary.

But in my new ( you know already ;) ) i've an adapted B13 and B15 adapted too. So far tests are ok. No FC on maps, hangouts,....

But then again, MiAssistant plays a crucial role in here.

All in all, this MF5.0 reacts different on all models, even on the same model the outcome maybe different as you and others could notice.

But i hope my new one will bring at least more stability :cyclops:
[ZTE Axon 7 Guides, News, & Discussion] sudeep_hm:
managed to install followed all the instructions. but no network shown.. what to do now ? please help.
[Nexus 6 Q&A, Help & Troubleshooting] .me:
Hello,

Tried all 7.x ROMs - and I am struggling with instagram videos are very choppy (the snapchat style ones) as well as camera crashes or buffer gets full.

Tried a number of kernels too

Any advice on how to fix that?

cheers
[Nexus 6 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
Stop using Instagram?

Seriously, you don't give enough information for anyone to really help you. For example, you mentioned trying all Android 7.x ROMs. Did you try going back to a stock ROM as well? Did you actually search the forum to see if other people have had the same issue? Did you provide a logcat so someone on XDA could attempt to troubleshoot the issue?

Gut instinct is telling me you have a hardware problem, i.e. a failing camera. Your first thing is get yourself back to a stock ROM and see if the problem occurs there. From there, you need to see if others have the same issue, and then you need to post a logcat.
[Nexus 6 Q&A, Help & Troubleshooting] .me:
Thank you. Will start from that

Thanks for a long reply
[OnePlus 3T Questions & Answers] mobilityguy:
I've been all over the OP3T forums looking for current information about the correct versions of TWRP and (Magisk or SuperSU) to use with stock OOS 4.1.6. I kept my old TWRP 3.0.4-1 and when I tried to apply SuperSU 2.79 SR3 I got an unusable system and had to restore from nandroid backup. I updated to TWRP 3.1.1-2 as per the Official TWRP app and now every time I try to reboot to system from TWRP it warns "No OS installed", but the reboot works fine. I have Magisk 13.2 ready to install but I'm reluctant until I know I have the right combination - the TWRP 3.1.1-2 backup is missing some partitions and I want to make sure I can at least recover my system if Magisk screws things up.

I've been all over the forums and all the relevant threads were closed months ago, or are written about OOS 4.0.3 or 4.1.1, or describes some hideous way someone turned their 3T into a pile of molten lava. Is there any current information about what combination of TWRP and a root zip will work with the latest OOS 4.1.6? Everything is stock except the unlocked bootloader. I don't want to flash a different ROM, I don't care about passing SafetyNet, I just want to root and go on with my life.

A couple of numbers is all I ask. I can't be the only one. Please - I've been without root for a week and it's bugging me.
[OnePlus 3T Questions & Answers] Didgeridoohan:
TWRP 3.1.1-2 has got at least one major bug where it reports the OP3T as a OP3. That'll mess up your OP3T specific installations... Don't know if there are any other bugs, since I'm staying on 3.1.1-0 until they fix that bug. You also have the option of using blu_spark's TWRP. I've never tried it, but many users swears by it.

What works for me:

OOS 4.1.6

Franco Kernel r25

TWRP 3.1.1-0 (official)

Magisk v13.2

Magisk Manager 5.0.6

No issues whatsoever (for me)...
[OnePlus 3T Questions & Answers] mobilityguy:
Thanks for that. I'd rather not change kernels, though. How likely is it that the same combination works with the stock kernel? Does anyone have that running?
[OnePlus 3T Questions & Answers] mobilityguy:
OK, I tried it. Swiped the Magisk 13.2 zipfile in TWRP. The script ran partway through and then said "Can't mount system" in red letters. Now the phone boots into OOS, Magisk Manager is there and says "Rooted but no root permissions, not allowed?" It has reported several times that it needs to update, to the same version of Magisk and Manager that are already there. I allowed it to go through the cycle and reboot, with no change to behavior. When I try to run an app that needs root I get the permissions screen, but when I grant I get the dialog that says "Rooted Android required" - Either the su binary could not be found or you did not allow root permission..."

So, the phone works fine but unprivileged as before. I'd like to try clearing the cache, but since TWRP still reports no OS found (3.1.1-0 does this, just like -2) I don't really want to write into a system the recovery can't see. Besides, the existence of the su binary doesn't seem like something a cache clear will fix.

Advice?
[OnePlus 3T Questions & Answers] mobilityguy:
Scratch that request. Things seem to be turning around - su works in terminal emulator, lets me ls privileged directories like /data. Root Explorer is working again. The only thing that isn't is AdAway, which can't write the hosts file. Otherwise the system seems to be rooted and working OK.

I'm still nervous that TWRP can't see that there's an OS on the phone, and I haven't seen any other reports of this.
[OnePlus 3T Questions & Answers] mobilityguy:
It looks like Magisk can't mount /system read-write. Adaway won't install, and neither will Busybox. Titanium Backup also reports problems. I tried installing Busybox and the installation failed when it tried to remount system /rw.

Will look for solutions to this problem and report back here.
[OnePlus 3T Questions & Answers] mobilityguy:
I've found many solutions to this problem, like installing busybox (Stericson Busybox apparently doesn't work in OOS 4.1.6, tried two others. Problem is, busybox will only install into a partition on /system, which requires that /system be read/write.
[OnePlus 3T Questions & Answers] JMB2K:
When I have issues with mounting system or anything like that, I go mount system myself in TWRP and it usually starts working after I reboot....I don't know why, it just works for me....if I see that error, that's the first place I go, everytime...
[OnePlus 3T Questions & Answers] mobilityguy:
That won't work either. When I go to the Mount page in TWRP I can't get the checkbox next to /system to check. It just stays empty.
[OnePlus 3T Questions & Answers] JMB2K:
I seem to remember having that problem once before.... Can't recall what I did, I think it involved something with the terminal... I'm not at my desk right now, I'll look into it shortly and see if I can remember
[General Questions and Answers] Sajid7890:
Mobile → Symphony V42

OS → Marshmallow 6.0

CPU → QUAD CORE Cortex A7

Kernel → 3.10.65

Pls anybody give the recovery.img file for my mobile. or suggest me how can I make it manually and easly pls pls
[General Questions and Answers] Ayub.123:
I created TWRP for this device. But touch not working in TWRP.
[Nexus 6 Q&A, Help & Troubleshooting] espionage724:
I want to unlock the framerate globally (for apps that don't have a hard-set limit), and I don't care about potential screen tearing or increased power usage/heat. How can I accomplish this?

The following props together or separately don't work:

debug.gr.swapinterval=0

debug.egl.swapinterval=0
[Nexus 6 Q&A, Help & Troubleshooting] lolvatveo:
don't use disable.egl.swap, screen image can teering
[Nexus 6 Q&A, Help & Troubleshooting] JustanAnonymousGuy:
I've been searching lately for a way to disable Vsync on Android. Just as in Windows, I don't really care about tearing, I just want the fastest possible response time. If anyone finds out if this works, please tell me. 🙏
[Nexus 6 Q&A, Help & Troubleshooting] lolvatveo:
egl is hsync, but in this case we don't care about hsync 'caz it not lock fps and not make gpu work harder, hotter and slower. this is my useful prop for qualcomm cpu device:

debug.sf.hw=1

debug.egl.hw=1

debug.gr.swapinterval=0

debug.egl.profiler=1

debug.performance.tuning=1

persist.hwc.mdpcomp.enable=true

debug.mdpcomp.logs=0

dalvik.vm.heapsize=36m

dev.pm.dyn_samplingrate=1

persist.demo.hdmirotationlock=false

debug.enable.sglscale=1

some additional prop

ro.debuggable=1

dalvik.vm.dexopt-flags=m=y,o=v,u=y

dalvik.vm.verify-bytecode=false

dalvik.vm.dexopt-data-only=1

dalvik.vm.checkjni=0

dalvik.vm.checkjni=false

dalvik.vm.check-dex-sum=false

dalvik.vm.jniopts=warnonly

dalvik.vm.jmiopts=forcecopy

dalvik.vm.execution-mode=int:jit

dalvik.vm.lockprof.threshold=500

dalvik.vm.stack-trace-file=/data/anr/traces.txt

video.accelerate.hw=1

persist.sys.ui.hw=1

persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb

persist.cust.tel.eons=1

debug.composition.type=gpu

debug.egl.profiler=1

debug.qc.hardware=true

debug.qctwa.statusbar=1

hwui.disable_vsync=true

hw3d.force=1

hw2d.force=1

ro.config.disable.hw_accel=false

ro.secure=0

ro.product.gpu.driver=1

com.qc.hardware=1

ENFORCE_PROCESS_LIMIT=false

ro.ril.sensor.sleep.control=1

ro.ril.set.mtu1472=1

ro.config.hw_power_saving=1

ro.config.hw_fast_dormancy=1

ro.config.hw_quickpoweron=true

persist.sys.use_dithering=0

pm.sleep_mode=1

htc.audio.alt.enable=0

htc.audio.hac.enable=0

not work? try debug.hwui.disable_vsync=true and disable vsync via terminal, find your vsync driver in /sys/kernel/debug (I'm ZArchiver)

echo 0 > /sys/kernel/debug/clk/vsync_clk_src/enable

echo 0 > /sys/kernel/debug/clk/gcc_mdss_vsync_clk/enable

echo 0 > /sys/kernel/debug/tracing/events/power/cpufreq_freq_synced/enable still not work add ' or " echo 'value': echo '0' and run command again

then use fps test app to check https://play.google.com/store/apps/details?id=com.wt.fpstest

warn: try each property to make sure your device not stuck at boot logo with some
[Xperia Z5 Accessories] sceryavuz:
I am looking a QC 2.0 supported charging dock station. Any advice?

Sony release DK52, but did not support QC 2.0 and it was not well producted.
[Xperia Z5 Accessories] icedlemontea:
You can probably buy any generic micro-USB dock and use a QC2.0 charger as they all accept the micro-USB power input anyway....
[Xperia Z5 Accessories] sceryavuz:
No. It doesn't support qc 2.0 with this way. Output is important for this..
[OnePlus X Q&A, Help & Troubleshooting] PlsHelpMeee:
When i was updating the twrp i managed to hard brick my phone, it just shows the 1+ logo and "powered by android" when turned on. if i hold the power button and volume up it shows the cyanogenmod logo and "fastboot mod" and stays there. If i hold power button and volume down it just shows the 1+ logo without the "powered by android".

i followed this guide https://xdaforums.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108

completed all the steps but the installed program cant recognise my phone when i plug it in.

When its in fastboot mode logo i can see it in device manager under portable devices listed as "ONE E1001" (it has a yellow ! triangle next to it)

When i try to turn the recovery (powerbutton+volume down) where it shows just the 1+ logo with no "powered by android" i can see it in the device manager under android phone as "Android Bootloader Interface"

When i just turn it on where it does display "powered by android" i can see it same as in fastboot mode, as "ONE E1001" under portable devices, (a yellow ! triangle appears after some time too)

i tried a similar guide here: https://xdaforums.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851

did everything, i have like 5 driver now from all the guides, i think all of them work, i just cant manage to get the programs to realize when the phone is pluged in. Is it possible that something is still wrong with the drivers?

pls help );
[OnePlus X Q&A, Help & Troubleshooting] Kéno40:
You're talking about Cyanogenmod logo. What was on your phone before? What did you do exactly?

Are you sure you know how to use Fastboot?

"fastboot oem device-info" output?

And then explain precisely at what step you have error.
[OnePlus X Q&A, Help & Troubleshooting] PlsHelpMeee:
i had CM12 before i tried to upgrade, i managed to go through the entire first guide now, the CM logo isn't appearing anymore, now its the 1+ logo and below it "fastboot mode" the drivers were a problem after all

now im stuck at the new recovery that is installed and cant install the ROM from it, even my old one that i had before all of this (CM12) that i have on my sd card.
[OnePlus X Q&A, Help & Troubleshooting] Kéno40:
OK, so you flash something incompatible.

After CM13 or so, the bootloader have to be upgraded and then you have to use a version compatible with it.

First look with fastboot command I give if BL still unlocked.

Do you know how to use fastboot commands?
[OnePlus X Q&A, Help & Troubleshooting] PlsHelpMeee:
kind of, "fastboot oem device-info" output is

(bootloader) Device tampered: true

(bootloader) Device unlocked: false

(bootloader) Charger screen enabled: false

(bootloader) Display panel:

(bootloader) console_enabled: 0

(bootloader) exec_console_unconsole: 0

OKAY [ 0.010s]

finished. total time: 0.011s

if i could install the twrp from here i could install the ROM too i think, is there a guide to do so while stuck like this?

"fastboot oem unlock" gives me

FAILED (remote: oem unlock is disabled)

finished. total time: 0.009s

i cant use adb commands, in the command prompt my computer doesent even see the device when i type "adb devices", i think its because oem, debuging, isnt turned on but i cant turn it on if i cant install a ROM and check it "on" in the settings of the androis OS.

all i can use are fastboot comands since my computer can see it as a fastboot device while not as a adb device. i have a bricked phone with a locked bootloader i think.
[OnePlus X Q&A, Help & Troubleshooting] Kéno40:
BL is locked so only solution is mega unbrick guide.

I never tried but oos 3.1.4 won't flash either...
[OnePlus X Q&A, Help & Troubleshooting] PlsHelpMeee:
i did the mega unbricked guide, this one ==> https://xdaforums.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108

i have the recovery dom the guide installed but it cant install any ROMs or the twrp, im trying to install them over fastboot but it also cant be done because my device is locked and i cant flash anything remotely. I also cant use adb for some reason because the command prompt cant see my phone under "adb devices". is there anything i can install with that recovery? i just stuck, spent so much time and still nothing :crying:

i think adb devices dont show because usb debugging is not turned on, i dont know how it can be turned on without and actual operating system on the phone..
[OnePlus X Q&A, Help & Troubleshooting] Kéno40:
THis guide push you back with OnePlus recovery and OOS.

That's not what you have?

You did something wrong...

At which step does it stop?

A few day ago, one of the file ws missing. Do you have it all?

---------- Post added at 10:43 PM ---------- Previous post was at 10:43 PM ----------

THis guide push you back with OnePlus recovery and OOS.

That's not what you have?

You did something wrong...

At which step does it stop?

A few day ago, one of the file ws missing. Do you have it all?