Database Info

[RECOVERY][TWRP][NX510J]TWRP Recovery 3.0.2-0 for Nubia Z9 Max

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Features::
Build based on latest CM13.0 and TWRP source.
Workaround on touchscreen. Touch screen fully works! No matter what your device's version is.
All function in a normal TWRP
Changelog:
15/7/11
First release
15/10/24
Sync latest TWRP source
Update prebuilt kernel from beta357
Fix a typo: nz510j, now it can be used to flash an official release
15/11/21
Sync latest TWRP source
Build kernel from new source
Add support for F2FS
16/03/12
Sync latest TWRP source (TWRP 3.0)
Use new kernel align with CM13
16/08/05
Sync latest TWRP source
Use new kernel align with CM13
Restructure device tree
Download link::
https://s.basketbuild.com/filedl/devs?dev=dianlujitao&dl=dianlujitao/nx510j/twrp_nx510j_v5_f2fs_dianlujitao.img
Install guide::
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Run "fastboot -i 0x19d2 flash recovery twrp_nx510j_v5_f2fs_dianlujitao.img"
4. Reboot
Source code::
https://github.com/MoKee/android_bootable_recovery-twrp/tree/mkm
https://github.com/dianlujitao/android_device_zte_nx510j/tree/twrp
XDA:DevDB Information
TWRP, Tool/Utility for all devices (see above for details)
Contributors
dianlujitao
Version Information
Status: Stable
Current Stable Version: 5
Stable Release Date: 2016-08-05
Created 2015-07-11
Last Updated 2016-08-04

how to install this .img?

Hi. Can you make a build for nx511j (z9 mini)?

djbosanac said:
how to install this .img?
Click to expand...
Click to collapse
I've added a simple install guide

How do we boot into recovery? I flashed the recovery but when I try to boot into recovery from fastboot it always boots to the main OS

Can't boot in this recovery after installing it.
Sent from my NX510J using XDA Free mobile app

Hi, it will works with newest ZTE firmware 3.06 ? or maybe someone has a newest version ? THX

Can not install official updates/ROMs. There is a misspelling in default.prop:
ro.product.name=nz510j
Must be:
ro.product.name=nx510j

5[Strogino] said:
Can not install official updates/ROMs. There is a misspelling in default.prop:
ro.product.name=nz510j
Must be:
ro.product.name=nx510j
Click to expand...
Click to collapse
Will be fixed as long as I have time, now I'm too busy

How long will this command take? All I get is < waiting for device >
Had to do this first:
- Connect phone while normally booted
- Run the installer that is automatically mounted on windows
- click 7 times the buildnumber in "about phone" to enable developer options
- enable usb debugging in developer options
Edit:
Installed your cyanogenmod build, but still have a problem. Cant reboot to recovery. What I have to do is get into fastboot, flash TWRP, reboot to recovery.
Edit2:
I can boot to recovery, only if usb is connected.

