yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
Did you guys used it?there is really no pro in saving battery life with smartpixel on.Sot stays the same
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] troy5890:
I've used it quite a bit when it was available and it saved me some good screen on time. Leaving it on, I made it through the day with 47% left instead of 32%
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xShottaZx:
So far so good. But i cant find the Option to invert the menu and back button... And i dont usw navbar. Can you tell me where do i find it and if not, how do i fix it?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] atmos929:
Oh!... oh!... my phone fell from my lap and screen was like this for a day... I just started hitting it from the other side and it fixed and hasn't happened ever since, I did suspect some loose cable connector.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Tuxiee:
Is anyone able to turn on the smart pixel setting? I can search for it and it shows up under 'battery', but I can't find the actual setting itself.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
there's actually no need to rely on smart pixels... You can use Pixel Filter which is basically the same crap only with the ability to make your own filter patterns (useful to turn more than 50% off without having too much color shift)

Only cons are that it gives a trippy effect when you rotate the screen, and you have to disable it when you want to sideload apps
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
Hello all,

Looking for help to help insure I don't screw up my phone.

Now that we're in the new year I'm thinking of updating and I must say I haven't had much luck with that on my axon 7.

A2017U w/ bootloader unlooked

TWRP - 3.2.1.0 - Do I need to update?

In recovery flash

1. A2017UV2.1.0B20v01_Bootstack_by_DrakenFX - is this the correct bootstack?

2. A2017U_OreoModem

3. Wipe - system, data, cache, dalvik, vendor

4. Flash dotOS-0-v2.5-Axon7-Unofficial-2018113

5. Open_gapps-Arm64-8.1-nano-20181229

6. SuperSU-v2.79 or v2.65?

Are these the proper steps and files I need to run this ROM? Am I missing anything?

Any help would be greatly appreciated thank you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
Hey! Glad you're up for the update. As far as I can see, you've gotten all the steps correct. Before you do anything, first make sure you make a vendor partition. This can be done with this tool. Simply flash the PARTY zip in TWRP, and select the options > Create vendor > 512 MB > From the END of the SYSTEM partition. After that's done, reboot to recovery and flash the latest version of TWRP here. Reboot once again to recovery, and then you can follow your steps. Use this bootstack instead of the v1 you've written. Also, a tip. I'd recommend using Magisk 17.3 for root, but you can also use SuperSU. I'm glad to see that you've done your research, that's always good.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
Wow thank you so much

I'm sure glad I asked and you responded

I'll be doing some more research and downloading

I suppose I need to learn Magisk sometime so I will attempt it

Thanks again!!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Tuxiee:
I never used the turning pixels off feature of smart pixels. I used the 'move display every x seconds' to avoid burn in, which was in the 'smart pixels' menu.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
and what do you think that option does?? ??

FYI, it moves the pixel filter one pixel to the side... If you have a 50% filter, you have half of the pixels off, hence you need to switch to the pixels that were off after some time to allow for consistent degradation (not that you would notice if it degraded unevenly though). Using that option by itself does nothing
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
Delete
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
Try this again for safety reasons. Heading out of town next week so I'll hold off till I return...just in case.

Anyhow hows this look for updating:

1. Recovery - flash PARTY_v0.5 zip

2. Using FLASHIFY flash recovery image TWRP 3.2.3-0 - not sure about this part???

3. Recovery - flash universal bootloader v2

4. Recovery - flash A2017U_OreoModem

5. Recovery Wipe - system, data, cache, dalvik, vendor

6. Flash dotOS-0-v2.5-Axon7-Unofficial-2018113

7. Flash Open_gapps-Arm64-8.1-nano-20181229

8. Flash Magisk 17.3 - never played with Magisk before so this will be interesting

Thanks for any assistance as always :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
Everything looks great. As for flashing ver 3.2.3-0 of TWRP, all you need to do is reboot to twrp, go to install, select flash image from bottom right corner, and select the .IMG file of twrp, and flash it as recovery. That's it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
Unfortunately I can not longer boot to any recovery after step 2.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
That's strange, I'm not sure what might be causing that. Can you still access the OS or boot into fastboot? If you can still boot into system, then luckily you're not in too much trouble.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
Thankfully system works :)

