Database Develop

[Stock ROM] A2017G TWRP flashable Images

Because meanwhile it's hard to find new A2017G images in Drakenfx TWRP thread I decided to open a new thread with the files from me.
Notes:
TWRP used 3.1.0.0
Coming from previous Stock Nougat System try to dirty flash the System and root with Supersu 2.79 (not sr3). After that wipe cache/dalvik.
If it isn't working this way, try formating system partition and flash system again. TWRP will tell you that there is no system installed and the system will for sure not boot if so. Restart into TWRP and flash the System and Supersu again. If this is still not working you have to factory reset your phone.
Keep care for Dragons. Its possible the update will change your data partition to f2fs. In combination with Supersu this is bad. If so you have to format data to ext4.
Using Supersu it's not necessary to install the no-verity patch, it's already included in Supersu.
Be carefull, next dragon ahead. Not installing Supersu after a virgin installation (data wiped/factory reset) will lead to a stock recovery instead of TWRP after the first boot.
[Nougat:]
B04:
I can't believe it. This ROM is up to now fully functional. ZTE finally did it. Cam is working, Dolby, Live Wallpaper also, no Tencent spyware, I wonder where the pittfall is!?!
Bootstack
https://www.androidfilehost.com/?fid=457095661767159296
System
https://www.androidfilehost.com/?fid=745425885120730040
Full Stock Reverter (If you like to revert Fastboot/Aboot/Recovery to Stock version)
https://www.androidfilehost.com/?fid=529152257862724933
B02:
Bootstack
https://www.androidfilehost.com/?fid=817550096634766076
System
https://www.androidfilehost.com/?fid=745425885120728390
Full Stock Reverter (If you like to revert Fastboot/Aboot/Recovery to Stock version)
https://www.androidfilehost.com/?fid=673368273298951352
B01:
Bootstack
https://www.androidfilehost.com/?fid=745425885120713802
System
https://www.androidfilehost.com/?fid=673368273298937254
[Marshmallow]
B09
Bootstack
https://www.androidfilehost.com/?fid=457095661767125769
System
https://www.androidfilehost.com/?fid=673368273298919671

@tron1 tried dirty flashing over b01 was stuck in ugly boot screen
same result after wiping and clean installing b02,
towards end of system.zip file to lines of red error line stating error log generated,and zip successfully flashed.

tuiyaan said:
@tron1 tried dirty flashing over b01 was stuck in ugly boot screen
same result after wiping and clean installing b02,
towards end of system.zip file to lines of red error line stating error log generated,and zip successfully flashed.
Click to expand...
Click to collapse
TWRP version?

tron1 said:
TWRP version?
Click to expand...
Click to collapse
twrp-3.0.3-1-ailsa_ii

tuiyaan said:
twrp-3.0.3-1-ailsa_ii
Click to expand...
Click to collapse
This is ancient. Try it with 3.1.0 or 3.0.4

Thanks alot.
Really handy to have all the files in one place.

Can I flash this ZTE_A2017GV1.2.0B02_Stock_System_by_tron1.zip on my A2017U variant with A2017U boot stack?

khangozzy said:
Can I flash this ZTE_A2017GV1.2.0B02_Stock_System_by_tron1.zip on my A2017U variant with A2017U boot stack?
Click to expand...
Click to collapse
I can only ask you to try and tell us if it is working. The other way it is working. I've been succesfully on BadBoys ROM with A2017G.

I'm on A2017G , LOS 14.1 from the 1st may. Can I dirty flash your B02 bootstack to get it up to date ?
Does the bootstack contains the latest baseband ?

tron1 said:
This is ancient. Try it with 3.1.0 or 3.0.4
Click to expand...
Click to collapse
tried it with 3.0.4 twrp no error but stuck in boot menu
tried with B01 and B02.
back to b10 with twrp zip

tuiyaan said:
tried it with 3.0.4 twrp no error but stuck in boot menu
tried with B01 and B02.
back to b10 with twrp zip
Click to expand...
Click to collapse
Tried flashing Supersu after flashing system? Also flashed Bootstack?

tron1 said:
Tried flashing Supersu after flashing system? Also flashed Bootstack?
Click to expand...
Click to collapse
Danke bro Danke
my device is alive and B02 updated
thank you for your patience
flashing SU did the job
i was missing this step

