[ROM][UNOFFICIAL][9.0.0_R47] dotOS 3.1 [AXON7][08/13/19]

SaintZ93 · Aug 13, 2019

" #DroidOnTime "

ROM Version: 3.1
Device: axon7
Maintainer: SaintZ93
Build Status: Unofficial

Code:

 * Your warranty is now void.
 * We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels. 
 * You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.

"This is a user-friendly thread, all your suggestions are important to us and will be taken into consideration.."

dotOS is an Android ROM which focuses on performance and stability. We focus on making our rom look and feel great without struggling on Performance and Battery! So that one can get most out of his/her device.....

CLEAN FLASH :
Download the latest build and GApps
Reboot to recovery
Make NAndroid backup (Not Necessary)
Wipe System, Data, Cache , Dalvik, Vendor
Flash the latest build and GApps
Reboot

DIRTY FLASH :
Download the latest build
Reboot to recovery
Flash the latest build
Wipe Cache
Reboot

Note: GApps only has to be flashed once whereas Magisk/Su is to be flashed every time you Dirty Flash the OTA Update.

DotOS Axon7 Downloads

OpenGApps

Note : Pico, Nano or Micro Gapps are recommended. We don't prefer STOCK/HEAVY Gapps

DotOSteam
AOSP
JDC Team
Aosp Extended
Dirty Unicorns
And all other open source Devs/Teams.

Mohan CM - Founder/Core Developer
Sam Grande - UI Developer/Project Co-ordinator
Iacob Ionut - UI Developer/ Core Developer
Hari Ambadi - Core GFX/Visual Designer

Special thanks:
Alexc Brookes - Arts & Wallpaper Designer
Paul Petrov - Arts & UI Designer

Important Links

Liked The ROm? Want to Help Us? Then gift us some credits

dot
OS source
dotOS-Device Sources
Device Tree
Kernel Source

Google Plus Community

Telegram Group
Telegram Channel

Website

REPORTING BUGS!
As soon as the problem occurs, take a logcat!
for more READ THIS

XDA:DevDB Information
[UNOFFICIAL][9.0.0_R47] dotOS 3.1 [AXON7][08/13/19], ROM for the ZTE Axon 7

Contributors
SaintZ93
Source Code: https://github.com/DotOS

ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Oreo Baseband
Based On: DotOS

Version Information
Status: Stable
Current Stable Version: 3.1
Stable Release Date: 2019-08-13

Created 2019-08-13
Last Updated 2019-08-13

leo22498 · Aug 14, 2019

Thank you for the rom, everything is working ok.

This is the best pie rom I have tried, everything is fast and smooth.

By the way, what does it means the "R47" at the title?

SaintZ93 · Aug 14, 2019

Google source code android release tag

troy5890 · Aug 14, 2019

Ah yes, my favorite custom ROM has returned in absolute glory. Thank you for bringing this to the Axon 7. Everything is running smooth and working well, with great stability.

Dragon502 · Aug 15, 2019

Not working for me, stuck on boot.

Diez3l · Aug 15, 2019

Hi all !
I have the same problem @Dragon502

That's ok for me, after doing a Flash EDL Axon7_LOS15.1_180925_B12Oki_TWRP_LABS1.3_FULL_EDL.zip

SaintZ93 · Aug 15, 2019

You didn't follow instructions then. Its been working for everyone, including me.

Dragon502 · Aug 15, 2019

SaintZ93 said:
You didn't follow instructions then. Its been working for everyone, including me.

