[13.01.207]I created device/kernel/vendor trees for Lenovo P2 (P2a42[kuntao_row] only).
Update[20.02.2017]:Work In Progress, just wait until it becomes bugless
How to install:
- Always make a nandroid backup before trying it.
- After making it make your wipes and install this zip.
Device Tree: https://github.com/Wzedlare/android_device_lenovo_p2a42
Kernel Source: https://github.com/Wzedlare/android_kernel_lenovo_msm8953
Vendor Blobs: https://github.com/Wzedlare/android_vendor_lenovo_p2a42
Credits and thanks goes to: @wzedlare @kaankulahli @celoxocis @DeftonesOT
Rezerved.
You can pull the missing blobs/files from the stock ROM. Just use Superr's Kitchen to extract them. I contacted him and he has already added support for the chunk file extract for Lenovo.
Look at my github repo for the partition sizes or lookup the "Lenovo P2 is coming soon" thread for all partition information.
You actually don't need root to figure out the partition size.
celoxocis said:
You can pull the missing blobs/files from the stock ROM. Just use Superr's Kitchen to extract them. I contacted him and he has already added support for the chunk file extract for Lenovo.
Look at my github repo for the partition sizes or lookup the "Lenovo P2 is coming soon" thread for all partition information.
You actually don't need root to figure out the partition size.
Click to expand...
Click to collapse
I will fix the partition sizes but I'm not sure about blobs because they seem to be symlinked to firmware and persist partitions
If you want a mirror for the files, let me know.
ilmervanhattem said:
If you want a mirror for the files, let me know.
Click to expand...
Click to collapse
Thanks, I think mega is good enough for now.
wzedlare said:
I will fix the partition sizes but I'm not sure about blobs because they seem to be symlinked to firmware and persist partitions
Click to expand...
Click to collapse
by Stock Rom i meant the "russian leak". Which i linked in post #3 in the TWRP thread.
celoxocis said:
by Stock Rom i meant the "russian leak". Which i linked in post #3 in the TWRP thread.
Click to expand...
Click to collapse
As I said before, there are some files symlinked to other parts like firmware and persist.I can't pull them because I am not root.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm trying to install the zip but it gave a an error 7. Can I edit the updater-script and remove the first 2 rows or this can be a problem? I can also upload the files you are missing just tell me where can i find the msadp cause I can't find it..
I (also) need to wait for 10 days to get the OEM bootloader unlocked, after that i am glad to volunteer.
The rom doesn't boot. After the reboot from the recovery it goes into bootloader and if I force it to start after the lenovo logo the screen became black with a blue led and the phone vibrates for 3 sec.
maxysoft said:
I'm trying to install the zip but it gave a an error 7. Can I edit the updater-script and remove the first 2 rows or this can be a problem? I can also upload the files you are missing just tell me where can i find the msadp cause I can't find it..
Click to expand...
Click to collapse
That''s because the TWRP i build was made specifically for zip files containing the proper "ro.build.product=" like stock zip files and stock OTA files do. Allowing TWRP to be compatible with those files and prefenting "not so advanced" users from installing the wrong ROM.
https://github.com/Celoxocis/android_device_lenovo_P2a42/blob/cm-13.0/system.prop#L4
You need to open up the zip file and change that information accordingly.
---------- Post added at 16:56 ---------- Previous post was at 16:54 ----------
maxysoft said:
The rom doesn't boot. After the reboot from the recovery it goes into bootloader and if I force it to start after the lenovo logo the screen became black with a blue led and the phone vibrates for 3 sec.
Click to expand...
Click to collapse
Meaning stock graphic blobs are not working with AOSP base.
celoxocis said:
That''s because the TWRP i build was made specifically for zip files containing the proper "ro.build.product=" like stock zip files and stock OTA files do. Allowing TWRP to be compatible with those files and prefenting "not so advanced" users from installing the wrong ROM.
https://github.com/Celoxocis/android_device_lenovo_P2a42/blob/cm-13.0/system.prop#L4
You need to open up the zip file and change that information accordingly.
---------- Post added at 16:56 ---------- Previous post was at 16:54 ----------
Meaning stock graphic blobs are not working with AOSP base.
Click to expand...
Click to collapse
Do you know how to fix that? I have everything of my computer and if you can tell me what files need to be changed I can try to fix it. Thanks
wzedlare said:
As I said before, there are some files symlinked to other parts like firmware and persist.I can't pull them because I am not root.
Click to expand...
Click to collapse
No! Everything that is in persist is actually just calibration data. Its called persist to "persist" between reboots.
Everything placed there comes from system.
For those files look in:
/system/etc/wifi/WCNSS_qcom_cfg.ini
/system/etc/firmware/wlan/prima/WCNSS_qcom_wlan_nv_lenovo.bin
./system/etc/firmware/wlan/prima/WCNSS_wlan_dictionary_lenovo.dat
just rename them properly for a bring-up.
Then I should change device name to p2a42 what about using msm8916 graphics blobs?
wzedlare said:
Then I should change device name to p2a42 what about using msm8916 graphics blobs?
Click to expand...
Click to collapse
Just change/add the assert information properly. Like this:
https://github.com/Alberto97/android_device_motorola_addison/blob/cm-14.1/BoardConfig.mk#L40
if you like to add more simply seperate them by a ","
msm8916 works for up to the same generation like (msm8939)
but i don't know about generation change like msm8953 is.
celoxocis said:
Just change/add the assert information properly. Like this:
https://github.com/Alberto97/android_device_motorola_addison/blob/cm-14.1/BoardConfig.mk#L40
if you like to add more simply seperate them by a ","
msm8916 works for up to the same generation like (msm8939)
but i don't know about generation change like msm8953 is.
Click to expand...
Click to collapse
Trying wont hurt, I will prepare a flashable fix for tester to try it.
wzedlare said:
Trying wont hurt, I will prepare a flashable fix for tester to try it.
Click to expand...
Click to collapse
I'll wait for it :good:
maxysoft said:
I'm trying to install the zip but it gave a an error 7. Can I edit the updater-script and remove the first 2 rows or this can be a problem? I can also upload the files you are missing just tell me where can i find the msadp cause I can't find it..
Click to expand...
Click to collapse
please try again graphics_fix.zip. Flash this over on installed the Rom.
Link=====> https://mega.nz/#!f5VywSRb!p-N_vYRiI3Z9nUX81iaKmp_DPS0z9B0TiVICJqR5HGc
kaankulahli said:
please try again graphics_fix.zip. Flash this over on installed the Rom.
Link=====> https://mega.nz/#!f5VywSRb!p-N_vYRiI3Z9nUX81iaKmp_DPS0z9B0TiVICJqR5HGc
Click to expand...
Click to collapse
Isn't working. Same as before
Related
INTRODUCTION
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*/WARNING
This tool is in [B]BETA[/B] phase and is not for noobs. If you use this, you are choosing to play with your device on your own.
I will not be responsible for any damage to your device or your belongings in your home.
If you blame me for anything that goes wrong I'll die laughing at you/*
Hello all!
Today I present you F2I converter. This tool can convert system folder back to ext4 image format suitable for flashtools without cygwin.
Basically, this tool was made in keeping mind the format used by lollipop structure where dat files were converted to ext4 format and then unpacked, repacking them was kind of hard (or lazy to do so in my case) as it required linux or Cygwin [Based on Xpirt's Guide. Now I've always preferred a way to avoid linux and cygwin
I managed to put together a set of tools that can easily convert the extracted system folder back to img for flashing and in lollipop can be converted back to dat format on windows.
So this is what this tool is capable of! If you on lollipop and want @xpirt guide to do so then here it is - [HOW TO] Lollipop DAT files | Compression and Decompression
FEATURES
• Supports all Android Versions
• Works without Linux or cygwin
• Generates Log that help to troubleshoot the issues
• No extra software required (Except Git for Windows)
• Supports both way conversion
• Suggest more features
• Much more to come!
HOW TO USE
You need GIT for windows to run this tool. Kindly download and install GIT from HERE
Now install GIT and when you're done download F2I converter and extract it in core C: directory. There will be a folder names as "IMG_WIN" kindly make sure it is extracted in C:
Recommended GIT is v 1.9.4 or newer.
Mostly everything is self-explanatory in the tool but when you will convert "SYSTEM" folder back to "EXT4 img" format you will be asked to enter size in bytes.
Here is what you are asked to do..
1) Open the system.img inside the respective folder you're working on and then right click on it and click Properties
2) In General tab you'll see something like this
Now copy the highlighted part and paste in the box shown below in image
Now you can continue. Ahead
DOWNLOADS
MAJOR LINK
MIRROR
BUGS
This tool is in BETA phase so you are likely to face some bugs. Though I have paid a lot of attention while creating this tool but you may encounter some small code errors (like path not found etc) I request you to kindly see for yourself and correct it.
You are likely to face this error mostly though
Code:
error in bla bla bla ..... failed to allocate block [NUMBERS] out of space?
If you encounter something like this then it will not work with your files. This will occur mostly in Android 2.3.x-4.4.x and in some cases with 5.0 and 5.1
I am trying to fix this issue. Please co-operate
Rest no major bug.
CREDITS
@xpirt for his awesome guide on lollipop compression and decompression of dat files
Google for being so hepful :angel:
XDA for it's awesomeness
XDA:DevDB Information
[F2I Converter] Convert System folder into EXT4 Image without cygwin on Windows!, Tool/Utility for all devices (see above for details)
Contributors
Tech N You
Version Information
Status: Beta
Current Beta Version: v1.0
Beta Release Date: 2015-05-03
Created 2015-05-03
Last Updated 2015-05-03
Reserved.
Reserved Again.
Nice Dude ! extracted xolo one files using this ... hoping to port it for q700s
Great tool mate!
Enviado desde mi OnePlus One
Tech N You said:
.....This tool is in BETA phase so you are likely to face some bugs.....I request you to kindly see for yourself and correct it......
Click to expand...
Click to collapse
i've tried this. see the screenshot. i find only 2 files to copy back to my rom zip.
what about "file_contexts"? can/should the original be retained?
large size difference between original "system.transfer.list" and modified one ok?
Doesn't work for me. I'm unable to find system.img. So I downloaded "sda2img.exe" and I made system.img with it. Then, when I try to recompress system folder in DAT format, there is this problem ( see the screenshot ).
Then I noted that after using it, in "Working_Do_Not_Touch", system.transfer.list and system.new.dat get losts.
m0han said:
i've tried this. see the screenshot. i find only 2 files to copy back to my rom zip.
what about "file_contexts"? can/should the original be retained?
large size difference between original "system.transfer.list" and modified one ok?
Click to expand...
Click to collapse
AlessandroXCV said:
Doesn't work for me. I'm unable to find system.img. So I downloaded "sda2img.exe" and I made system.img with it. Then, when I try to recompress system folder in DAT format, there is this problem ( see the screenshot ).
Then I noted that after using it, in "Working_Do_Not_Touch", system.transfer.list and system.new.dat get losts.
Click to expand...
Click to collapse
Thanks for trying out the tool. You must use same file_contexts
As per your issue sir thing is the output is cleaned up and no file is left back. I request you to try the size from xpirts post on this. Kindly check that and reply back.
[system_new.img?]
Any ideas on how to fix this:
When I try repacking [system folder] back to [system.new.dat] the program throws an error : File not found -- system_new.img
MeTaL-01 said:
Any ideas on how to fix this:
When I try repacking [system folder] back to [system.new.dat] the program throws an error : File not found -- system_new.img
Click to expand...
Click to collapse
Option 4 is the correct one for Lollipop i see u chose option 3
Tech N You said:
....You must use same file_contexts.....
Click to expand...
Click to collapse
did so. upon trying to flash rom zip file, "error executing binary in zip....."
Tech N You said:
Option 4 is the correct one for Lollipop i see u chose option 3
Click to expand...
Click to collapse
I've tried both, none work
MeTaL-01 said:
I've tried both, none work
Click to expand...
Click to collapse
Okay then let me recheck whole thing and I'll revert back to you
ahh boy, you never cease to amaze me. Thanks for this
kirito9 said:
ahh boy, you never cease to amaze me. Thanks for this
Click to expand...
Click to collapse
Glad to know you liked this tool :good:
I keep getting a Permission denied error when using option 4. Any ideas why??
LupusGrande said:
I keep getting a Permission denied error when using option 4. Any ideas why??
Click to expand...
Click to collapse
Tool is not getting administrative privilege.
Kindly make your Windows user prompt to lowest
Tech N You said:
Tool is not getting administrative privilege.
Kindly make your Windows user prompt to lowest
Click to expand...
Click to collapse
after conversion there is nothing in system folder
well done bro ......................though small glitches bt overall grt tool (Y)
I can't convert the system folder back to dat files.
I use option 4 but nothing works.
Where I have to put the system.transfer.list and the system.new.dat?
What I have to do?
So when it comes to the newly released EMUI8 for Honor 9 things get a little bit tricky, as we don't have any official update for our region yet (only for C900 and AL variants - chinese).
Every file i provided have been built during the way finding how stuff works on oreo - and alot of stuff changed EDIT: Official update is out for C432 - i recommend to not use the provided TWRP for daily, reliable usage.
PART 1
0. download the B360a zip from my mega folder
1. read README.txt from fw zip and follow the steps carefully (easy install)
2. have fun with official oreo
Rollback instructions
1. copy the rollback zip and nocheck recovery (!!oreo version!!) to the root of your MicroSD card
2. enable usb debugging in developer options
3. connect your phone to your computer, start an adb shell and issue the following commands:
Code:
dd if=/storage/sdcard1/STF_RECOVERY_OREO_NoCheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
dd if=/storage/sdcard1/STF_RECOVERY_OREO_NoCheck.img of=/dev/block/bootdevice/by-name/erecovery_ramdisk
echo --update_package=/sdcard/update_rollback_al10c00b190.zip > /cache/recovery/command
4. last but not least reboot recovery, again in adb shell:
Code:
reboot recovery
5. your device should start to flash a chinese version of nougat (EMUI 5.1)
hint: if you get an error during the installation, just press the reboot button, it still boots.
device crashes during boot? do a low-level data partition format, boot into erecovery when you get asked to.
6. prepare the MicroSD (8gb atleast, exFAT formatted)
download the C432 firmware and extract it
copy the dload folder you extracted to the root of your MicroSD
7. if required unlock your bootloader
8. flash the nocheck recovery (nougat version) to recovery and recovery2 partition using fastboot
Code:
fastboot flash recovery STF_RECOVERY_NoCheck.img
fastboot flash recovery2 STF_RECOVERY_NoCheck.img
9. boot your device into force dload mode (keep vol+, vol- and power pressed until the installation starts)
10. you should boot into a fresh L09C432B100 installation
I've uploaded every file you need for the process to mega.nz - please do not mirror any of the stuff provided!
[url]https://mega.nz/#F!W1QUAIbZ!7Gbf79dC6NwD1e_zdY_O3Q[/URL]
Huge thanks to @LastStandingDroid for providing the modified SuperSU installation package.
Best Regards,
OldDroid
To fix the file manager, open your root file explorer and follow the steps carefully:
1. create a folder called "normal" in /cust/hw
2. create a second folder in the previously created one, name it "app"
3. now move HwCloudDrive_Local folder from /cust/hw/eu/app to /cust/hw/normal/app
4. reboot
Thank you!
I'll try it!
Does bootloader uncloked ?
After I done the factory reset my themes lost again, and the boot animation too...and the apps....
I mean, I done everithing what you said and the themes come back...but after i relocked the bootloader its gone....like if i didn't do anithing :S (sorry for my bad English)
Should i try again?
BobekMark said:
After I done the factory reset my themes lost again, and the boot animation too...and the apps....
I mean, I done everithing what you said and the themes come back...but after i relocked the bootloader its gone....like if i didn't do anithing :S (sorry for my bad English)
Should i try again?
Click to expand...
Click to collapse
don't relock the bootloader after the whole process
OldDroid said:
don't relock the bootloader after the whole process
Click to expand...
Click to collapse
Ohh.... i see...ty
i will try it again
---------- Post added at 06:14 PM ---------- Previous post was at 05:19 PM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is my result. :\
It's okay, or there should be some other apps? Or should it be C432 instead of C900 ? :S
(There is no Huawei Account option :S )
BobekMark said:
Ohh.... i see...ty
i will try it again
---------- Post added at 06:14 PM ---------- Previous post was at 05:19 PM ----------
This is my result. :\
It's okay, or there should be some other apps?
(There is no Huawei Account option :S )
Click to expand...
Click to collapse
which h9 version do you have, C432?
OldDroid said:
which h9 version do you have, C432?
Click to expand...
Click to collapse
Yes (I updated the pictures)
BobekMark said:
Yes (I updated the pictures)
Click to expand...
Click to collapse
thats normal, your phone is still running c432, this is just a ui thing, if it disturbs you i can post the path where the version is beeing set
OldDroid said:
thats normal, your phone is still running c432, this is just a ui thing, if it disturbs you i can post the path where the version is beeing set
Click to expand...
Click to collapse
And the apps are ok?
When i was in the root explorer i still see applications like File Manager and Huawei apps :S
BobekMark said:
And the apps are ok?
When i was in the root explorer i still see applications like File Manager and Huawei apps :S
Click to expand...
Click to collapse
where did you find them?
I have problem with installation.
I have NTFS system files on my SD card and i can't mount this card in TWRP.
What i have to do?
Format to FAT32 or what?
So awesome, thank you for that.
Is there a version of this that will work the same or similar on the P10 (standard P10). Thanks
OldDroid said:
where did you find them?
Click to expand...
Click to collapse
There
BobekMark said:
There
Click to expand...
Click to collapse
Install em as normal apk it'll be visible.
I don't like your settings it looks so color less
[emoji6]
Sent from my DUK-L09 using Tapatalk
LastStandingDroid said:
Install em as normal apk it'll be visible.
I don't like your settings it looks so color less
[emoji6]View attachment 4337715View attachment 4337718View attachment 4337719
Sent from my DUK-L09 using Tapatalk
Click to expand...
Click to collapse
Ok...but i don't have Huawei "Support" or account or idk what.....but for example...the themes app is different, because i can't log in any Huawei Account ...it's not an option to log in :\
Hi! And first of all, thanks a lot for this guide as you just gave hopeless H9 owners a bit of light...
Now I haven't gone through the process yet but I got a bit confused as of part.3 (that is recommended but not needed), should we unroot BEFORE flashing Ramdisk and Recovery Ramdisk? I then have an old UnSu script by Osmosis, would it work or the "Full Unroot" option from the SuperSu app is okay?
Thanks in advance for your reply and Thanks again for this guide!! Cheers
BobekMark said:
Ok...but i don't have Huawei "Support" or account or idk what.....but for example...the themes app is different, because i can't log in any Huawei Account ...it's not an option to log in :\
Click to expand...
Click to collapse
Install huawei services from play store but it won't help ;P
Because online themes is disabled by default
Sent from my DUK-L09 using Tapatalk
Hi Everyone
We all know that Xiaomi added Anti roll-back to latest Stable/Beta ROMs and many users bricked their phones because of it, check my thread about ARB Here, then check out this one
Here ill provide a Guide to Mod Miui ROMs to flash it without "firmware-update", to prevent any potential bricking while switching between Miui Based ROMs
Download Xiaomi Flashable Firmware Creator and follow those steps:
1- Download .exe for windows, or the one without extension for linux, and download Miui Based ROM you want to edit
2- Put them in the same folder tool & .zip file
3- Open CMD/Terminal in that folder and type the command you want with file name, it has three options
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
-F FIRMWARE, Create normal Firmware zip
-N NONARB, Create non-ARB Firmware zip
-L FIRMWARELESS, Create Firmware-less zip
Commands will be like this.
Code:
create_flashable_firmware.exe -F miui_HMNote5HMNote5ProGlobal_8.11.23_12bcf570ce_8.1.zip
create_flashable_firmware.exe -N miui_HMNote5HMNote5ProGlobal_8.11.23_12bcf570ce_8.1.zip
create_flashable_firmware.exe -L miui_HMNote5HMNote5ProGlobal_8.11.23_12bcf570ce_8.1.zip
Run the command you want and result file will be in the same folder
Final Zips after running all the commands
Manual Method
ill post two way of doing it, on PC & Mobile, ill start off with PC method:
Open ROM ZIP and remove firmware-update & META-INF folders
[*]Copy over my modified META-INF folder
[*]and Done, copy over the modded ZIP to your phone and flash
Check attachments or Drive folder for already modified scripts to use
2nd Post will have Mobile method
NOTE: never contact me on PM's or on Telegram, because ill simply ignore your msgs, ask in here or in whyred chats
Mobile Method
with this mehtod, ill be using FX File Explorer, you could use MiXplorer also, just make sure to follow the same steps
Extract ROM
[*]Remove firmware-update & META-INF folders
[*]Copy over my modified META-INF folder
[*]Re-Zip/Compress ROM files
[*]Make sure to use those settings or TWRP wont flash it
[*]and Done, Flash from TWRP
Check attachments or Drive folder for already modified scripts to use
NOTE: never contact me on PM's or on Telegram, because i'll simply ignore your msgs, ask in here or in whyred chats
Editing Fastboot ROMs
Fastboot ROMs are easy to edit, just follow these simple steps
Excract ROM
Copy over included flash scripts to ROM folder
Then Run the script you want to use, like flash_all.bat to flash everything and wipe data, or use MiTool to flash it
Scripts are included in OP
Thanks...great work buddy
Super Helpful Guide @AL_IRAQI
Cheers
Thank you very much. Greatfull for this information
---------- Post added at 03:00 PM ---------- Previous post was at 02:40 PM ----------
Is that possible with bootloader locked?. Is possible to flash oficial modded rom with stock recovery?
Thanks for the guide!
Can something similar be done with Fastboot roms?
You reported the Xiaomi have blocked using old roms with Mi Flash.
So if something happens to our devices, we can use Mi Flash with modded rom, so not to trigger ARP. Or do you need permission(from them) to even flash roms with that now?
Also does NON_HLOS.bin contain bootloader files?
Thank you very much.
Can i do it with OTA rom which is smaller download size?
Very Nice..
whats the diferences between META-INF-EU-Miui and META-INF-Stock-Miui ?
thanks
Can I go back to 9.5.17.0 from 9.5.19.0 by modding with this method?
ahadrox said:
Can I go back to 9.5.17.0 from 9.5.19.0 by modding with this method?
Click to expand...
Click to collapse
im thinking update from 9.5.17 to 9.5.19, what your opinion of 9.5.19
0Jos0 said:
Thank you very much. Greatfull for this information
Is that possible with bootloader locked?. Is possible to flash oficial modded rom with stock recovery?
Click to expand...
Click to collapse
Nope, only for TWRP
corkiejp said:
Thanks for the guide!
Can something similar be done with Fastboot roms?
You reported the Xiaomi have blocked using old roms with Mi Flash.
So if something happens to our devices, we can use Mi Flash with modded rom, so not to trigger ARP. Or do you need permission(from them) to even flash roms with that now?
Also does NON_HLOS.bin contain bootloader files?
Click to expand...
Click to collapse
for fastboot its different, will share in here later, NON_HLOS is the modem mostly
kesley said:
Can i do it with OTA rom which is smaller download size?
Click to expand...
Click to collapse
Yeah, but ota script is different
zoko said:
Very Nice..
whats the diferences between META-INF-EU-Miui and META-INF-Stock-Miui ?
thanks
Click to expand...
Click to collapse
EU is for Xiaomi,eu ROMs, and Stock is for miui.com ROMs
ahadrox said:
Can I go back to 9.5.17.0 from 9.5.19.0 by modding with this method?
Click to expand...
Click to collapse
Yeah
zoko said:
im thinking update from 9.5.17 to 9.5.19, what your opinion of 9.5.19
Click to expand...
Click to collapse
You can do it
So with this method we can downgrade.. Like am on MIUI 8.7.12 and want to go back to 9.5.13.0
This method work for all versions miui?
Will this work with incremental packages?
for fastboot its different, will share in here later, NON_HLOS is the modem mostly
please do so. for fastboot roms/ thanks
can we flash the modified recovery ROMs through updater in miui? or it can only be flashed through custom recovery?
Sent from my Xiaomi Redmi Note 5 using XDA Labs
Have you tried downgrading to 9.5.17 using the modded way?
Please add masik 2.0
Edit : masik 2 Rom already have anti roll back thing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I would like to share my personal derpfest 11 builds for sunfish:
Derpfest 11:
File folder on MEGA
mega.nz
boot.img for flashing first time:
File on MEGA
mega.nz
### Install instructions for custom roms ###
### (Lineage, DerpFest, Superior, Dirty Unicorns, etc) ###
- Flash stock 11 or upgrade to 11 if you are still on 10.
- Download the separate boot.img for use in next step (see notes)
- Flash the downloaded boot.img to both slots: fastboot flash --slot all boot boot.img
- Boot to recovery using the volume buttons on phone itself.
- Perform a factory reset (first install only) in the recovery menu
- Apply update from adb (Apply update >> Apply from ADB)
- Run command on PC: adb sideload zipname.zip and press enter
- Reboot
====
Device tree:
https://github.com/koen01/android_device_google_sunfish/tree/derp/
Kernel source:
https://github.com/koen01/Pixel-4/commits/kangtopia-sunfish
====
Many thanks to Dirty Unicorns and Flar2!
Using their works as base.
ny-hardcore said:
I would like to share my personal build for sunfish:
Defest 11:
https://mega.nz/file/FAdzBaLI#ImShMEXI2NSXf8e45myt6dZ06Ze79grj_Cg_dXxgDJU
====
Device tree:
https://github.com/koen01/android_device_google_sunfish/tree/derp/
Kernel source:
https://github.com/koen01/Pixel-4/commits/kangtopia-sunfish
====
Many thanks to Dirty Unicorns and Flar2!
Using their works as base.
Click to expand...
Click to collapse
Any chance you could post the boot image extracted from this so that people that want root can patch it with magisk?
beanaman said:
Any chance you could post the boot image extracted from this so that people that want root can patch it with magisk?
Click to expand...
Click to collapse
You can extract the payload.bin file with payload dumper to get the boot.img file. I can do it when I get a chance if the dev is too busy to do so. I'm kinda busy right now, but can do it later.
---------- Post added at 12:28 AM ---------- Previous post was at 12:00 AM ----------
I uploaded it to my drive after extracting payload.bin file. Here you go!!!!
https://drive.google.com/file/d/1DLsQjc0i0v4GknC4TlBL8mjvcF1wRx07/view?usp=sharing
I currently use DU and would like to try it, can someone write instructions please ?
beanaman said:
Any chance you could post the boot image extracted from this so that people that want root can patch it with magisk?
Click to expand...
Click to collapse
I uploaded it to my drive after extracting payload.bin file. Here you go!!!!
https://drive.google.com/file/d/1DLsQjc0i0v4GknC4TlBL8mjvcF1wRx07/view?usp=sharing
---------- Post added at 12:38 AM ---------- Previous post was at 12:29 AM ----------
switcher said:
I currently use DU and would like to try it, can someone write instructions please ?
Click to expand...
Click to collapse
You need to use the DU custom recovery which I assume you already have if you are using their rom. Boot to recovery and factory reset, then sideload rom.
Then boot your phone. If you want to root your phone, I supplied the boot.img file from the payload.bin file that I extracted for the dev. You can use that to patch file with magisk beta then flash that patched file in fastboot by the following, fastboot flash boot magisk_patched.img
This is awesome thank you to the dev for keeping our device alive!
Archangel said:
This is awesome thank you to the dev for keeping our device alive!
Click to expand...
Click to collapse
.....
Did you really just say that out loud about a device that is like 3 months old?
?
Sent from my Pixel 4a using Tapatalk
rignfool said:
.....
Did you really just say that out loud about a device that is like 3 months old?
?
Click to expand...
Click to collapse
Yup
Archangel said:
Yup
Click to expand...
Click to collapse
Lol
There's very little development for the 4a. This is a fact.
bobbarker2 said:
There's very little development for the 4a. This is a fact.
Click to expand...
Click to collapse
That's because since Android 11, there are many more obstacles in the way in building a rom. There is no working TWRP for our device for Android 11. Building a custom recovery into the rom is more work. These developers do this in their free time, they have full time jobs, and family.
Has anyone been successful at flashing this? When I tried, I got signature errors with install aborted. Even tried downloading the file again just to make sure that it wasn't corrupted.
Yes, and I'm betting that you are using stock recovery which is what would cause this error.
Download this: 20200913-OFFICIAL-boot.img
Download and put inside your adb tools folder. Reboot to bootloader and fastboot flash --slot all boot official-boot.img
Then boot into recovery and factory reset. Then sideload rom by the following, adb sideload rom.zip or whatever the name is called. Then reboot phone and it will work. If you want to root, I've given instructions on that previously.
fossiltkm said:
Has anyone been successful at flashing this? When I tried, I got signature errors with install aborted. Even tried downloading the file again just to make sure that it wasn't corrupted.
Click to expand...
Click to collapse
Yes, and I'm betting that you are using stock recovery which is what would cause this error.
Download this: 20200913-OFFICIAL-boot.img
Download and put inside your adb tools folder. Reboot to bootloader and fastboot flash --slot all boot official-boot.img
Then boot into recovery and factory reset. Then sideload rom by the following, adb sideload rom.zip or whatever the name is called. Then reboot phone and it will work. If you want to root, I've given instructions on that previously.
I just uploaded a new build synced with latest derpfest sources.
Also dit some changes to Devicetree for smoothnes (vulkan backend and triple buffering) and enabled the aosp blur
Check the mega folder linkt in first post for latest release
ny-hardcore said:
I just uploaded a new build synced with latest derpfest sources.
Also dit some changes to Devicetree for smoothnes (vulkan backend and triple buffering) and enabled the aosp blur
Check the mega folder linkt in first post for latest release
Click to expand...
Click to collapse
They can ignore my previous post. I appreciate your time in development here. It's limited with this device and I understand devs have full time jobs, and a family and they do what they can with their time. Much appreciated.
ny-hardcore said:
I just uploaded a new build synced with latest derpfest sources.
Also dit some changes to Devicetree for smoothnes (vulkan backend and triple buffering) and enabled the aosp blur
Check the mega folder linkt in first post for latest release
Click to expand...
Click to collapse
Your latest build is running great for me, and I love the AOSP Blur effect . One question though, are you able to set a lock screen wallpaper different from the home screen? By no means is it a big deal, just wondering if it's been working as it should for you.
I really appreciate you sharing your personal builds with us, your time as well!
fossiltkm said:
Has anyone been successful at flashing this? When I tried, I got signature errors with install aborted. Even tried downloading the file again just to make sure that it wasn't corrupted.
Click to expand...
Click to collapse
fossiltkm said:
Your latest build is running great for me, and I love the AOSP Blur effect . One question though, are you able to set a lock screen wallpaper different from the home screen? By no means is it a big deal, just wondering if it's been working as it should for you.
I really appreciate you sharing your personal builds with us, your time as well!
Click to expand...
Click to collapse
I noticed this on Superior os as well. Also navbar layout options don't work.
Edmontonchef said:
I noticed this on Superior os as well. Also navbar layout options don't work.
Click to expand...
Click to collapse
I only use gestural navigation so I can't comment on this. Will look into it to check if it's broken upstream.
fossiltkm said:
Your latest build is running great for me, and I love the AOSP Blur effect . One question though, are you able to set a lock screen wallpaper different from the home screen? By no means is it a big deal, just wondering if it's been working as it should for you.
I really appreciate you sharing your personal builds with us, your time as well!
Click to expand...
Click to collapse
I'm seeing this too. Will check with official derp.
Is there a list of features for this ROM? I'm particularly interested in navigation button customization, i.e. long-press kill-app, launch activity, toggle screen rotate, etc.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto Z Play
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Moto Z Play.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
addison
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
The EQ Apps for Audio Mods (eg. JBL2 App) won't work, and will crash.
Audio Mods have no alarm or notification audio through them.
Camera Mods don't (and won't ever) work.
Volume may be lowered when locking and unlocking the device
Non-original touchscreens may fail to respond
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Official Lineage OS builds for addison ship with full Project Treble compatibility! Flash GSI's to your heart's content after flashing Lineage. Please don't report GSI bugs here, report them instead to the GSI's maker.
Code:
Technical details on our Treble implementation:
Treble is enabled with VNDK30, and VNDK runtime enforcement. VNDK runtime enforcement means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run GSIs. without need for hacks or additional flashable zips. We relabeled /oem to /vendor (as /oem isn't wasn't used in custom ROMs anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image.
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_msm8953
Hi there, just tried this new ROM and it is pretty nice that most functions are working well, really appreciate your maintainance!
However, this ROM has the same bugs as the previous AICP one does, like touching the fingerprint sensor would lead to immediate lock screens (could be fixed when deleted the fpc1020.kl file in vendor), and failing to read an adaptive Type C headphones bugs, hope they could be fixed later.
Touch2Fin said:
Hi there, just tried this new ROM and it is pretty nice that most functions are working well, really appreciate your maintainance!
However, this ROM has the same bugs as the previous AICP one does, like touching the fingerprint sensor would lead to immediate lock screens (could be fixed when deleted the fpc1020.kl file in vendor), and failing to read an adaptive Type C headphones bugs, hope they could be fixed later.
Click to expand...
Click to collapse
Yes, it does as it's based on the same trees
Also don't report the fact that pressing the fp will lock the screen as a bug, it's an intended feature, what's not intended is the fact that for some reason it can't be disabled right now
- Is there a minimum firmware base requirement?
- Which GSI variant is supported?
VR25 said:
- Is there a minimum firmware base requirement?
- Which GSI variant is supported?
Click to expand...
Click to collapse
- MB; yes there is, it's just the latest Oreo firmware, on retail channel that would be OPNS27.76-12-22-9
- ARM64 A-Only, given that this device has no A/B support
Also aren't you the guy that made acc?
marcost22 said:
- MB; yes there is, it's just the latest Oreo firmware, on retail channel that would be OPNS27.76-12-22-9
- ARM64 A-Only, given that this device has no A/B support
Also aren't you the guy that made acc?
Click to expand...
Click to collapse
As expected, thanks. This treble implementation is such a gem!
Yes, I'm the acc guy.
Which gapp i should download.. there are 6 files.. i have already tried 3 file form given link..but everytimes showing error.. plz mentioned the perticular download link of gapp
@marcost22 million of thanks to you, never thought will see a official lineage os for moto z play. Its based on 64 bit ?
I would like to say "YOU ARE THE BEST" !!
Subu1990 said:
Which gapp i should download.. there are 6 files.. i have already tried 3 file form given link..but everytimes showing error.. plz mentioned the perticular download link of gapp
Click to expand...
Click to collapse
MindTheGapps-11.0.0-arm64-20220217_100228.zip this one will work !!
VR25 said:
As expected, thanks. This treble implementation is such a gem!
Yes, I'm the acc guy.
Click to expand...
Click to collapse
Thanks!
Also funny finding you here
Subu1990 said:
Which gapp i should download.. there are 6 files.. i have already tried 3 file form given link..but everytimes showing error.. plz mentioned the perticular download link of gapp
Click to expand...
Click to collapse
MindTheGapps-11.0.0-arm64-20220217_100228.zip | by Alessandro Astone for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Also you are expected that if you are able to install a rom, you are able to do a little googling and reading
bunt009 said:
@marcost22 million of thanks to you, never thought will see a official lineage os for moto z play. Its based on 64 bit ?
I would like to say "YOU ARE THE BEST" !!
Click to expand...
Click to collapse
Yes, as all my roms it is a 64bits rom
marcost22 said:
Thanks!
Also funny finding you here
Click to expand...
Click to collapse
I also find funny the fact that you opened this thread just two days before my Z Play got out of the repair store. Nice timing!
Sorry if it's bothering you, when you apply the ROM the front flash is on directly. Did I do something wrong?
Nelsobrinho said:
Sorry if it's bothering you, when you apply the ROM the front flash is on directly. Did I do something wrong?
Click to expand...
Click to collapse
The front flash is on all the time? That's odd
Care to get me a logcat of it? Also, what fw version you were running before
marcost22 said:
The front flash is on all the time? That's odd
Care to get me a logcat of it? Also, what fw version you were running before
Click to expand...
Click to collapse
Sorry friend I posted here but I got very impatient and re-applied the rom and the front flash is ok. The only downside is that NFC is not working in practice, despite being available in the settings menu. Does anyone know or have the same bug?
Nelsobrinho said:
Sorry friend I posted here but I got very impatient and re-applied the rom and the front flash is ok. The only downside is that NFC is not working in practice, despite being available in the settings menu. Does anyone know or have the same bug?
Click to expand...
Click to collapse
Do you by any chance have the chinese (XT1653-03) variant? If not, can you grab me a logcat of the behaviour so i can check it?
Nelsobrinho said:
Sorry friend I posted here but I got very impatient and re-applied the rom and the front flash is ok. The only downside is that NFC is not working in practice, despite being available in the settings menu. Does anyone know or have the same bug?
Click to expand...
Click to collapse
First, thank you very much for the ROM @marcost22
I think it's amazing to bring an "updated" android to an old smartphone
Here I had the same problem with NFC (my variant is XT1635-03)
How I "solved":
restart in twrp (use latest that can mount vendor folder)
mount the vendor partition
Go to /vendor/etc folder
delete the file libnfc-nxp.conf
rename the file libnfc-nxp_retcn.conf to libnfc-nxp.conf
If you have magisk, it won't work.
You have to do this configuration before installing magisk.
joaoantonioe said:
First, thank you very much for the ROM @marcost22
I think it's amazing to bring an "updated" android to an old smartphone
Here I had the same problem with NFC (my variant is XT1653-03)
How I "solved":
restart in twrp (use latest that can mount vendor folder)
mount the vendor partition
Go to /vendor/etc folder
delete the file libnfc-nxp.conf
rename the file libnfc-nxp_retcn.conf to libnfc-nxp.conf
If you have magisk, it won't work.
You have to do this configuration before installing magisk.
Click to expand...
Click to collapse
That retcn file is there for this purpose, but it should be getting done automatically on boot. I'll have to redo this some other time
marcost22 said:
That retcn file is there for this purpose, but it should be getting done automatically on boot. I'll have to redo this some other time
Click to expand...
Click to collapse
"delete the file libnfc-nxp.conf
rename the file libnfc-nxp_retcn.conf to libnfc-nxp.conf"
I redid the whole process but when I get to this part when I delete and rename the file I restart the system and NFC is already disabled even without installing Magisk. I still don't have NFC
Nelsobrinho said:
"delete the file libnfc-nxp.conf
rename the file libnfc-nxp_retcn.conf to libnfc-nxp.conf"
I redid the whole process but when I get to this part when I delete and rename the file I restart the system and NFC is already disabled even without installing Magisk. I still don't have NFC
Click to expand...
Click to collapse
What is your variant?
My variant is XT1653-02