tron1 said:
I can only ask you to try and tell us if it is working. The other way it is working. I've been succesfully on BadBoys ROM with A2017G.
Click to expand...
Click to collapse
It works well with my lastest A2017U B25 bootstack.
Btw, how can I disable the Mi-POP notification when it turned on?
Sent from my ZTE A2017G using Tapatalk

khangozzy said:
It works well with my lastest A2017U B25 bootstack.
Btw, how can I disable the Mi-POP notification when it turned on?
Click to expand...
Click to collapse
Should be digged somewhere in the settings. Can't tell you exactly because I've removed this piece of crapware.

khangozzy said:
It works well with my lastest A2017U B25 bootstack.
Btw, how can I disable the Mi-POP notification when it turned on?
Sent from my ZTE A2017G using Tapatalk
Click to expand...
Click to collapse
It can't be removed while mipop is active. Hope it'll be fixed in next update

joaste said:
It can't be removed while mipop is active. Hope it'll be fixed in next update
Click to expand...
Click to collapse
It doesn't show on US B19 ROM.
Sent from my ZTE A2017G using Tapatalk

khangozzy said:
It doesn't show on US B19 ROM.
Sent from my ZTE A2017G using Tapatalk
Click to expand...
Click to collapse
Not even when you drag down the notification window?

joaste said:
Not even when you drag down the notification window?
Click to expand...
Click to collapse
Yes
Sent from my ZTE A2017G using Tapatalk

Update!!! B04 is up and running.

I'm on Marshmallow B09 unlocked and twrp. Can I just flash B04 Bootstack and after that B04 System for upgrading to nougat?
And which SuperSU version to flash for root?
and which partitions i need to wipe before/after flashing Nougat?
Thank you!

[WARNING] "DUAL-RECOVERY" Huawei/ Honor - PRA - 2017

[WARNING]"DUAL-RECOVERY" Huawei/
Honor - PRA - 2017​
I have recommended a dual recovery several times.
TWRP on the recovery2 partition (eRecovery)
Now I have noticed the following:
With a forced update (UPDATE. APP) TWRP will be overwritten with the original on the recovery partition. Not if it's on partition 2. That's a big brick risk.
So, please forget about the dual recovery.​

ChinHon said:
[WARNING]"DUAL-RECOVERY" Huawei/
Honor - PRA - 2017​
I have recommended a dual recovery several times.
TWRP on the recovery2 partition (eRecovery)
Now I have noticed the following:
With a forced update (UPDATE. APP) TWRP will be overwritten with the original on the recovery partition. Not if it's on partition 2. That's a big brick risk.
So, please forget about the dual recovery.​
Click to expand...
Click to collapse
Thanks for the info! But... Only need forgot the twrp in recovery2 if want to force update with update.app method, no? If want, just flash original recovery2 and ready to run update.app method, no?
Thx again!
Enviado desde mi PRA-LX1 mediante Tapatalk

dannyzamora said:
Thanks for the info! But... Only need forgot the twrp in recovery2 if want to force update with update.app method, no? If want, just flash original recovery2 and ready to run update.app method, no?
Thx again!
Enviado desde mi PRA-LX1 mediante Tapatalk
Click to expand...
Click to collapse
The eRecovery is a prerequisite for the UPDATE. APP. Missing it will lead to brick later. For example, if you perform a new unlocking. Then the device will no longer boot. Adb cannot find a connection. You can't flash anymore. No recovery and no TWRP. Running the UPDATE. APP again is not possible anymore. Total brick!

P10 Oreo system update (B365) on L29-C432B360+Magisk v16