5[Strogino] said:
Can not install official updates/ROMs. There is a misspelling in default.prop:
ro.product.name=nz510j
Must be:
ro.product.name=nx510j
Click to expand...
Click to collapse
EDIT: The following isnt needed anymore as of the latest update!
To bypass this problem I use another TWRP now from here: http://www.androidiani.com/forum/mo...3-z9-max-lollipop-5-0-2-cuoco92-firmware.html
Download: https://mega.nz/#!OgYljCAa!eH54Uc7Tdld1N3Oz3L4TIr1uiBx6EZSILf67MFgpgJk"
Translated:
- Install the drivers ( http://pdanet.co/a/ )
- Unzip the ZIP
- Start the file "Install_TOOL.exe"
- Coose 2: "Install TWRP 2.8.6.0"
- Wait for restart to the new TWRP (in nubia style!)
Click to expand...
Click to collapse

jogai said:
To bypass this problem I use another TWRP now from here: http://www.androidiani.com/forum/mo...3-z9-max-lollipop-5-0-2-cuoco92-firmware.html
Download: https://mega.nz/#!OgYljCAa!eH54Uc7Tdld1N3Oz3L4TIr1uiBx6EZSILf67MFgpgJk"
Translated:
Click to expand...
Click to collapse
A friend of mine received this smartphone this week and he's unable to get twrp installed, tried many different methods, but apparently the touchscreen doesn't work when he needs to press an option. He did it through Win XP, maybe that's the reason why... I'm nervous as well as I ordered the phone as well through the same seller...
I really don't know why it's not working...

jogai said:
To bypass this problem I use another TWRP now from here: http://www.androidiani.com/forum/mo...3-z9-max-lollipop-5-0-2-cuoco92-firmware.html
Download: https://mega.nz/#!OgYljCAa!eH54Uc7Tdld1N3Oz3L4TIr1uiBx6EZSILf67MFgpgJk"
Translated:
Click to expand...
Click to collapse
already fixed

K3nshiro said:
A friend of mine received this smartphone this week and he's unable to get twrp installed, tried many different methods, but apparently the touchscreen doesn't work when he needs to press an option. He did it through Win XP, maybe that's the reason why... I'm nervous as well as I ordered the phone as well through the same seller...
I really don't know why it's not working...
Click to expand...
Click to collapse
Try my latest release,
and plz tell me which of the following path exists on your friend's phone:
/sys/bus/i2c/devices/2-004a
/sys/bus/i2c/devices/2-005d
/sys/bus/i2c/devices/2-0024

dianlujitao said:
Try my latest release,
and plz tell me which of the following path exists on your friend's phone:
/sys/bus/i2c/devices/2-004a
/sys/bus/i2c/devices/2-005d
/sys/bus/i2c/devices/2-0024
Click to expand...
Click to collapse
Thank you dianlujitao,
I hadn't seen that you had already fixed the typo, sorry for that.
I've told my friend about the new TWRP and asked him about the path - if he asks me where to find this on the phone, where should he look for, or can this be found through Windows as well ?
I'll keep you informed about my findings.
Thanks again,
Ken

K3nshiro said:
Thank you dianlujitao,
I hadn't seen that you had already fixed the typo, sorry for that.
I've told my friend about the new TWRP and asked him about the path - if he asks me where to find this on the phone, where should he look for, or can this be found through Windows as well ?
I'll keep you informed about my findings.
Thanks again,
Ken
Click to expand...
Click to collapse
Can be found even through CM file manager.
Run adb shell on computer, then use ls to find it

Hey!
I got it working on my Z9 max
Didn't work though through root path on internal storage, had to run it through another path on my pc.
Fiddling around a bit these days before I try out your Cyanogen Rom.
Btw, do you have a proper link (nubia official) for the download of the new Nubia UI?
I tried to locate it on nubia.cn, but I'm unable to find it...
I'd really appreciate if you could reveal the link
Cheers
Sent from my NX510J using Tapatalk

K3nshiro said:
Hey!
I got it working on my Z9 max
Didn't work though through root path on internal storage, had to run it through another path on my pc.
Fiddling around a bit these days before I try out your Cyanogen Rom.
Btw, do you have a proper link (nubia official) for the download of the new Nubia UI?
I tried to locate it on nubia.cn, but I'm unable to find it...
I'd really appreciate if you could reveal the link
Cheers
Sent from my NX510J using Tapatalk
Click to expand...
Click to collapse
http://bbs.nubia.cn/thread-554721-1-1.html
Latest nubia ui v3.62

dianlujitao said:
http://bbs.nubia.cn/thread-554721-1-1.html
Latest nubia ui v3.62
Click to expand...
Click to collapse
Thanks a ton dianlujitao,
Sorry for late reply, I'm currently on vacation, I'll do it when I return.
I got a couple of questions regarding this. If you can and if you want, I'd appreciate if you could give them a look, no hurry. I'm very well aware that this is your time, and I have no right to request anything.
I just don't want to brick the phone
1. Can I use your Twrp to make a Nandroid backup?
2. Can I use your Twrp to flash it (The Brush file) or should I do it with default recovery?
3. As per instructions, it says that I should unroot it and reset to factory values.... Is this necessary?
4. Where does your Twrp save the backup, to internal memory or SD card?
Last but not least, I have to say that so far the phone has impressed me, specially the camera, awesome pics.
I let the device store them on the SD card, and sometimes I have seen (4 times to be precise) that the pic is corrupt. Would you know if this is fault of the phone or of the SD card?
Cheers,
Ken
P. D. Do you have a PayPal account for donations setup for instance?
Sent from my NX510J using Tapatalk

K3nshiro said:
Thanks a ton dianlujitao,
Sorry for late reply, I'm currently on vacation, I'll do it when I return.
I got a couple of questions regarding this. If you can and if you want, I'd appreciate if you could give them a look, no hurry. I'm very well aware that this is your time, and I have no right to request anything.
I just don't want to brick the phone
1. Can I use your Twrp to make a Nandroid backup?
2. Can I use your Twrp to flash it (The Brush file) or should I do it with default recovery?
3. As per instructions, it says that I should unroot it and reset to factory values.... Is this necessary?
4. Where does your Twrp save the backup, to internal memory or SD card?
Last but not least, I have to say that so far the phone has impressed me, specially the camera, awesome pics.
I let the device store them on the SD card, and sometimes I have seen (4 times to be precise) that the pic is corrupt. Would you know if this is fault of the phone or of the SD card?
Cheers,
Ken
P. D. Do you have a PayPal account for donations setup for instance?
Sent from my NX510J using Tapatalk
Click to expand...
Click to collapse
1. yes, but system,boot and data is enough
2. yes
3. no
4. it's up to u
5. no idea
6. I forgot my paypal passward and passward reset answer, so...

[AIO] Prepare your device (and your knowledge) for any GSI

Preliminary operations/infos
First of all: what's Treble?
Find it out here.
How do I obtain my bootloader unlock code?
GO HERE, FAST!
Huawei officially ceased the unlocking service.
How do I get Treble on my device?
At the moment of this write down, EMUI it's still in private BETA.
The only chance to obtain it it's to follow this guide CAREFULLY.
What if I want to revert to EMUI 8/5?
Follow the steps described in the guide to get treble on your device using EMUI 8 files if you want to revert to EMUI 8, or EMUI 5 if you wish to revert to it.
The road it's long...
So, you're sitting there, not understanding why there are so much ROMs in this section and why you shouldn't use the ones appearing in Treble-Enabled Device Development since you worked so hard to get Treble on it.
Let's try to answer a universal question.
What's the difference from the "standard" GSIs and the ROMs in this section?
Well, the ROMs here were made keeping an eye on the "optimization per-platform" concept, basically tracking down some proprietary stuff inheriting them under /system .​
**WHAT FOLLOWS ARE PERSONAL OPINIONS**
I honestly think, that we should cut off this approach.
Inheriting stuff under /system has no more sense.
Am I saying that what I did till now had no sense?
Yes.
The whole Treble concept relies on moving away from system, any vendor related stuff.
So why in the hell should we inherit proprietary stuff in our system partition again?
When we have other ways to don't mess with it?
The only stuff that still "deserves" to have something to do with /system it's the Huawei Camera.
Everything else, belongs to /vendor.
Furthermore, our goal, as developers and users, should be to track down specific-platform bugs and report them.
Co-operation is the sake of open-source and the key to success in a wonderful GSI experience for everyone.​

Is my device ready to use a "standard" GSI?
Pretty much.
Huawei doesn't ship any overlay under /vendor in our PRA, because it's inherited in EMUI under /system.
But, you can follow this guide, to include the needed overlay to be fully GSI-ready.
Also, you need this thread too to fix offline charging on your Huawei device.​
Known Bugs on GSI and "specific-GSI"
NFC has been an annoying issue all along the development process on some Huawei devices.
But this flashable zip, seems to solve the issue on our PRA.
Indeed it needs more testing.​
Available tools/software for your PRA
ADB and Fastboot
TWRP
MindTheGapps
Huawei Camera Magisk
OEMInfo (TWRP backup)
HuRU
Stock Ramdisk (ramdisk partition)
Stock Recovery (recovery_ramdisk partition)​​
Specific-GSI available
Lineage OS https://forum.xda-developers.com/p8...t/rom-lineage-os-huawei-p8-lite-2017-t3787193
CrDroidhttps://forum.xda-developers.com/p8.../rom-crdroid-4-2-huawei-p8-lite-2017-t3785615
AospExtendedhttps://forum.xda-developers.com/p8.../rom-aospextended-5-4-huawei-p8-lite-t3778938
AOSPhttps://forum.xda-developers.com/p8...ent/rom-aosp-r23-huawei-p8-lite-2017-t3779115
Resurrection Remix 6https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-rros-pra-t3774444
SlimRom 8
AICP​
Specific GSIs are now discontinued.
Go to the Treble Enabled Development sub to get some ROMs to flash!
NOTE:
This ROMs will be discontinued in a couple of weeks, since the installation of the overlay (previously highlighted in the paragraph "Is my device ready to use a "standard" GSI?") will give access to a full fledged GSI experience without the need of specific GSIs.
Custom kernels
Labyrinth​

Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
If this isn't clear enough, please, check this contribution.
Playstore download pending fix
Access https://play.google.com/apps/testing/com.google.android.gms/join
Apply for the beta
Update Google Play Services to the beta
Profit
Magisk keeps crashing?
Turn off its "Check for update feature" and praise for the arrival of a new Magisk version.
From 16.6 version, Magisk it's fully working.
Please, refer to this thread for a correct installation.
How to report bugs
Boot problems:
Please do dump /splash2 partition and sys/fs/pstore content via adb pull in my TWRP.
adb logcat > file.txt
Quirks on booted system:
Please take a full bugreport when the bugs happens via Developer Options
or​
adb logcat > file.txt
send file.txt to the developer

Hey you!
If you're reading this message I want you to help this community.
Share your thoughts about this posts or post your un-answered questions below.
The more we share, the best experience we'll get.
Also, please respect my work.
If you do integrate some of this infos in your thread/website or whatever, add me in the credits.
Furthermore, feel free to join us at @GSI_HI6250 on Telegram, we're funny people, I swear.
Is this non-clear somehow?
Or you just need help?
Fill the help form below.
Device Variant:
Device Firmware:
Is your device rebranded?:
How frequently this issue happens?
Is this happening now?
Describe the issue:
Describe steps to reproduce the issue:
Attach logcats/full bugreports as described on the paragraph "How to report bugs"​
Or simply join the telegram group.
Peace.

Dil3mm4 said:
Kaioken reserved
Click to expand...
Click to collapse
Super Saiyan reserved
Lol

Dil3mm4 said:
Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
Playstore download pending fix
Access https://play.google.com/apps/testing/com.google.android.gms/join
Apply for the beta
Update Google Play Services to the beta
Profit
Magisk keeps crashing?
Turn off its "Check for update feature" and praise for the arrival of a new Magisk version.
How to report bugs
Boot problems:
Please do dump /splash2 partition and sys/fs/pstore content via adb pull in my TWRP.
Quirks on booted system:
Please take a full bugreport when the bugs happens via Developer Options
or​
adb logcat > file.txt
send file.txt to the developer
Click to expand...
Click to collapse
THAT WORKED. FINALLY 8.1 WITH BOOTLEGGERS GSI, 128GB micro SDXC as INTERNAL. I AM HAPPY
for beginners:
boot after working rom in twrp
go in advanced
go to file manager
go to /vendor/etc/
open file "fstab.hi6250" (after copying with and having a recovery of it, open with notepad++ or something else)
there should be a line with: "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
erase the part: ",fileencryption=aes-256-xts:aes-256-cts"
save
erase the original fstab.hi6250 file in vendor/etc
and put the new fstab.hi6250 file in
reboot in bootloader
flash stockrecovery.img
reboot recovery
factory reset in stock recovery
reboot
DONE.
now you can see the SD card as internal and use for apps.

Need your help
Hey OP,
Thanks for all your work. Really a big fan.
There is a problem I've noticed on most of the treble roms. After using apps for a while, they begin to FC.
Love your roms and would like to continue using them

Mister746 said:
Hey OP,
Thanks for all your work. Really a big fan.
There is a problem I've noticed on most of the treble roms. After using apps for a while, they begin to FC.
Love your roms and would like to continue using them
Click to expand...
Click to collapse
Updated last post, please submit the infos needed via that form.
Thanks.

Hi, i am experiencing a weird bug on every GSI, specifically, snapchat video recording is fine and smooth, but after tapping on the "send" button it says "failed to add" and doesnt even give a chance to resend the same snap. It happens on all treble roms i've teted so far (i tested every specific GSI for PRA, and some openkirin and otger ones). @dill3m4 do you have any idea how to fix it? I hope there is a way to do a flashable zip or something like the NFC fix. Once i get back home (2-3 days) i will post some logs, in the meantime, can someone please confirm if the issue persists, and gather logs? ?

can i use this method in stock firmware(rooted) because i cant see any fstab file in vendor/etc/

jedtan025 said:
can i use this method in stock firmware(rooted) because i cant see any fstab file in vendor/etc/
Click to expand...
Click to collapse
Just making sure but you are on emui8 right? Also are you checking with a file manager in Android or are you searching in twrp?

neondragon1909 said:
Just making sure but you are on emui8 right? Also are you checking with a file manager in Android or are you searching in twrp?
Click to expand...
Click to collapse
im searching in twrp bro. bro question. im using pra lx2 oreo firmware. and im wanna go back to nougat. it is possible? i got the firmware now but dont know how to flash nougat. dload failed. and i cant use hurupdarer bcos nougat firmware only has 2 zip file

jedtan025 said:
im searching in twrp bro. bro question. im using pra lx2 oreo firmware. and im wanna go back to nougat. it is possible? i got the firmware now but dont know how to flash nougat. dload failed. and i cant use hurupdarer bcos nougat firmware only has 2 zip file
Click to expand...
Click to collapse
I couldn't find the file using TWRP either. Had to use root explorer to find and edit the file. As for hurupdater, I'm not sure if it's the same for your region, but for pra-la1 there were 3 files.
And as for the the 2 files, I successfully flashed using the updater with only the update.zip so try updating anyway. If that doesn't work, use the eRecovery

Update:
Added Magisk news;
Added stock PRA ramdisk

UPDATE:
Added Offline Charging Fix in post #2
Added references to Treble Enabled device development;
New Huawei Magisk Camera;

Hello,
I'm having problems finding the download links in the guide to obtain Treble, I've searched here and clicked on the link to the guide but there i can't find it eather.

cyprian99 said:
Hello,
I'm having problems finding the download links in the guide to obtain Treble, I've searched here and clicked on the link to the guide but there i can't find it eather.
Click to expand...
Click to collapse
Obtain what?
Treble roms?

Yay! Emui 8.0 has arrived on my c432 pra-lx1 (b360) . Everything is perfect.

The guide to get treble is unclear, how can the very first step be to download update.zip? I did and now i have a trojan, thanks a lot

How to unlock bootloader? Now the Huawei site is unavailable
Wysłane z mojego PRA-LX1 przy użyciu Tapatalka

[MultiROM] MultiROM for Polaris [28.01.20]

New member, had to post it in this section.
This is a test version of MultiROM.
WARNING
It is DANGEROUS to flash MultiROM to your device. It can cause data loss. If you have important files on your phone, NEVER try to do that.
Introduction
MultiROM is a boot manager that allows you to flash multiple roms into the device.
This port for Polaris is based on Tasssadar's work and Vasishath's modification. It seems to work fine now.
You can refer to Vasishath's original post for installation guide.
Reference Links:
[XDA Thread] https://forum.xda-developers.com/poco-f1/development/multirommiui-custom-roms-gsi-t3868734
[Github][MultiROM] https://github.com/ARTI5T/multirom
[Github][Modified-TWRP] https://github.com/ARTI5T/android_bootable_recovery
Download link is below.
Notes:
* You can use MultiROM only with decrypted devices.
* Flash a patch to disable force encryption after flash a ROM with force encryption.
* Don't manually encrypt your data in any ROMs.
* If you want to flash treble GSI, choose A-only images.
** Flashing A/B GSI is theoretically possible if you flash it to a secondary ROM which supports system-as-root. (NOT TESTED)
* Unfortunately, until now, we cannot update a secondary ROM with treble GSI. Now you can update a secondary ROM with system.img.
* Always backup your file before flashing. Especially boot.img or boot partition.
* Be careful with your lockscreen password. You can only set password in either primary ROM or secondary ROMs. Refer to vasishath's thread for more details.
* Not all ROMs are compatible with MultiROM.
* Android 10 can be flashed as a primary ROM. If you have an android 10 ROM as primary, you need an android 9 boot.img and vendor.img in case you have GSIs based on android 9.
Known issue:
* Sometimes touch in TWRP or MultiROM boot screen doesn't work. If you are in TWRP, just reboot. If you are in boot screen, you can also reboot or use volumn +/- instead.
* If you want to uninstall MultiROM, you may need to flash the stock boot.img (In case it can't boot). So please backup your boot.img before flashing.
* Still some bugs with system/vendor compatibility verification. If you meet such errors, please flash a "base firmware" (e.g., MIUI) first, and then flash your zip in "List ROMs".
* In some rare cases, flashing a zip in secondary ROMs may cause primary ROM damage.
This port is only for DECRYPTED device. Don't flash if your device is encrypted.
Please BACKUP before you flash MultiROM.
We're not responsible for any loss caused by this modification.
Download link:
[Google Drive] https://drive.google.com/drive/folders/1C2d3GQT5WVsw83XU6J5qA_oJOYMxyXNX?usp=sharing

Update Log:
28-01-20: Support Android 10 as secondary ROMs. Fix bugs which in some cases cause error 7 when flashing.
17-08-19: Add "Install system.img/vendor.img" in "List ROMs".
16-08-19: Add "skip compatibility verify". Fix some small bugs.
15-08-19: Merge omnirom 3.3.1 source code.
14-08-19: Initial release
Tested on:MIUI11(Android10);ArrowOS(Android 10);LOS17;Flyme8(Android9)

Fantastic. Will try it tomorrow morning and report. Looking forward to it!

I'm having some issues with flashing error for the secondary ROMS. I always get a different error, but from what I can see, they are "outdated" TWRP errors.
Primary ROM is RR. Appears to work.
When I flash a secondary ROM I get:
Pixel3: Zip Treble compatability error. Invalid zip file format.
Arrow: Zip Treble compatability error. Invalid zip file format.
Downloading a few other roms to test, but probably the same error
Any solution?
edit:
Started completely over from scratch. Completely wiped data, installed latest vendor/firmware/ etc...
Still have the same issue, but different flashing error:
With pixel3rom
"string resource 'zip_compatible_err' not found.
Using default value.
ZIP Treble compatibility error!
invalid zip file format.
And then it just aborts.
With arrow OS:
Zip treble compatibility error
invalid zip file format
And then it just aborts.

Firipu said:
I'm having some issues with flashing error for the secondary ROMS. I always get a different error, but from what I can see, they are "outdated" TWRP errors.
Primary ROM is RR. Appears to work.
When I flash a secondary ROM I get:
Pixel3: Zip Treble compatability error. Invalid zip file format.
Arrow: Zip Treble compatability error. Invalid zip file format.
Downloading a few other roms to test, but probably the same error
Any solution?
Click to expand...
Click to collapse
Yes, the recovery is outdated (version 3.2.3-0). Vasishath's repository hasn't been updated yet. You can try to delete compatibility.zip in the zip file and see if it works. I've only tested some old Roms (RR treble, pixel experience) and they worked fine. I will also try to merge new features from official TWRP. BTW, I am just an amateur developer so maybe it will take some time or even not possible.

__ART1st__ said:
Yes, the recovery is outdated (version 3.2.3-0). Vasishath's repository hasn't been updated yet. You can try to delete compatibility.zip in the zip file and see if it works. I've only tested some old Roms (RR treble, pixel experience) and they worked fine. I will also try to merge new features from official TWRP. BTW, I am just an amateur developer so maybe it will take some time or even not possible.
Click to expand...
Click to collapse
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)

Firipu said:
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Click to expand...
Click to collapse
Okay. I'll try to update my code. Perhaps a looooooong time

Firipu said:
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Click to expand...
Click to collapse
Now you can try the new recovery.img with version 3.3.1 and let me know the result. It may fix that issue (haven't tested yet myself)

Firipu said:
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Click to expand...
Click to collapse
Just remove the asserts lines in updater scripts. That would do it.
Sent from my Pixel 3 using Tapatalk

I do everything good, only one problem, install both roms good, making boot good,and when I go from one rom to the other the pin thont work,say it's another pin, somebody can help me?
Sent from my [device_name] using XDA-Developers Legacy app

paulojorjealmeida said:
I do everything good, only one problem, install both roms good, making boot good,and when I go from one rom to the other the pin thont work,say it's another pin, somebody can help me?
Click to expand...
Click to collapse
It always happened to me with multirom and dualbootpatcher. You have to delete locksettings files in data/system directory...

paulojorjealmeida said:
I do everything good, only one problem, install both roms good, making boot good,and when I go from one rom to the other the pin thont work,say it's another pin, somebody can help me?
Click to expand...
Click to collapse
Go to /data/system and delete all *.key files.Now you should get in without typing any password.

Lucas_Maximiliano said:
Go to /data/system and delete all *.key files.Now you should get in without typing any password.
Click to expand...
Click to collapse
Thanks men
Sent from my [device_name] using XDA-Developers Legacy app

paulojorjealmeida said:
Thanks men
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Alô,thats its not de solucion,i sink,but you now how to fix the pin problem
Sent from my [device_name] using XDA-Developers Legacy app

paulojorjealmeida said:
Alô,thats its not de solucion,i sink,but you now how to fix the pin problem
Click to expand...
Click to collapse
If you have the password problem, go to vasishath's thread and download a patch to clear password.

Im having error 7 when installing multirom zip, i am in MIUI EU 9.8.9 now, does that has anything to be with it? im really looking forware to install it but i dint know the issue, maybe it has to be with the updater script, i dont know.
Edit, even tho it showed error 7 when flashing mulrom zip, everything seems to work just fine. Should i reinstall it or is it ok?

Kripton_ said:
Im having error 7 when installing multirom zip, i am in MIUI EU 9.8.9 now, does that has anything to be with it? im really looking forware to install it but i dint know the issue, maybe it has to be with the updater script, i dont know.
Edit, even tho it showed error 7 when flashing mulrom zip, everything seems to work just fine. Should i reinstall it or is it ok?
Click to expand...
Click to collapse
Install fw+vendor 9.7.25.eu,for me resolve the problem
Sent from my [device_name] using XDA-Developers Legacy app

Kripton_ said:
Im having error 7 when installing multirom zip, i am in MIUI EU 9.8.9 now, does that has anything to be with it? im really looking forware to install it but i dint know the issue, maybe it has to be with the updater script, i dont know.
Edit, even tho it showed error 7 when flashing mulrom zip, everything seems to work just fine. Should i reinstall it or is it ok?
Click to expand...
Click to collapse
Are you sure your are using MIX2S Polaris? Not Mi8 or Poco F1 or MIX3?

It works fine on my device,I use Android Q gsi for internal,the MIUI is secondary.the problem is higher version of MIUI couldn't boot,it just reboot to recovery after "mix" logo on MIUI stable 10.3.4.0.

Writesin said:
It works fine on my device,I use Android Q gsi for internal,the MIUI is secondary.the problem is higher version of MIUI couldn't boot,it just reboot to recovery after "mix" logo on MIUI stable 10.3.4.0.
Click to expand...
Click to collapse
Did you boot any version of MIUI successfully? Could you try another version to see if it can boot? It can sometimes be the ROM's problem. If it still fails to boot, please tell me the version that can boot and the version which can't boot. But I am a student so maybe not too much time on debugging.

Latest Android 10 - unsupported/Unknown format from Magisk

Hi,
New PH-1 owner here. Just got the phone new from Amazon. It was on 7.1.1. Immediately it upgraded to 9.0, and then to 10, build QQ1A-200105.32 with Feb. security updates. Impressive! After reading through some (a lot) of the material collected about the phone, I decided that at first I'd only root it (i.e. without installing TWRP) with Magisk. After getting familiar with the two rooting guide ("[GUIDE] Rooting your Essential PH-1" and "[Guide] How to Install TWRP & Root Essential PH-1(Method 2)") I actually followed this write up, and it :crying:FAILED.
I tried both ('PH1-Images-QQ1A.200105.032.zip', and 'PH1-OTA-QQ1A.200105.032.zip') Essential provided images and with both Magisk (v. 20.3 and MMgr. v. 7.5.1) failed with "Unsupported/Unknown image format"
So, that's the status, and I'll welcome any and all advise on the above, but in the meantime, a question:
1 - If I flash this ('4.4.166-stock-twrp-mgk181.img') image will I loose Android 10,or the ability to have later upgrades?
Thanks!

MarSOnEarth said:
Hi,
New PH-1 owner here. Just got the phone new from Amazon. It was on 7.1.1. Immediately it upgraded to 9.0, and then to 10, build QQ1A-200105.32 with Feb. security updates. Impressive! After reading through some (a lot) of the material collected about the phone, I decided that at first I'd only root it (i.e. without installing TWRP) with Magisk. After getting familiar with the two rooting guide ("[GUIDE] Rooting your Essential PH-1" and "[Guide] How to Install TWRP & Root Essential PH-1(Method 2)") I actually followed this write up, and it :crying:FAILED.
I tried both ('PH1-Images-QQ1A.200105.032.zip', and 'PH1-OTA-QQ1A.200105.032.zip') Essential provided images and with both Magisk (v. 20.3 and MMgr. v. 7.5.1) failed with "Unsupported/Unknown image format"
So, that's the status, and I'll welcome any and all advise on the above, but in the meantime, a question:
1 - If I flash this ('4.4.166-stock-twrp-mgk181.img') image will I loose Android 10,or the ability to have later upgrades?
Thanks!
Click to expand...
Click to collapse
First, TWRP doesn't work well with latest stock ROM (QQ1A.200105.032), if you'd like to use TWRP, you should use one level down (QQ1A.200105.007)
Second, there's no more upgrade for this ROM, Essential stopped support it, and Feb update was the last one.

Thanks for your reply. For now, all I would love is to get root and not loose the ability to get future updates from Google (I do understand Essential is toast, but with Android 10 Google will provide many updates, right?). So, not much interest in TWRP, just root.
Regarding 4.4.166-stock-twrp-mgk181.img: what Android version does it have, and when installed, can it be upgraded?
Thanks

MarSOnEarth said:
Thanks for your reply. For now, all I would love is to get root and not loose the ability to get future updates from Google (I do understand Essential is toast, but with Android 10 Google will provide many updates, right?). So, not much interest in TWRP, just root.
Regarding 4.4.166-stock-twrp-mgk181.img: what Android version does it have, and when installed, can it be upgraded?
Thanks
Click to expand...
Click to collapse
Maybe I don't quite clear about your question, but why do you use that TWRP file?
I always use the official one from TWRP
https://twrp.me/essential/essentialph1.html
And regarding to Google update, as long as you don't use custom rom + microg then I believe you always get updated from Google Play store for your apps.

chanh2018 said:
Maybe I don't quite clear about your question, but why do you use that TWRP file?
I always use the official one from TWRP
https://twrp.me/essential/essentialph1.html
And regarding to Google update, as long as you don't use custom rom + microg then I believe you always get updated from Google Play store for your apps.
Click to expand...
Click to collapse
Ah, yes! My interest in 4.4.166-stock-twrp-mgk181 image is because, a) I failed to get root with Magisk, and b) this is a `fastboot` image that's already rooted (notice the mgk181 part of the name), BUT because it was made in January of 2019, I think (if it does, and I know too little to know that) it contains older version of Android, hence the question about whether I will be able to update from it.
Thanks