I can assure you I have, they are not that complex.
If I messed up something is in the "treblerization" which I still find quite confusing. What I did was:
- wiping everying
- creating vendor partion with TWRP w/PARTY mod.
- reflashing Draken's bootstack and modem
- flashing NFound v1.1 zip (vendor's?)
- reflashing TWRP since NFound's zip rolls it back
- wiping everything again (system, vendor, data, cache and dalvik) (rom's instructions)
- flash dotOs
- flash Gapps
- reboot

Notice that on boot I had and still have the "your device is corrupt" thing, but it lets me boot. It would be amazing if someone could help me remove that or at least tell me what component does that.
Anyway, from the reboot it hangs loading on the dynamic initial logo. I waited the first time about 30 min and about 15 the second time I did it.

Now I am running AOKP Oreo which seems to be working fine.
I needed a new a ROM because the AEX I was running messed up the USB connection which I need for app devel.

I believe this is all. Hopefully I recalled correctly what I did even if the "treblerization" thing is still confusing to me, or at least its practical implementation is.

SaintZ93 · Aug 15, 2019

Dragon502 said:
I can assure you I have, they are not that complex.
If I messed up something is in the "treblerization" which I still find quite confusing. What I did was:
- wiping everying
- creating vendor partion with TWRP w/PARTY mod.
- reflashing Draken's bootstack and modem
- flashing NFound v1.1 zip (vendor's?)
- reflashing TWRP since NFound's zip rolls it back
- wiping everything again (system, vendor, data, cache and dalvik) (rom's instructions)
- flash dotOs
- flash Gapps
- reboot

Notice that on boot I had and still have the "your device is corrupt" thing, but it lets me boot. It would be amazing if someone could help me remove that or at least tell me what component does that.
Anyway, from the reboot it hangs loading on the dynamic initial logo. I waited the first time about 30 min and about 15 the second time I did it.

Now I am running AOKP Oreo which seems to be working fine.
I needed a new a ROM because the AEX I was running messed up the USB connection which I need for app devel.

I believe this is all. Hopefully I recalled correctly what I did even if the "treblerization" thing is still confusing to me, or at least its practical implementation is.

Do not use NFounds crap as these new ROMs are device related and not GSI.

Dragon502 · Aug 15, 2019

SaintZ93 said:
Do not use NFounds crap as these new ROMs are device related and not GSI.

So I should have removed the vendor's partition to flash this ROM? AOKP seems to work fine but it lacks some feature (like night light) and is still Oreo. Maybe when I find the time I may attempt again.

Choose an username... · Aug 15, 2019

Dragon502 said:
I can assure you I have, they are not that complex.
If I messed up something is in the "treblerization" which I still find quite confusing. What I did was:
- wiping everying
- creating vendor partion with TWRP w/PARTY mod.
- reflashing Draken's bootstack and modem
- flashing NFound v1.1 zip (vendor's?)
- reflashing TWRP since NFound's zip rolls it back
- wiping everything again (system, vendor, data, cache and dalvik) (rom's instructions)
- flash dotOs
- flash Gapps
- reboot

Notice that on boot I had and still have the "your device is corrupt" thing, but it lets me boot. It would be amazing if someone could help me remove that or at least tell me what component does that.
Anyway, from the reboot it hangs loading on the dynamic initial logo. I waited the first time about 30 min and about 15 the second time I did it.

Now I am running AOKP Oreo which seems to be working fine.
I needed a new a ROM because the AEX I was running messed up the USB connection which I need for app devel.

I believe this is all. Hopefully I recalled correctly what I did even if the "treblerization" thing is still confusing to me, or at least its practical implementation is.

- creating vendor partion with TWRP w/PARTY mod.

did you select 512mb and System? That's what you need to use. Anyways the best way would probably be installing LOS 16 as it makes you a vendor partition, but you'd have to delete the previous one for that.

- flashing NFound v1.1 zip (vendor's?)

Yes, that's NFound's vendor files, made for GSI's. This isn't needed as any new device specific ROMs come with a vendor, so it'll get overwritten. hell, you actually wipe vendor after reflashing TWRP. also, no need to be using NFound's ancient stuff anymore, only the TWRP is useful and even then I prefer Oki's

Also you might want to flash Magisk before booting

Dragon502 · Aug 15, 2019

Choose an username... said:
- creating vendor partion with TWRP w/PARTY mod.

did you select 512mb and System? That's what you need to use. Anyways the best way would probably be installing LOS 16 as it makes you a vendor partition, but you'd have to delete the previous one for that.

No, I made a 800mb one from data but from the end of the partition. It should make no difference the size of the partion, shouldn't it?

Choose an username... said:
-
- flashing NFound v1.1 zip (vendor's?)

Yes, that's NFound's vendor files, made for GSI's. This isn't needed as any new device specific ROMs come with a vendor, so it'll get overwritten. hell, you actually wipe vendor after reflashing TWRP. also, no need to be using NFound's ancient stuff anymore, only the TWRP is useful and even then I prefer Oki's

Also you might want to flash Magisk before booting

Finally is starting to make sense, therefore these ROMs are "treblerized" but prepackaged to be device specific right?

As concerning the bootstacks, with an A2017G, does it makes sense for me to still have Draken's or I can safely upgrade to a B03 full EDL with the Axon tool? What would change between the versions?

Dragon502 · Aug 15, 2019

Attempt update

Logs:

Code:

 #########################################
 #                                       #
 #             - P A R T Y -             #
 #                                       #
 #   The Android Partition Treblerizer   #
 #                                       #
 #########################################
 #                                       #
 #     v0.6 (c) Oki @ XDA 2018-08-31     #
 #                                       #
 #########################################
 
 
 This tool creates or removes the vendor
 partition taking space from system or
 userdata partitions. This way, developers
 will be able to create Treble ROMs for
 legacy devices. and users can switch back
 and forth from Non Treble to Treble ROMs.
 
 Press Vol Up to continue...
 
 CURRENT CONFIGURATION:
 SYSTEM size: 5.5 GB
 DATA size:  52.41 GB
 VENDOR SIZE: 512 MB
 
 
 - Vendor partition detected after SYSTEM partition.
   Do you want to remove Vendor and return to stock
   partition table?
   Vol UP: YES / Vol DN: NO
 
 - No changes were applied to the partition table.
I:Updater process ended with RC=0
I:Install took 5 second(s).
Updating partition details...
I:Data backup size is 0MB, free: 44461MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=0
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:operation_start: 'Flashing'
Installing zip file '/external_sd/dotOS-P-v3.1-axon7-UNOFFICIAL-20190813-0014.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:Update binary zip
Verifying package compatibility...
Package doesn't contain compatibility.zip entry
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
SELinux: Loaded file_contexts
Checking for TZ version TZ.BF.4.0.1-00353Checking for TZ version TZ.BF.4.0.1-00353

script aborted: assert failed: axon7.verify_trustzone("TZ.BF.4.0.1-00353") == "1"
assert failed: axon7.verify_trustzone("TZ.BF.4.0.1-00353") == "1"error: 25
Updater process ended with ERROR: 7
I:Install took 0 second(s).
Error installing zip file '/external_sd/dotOS-P-v3.1-axon7-UNOFFICIAL-20190813-0014.zip'
Updating partition details...
I:Data backup size is 0MB, free: 44461MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=1
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'copylog'
I:Set page: 'action_page'
I:operation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /external_sd/recovery.log

script aborted: assert failed: axon7.verify_trustzone("TZ.BF.4.0.1-00353") == "1"
If I have to guess it seems like the issue comes from the bootstack. I tried with the B04 I found for SL!M8 as I am downloading B03_FULL_EDL.

Dragon502 · Aug 15, 2019

Update: The "your device is corrupted... " screen went away with Drakens B03 bootsack I have managed to find, but the ROM still throws the same error with the verify_trustzone issue.

Diez3l said:
Hi all !
I have the same problem @Dragon502

That's ok for me, after doing a Flash EDL Axon7_LOS15.1_180925_B12Oki_TWRP_LABS1.3_FULL_EDL.zip

Oh, I did not see that. I am going to try that.

---------- Post added at 10:44 PM ---------- Previous post was at 10:04 PM ----------

Yup, LOS 15 Bootstak, although brough back the "your device is corrupted" screen, did the trick. DotOS Pie is working for me.
Now it is time to check if everything works. Thank you both @Diez3l and @SaintZ93.

leo22498 · Aug 15, 2019

Hello, I have a problem, I can't switch data service network from sim1 to sim2

Sent from my ZTE A2017U using Tapatalk

Choose an username... · Aug 16, 2019

Dragon502 said:
No, I made a 800mb one from data but from the end of the partition. It should make no difference the size of the partion, shouldn't it?

It does. Your partition is literally all wrong lol, should be System and 512.

Dragon502 said:
Finally is starting to make sense, therefore these ROMs are "treblerized" but prepackaged to be device specific right?

Not really - Treble is something inherent to the device, and on new devices, which have treble by default, everything is made to work with it. Think about it as a simple move of some files to a specific partition.
ROMs use Treble but at the same time are made with the actual phone device tree. GSIs use the generic device tree instead

Dragon502 said:
As concerning the bootstacks, with an A2017G, does it makes sense for me to still have Draken's or I can safely upgrade to a B03 full EDL with the Axon tool? What would change between the versions?

I'm not getting this one - B03 full EDL? You wanna return to stock?

Dragon502 · Aug 16, 2019

Choose an username... said:
It does. Your partition is literally all wrong lol, should be System and 512.

That is some prerequisite I would write in the installation instruction.

Choose an username... said:
Not really - Treble is something inherent to the device, and on new devices, which have treble by default, everything is made to work with it. Think about it as a simple move of some files to a specific partition.
ROMs use Treble but at the same time are made with the actual phone device tree. GSIs use the generic device tree instead

Ah, ok. They are device specific ROMs repackaged to fit in "treblerized" phones.

Choose an username... said:
I'm not getting this one - B03 full EDL? You wanna return to stock?

Nope, I wanna understand what is the difference between a full EDL and a boostack zip. Well, I have found that they contain a stock image.

Thank you for the enlightment.
As a final update everything I care about seems to be working (DAC, baddar kernel, Ainur narsil, usb debugging and night light).

Choose an username... · Aug 16, 2019

Dragon502 said:
That is some prerequisite I would write in the installation instruction.

Oki's fault - anyways not many people use Party, and the one swho did sometimes had non-working vendors even though they were correct.

Dragon502 said:
Ah, ok. They are device specific ROMs repackaged to fit in "treblerized" phones.

Still no. Our phone IS Treble now, hence the ROM has to be treble. The thing that has been "treblerized" is the Axon7.
You can't take any ROM and "repackage" it, you have to build it specifically for a certain phone. then, it gets whatever it needs to run on it

Dragon502 said:
Nope, I wanna understand what is the difference between a full EDL and a boostack zip. Well, I have found that they contain a stock image.

The bootstack zip has some files like fastboot, the boot stuff like boot image and everything that supports it, modem image, etc.
A full EDL zip is the whole damn system, so you also get stock system and the recovery which is 90% of the full edl zip

kirknado18 · Jan 25, 2020

Choose an username... said:
Oki's fault - anyways not many people use Party, and the one swho did sometimes had non-working vendors even though they were correct.

Still no. Our phone IS Treble now, hence the ROM has to be treble. The thing that has been "treblerized" is the Axon7.
You can't take any ROM and "repackage" it, you have to build it specifically for a certain phone. then, it gets whatever it needs to run on it

The bootstack zip has some files like fastboot, the boot stuff like boot image and everything that supports it, modem image, etc.
A full EDL zip is the whole damn system, so you also get stock system and the recovery which is 90% of the full edl zip

This rom does not boot on my axon a2017u bootloops

[ROM][UNOFFICIAL][9.0.0_R47] dotOS 3.1 [AXON7][08/13/19]

Senior Member

Member

Senior Member

Senior Member

Member

New member

Senior Member

Member

Senior Member

Member

Senior Member

Member

Member

Member

Member

Senior Member

Member

Senior Member

Senior Member

Similar threads

Top Liked Posts