Hello, I have a P10 L09C113 rebranded in L29-C432B360 and then rooted with Magisk V16 installed via TWRP 3.2.1-o by Blackball (https://forum.xda-developers.com/p10-plus/development/recovery-twrp-3-2-1-0-oreo-t3734993)
Today I received a notification about a system update to 8.0.0.365 via OTA (about 300 MB) on system settings app.
Is it safe to accept the update?
Or do I have to flash the stock recovery first?
Or do I have to uninstall Magisk before and then to flash stock recovery?
Or ?

Balteck said:
Is it safe to accept the update?
Or do I have to flash the stock recovery first?
Or do I have to uninstall Magisk before and then to flash stock recovery?
Or ?
Click to expand...
Click to collapse
Exciting!
I recommend this method as it will ensure it works correctly:
https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286
You will indeed need the stock recovery, and this method does it all for you. Simply re-flash TWRP and Magisk after its installed and booted once. Good luck!

Silently said:
Exciting!
I recommend this method as it will ensure it works correctly:
https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286
You will indeed need the stock recovery, and this method does it all for you. Simply re-flash TWRP and Magisk after its installed and booted once. Good luck!
Click to expand...
Click to collapse
at the end I flashed stock recovery and used Firmware Finder App.
In this way I downloaded the firmware from system settings app and updated successfully.
Now I will flash TWRP, but I'm looking for the best one:
 @Blackball that cannot decrypt /data or @espaciosalter20 that decrypt /data, but I don't know if is able to flash Magisk

Balteck said:
Now I will flash TWRP, but I'm looking for the best one:
@Blackball that cannot decrypt /data or @espaciosalter20 that decrypt /data, but I don't know if is able to flash Magisk
Click to expand...
Click to collapse
TWRP 3.2.1-0 for P10 v0.1 from Pretoreiano80 works well for 8.0 ROMs (like stock firmware you have flashed.
(Blackball's is useful if you're exploring 8.1 ROMs (such as the available Treble images))

Silently said:
TWRP 3.2.1-0 for P10 v0.1 from Pretoreiano80 works well for 8.0 ROMs (like stock firmware you have flashed.
(Blackball's is useful if you're exploring 8.1 ROMs (such as the available Treble images))
Click to expand...
Click to collapse
Thank you, but I read on thread:
Some of you have been reporting that mounting /system or another partitions doesn't work. I have discover that you need to decrypt data *before* to mount any other partitions.
I didn't set pin or fingerprint on my P10.
May I use this TWRP to backup and restore partition (system/boot in readonly image) and install Magisk v16?

Balteck said:
May I use this TWRP to backup and restore partition (system/boot in readonly image) and install Magisk v16?
Click to expand...
Click to collapse
The worst you can do is try. Seriously, backing up will not damage your system and if you see any errors then try a different TWRP version. You can flash as many of those as you like through fastboot until you find one that works for you!

Backup for sure, but flash magisk?
Could it corrupt system or data?
Inviato dal mio VTR-L29 utilizzando Tapatalk

Balteck said:
Backup for sure, but flash magisk?
Could it corrupt system or data?
Click to expand...
Click to collapse
If you have a backup it doesn't matter

[GUIDE] GSI (Generic System Image) howto

Project Treble gives a nice opportunity to run generalized system image on newer android devices compatible with this technology.
Of course, our Realme X2 should run it too.
Here is super quick howto, rather a concept You do not need root or Magisk or selinux=permissive for this. But having them is not a problem too.
Beware you will lose all your data, so make a backup in advance.
1 Simplified procedure, by using fastboot mode only​
Unlock bootloader of your device
Download the GSI from, say, here, extract it.
Modify vbmeta from a computer with a command fastboot --disable-verification flash vbmeta vbmeta.img (vbmeta.img is attached)
Format userdata partition with fastboot format userdata command
Flash system.img from the second step with a command fastboot flash system extracted-file-name.img
Issue command fastboot reboot
2 Full procedure, with vendor modification​Follow the next procedure only if your GSI has issues with encryption of userdata.
Unlock bootloader of your device
Download the GSI from, say, here, select ARM64+GMS, unzip it.
Modify vbmeta from a computer with a command fastboot --disable-verification flash vbmeta vbmeta.img (vbmeta.img is attached)
Flash TWRP or another custom recovery and boot it
Mount vendor partition in RW mode (simply do not tick 'Mount system partition read-only')
(this is not needed for some GSIs) Replace /vendor/etc/fstab.qcom file with the attached by the command adb push fstab.qcom /vendor/etc/
Flash system.img from the previous step with a help of TWRP to system partition of your phone.
Format Data (I use rm -rf instead of formatting in settings)
Now reboot and enjoy.
Note. The files are for RMX1991. I know for sure that vbmeta.img is identical for RMX1993 too, but I do not know about fstab.qcom yet. So 1993 owners, check this first. The only change inside is deletion of encryption option for userdata.
EDIT. fstab.qcom is identical for CN and EU versions, this is verified.

Here we can keep the list of images which are working fine with the device.
GSI from Google, Android 10: here (choose ARM64+GMS)
AOSP 10.0 v204 by phhusson: here. Choose arm64-ab- one, either vanilla or with gapps.
LineageOS 17.0 by AndyYan: here. Choose treble_arm64_bvN one
Pixel Experience 10.0 (thanks @vocoderism for the link): here
AOSP 10.0 v215 (3 pc.) - take -ab- ones, there are floss, gapps, vanilla. These are with 2020-04-05 security patch level, but FP does not work

And then?
Which android i have now?
Its realme free

If you want to go back you need the recovery stock, does anyone have the file image of the 1993 version so as to have it on file for a possible stock recovery?

Can we flash now the Global version firmware to China X2?

No not realy. Do a backup from system inside twrp and go back.
---------- Post added at 12:29 PM ---------- Previous post was at 12:28 PM ----------
Why you like china version???

djsven said:
No not realy. Do a backup from system inside twrp and go back.
---------- Post added at 12:29 PM ---------- Previous post was at 12:28 PM ----------
Why you like china version???
Click to expand...
Click to collapse
No i don't..

yakovpol said:
Here we can keep the list of images which are working fine with the device.
AOSP 10.0 v204 by phhusson: here. Choose arm64-ab- one, either vanilla or with gapps.
LineageOS 17.0 by AndyYan: here. Choose treble_arm64_bvN one
Click to expand...
Click to collapse
Did you try to install oppocamera.apk to see if it works? Also any bug that you see from the treble?

Works also on rmx1993 variant
I chiose PE android 10 gsi with permissive v5
All works except fingerprint on display
Inviato dal mio Phh-Treble vanilla utilizzando Tapatalk

vocoderism said:
Works also on rmx1993 variant
I chiose PE android 10 gsi with permissive v5
All works except fingerprint on display
Inviato dal mio Phh-Treble vanilla utilizzando Tapatalk
Click to expand...
Click to collapse
Thank you for reporting regarding RMX1993.
What is PE? Can you provide a link for this GSI?

yakovpol said:
Thank you for reporting regarding RMX1993.
What is PE? Can you provide a link for this GSI?
Click to expand...
Click to collapse
PE is pixel experience
Gsi link
https://sourceforge.net/projects/ex...20191115-1221-BETA-UNOFFICIAL.img.xz/download
Inviato dal mio Nokia 6.2 utilizzando Tapatalk

flashing steps please?

kmrazon said:
flashing steps please?
Click to expand...
Click to collapse
Unlock bootloader
Flash twrp and boot It
Copy extracted IMG Giles on sdcard
Formata data and rebbot ti twrp again
Flash IMG file on system image
Format data again and reboot ti twrp again
Flash magisk zip v20 or above and reboot ti sysyem
Inviato dal mio Nokia 6.2 utilizzando Tapatalk

vocoderism said:
Unlock bootloader
Flash twrp and boot It
Copy extracted IMG Giles on sdcard
Formata data and rebbot ti twrp again
Flash IMG file on system image
Format data again and reboot ti twrp again
Flash magisk zip v20 or above and reboot ti sysyem
Inviato dal mio Nokia 6.2 utilizzando Tapatalk
Click to expand...
Click to collapse
Any other gsi works? Evo X? Or latest PE?
So basically all A/B should works?
And till now common bugs: in display FP right?

Should work a/b
Inviato dal mio Nokia 6.2 utilizzando Tapatalk

vocoderism said:
Should work a/b
Inviato dal mio Nokia 6.2 utilizzando Tapatalk
Click to expand...
Click to collapse
you find any way for double tap to wakeup?

Many thanks for the guide. I can confirm that I am able to flash PE GSI, either TWRP or fastboot way.
(You may not need `fstab.qcom` if you flash PE GSI, I skipped this step)
However, The phone was stuck on Google loading screen, I waited for a such long time, probably 30mins. Then I had to reboot a few times, maybe 4 times. Eventually, I was able to see the initial setup page.
After seeing the initial page, I flashed PE GSI again, this time I didn't even to wait for a long time, about 2 mins to see the initial page. I think everything works! Haven't tried NFC yet.
However, I can't see fingerprint option in PE GSI options/settings, I can't confirm whether fingerprint works. After unlocking bl, I was still able to use fingerprint with ColorOS 6.1, so I assume fingerprint may still work.
Always-On-Display can't be found in Settings, so guess need to find a patch etc.

why i don't boot to system? , it boot to recovery

BaDuc said:
why i don't boot to system? , it boot to recovery
Click to expand...
Click to collapse
It might be the phone simply cannot boot system: something went wrong.

yakovpol said:
It might be the phone simply cannot boot system: something went wrong.
Click to expand...
Click to collapse
in step 4,5,8 i understand, i have HTC u11+ i have need wipe and install gsi system

Upgrade to stable ui 1 android 10

Hi,
I want to upgrade my smartphone to latest version stable android 10. I'm rooted and use twrp unofficial mauronofrio 3.3.1.12
I'd want to say if these passages are correct
1) upgrade latest unofficial twrp 3.3.1.1.3
2) uninstall magisk canary
3) install latest RMX1931EX_11.C.23 ozip with new twrp
4) install vbmeta.img
5) install canary magisk manager
6) factory reset
7) reboot
Is this procedure correct?
Thanks

