yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] raystef66:
I would recommend my crDroid Pie which is being maintained with sec. patches. You can find it here : https://xdaforums.com/showpost.php?p=81773269&postcount=84

Other ones like RR and Viper won't be maintained anymore. Maybe [MENTION=8823286]runninghamster[/MENTION] is planning to do some updates on PE or Havoc? Don't know about his plans tbh.

But as said try the crDroid 5.11. I expect sources will be updated soon on march sec.patches too. If so i'll update the build ;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] g0dzstar:
Thanks! I have tried your crDroid and RR but I keep getting the error.

E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zipe file xxx
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] raystef66:
Did you flash the los15 v2 already ? https://androidfilehost.com/?fid=11410932744536985259

Otherwise, try to go into the zip rom. Open META-INF and open the updater-script. For now remove the first assert lines. Save it back into the zip and try to flash again.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] g0dzstar:
I have tried both options already but crdroid, RR and pixelexperience for axon 7 all fail on this part in the updater-script.

block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");

I come from android 10 treble, maybe it has to do something with this? I am completely clueless :/
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] klałn:
How did you downloaded these zips?

I reminding myself, that I had a problem with zips/apks when I used stock web browser on custom rom, which used webview.

I was stuck with internet access without anything else. Borrowed a phone to send f-droid to my phone.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] raystef66:
Also try this : https://xdaforums.com/showpost.php?p=81479637&postcount=124
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] g0dzstar:
Tried it and still get the same issue. Tried with crDroid and PixelExperience.

I thought this would truly fix it haha, I have attached the log from twrp.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DonCatoli:
DELETE
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Link500X:
Is there any way to get RCS (google messages chat features) to work? Yesterday, I tried LOS 10, and it activated fine on that. But, I couldn't get the camera to work (plus the lack of slim recents), so I decided to try RR, since it is newer than Havoc (I had been running Havoc for several months, but RCS didn't work with that either). I'm hesitant to go to crDroid without either slim or omni recents.

Aside from the RCS issue, this rom has been working great so far though. Thank you

Edit: nvm, rcs randomly started working
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] coliotte:
first

thank you so much for this amazing rom i'm using it for week now and am loving in it

any ways i can't find "*key reverse on boot (recent/home/back)" option and i have the latest version of this rom installed can some one tell me where i could find it ?

---------- Post added at 02:52 AM ---------- Previous post was at 02:48 AM ----------

never mind found it xd
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Smedslund:
I can't get around the error 7 messages. I have tried every TWRP from 3.2.3 to 3.4.0. I have tried universal_bootloader. I simply don't get it. Any sugesstions?
[Android Q&A, Help & Troubleshooting] DJRichieDee:
Hi just recently got huawei and wanting to use the windows version of the theme creator. The program installs OK but won't load. I'm currently working on Windows 10. I've read that there is some conflict between 64 bit and 32 bit however I can only see the 64 bit version on the site. Can anyone shed some light on this or does anyone have a work around

Thanks

Rich
[Huawei Mate 9 Guides, News, & Discussion] aureliolage:
Please,

AFTER update FFinder - MHA-LGRP2-OVS 9.1.0.252 - via EMUI FLASHER, Mate 9 no starts Brick, i update and after my mate9 stuck in huawei logo and reboot for erecovery, no starts more .

MHA - L29 C432 ( why this update FF no works ???? )
[Huawei Mate 9 Guides, News, & Discussion] robogo1982:
Why did you flash a LGRP2-OVS unauthorized ROM? The C432 just got an update pushed from Huawei.