I'm going to try adb on my computer this weekend and see if I can reflash the TWRP img.

Oh well!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
For some Reason my USB debugging was off...do you think that could have caused this issue?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
Adb didn't even work.

No recovery what's so ever.

Phone still works that's good.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
For ADB, Use 15 second ADB installer (Google it) and install it on your computer. Enable USB Debugging and connect the phone to the computer. Allow permission for USB debugging when it prompts you on the phone. Then open up a command prompt window and type 'adb devices' to check if your device shows up. After that, you can either do 'adb reboot edl' and use the Axon 7 EDL Tool by djkuz (find it in the forums) to flash recovery again, or flash the twrp img straight from ADB.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
Thanks for trying

Any attempt to get to edl or bootloader the phone just turns off.

Thought I'd lost my phone once ! Thankfully it's not dead.

Bummed ☹️ but not broken... completely.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
When the phone "switches off" whilst you're trying to put it into EDL, can you open Device Manager on the computer and under Ports , check whether it says Qualcomm EDL 9008 or DFU?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
I see it as A2017U

I kind of remember some of this. I tried updating my driver but I don't think I did it right

I'm trying to get it to say EDL 9008 correct?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
Yep, when you type adb reboot edl, the phone screen should go completely black and in Device Manager under ports, it should Qualcomm edl 9008 or anything of that sort.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
Thanks I'll work on it more later.

I know I have that stuff on my work PC so hopefully I can get it done!

Thanks again for sticking with me.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
Sounds to me like you have messed up things when installing the drivers.

Connect it up to your PC and uninstall the driver in device manager that shows A2017U.

Then unplug the phone, reboot your computer and follow the steps here: https://xdaforums.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413

Make sure that you uninstall any previous driver packages or mi flash versions before following the guide and only use the drivers and the miflash version mentioned in above guide.

Once you are on the nougat release in that thread (for A2017U) you can take it from there.

If it doesn't work, try using a different computer and/or USB port, if you are using USB 3 ports this can especially be a problem with some computers.

EDIT#

A much easier way would be just to use a micro SD card and just do the official oreo update direct on the phone: https://community.zteusa.com/discus...rd-only-axon-7-a2017u-now-on-android-oreo-b20
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
Running hamster and Dodgexander thanks for the help.

I did some experimenting last night and fixed my recovery using Flashify. App is pretty cool.

I must have had a bad download (always check my MD5s). Anyway wanted to let you know if you see anyone else in the same boat as I was in Flashify fixes it and it's super easy to use.

Thanks again.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ls117:
what dolby zip am i supposed to flash? was expecting someone to have posted it by now, i'm assuming the ones in magisk wont work. already followed the old flashing order from the edl thread by oki, but dolby just crashes.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
Try this https://xdaforums.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ls117:
the recorder app doesnt seem to work either. i reset my phone and im gonna try and get dolby working, but the recorder wasnt working before and isnt after a clean flash either.

****

so dolby just won't install. the latest one in that thread doesnt work, give me an error.

data/adb/magisk.img mount failed

the dolby zip from this thread flashes with no problem but crashes when you try to open it

https://xdaforums.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693

v4a works fine but between the recorder app and dolby not working, i can't stick with this one.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] to1ya42:
This is a best Axon ROM I ever seen, big thanks for this experience! I love this v2.5 special ROM a lot

Is it possible to upgrade by custom kernel or something else to improve battery life?

Everyone who have came from another stock oreo rom and have problems with installation, just put this ROM on sdcard with needed twrp.img , and make a full wipe, wipe encryption data, then flash zip with twrp, rom, magisk and etc.

Im not advanced user and can be fully incorrect, but it's made my day yesturday, please correct if i was wrong
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HunterBlade:
So I'm currently on NFound's final release of AEX and I'm thinking about maybe switching to this mainly because of the Pie-like interface and more recent security patch (Nov. instead of Sept.), but I do have a couple of questions that I was wondering if anyone who's using this ROM currently can answer:

Does VoLTE and WFC work on this ROM?

I saw on the front page that this was considered a "normal" ROM with a built-in vendor partition. Does this mean I have to un-treblize my phone before installing the ZIP or will it automatically skip that step if I already have a vendor partition?

Is this ROM & vendor combo able to lower the screen brightness all the way to 1? I know in NFound's case, it isn't possible without Kran's overlay patch, which I don't think will work with this vendor since it's LOS based.

Is there an option to customize notification light on a per-app basis like what LOS and AEX has?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
1. No.

2. No, all you need to do is wipe system, data, cache, dalvik and vendor, and then simply flash dotos zip + gapps. All you need before hand is a vendor partition. This applies to all treble ROMs.

3. That option isn't currently on any ROM, you'll need Kranoner's overlay to do it. So far I'm not sure if it works on dotos, you'll have to try it out.

4. Not that I know of.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ls117:
so this version of dolby is the one that actually works.

https://xdaforums.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192

it baffles me that in a thread full of people trying a rom, no one had a straight answer for a dolby question.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HunterBlade:
Dang...I was hoping there'd be at least one treble ROM that supports VoLTE and WFC. Oh well, thanks anyways for the info!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] baconboy:
This ROM sounds good! I need to update my ancient Resurrection Remix ROM. There's lots of good information in this thread. I guess I have to create a VENDOR thing and update TWRP to install this?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
Old news,and this version is crap.Doesnt reach the level of dolby atmos.

On previous dotos build,dolby atmos was working
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
Yep. Just scroll through some of the posts and read through them, should be fairly easy to create a vendor partition. If you need any extra help, just ask.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcdw:
Heh heh, maybe because this is a ROM thread and not a Dolby one?

ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, XDA Legacy
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
So I flashed this finally, a week ago... and my device was in a state that said my device was corrupt over and over again. I managed to get to twrp and reflashed everything in order to no avail.

I ordered a new cheap a$$ phone to get by with.

Was reading up on some thing's and decided to try again and it booted up!!!! Now I'd like to root if possible. I'm unsure if I should attempt this now that the phone is working again but not having all my features takes away from the experience.

Any words of wisdom?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HTC55555:
This is awesome

Thank you!!!
[G 2014 Q&A, Help & Troubleshooting] HydroAG:
hi guys, i've a problem with my moto g xt1068, i was on oreo pixel experience when my phone and my battery was completely discharged, i connected the charger but my phone went in bootloop, i've tried to get into recovery by the AP fastboot screen, but the phone stuck in the twrp logo, so i've tried to use fastboot tool e reinstall twrpl, the log was succesful but nothing change in the phone, when i try to reboot in recovery i've the same old twrp logo, after if i try to reinstall the whole system the fastboot log still succesful but nothing change in the phone, still the old bootanimation/recovery logo, my bootloader version is 48.87 and i can't downgrade it, the only positive result was the command "fastboot boot recovery.img" that restarted the phone in stock recovery, but i can't do nothing all adb command are blocked, i'cant wipe data/chache partition, anyone can help me ?

sorry for my bad english guys :/
[G 2014 Q&A, Help & Troubleshooting] midish:
try fastboot erase cache

or try downloading and flashing twrp again (fastboot flash recovery twrp-x.xxxxxx.img) then cleaning cache
[Upgrading, Modifying and Unlocking] DoZe2:
Hi :)

Dump from phone of a friend :

ROM version : 1.13.73.1

DATE of ROM : 01/29/08

Radio ROM : 03.18.90

Protocole : 4.1.13.60

OS : WM Mobile 6 Pro 5.2.1944 (Build 18547.0.7.3)

pdocread -l

99.18M (0x632d000) DSK1:

| 3.08M (0x313400) Part00

| 3.32M (0x352800) Part01

| 92.78M (0x5cc7000) Part02

142.12M (0x8e1e800) DSK2:

| 142.12M (0x8e1e400) Part00

STRG handles:

handle 53aedb0a142.12M (0x8e1e400)

handle d3ba8dc2 92.78M (0x5cc7000)

handle 53ba8fce 3.32M (0x352800)

handle d3bc5dda 3.08M (0x313400)

disk 53aedb0a

0 partitions, 0 binary partitions

customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

disk d3ba8dc2

0 partitions, 0 binary partitions

customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

disk 53ba8fce

0 partitions, 0 binary partitions

customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

disk d3bc5dda

0 partitions, 0 binary partitions

customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

C:\ROM>pdocread -w -d DSK1: -p Part00 0 0x313400 part00.raw

CopyTFFSToFile(0x0, 0x313400, part00.raw)

C:\ROM>pdocread -w -d DSK1: -p Part01 0 0x352800 part01.raw

CopyTFFSToFile(0x0, 0x352800, part01.raw)

C:\ROM>pdocread -w -d DSK1: -p Part02 0 0x5cc7000 part02.raw

CopyTFFSToFile(0x0, 0x5cc7000, part02.raw)

And the last One, part00 of DSK2: of 142.12M

C:\ROM>dir *.raw

Le volume dans le lecteur C s'appelle Master

Le numéro de série du volume est C684-5249

Répertoire de C:\ROM

14/04/2008 19:28 3*224*576 part00.raw

14/04/2008 20:23 149*021*696 part00bis.raw

14/04/2008 19:29 3*483*648 part01.raw

14/04/2008 19:38 97*284*096 part02.raw

4 fichier(s) 253*014*016 octets

As you can see the part00bis.raw is big, but the phone have "Orange navigator" and perhaps the map is in this area. Someone can confirm this ?

I want to upload to FTP but Log/pass xdaupload seems don't work :confused:
[Upgrading, Modifying and Unlocking] katjie:
Orange navigator is not included in the ROM. It's been placed on the 1gb micro sd card bundled with the phone (nice bundle I have to say, since they provide a car charger, a phone/GPS car holder plus what you find in other HTC packs).

On the micro SD, your friend will find a cab that will be auto installed when you insert the card.

It's a shame Orange removed TomTom and only provides their poor navigator.
[Upgrading, Modifying and Unlocking] DoZe2:
i know this cab is made to install orange navigator,but, no map ?

For info, i install tomtom 6.020 and a map : works perfectly

Just set the GPS antenna : NMEA 4800 and COM4
[Upgrading, Modifying and Unlocking] katjie:
Maps are downloaded from orange servers when planning a way to go. That's what makes their home cook navigator so bad imho.

You can also nemea com4 at 9600 bauds. Indeed TomTom works perfectly. I called Orange today to tell them I was kinda disappointed that they removed TomTom from the bundle. They replied that it was made on purpose to only offer a pay as you go AGPS program (aka Orange Navigator). They also added that if customer were not ok with this, they could as well buy TomTom for about one hundred euros. Their policy is quite simple: Pay and shut up. Anyway I already own TomTom but would have loved to get an extra license...

Pharos is an OK phone. Not the best but ok. (I'll probably buy a TyntII by the end of the year or equivalent but got the pharos for free in replacement of a touch). Since I dont use Wifi that much and tought that HTC cube was sometimes a real pain in the neck, the lack of such features is not that bad (I'll rather buy a laptop soon and get a larger screen, decent browsing and so on with wifi).

Final words: Please, please, please admins open a new section for Pharos...
[Upgrading, Modifying and Unlocking] SamB76:
I've got exactly the same thing.

Do you know Pharos is not present on the HTC e-Club? (they do not recognize my serial number)
[Upgrading, Modifying and Unlocking] jefferalgan:
Hello every body

Im agree when a new section with pharos ??

For the eHTC Club, got the same pb SN not recognize ??? Why ??

Did someone replace the original ROM form HTC against the one give with orange ?

I saw a Pharos "without operator" and it seems to go faster than mine !!!

For people who want to install SDHC 8Go, i confirm there no problem with PHAROS.

Jefferalgan
[Upgrading, Modifying and Unlocking] suracha:
Pharos Sub-Forums