euri007 said:
Hi,
I want to upgrade my smartphone to latest version stable android 10. I'm rooted and use twrp unofficial mauronofrio 3.3.1.12
I'd want to say if these passages are correct
1) upgrade latest unofficial twrp 3.3.1.1.3
2) uninstall magisk canary
3) install latest RMX1931EX_11.C.23 ozip with new twrp
4) install vbmeta.img
5) install canary magisk manager
6) factory reset
7) reboot
Is this procedure correct?
Thanks
Click to expand...
Click to collapse
The magisk does not work, if you find any way please tell me, why and tried everything and nothing that I manage to make it work
Enviado desde mi RMX1931 mediante Tapatalk

Hello, same for me I would like to update my phone from twrp to the latest version RMX1931EX_11_C.23, And I don't know how to do it if you can help me
And I'd like to know if the fingerprint works after switching to this version
Thanks in advance

Hi all!
Realme UI manual update link for RealMe X2 Pro is available in Realme India site. Here is the link.
https://www.realme.com/in/support/software-update
I m also thinking of updating it using this link. I hope it is same for European versions too.

ok magisk
I use Magisk 24 with twrp orange and modified vbmeta, but the fingerprint is broken

ogutolopes said:
I use Magisk 24 with twrp orange and modified vbmeta, but the fingerprint is broken
Click to expand...
Click to collapse
Could you pass me the magisk you used and the twrp, And I installed them all and it doesn't work for me, please send them to me and tell me how you did it
Enviado desde mi RMX1931 mediante Tapatalk