Send it to a Huawei repair centre to have it fixed and don't flash it if you don't know what you are doing.
[Huawei Mate 9 Guides, News, & Discussion] aureliolage:
LGRP2-OVS is not C432 ??? but in german appear 9.1.0.252 C432 my model, ( no have L29 C432 dload files for download ? for i install via dload method ??

easy firmware have C432 9.1.0.252 but is paid :(
[Huawei Mate 9 Guides, News, & Discussion] Licaon_Kter:
Seeing the same with it updated via Huawei Updater, aka official update.

Looks like OpenKirin RR Pie works ok to get the device back working aureliolage
[Huawei Mate 9 Guides, News, & Discussion] aureliolage:
i try all GSI only RR open kirin works in my mate9

9.1.0.252 / 255 nothing boot my device, only chance is appear L29 C432 9.1.0.252 free download for try DLOAD, but nobody passed me to room :(
[Huawei Mate 9 Guides, News, & Discussion] ante0:
To get back to your previous firmware, use this twrp: https://xdaforums.com/mate-9/development/recovery-twrp-3-2-1-0-t3914798

All other twrp reboots after a few seconds when you boot them.

Download update_full_base.zip for the build you were on before updating.

Download NoCheck for Pie: https://mega.nz/#!JeBQzAQR!exT4L16fFiIcovJnnukFXLw0RKfaJzPXFrk4NOgcn2Y

Boot to fastboot and flash TWRP to recovery_ramdisk

Since Huawei disabled booting directly to recovery on 9.1 you will have to boot to eRecovery (hold vol up on the screen where it says to hold it).

In eRecovery tap on Wipe/factory reset, type Yes and then tap on Factory reset. Phone will reboot to TWRP.

Open a command prompt when you're in TWRP and use these commands:

adb shell "mkdir -p /data/update/hwota/"

adb push PIE-NoCheck.img /data/update/

adb push update_full_base.zip /data/update/hwota/

adb shell "dd if=/data/update/PIE-NoCheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk"

adb shell "echo --update_package=/data/update/hwota/update_full_base.zip > /cache/recovery/command"

adb reboot recovery

Phone will boot to NoCheck recovery and flash update.
[Huawei Mate 9 Guides, News, & Discussion] aureliolage:
the firmwares before is 9.0.1.191 C432 ( but have 2 files in FF )

dload 9.0 C432 files cause brick?

emuiflasher with 9.0 c432 cause brick too?

only no brick is here your tutorial?

other question...

before flash my mate 9 is ( 9.0.1.191 C432 )

C432 receiver update ota Emui 9.1 9.1.0.252 ok

in Ffinder appear MHA-LGRP2-OVS 9.1.0.252

why after i update with emuiflasher this firmware my mate9 brick??

edit..... i try this commands, after reboot no update, go to stock recovery and no appear update no Check
[Huawei Mate 9 Guides, News, & Discussion] ante0:
Then you must've done something wrong or cache recovery needs to be wiped first, you can do that from erecovery.

The update on FF might not be the same you get on Phone.

Since Huawei started with their "unified" builds, although they should work on any cust they don't.

---------- Post added at 02:04 PM ---------- Previous post was at 01:25 PM ----------

Sorry, typo in the last command:

adb shell "--update_package=/data/update/hwota/update_full_base.zip > /cache/recovery/command"
[Huawei Mate 9 Guides, News, & Discussion] jeffrimerman:
I thought I read somewhere they are merging all the regions to the same final 9.1 so maybe that MHA-LGRP2-OVS 9.1.0.255 is the final version. I thought 9.1 was already being pushed out and that ovs is dated like July 29 and we're already going to be in September. I think 9.1 is supposed to be 1 file only now vs 2 for 9.0.1 vs 3 for Oreo. I used "flashy" and went from oreo to 9.0 easily. I noticed a guy used on his mate 10 and another on his p20 pro and worked fine. It won't work for 9.1 though.
[Huawei Mate 9 Guides, News, & Discussion] jakeslam78:
Can we update from 8.0.0 (Oreo) to 9.1 directly? Or it has to be first updated to 9.0? I have a backup phone Mate 9, stuck at 8.0.0.
[OnePlus 7 Pro Guides, News, & Discussion] jhakjhuk1853:
Tried and tested method to update to DP4 with twrp and root working.

If you update to DP4 directly before installing twrp you will be stuck without twrp.

You need USB pendrive and otg for it.

Steps

1. Update your phone to latest available official version.

2. Boot to fastboot and install TWRP (of course you need boot loader unlocked)

3. Flash DP4 from Thumbrive (keep it in external storage only)

4. Flash Recivery TWRP.zip from thumb drive

5. Reboot recovery

5. Flash DP4 again followed by Twrp.zip

6. Reboot recovery and flash magisk and any other mods you need.

7. Reboot

If you followed every steps correctly you will have working TWRP and root on DP4.

I am using it since DP2 and never had issues.

Note. Since Q diesnt allow twrp to read internal storage you will need usb drive for flashing mod also.

I have uploaded a video with DP4 Features if you want to know about its features.

New features

1. Volte working

2. Names of themes changed

3. System UI settings changed

4. Fingerprint faster

5. Overall phone is faster now.

Removed google assistant swipe shortcut.

Video link here

[youtube]GN82VerzS24[/youtube]
[OnePlus 7 Pro Guides, News, & Discussion] Bosstazem:
Too late for me :( I currently stuck with DP4 with no TWRP. any idea how can I get TWRP again. The fastboot command isn't working anymore.
[OnePlus 7 Pro Guides, News, & Discussion] jhakjhuk1853:
You need to use msm tool for reverting to stock

Or Stock reset rom for downgrade.

Then follow my steps
[OnePlus 7 Pro Guides, News, & Discussion] Bosstazem:
Is there any way to downgrade without MSM tool? I have a Mac. Local update doesn't work. Thanks for the reply.
[OnePlus 7 Pro Guides, News, & Discussion] jhakjhuk1853:
Try MP version from DP Version package via local upgrade.

This will be available once the official thread is created by oneplus.

Or you may try DP to MP version for DP3
[OnePlus 7 Pro Guides, News, & Discussion] Bosstazem:
The old MP version works! :good:
[OnePlus 7 Pro Guides, News, & Discussion] Mike02z:
I just used the stock firmware .img file via fastboot. I restored 9.5.7 with no issues. Of course you'll lose all your data.
[OnePlus 7 Pro Guides, News, & Discussion] TapioH:
I was able to install twrp and magisk on dp3, i think you can do it with dp4 aswell.

I just fastboot flash boot twrp.img , it says slot a ok, slot b fail.

So i switched active slots and reboot, which boots to twrp installed on other slot. While in twrp (which cannot access data) i installed twrp through adb, switched active slot and installed twrp again. Same for magisk 19.4 installer.

After installing twrp and magisk to both slots i switched active to B and rebooted, which took me to rooted dp4.

Hope that made any sense

Oh and while in twrp, i used twrp installer (latest) to install twrp to both slots.
[OnePlus 7 Pro Guides, News, & Discussion] knives of ice:
why do you possibly need to flash the rom and twrp TWICE? shouldn't the usual upgrade process for a rom if you are already rooted still work?

Flash the Q rom

flash twrp

reboot to recovery

flash magisk?

don't understand the reason to flash both twrp and the rom 2 times as posted in the instructions

regardless, i followed the exact steps and it didn't work for me. i boot to a plain black screen and can't get past it. any ideas?
[OnePlus 7 Pro Guides, News, & Discussion] Arden144:
Repeating the steps twice installs the ROM to both system slots
[OnePlus 7 Pro Guides, News, & Discussion] tylers24:
Can you elaborate on step 2? Do we flash twrp.zip the same as the other steps? or do we flash the twrp-installer?
[OnePlus 7 Pro Guides, News, & Discussion] kpmohamedhussain:
1. Downloaded the 9.5.11 update from Oxygen Updater (DONT REBOOT)

2. Went to Settings\System\System Update and click on the wheel on upper right corner.

3. Select Local Upgrade, then install the update (DONT REBOOT)

*DO NOT REBOOT after applying the update.

4. Remove Magisk modules that may cause problems (Call Recording is one of them)

5. Launch Magisk, and click the first "install"

6. Choose the "Install to inactive slot (OTA)" option

7. Reboot once completed

8. Download TWRP (from another location) and then go into Magisk and install it, but ***DO NOT REBOOT!!***

9. Install Magisk again. Click Install, then select "Direct Install" option.

10. Reboot

Will this work for DP4 as well????
[OnePlus 7 Pro Guides, News, & Discussion] pro_granade:
Downgrade using the rollback package, when I did it on Beta 3 it did not relock my bootloader.
[OnePlus 7 Pro Guides, News, & Discussion] spawnn617:
I don't think so - what I've read on Oneplus page, when you hit restart (after installing magisk) it will reboot and during that erase all data. then reboot again to system. So you cannot restart via system updater,, you need use TWRP to flash it, so i would stick to the 1st post instructions (including 2-times install t ocover both slots). But hey, ican be wrong, you can try and let us know, it would be easier for sure :D
[OnePlus 7 Pro Guides, News, & Discussion] klym.software:
Is this the only way to get root on DP4?
[OnePlus 7 Pro Guides, News, & Discussion] twinnfamous:
Simple way

Info for TMobile gm1915 on 9.5.11

You must have magisk installed.

Update through local upgrade method and don't reboot. Then go to magisk select modules hit + and find twrp installer install twrp and then choose install magisk choose install to inactive slot. Then reboot.

Data does not get wiped but fingerprints need to be added again.

Also twrp decryption does not work so best to keep otg USB with you with whatever you may want to flash.

You don't have to flash to both slots it's not necessary but do as you wish.
[OnePlus 7 Pro Guides, News, & Discussion] kpmohamedhussain:
Is it to upgrade from 9.5.11 to dp4 without data loss???
[OnePlus 7 Pro Guides, News, & Discussion] twinnfamous:
Yes
[OnePlus 7 Pro Guides, News, & Discussion] reef2009:
Hi, I followed all the steps in OP and didnt. using latest twrp and magisk 19.3 (stable)

Now my phone is still starting its first boot about 15 minutes.

Update:

Probably the problem: installed magisk modules.

Anyway after some research default twrp is'nt mounfing local storage. The latest custom TWRP is! So no issues with USB Anymore, just use local storage like u used to do! This is actualy the only way to use the Magisk uninstaller because you need to mount data for uninstalling magisk modules.

https://xdaforums.com/oneplus-7-pro/development/recovery-unofficial-twrp-recovery-t3931322

Anyway it took me a view hours of testing but now it works smooth! ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
Bootleggers ROM is an aftermarket firmware based on AOSP with some patches and fixes from LineageOS and various other projects. The idea is to bring custom features and some of the most useful apps on your device, with the goal of Making you feel like 家.

With an almost stable source, this ROM is also packed with some custom wallpapers (avaliable on ShishuWalls), ringtones, fonts, and themes to bring to your device into a more fresh look and give you always a good experience.

* QS Rows and Colums
* Volume Keys: Wake up, skip tracks and switch according to rotation
* Show song album cover, visualizer and battery info on Lockscreen
* Power Menu Items
* Battery LED light settings
* Suspend Actions: Make your device disable GPS and switch to 2G when you're not using it
* AppOps: Manage your apps permissions in an advanced way
* Recent Styles: Dig the new Pie Quickstep recents, go back to the classic layout or use the Android Go layout
* Network icons: Show or hide the cross, switch between 4G or LTE, use the classic icon layout before Pie or toggle roaming icon too!

Also, you can check a full list of Features available here

Thanks to this people, this ROM could be possible, so, i have to give a big thanks to:

Shishu (For being there)

* Ground Zero ROMs Team
* AOSPExtended
* ABC ROMs
* NitrogenOS
* AICP
* DirtyUnicorns
* Lukas Koller (Camera Roll dev)
* fxckingdeathwish (for the amazing photos for wallpaper/headers)
* OmniROM
* CyanogenMod/LineageOS
* PixelExperience
* PureNexus
* merothh
* Resurrection Remix
* AOSiP
* CrDroid
* CypherOS
* PureKat
* theimpulson
* MatiHalperin
* Project Xtended
* Pixeldust Project
* AquariOS
* Alejandro Ponce (Quetzal/Calypso dev)
* PixysOS
* The Memedo Testers team
* Every maintainer who decided to give our project a shot
* You for your interest on our project

Download: Unofficial build here

Device Sources :

https://github.com/OrdenKrieger/android_device_zte_axon7

Kernel Sources :

https://github.com/OrdenKrieger/android_kernel_zte_msm8996

- If you find that your mobile data does not seem to work, go into Settings > Network and Internet > Mobile Network > Access Point Names and fill in the APN manually by googling for your carrier's APN online.

​

XDA:DevDB Information

bootleggers, ROM for the ZTE Axon 7

Contributors

[MENTION=8823286]runninghamster[/MENTION]

Source Code:

https://github.com/BootleggersROM

ROM OS Version: 9.x Pie

ROM Kernel: Linux 3.18.x

Based On: AOSP

Version Information

Status: Unofficial, Stable

Stable Release Date: 2019-08-03

Created 2019-01-03

Last Updated 2019-08-03
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
Reserved
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] leo22498:
Thank you, this rom is the fastest I have tested from the last posted roms, no issues found for now
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Sakuma_Eitarou:
mobile data not work anyway. Why post the rom if it has similarr bugs?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] leo22498:
First of all, sorry if my english is bad.

The rom works well, I can use my mobile data, you just have to read carefully instructions, especially this part "- If you find that your mobile data does not seem to work, go into Settings > Network and Internet > Mobile Network > Access Point Names and fill in the APN manually by googling for your carrier's APN online."View attachment 4801370
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Sakuma_Eitarou:
my English is bad too, I filled the APN on my own, but it didn't give anythingI filled the APN on my own, but it didn't give anything......10 minutes later mobile internet works, i just change type of mobile signal on my second sim
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
Sorry about the apn issue, I will try to fix it in the next release.

As for the APN not working, try filling out all the APN information correctly, and then make sure it's selected via the small dot. Reboot the device, and check if it's working.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DeepAnger:
Hello, thank you for this promising ROM. I can't find a messaging app. Is that normal ?
[Vivo Nex Accessories] RicksonNL:
I just got a screen protector from Amazon and you guessed it, it's too small.. I want to know if this one fits. I know about the dome screen protector, but I think it is too expensive.

I can't post the link so please Google:

FlightLife Panzer Glass Vivo Nex S

Thank you
[Vivo Nex Accessories] RicksonNL:
So after checking with the supplier I bought one. The fit is pretty good, there just a very small gap on the left and right and at the bottom:

https://imgur.com/a/Xt0DPQ4

Price was 18 euros.
[Vivo Nex Accessories] RicksonNL:
I think the Dome screen protector would have been better. The price is now just $25.30 using the discount code on their website... :rolleyes:

whitestonedome.com/collections/vivo-1/products/vivo-nex-a-s-dome-glass
[Vivo Nex Accessories] cho9736:
is the deal still alive?
[Vivo Nex Accessories] RicksonNL:
No I don't think so
[Vivo Nex Accessories] RicksonNL:
Its on sale now, and you can get 45% off with a code, total price is just 19,25 USD! I'm getting one now. :)
[Vivo Nex Accessories] cho9736:
but the shipping killed it :(
[Oukitel (All phone models)] JR44:
Sorry, can not find any threads her on this

New Oukitel WP2 Android 8

Unlocked bootloader using ADB

ran "fastboot flash recovery WP2.img" and computer said finished

'phone said OK!

Tried "fastboot recovery" BUT all the 'phone will display is ==> fastboot mode in micro writing bottome left of screen

Tried volume up/power - nothing volume down/power - after warning about unlocked bootloader

bot into STANDARD Android 8 boot menu.

Having unlocked many Samsung 'phones, this is confusing me!

Also, after this how do you actually root the 'phone (or is twrp the root kit) as super SU reports

unrooted telephone.

Any clues gratefully accepted

Thanks

John
[Oukitel (All phone models)] Droidriven:
After fastboot flashing TWRP, type the command below.

adb reboot recovery
[Oukitel (All phone models)] JR44:
Thanks for reply but ONLY boots into the stock android 8 recovery and will not boot into twrp

tried various methods and each time adp says flashed recovery (tried it with different names recovery.img twrp.img etc)

and shows data transferred on 'phone screen.

BUT your suggestion and all those on the various websites but will still not boot into the custome recovery

and although I am used to working on Samsung 'phones, this one beats me! Eveb fulll factory reset 3 times!

TWRP is recovery-20181231-0237.img from multiple sites.

I do not know how to find if the recovery has actually been installed or something is stopping it running.

Just tried again in case:-

ANDROID RECOVERY

OUKITEL /WP2/WP2

8.0.0/o00623/1532584305

user/release-keys

use vol.....

hen usual list+-

reboot system now

reboot to bootloader

etc etc

no TWRP

'Phone does show "strange condition - unlocked bootloader - device can not be trusted" on each boot,

so everything else seems fine.

Spent 5 hours on this! Was going to use super su but could use magisk instead IF I can get to the

recovery stage!

rgds
[Oukitel (All phone models)] Droidriven:
After flashing TWRP, you can't let the device boot to any other mode, you have to boot directly to recovery. If you allow the device to boot into any mode other than recovery, it will revert back to stock recovery. The only way to keep TWRP is to boot directly into TWRP immediately after flashing.

Try this, flash the TWRP file using the fastboot flash recovery (name of file) command. Then, after it flashes, try using this command:

fastboot boot recovery (name of your specific file)

This may allow you to boot into TWRP and keep TWRP recovery so that you can boot into it at any time after that.
[Oukitel (All phone models)] JR44:
Thanks for reply but does not work...

WP2 has already had bootloader unlocked developer options and adb commands, including an automatic wipe of 'phone.

Then without touching anything else, the follwoing have been entered from a clean boot of 'phone and Win7. twrp.img file is named "recovery.img" in same directory as adb etc (C:\ for testing)

twrp file is "recovery.img" in same directory as adb etc (C:\ for testing)

twrp file is "recovery.img" in same directory as adb etc (C:\ for testing)

issue command> adb reboot bootloader

computer response OK

'phone shows "fastboot" in miniscule text

issue command> "fastboot flash recovery recovery.img"

computer says> "target reported max download size 134217728 bytes"

then

"sending 'recovery' (15010kb)"

then

"OKAY [0.65 seconds}"

then

"writing 'recovery'..."

then

"finished. total time 1.06 s"

'phone says "transmission ok then a checksum"

after a wait

issue command> "fastboot boot recovery.img"

computer says "downloading 'boot.img'"

then

"OKAY 0.64 s"

then

"booting....."

then OKAY 0.47s"

then

"finished"

'Phone boots into normal logo then to a NORMAL STARTUP - NOT to any bootloader

argh!!!

adb devices returnes OUKIWP2000015176

Any clues as to what is wrong or what I am missing!

cheers

John

UK
[Oukitel (All phone models)] Droidriven:
I don't know, I'll keep looking, if I find anything useful, I'll post it.