Guys, the Pharos Sub-Forums has already been launched. I hope to see you soon.
[Moto G5 Questions & Answers] ahmedAZ:
my build number is NPPS25.137-93-14

I want to update to oreo but read some posts says that i can not because of build number

HELP
[Moto G5 Questions & Answers] Andrej_SK:
You must be running NPPS25.137-93-2-5 to be able to update through OTA. However, you can still update to Oreo using fastboot method (link here: https://xdaforums.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244), but most probably, you will loose all of the data stored in the phone.
[Moto G5 Questions & Answers] ahmedAZ:
Is it safe to downgrade?

Some people say you may hard brick
[Moto G5 Questions & Answers] ahmedAZ:
Using adb don't need to downgrade?
[Moto G5 Questions & Answers] Andrej_SK:
It's safe as long as you don't try to flash gpt and bootloader. Downgrading one (or both) of these partition results in hardbrick.
[Moto G5 Questions & Answers] ahmedAZ:
But if i install oreo custom rom fingerprint may not work because it needs updated bootloader

I have read something like that on forum
[Moto G5 Questions & Answers] Andrej_SK:
If you update to official Oreo but then decide, you want to install CustomROM, you have to downgrade to Nougat first. Otherwise, your fingerprint won't simply work with any CustomROM. I have already mentioned it in this thread https://xdaforums.com/g5/help/finger-print-sensor-issue-oreo-roms-t3853491.

Btw, bootloader version is not related to fingerprint working or not with CustomROM. There's another partition that makes difference in it.
[Moto G5 Questions & Answers] ahmedAZ:
So it is better to be on nougat if i want custom roms in future?

Treble project needs stock nougat or oreo?
[Moto G5 Questions & Answers] Andrej_SK:
In my opininon yes, but your opininon might be different. Downgrading from official Oreo to official Nougat isn't difficult at all. You just have to remember, you can't flash gpt and bootloader. It's also recommended to avoid erase modem commands to prevent loss of IMEI.

None of them. Treble project needs Treble TWRP and Treble LineageOS installed firstly for correct functionality of other Treble CustomROMs. More info in this thread https://xdaforums.com/g5/development/treble-project-treble-cedric-t3820451.
[Moto G5 Questions & Answers] akshayshirkar10:
Hi everyone , I have not yet received update for Oreo ? Indian region, having same build no , my bootloader is unlocked as well
[Moto G5 Questions & Answers] achintyakv:
Same problem here. I have also the same build number on amzin software channel. Didn't receive the update till now. It says there is no update available.
[Moto G5 Questions & Answers] Chekm8Qc:
I was on 137-93-14 too. I flashed the fastboot firmware 137-93-2-5 to go back full stock and official. No need to re lock bootloader..then I downloaded the latest OTA update 28.85-16 and installed it via ADB sideload.

My phone is xt1670 on channel retca..though I can't say for sure what difference it makes if your on amzin. Wish I could help more.
[Moto G5 Questions & Answers] achintyakv:
No problem bro Yesterday I flashed the fastboot files and successfully updated to oreo which I found on this thread.

https://xdaforums.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244

Btw you have taken the long step bro. No need to get back to 137-93-2-5.

Cheers!
[Moto G5 Questions & Answers] ahmedAZ:
i updated through twrp
[Moto G5 Questions & Answers] Chekm8Qc:
[MENTION=5754598]achintyakv[/MENTION]

Yeah your right that was definitely the long way hehe. It's cause I wasn't sure that th oreo fastboot method would have worked for me. I had tried the TWRP version and it kept boot looping so I thought the other way would be safer :)
[Android Stick & Console RockChip based Computers] SaYLoR007:
Hello i have TV BOX MXQ 4K with rk3229 + wifi 6181 . My original firmware died and i flashed it and now Wifi not working!!!

Maybe someone have firmare for it with this wifi????

Thank you for help!!!
[Android Stick & Console RockChip based Computers] pcmender2005:
Have a look here mate.

https://chinagadgetsreviews.com/?s=Mxq+4k