Lets goo
fastboot flash recovery OrangeFox-R10.1_1.img
boot in twrp
flash OrangeFox-R10.1_1.zip
rebbot in recovery
flash magisk 20.4
reboot recovery
flash vbmeta.img (FOR RECOVERY)
Clean caches
Reboot

ogutolopes said:
fastboot flash recovery OrangeFox-R10.1_1.img
boot in twrp
flash OrangeFox-R10.1_1.zip
rebbot in recovery
flash magisk 24
reboot recovery
flash vbmeta.img (FOR RECOVERY)
Clean caches
Reboot
I can't post a link here yet but send me an email and I'll send you the link to post to everyone with the google drive files.
gmail is amigulopes
Click to expand...
Click to collapse
[email protected] Send me all the files and the vbmeta please
Enviado desde mi RMX1931 mediante Tapatalk

Ok go
Post the link for everyone please
I haven't tested it on RMX1931EX_11.C.23, I'm using RMX1931EX_11.C.20

ogutolopes said:
fastboot flash recovery OrangeFox-R10.1_1.img
boot in twrp
flash OrangeFox-R10.1_1.zip
rebbot in recovery
flash magisk 24
reboot recovery
flash vbmeta.img (FOR RECOVERY)
Clean caches
Reboot
I can't post a link here yet but send me an email and I'll send you the link to post to everyone with the google drive files.
gmail is amigulopes
Click to expand...
Click to collapse
Thanks Bro and I'll try it tomorrow, thanks for the help [emoji847]
Enviado desde mi RMX1931 mediante Tapatalk

ogutolopes said:
Post the link for everyone please
I haven't tested it on RMX1931EX_11.C.23, I'm using RMX1931EX_11.C.20
Click to expand...
Click to collapse
with RMX1931EX_11_OTA_1230 i am able to boot device thanks :laugh:

I tested it yesterday ... Magisk works for me too in C23

ogutolopes said:
I tested it yesterday ... Magisk works for me too in C23
Click to expand...
Click to collapse
So, when somebody that made it work will make a guide explaining the steps for once?

deviantor said:
So, when somebody that made it work will make a guide explaining the steps for once?
Click to expand...
Click to collapse
Follow steps explained in post 7 of this thread.
Remember fingerprint sensor doesn't work

Hello, you have a lead if they will fix the fingerprint problem, commils have done it on the older version?