MarSOnEarth said:
Thanks for your reply. For now, all I would love is to get root and not loose the ability to get future updates from Google (I do understand Essential is toast, but with Android 10 Google will provide many updates, right?).
Thanks
Click to expand...
Click to collapse
As I understand it Google will push some updates/security patches for Android via Play store but not everything, you still need updates from your manufacturer (which we now won't get) so you likely won't have all security patches, for this you need an up to date custom ROM like LineageOS (only at ver 9 pie currently) or maybe use the GSI (see Android 11 preview thread) but that is still in development at the moment so probably not suitable for daily use due to bugs & missing features.

MarSOnEarth said:
I actually followed this write up, and it :crying:FAILED.
I tried both ('PH1-Images-QQ1A.200105.032.zip', and 'PH1-OTA-QQ1A.200105.032.zip') Essential provided images and with both Magisk (v. 20.3 and MMgr. v. 7.5.1) failed with "Unsupported/Unknown image format"
Click to expand...
Click to collapse
I don't use TWRP, but I do have root, so if that's enough for you, see the steps below. Magisk version that you mentioned (v.20.3 and MMgr. v.7.5.1) works perfectly.
Since you are already on Feb update (the latest and the last one from Essential), you don't need the OTA zip. You only need the "PH1-Images-QQ1A.200105.032.zip" - the full fastboot image. Make sure you download and install the ADB/Fastboot from Essential website on your PC - it comes bundled with the Windows driver linked on their Developer page. Also make sure you have a good USB cable (do NOT use the one that comes with the phone!), and avoid using USB3 ports on your PC (use USB2 instead).
1. Extract boot.img from PH1-Images-QQ1A.200105.032.zip.
2. Install Magisk Manager, if not installed already.
3. Copy the extracted boot.img to the phone, then patch it with Magisk.
4. Copy the patched boot.img to PC.
5. Reboot the phone into bootloader.
6. Run the command "fastboot flash boot <your_patched_boot>.img" from your PC.
7. Reboot the phone.
8. Enjoy the root access.

IronRoo said:
As I understand it Google will push some updates/security patches for Android via Play store but not everything, you still need updates from your manufacturer (which we now won't get) so you likely won't have all security patches, for this you need an up to date custom ROM like LineageOS (only at ver 9 pie currently) or maybe use the GSI (see Android 11 preview thread) but that is still in development at the moment so probably not suitable for daily use due to bugs & missing features.
Click to expand...
Click to collapse
True. Eventually, a proper custom recovery, like TWRP, might be essential (har, har) years down the road (although I only now am coming down from a Moto X (first gen, 2013) that between AFWall and XPrivacy I managed to keep on stock firmware all along), but now I need to get this phone prepped up for daily use, and that means getting root first of all (and from kt-Froggy's note I shall... I see now where I goofed).
I appreciate your input. Thanks!

kt-Froggy said:
I don't use TWRP, but I do have root, so if that's enough for you, see the steps below. Magisk version that you mentioned (v.20.3 and MMgr. v.7.5.1) works perfectly.
Since you are already on Feb update (the latest and the last one from Essential), you don't need the OTA zip. You only need the "PH1-Images-QQ1A.200105.032.zip" - the full fastboot image. Make sure you download and install the ADB/Fastboot from Essential website on your PC - it comes bundled with the Windows driver linked on their Developer page. Also make sure you have a good USB cable (do NOT use the one that comes with the phone!), and avoid using USB3 ports on your PC (use USB2 instead).
1. Extract boot.img from PH1-Images-QQ1A.200105.032.zip.
2. Install Magisk Manager, if not installed already.
3. Copy the extracted boot.img to the phone, then patch it with Magisk.
4. Copy the patched boot.img to PC.
5. Reboot the phone into bootloader.
6. Run the command "fastboot flash boot <your_patched_boot>.img" from your PC.
7. Reboot the phone.
8. Enjoy the root access.
Click to expand...
Click to collapse
Thanks! From the above, it looks like I messed up on the very first step; I was giving Magisk the whole PH1-Images-QQ1A.200105.032.zip file and not the boot.img extracted from it. Oops!

MarSOnEarth said:
Thanks! From the above, it looks like I messed up on the very first step; I was giving Magisk the whole PH1-Images-QQ1A.200105.032.zip file and not the boot.img extracted from it. Oops!
Click to expand...
Click to collapse
That was my suspicion from how I read your post... ? Yeah, you need just the boot image extracted from the zip. The process is really simple, and it's been working for me with no issues, apart from one specific laptop where I was consistently getting errors for no apparent reason, so I just used other PCs.

kt-Froggy said:
That was my suspicion from how I read your post... Yeah, you need just the boot image extracted from the zip. The process is really simple, and it's been working for me with no issues, apart from one specific laptop where I was consistently getting errors for no apparent reason, so I just used other PCs.
Click to expand...
Click to collapse
OK, that worked splendidly. Thanks!

No space in system partition.

I had my oneplus one unused for a while and wanted to make some use out of it.
So i installed twrp and tried flashing lastest custom rom into it.
I was successful in flashing official Lineage and rr remix to it,but whenever i try to install gapps,it says no enough space in the system partition.
I tried resizing it through the wipe menu but that somehow doesn't work,i.e. the size of system remains the same,which i tried after installing os.
I hope this info can atleast give you a brief idea what i am talking about,any help is appreciated.

Use recommended by Lineage OS team MindTheGapps.
Opengapps doesn't fit anymore.

ImmortAlex said:
Use recommended by Lineage OS team MindTheGapps.
Opengapps doesn't fit anymore.
Click to expand...
Click to collapse
This was pretty straight forward,how did i miss that.This worked for me,installed with Lineage OS.Thank you very much.
I tried installing lineage 18 onto one of my other device for which i was able to install open gapps pico,i don't know why it won't work for opo.
As i am not able to increase my system partition from twrp,i think there is some different issue aswell,i don't have enough understanding of these stuff to understand what the problem is.
I tried installing open gapps with rr remix aswell,but recieved the same error.
Anyways, thank you so much,i really appreciate your help.

Hi, i making this video showing to how to resize system partition on opo u can check it out here:

alprtewwqfr said:
Hi, i making this video showing to how to resize system partition on opo u can check it out here:
Click to expand...
Click to collapse
I will try this after some time,i don't have enough time right now for this. Thank you

ok! If you have any problem fell free to ask me!

Have a look at guide to re-size system partition at: https://forum.xda-developers.com/t/...system-partition-and-maybe-even-more.4153599/
Only issue I had was being able to install Magisk. Couldn't use TWRP and patched boot.img method which worked a treat.