Related
New to Nexus 9 and just wondered if the Vendor img has to match the ROM? Do you need to flat the corresponding bootloader image.
I ask because I recently flashed the latest vendor but got the vendor warning until I flashed the previous vendor.
I thought as long as I am on the latest vendor I could load any M rom.
WARNING: You'll most probably loose ALL your data, and might break your phone. Please use with extreme caution!
The goal of this ROM is to experience ColorOS 6.0 on any non-oppo and non-realme phone.
For a list of treble supported devices, consult and fill https://github.com/phhusson/treble_experimentations/wiki
How to flash:
1- Flash a treble pie rom (CAF vendor recommended.)
2- Extract 7z file and flash system.img
3- If base rom isn't permissive flash permissiver.
4- Reboot
Bugs:
- Fingerprint
- Since it's oem port maybe more on your device. But common bug is Fingerprint.
Download:
system.img for A-A/B ARM64 devices
Telegram Account: MacTavishAO In case of any problem please send me logs.
Thanks to: @erfanoabdi for everything..
Reserved. You can follow me on github.
Changelog:
1.0: Initial release.
Does it include stock sounds and ringtones? Thanks
ZoiraP said:
Does it include stock sounds and ringtones? Thanks
Click to expand...
Click to collapse
yes
Nice work.
Keep it up.
After reebot after flashing system, back to recovery. Any solution? Device Nubia Z17 (NX563J)
surfer30 said:
After reebot after flashing system, back to recovery. Any solution? Device Nubia Z17 (NX563J)
Click to expand...
Click to collapse
You need pie treble vendor, permissiver.
I flashed over Lineage 16GSI (android 9). But not flashed permissiver - you sugested tryed once more?
Kanka Lenovo Z5 direk crash diag bölümüne atıyor dediklerini harfiyen yaptığım halde.
Lenovo Z5(L78011) didnt work.
Stuck on boot logo. My Vendor is CAF and flashed permissiver V2
Couldn't flash in nokia 6.1 plus
Image file size larger than target device eror in twrp ..
Plz solve my problem..:crying:
Either bootloops or doesn't get past the boot image on Note9 N960F no matter what. (Different kernels, flash on different systems etc.)
rahul387 said:
Image file size larger than target device eror in twrp ..
Plz solve my problem..:crying:
Click to expand...
Click to collapse
That isnt how it works
Some random said:
That isnt how it works
Click to expand...
Click to collapse
When i flash color os in my nokia 6.1 plus .. its showing me that the image file is bigger than target device!!
Any solution for me ..?
I have 2 questions :
1) Can I flash this ROM on Mi Max 2 with Orange Fox 10 recovery?
2) Can this be used for daily life usage?
Thank you
No boot
System partition smaller than image
rahul387 said:
When i flash color os in my nokia 6.1 plus .. its showing me that the image file is bigger than target device!!
Any solution for me ..?
Click to expand...
Click to collapse
I read that we have to resize the system partition when that error occurs. It's too advanced for me so I left it.
Kicked into fastboot
I've tried installing it exactly as described here and also how it's described for other pie GSIs for oneplus5t but I only get kicked into the fastboot mode. I really like to try out this rom on an amoled display. Any specific methods I should follow? (I used mokee phh treble vendor as that was recommended in most forums, am also decrypted..maybe i have to try by flashing noverity too) all gsi tutorials and pages for oneplus 5t are about a year old so i'm not sure I can follow that and succeed. Any help would be appreciated. Thanks.
I cant install in redmi 6a
Galaxy A3 2017? (a3y17lte)
I have discovered a thread of the project treble port, how to fix stuck on boot screen?
I installed the pixel experience rom a while back but never flashed vendor and firmware or whatever it is called. Now i wanna switch to Lineage because this non OTA is annoying. Do i have to flash vendor first or can i just install Lineage? I've read a couple of times that it is bad to make a new install without vendor but never an explanation why. I've also read that i shouldn't install the wrong version of vendor but i couldn't find which one is the one i need, so i just didn't update for a while and left everything like it is.
Thanks for help
PE filesize is 1.3gb, most probably it seems like PE has vendor image embeded! and LOS also comes with vendor image!
if pe was working fine with you! you can clean flash LOS without flashing vendor image!
however always take backup!
vendor image can be found at https://mirror.akhilnarang.me/MIUI/beryllium/ 9.6.27-9 is recomended!
If you want to go the LineageOS route, go to the LineageOS thread and read through it for the minimum version of the firmware file you'll need. Vendor is now embedded in the ROM so no need to install. However, you can still install the vendor/firmware file before flashing LineageOS as the vendor part will be overwritten. Don't forget to do a full backup before you start, better safe than sorry.
YasuHamed said:
PE filesize is 1.3gb, most probably it seems like PE has vendor image embeded! and LOS also comes with vendor image!
if pe was working fine with you! you can clean flash LOS without flashing vendor image!
however always take backup!
vendor image can be found at https://mirror.akhilnarang.me/MIUI/beryllium/ 9.6.27-9 is recomended!
Click to expand...
Click to collapse
thanks, only one thing, i have an old installation of PE without vendor embedded, is that still no risk?
guhvanoh said:
If you want to go the LineageOS route, go to the LineageOS thread and read through it for the minimum version of the firmware file you'll need. Vendor is now embedded in the ROM so no need to install. However, you can still install the vendor/firmware file before flashing LineageOS as the vendor part will be overwritten. Don't forget to do a full backup before you start, better safe than sorry.
Click to expand...
Click to collapse
Ok, i'll probably flash vendor before then. Thanks for the info!
please give me vindor image for Realme 5 Pro i have lost my vendor image...
Hello,
I've uploaded some image files for Nokia 3.2 and want to share them.
I've packed some images for Nokia 3.2 00WW variant (e.g. Magisk, fastboot ROM) and will upload user images for the 00EEA variant, too.
It just needs some more time to upload completely.
EDIT: I transfered all the files to Mega.nz
https://mega.nz/folder/hVMTiCbT#OhmmxhtKabnNn2hWfiIgHQ
P.S. if someone has the european Variant and wants to provide matching Magisk Patched boot images just send me a link to those and i will add them to my Mega.nz folder
Hello,
i just uploaded the patched boot image december 2019 for the europe 00EEA version in other thread under https://forum.xda-developers.com/attachment.php?attachmentid=4929795&d=1579367908.
Perhaps you can add it to your google drive.
Greetings
Hi, sorry i didnt see it. Could you created a Copy of it with dm-verity disabled? You can do it with superr's kitchen. So that we have a magisk Image for GSIs.
Thanks
P.S. i will Upload the magisk patched image tomorrow.
EDIT: I can Just remove dm verity on my own. :silly:
I've created a Telegram Channel for Nokia 3.2
Updates regarding Source Code, the Google Drive mirror (magisk stuff,Firmwares etc.) And any helpful information will be posted by me on the Channel.
Note information inside ReadMe file on the Google Drive link
TA-1156 Qcn
Hello, can you upload Nokia 3.2 TA-1156 models qcn file?
accidentally delete all partitions and now i want to restore imei numbers and serial number to get the mobile network
chinovaso said:
Hello, can you upload Nokia 3.2 TA-1156 models qcn file?
accidentally delete all partitions and now i want to restore imei numbers and serial number to get the mobile network
Click to expand...
Click to collapse
Hi I don't have any qcn file. My Nokia 3.2 is currently being repaired. But I've found a tool what could help you.
https://www.getdroidtips.com/download-imei-qcn-tool/
Just test it and look if it works
chinovaso said:
Hello, can you upload Nokia 3.2 TA-1156 models qcn file?
accidentally delete all partitions and now i want to restore imei numbers and serial number to get the mobile network
Click to expand...
Click to collapse
Thank you s3tupw1zard, but I try this tool already, it works , *06# when it checks it shows the imei numbers but there still no a gsm signal.
Also the serial number is shown as 012345678E0000 and in *#*#4636#*#* servise menu when i chek says Mobile radio is oFF
How to flash using fastboot
Hey mate
Can u guide me through flashing magisk boot img
Im kinda of confused becoz of A B partitions
Any detailed guide would be appreciated
Im on latest January update 2020
Nokia 3.2 (deadpool)
chinovaso said:
Thank you s3tupw1zard, but I try this tool already, it works , *06# when it checks it shows the imei numbers but there still no a gsm signal.
Also the serial number is shown as 012345678E0000 and in *#*#4636#*#* servise menu when i chek says Mobile radio is oFF
Click to expand...
Click to collapse
Hi,
I can't help you in this case. Best would be if you send it in.
You can get your imei with 'fastboot getvar all' (without quotes) to send it in.
You need the imei for sending it in. Dont worry about warranty the ar not allowed anymore to denying warranty due to new google terms.
Just go to nokia website and order a repair.
No0bGuy said:
Hey mate
Can u guide me through flashing magisk boot img
Im kinda of confused becoz of A B partitions
Any detailed guide would be appreciated
Im on latest January update 2020
Nokia 3.2 (deadpool)
Click to expand...
Click to collapse
I write a short guide into a new thread. I pack some files for gsi flashing together.
You will find this guide in about 30 Minutes on the Nokia 3.2 Guides section
Hello,
i uploaded the january 2020 patched boot.img for the European 00EA with dm-verify=off.
Please include on your googledrive!
https://forum.xda-developers.com/attachment.php?attachmentid=4956671&d=1582404743
Greetings
Using these images
Hi All
i've bought a Nokia 3.2 for installing lineageOS ! So i could unlock it and installed this ASOP-Image (probably the 00WW-Version) thru ADB and fastboot with the result to get a crappy OS without WiFI.
At the end i needed about 10 days to get a connection (probably thru qualcomm-drivers) to the pc again, where i can use your (hopefully working) images.
In order to avoid a malfunctioning NOKIA, i am asking about the right way to install the 00EA-Version:
Again i can use adb and fastboot, so first step is to use flash-user-bin.bat for flashing boot.bin, dtbo.bin, system.bin, vendor.bin and vbmeta.bin !
Now there should be a working OS with WiFI, second step would be patching boot_jan2020_dmOFF_00EA.img and third step patching twrp-3.2-dpl-00eea.img.
At last it should be possible to install LineAgeOS thru Magisk Manager (or CWM) ?
Thanks for your advices
Your device needs the images with the same version. So boot.img from January combined with firmware from December lead into bugs like WiFi not working. Reboot to bootloader, there is a info where either 00WW (international Variant) or 00EEA (European Variant) is written. I've uploaded a GSI base for both variants on the Google drive Link at the beginning of this thread. You can find both base 7z Files Inside GSI folder. But be sure which Variant you have. After executing flash-all.bat execute the other bat file (it will flash magisk patched img with dm-verity removed) and after that finishes you can flash any GSI to system.
And you can't install ROMs through Magisk. It is Superuser. You need to be in Bootloader mode.
And USB debugging needs to be on and your PC needs to be authorized by your device. Just activate USB debugging in developer options and type adb devices. There should appear a prompt.
thx
for fast reply. It should be 00EEA, because i've bought it in Austria. I think, i have seen it in the settings/my phone too.
So i will use the GSI-Version tomorrow. With Magisk-Manager i should could load this TWRP-Image (on a SD-Card) too ?
Stupid Question: what is the meaning of the shortciut GSI ?
Regards
other bat-file
s3tupw1zard said:
Your device needs the images with the same version. So boot.img from January combined with firmware from December lead into bugs like WiFi not working. Reboot to bootloader, there is a info where either 00WW (international Variant) or 00EEA (European Variant) is written. I've uploaded a GSI base for both variants on the Google drive Link at the beginning of this thread. You can find both base 7z Files Inside GSI folder. But be sure which Variant you have. After executing flash-all.bat execute the other bat file (it will flash magisk patched img with dm-verity removed) and after that finishes you can flash any GSI to system.
Click to expand...
Click to collapse
Hi s3tupw1zard !
where is this other bat-File ? This GSI (generic system image)-Folder of 00EEA is empty, but i've used user_images_00EEA.7z and this is working perfectly.
In spite of it i would like to change booting (with magisk-patched.img). but this is existing for 00WW only. I've tried to flash twrp-Image too, but there i've got errors, so i've flashed user_images_00EEA completely again.
Thanks for your work
At last
i could create something, but still there is something missing !
I've downloaded boot_nodm_magisk_patched.img from shared googleDrive and patched it with MagiskManager.
Unfortunelately i tried to flash this file without renaming - so i had to reset to factory settings, because booting was not working.
After that, i was remembering to rename this boot-file to boot.img, flashed to factory new system - following flashing the system with LineAgeOS from Andy - https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/ (renamed it to system.img)
The result: booting procedure for working LineAgeOS needs about 5 minutes and wifi is missing !
Does anyone have a clue ?
Do i need to setup system with user-Image (December 2019) from Manuels Google Drive before ?
ThankYou for advices
Gerhard
Then you flashed the wrong boot.img.
You must look for your Version - 00WW or 00EEA - and you must have the corresponding security level to your firmware, means January or December ........
00ww - 00eea
page1875 said:
Then you flashed the wrong boot.img.
You must look for your Version - 00WW or 00EEA - and you must have the corresponding security level to your firmware, means January or December ........
Click to expand...
Click to collapse
thanks for reply.
If i am lucky, i will use boot_jan2020_dmOFF_00EA.img next time - but for now i have (possibly) corrupted partition table file and so device is ended in a fastboot-mode loop - Android ONE Logo flashes up less than 1 second
So hopefully with fastboot flash partition Firmware\gpt_both0.bin (gpt_both0.bin from Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL) i can restore partition table file in spite of this 00WW-Version.
Does anyone have seen firmware for 00EEA-Version ?
cheers
Idiots Guide
The reason for infinite bootloop and ADB-Flash error messeage 'FAILED (remote: partition table doesn't exist)' may be (as i remember) is to rename boot.bin from user_images_00EEA of our wizard to boot.img.
Resetting to factory defaults is not possible anymore - so beware of it !
I have been trying to build a custom aosp based ROM for pixel 4a, I have made changes to few xml files that goes into vendor/etc/ folder. I built a script to extract vendor blobs from the official vendor image provided by google and also generated build instructions for corresponding files.
I'm able to build the vendor image successfully. All the vendor files are present in the custom built vendor img, when I checked.
After flashing the images, the phone gets stuck in google logo.
I have made sure that bootloader is unlocked., osp version and vendor build version match.
1. Is there a way to build vendor image? Is my approach correct?
2. How can boot loop be debugged? -- ADB is not available at this point of time in boot process.. I'm also not able to boot into recovery, I keep getting bootloader screen.
Any help, links, refs, guides would be helpful
If you are rooting after or during the build process both boot.img and vendor_boot.img files need to be patched. If you are at bootloader(fastboot) you can fastboot flash vendor.img etc
toolhas4degrees said:
If you are rooting after or during the build process both boot.img and vendor_boot.img files need to be patched. If you are at bootloader(fastboot) you can fastboot flash vendor.img etc
Click to expand...
Click to collapse
I'm able to flash the vendor image. I don't want to root the phone. When I use the official vendor image, the phone boots but not when I use vendor image that I built. Is there a way to build vendor image? or How can I debug boot loop?
toolhas4degrees said:
If you are rooting after or during the build process both boot.img and vendor_boot.img files need to be patched. If you are at bootloader(fastboot) you can fastboot flash vendor.img etc
Click to expand...
Click to collapse
Yes, he can use magisk manager to patch the image then flash them in fastboot mode using adb like you said
poppopret_ said:
I have been trying to build a custom aosp based ROM for pixel 4a, I have made changes to few xml files that goes into vendor/etc/ folder. I built a script to extract vendor blobs from the official vendor image provided by google and also generated build instructions for corresponding files.
I'm able to build the vendor image successfully. All the vendor files are present in the custom built vendor img, when I checked.
After flashing the images, the phone gets stuck in google logo.
I have made sure that bootloader is unlocked., osp version and vendor build version match.
1. Is there a way to build vendor image? Is my approach correct?
2. How can boot loop be debugged? -- ADB is not available at this point of time in boot process.. I'm also not able to boot into recovery, I keep getting bootloader screen.
Any help, links, refs, guides would be helpful
Click to expand...
Click to collapse
Did you already check the tutorials or how-to's available on XDA e.g. the tutorials of @AlaskaLinuxUser like
[Guide][Video Tutorial] How to build Custom ROMs and Kernels![10,P,O,N,M,L]
Hey everyone! There is also a telegram channel where you can drop in for some help: https://t.me/joinchat/HR_8JgyDBdw_DvmndPl0kg I really hope that you have enjoyed the series, and that it was helpful to you in your Android career! Praise...
forum.xda-developers.com
or
[Guide][Video Tutorial] Intermediate to Advanced Custom Rom and Kernel Building
Hey everyone! There is also a telegram channel where you can drop in for some help: https://t.me/joinchat/HR_8JgyDBdw_DvmndPl0kg I really hope that you have enjoyed the series, and that it is helpful to you in your Android career! Praise God...
forum.xda-developers.com
The XDA University might also be of good help:
XDA-University
Tutorials, How-To Guides and More. Learn about mobile phone development, hacking, flashing, rooting and many other topics!
forum.xda-developers.com
Just search a bit and you'll find much more.