Oreo Rom For Lenovo Vibe P1mKernel is made by SaMad SegMane and rom is by SnowCatPDAhttps://github.com/SnowCat6
How to Flash The rom on Lenovo Vibe P1m
Requirements
A windows or linux pc
some time
fully charged device
internet to download Required Files
Backing UP IMEI
Flash Oreo Recovery through twrp or SPFT
Boot in to Recovery
Select NVRAM and NVDATA and backup
Move whole TWRP folder to a safe location ( to computer or sdcard )
Flashing The Rom
Backup all personal data
Download this rom , Extract the files
open SPFT
load MT6735M_Android_scatter-8_1-clean.txt from OREO_ROM folder
set the preloader file SPFT manually
select FORMAT+DOWNLOAD
turn of the device
connect it to computer
wait for the flashing to complete
ones done restart to recovery
copy backed up TWRP folder to internal storage
Reboot back to Recovery
restore NVRAM , NVDATA backup
Flash Accelerometer Fix
Flash SuperSU or Magisk if you wan't
reboot to system
Note : P1m Currently have 3 known LCM's , all of them are working so all users should be able to boot this
Going Back to Older Android Versions
Load MT6735M_Android_scatter-8_1.txt or another scatter file of a working rom
Choose Format+Download
Turn Off the device
Plug the device in
Reboot when done
Specifications
Android Version : 8.1.0
Kernel Version : 3.18.79
SOC version : MT6735 64bit
What's Working
All LCM drivers
touch
audio through headset and call speaker
mic
both sims
wifi & hotspot
bluetooth
Proximity Sensor
Light Sensor
All hardware buttons
What's not working or Partially working
Audio through main speaker
camera
charging is a bit slow [1A]
GPS
Accelerometer [x axis only have positive values]
Note : rom is compiled from an earlier version of android oreo alps sources, so there are many minor ui, rom based issues
Downloads
Oreo Recovery
Oreo Rom
Accelerometer Fix
Sources
Kernel Tree
Vendor Tree
Device Tree
Note :
compiling rom with this sources will result in non booting rom,this is due to mtk not providing provide sources of vendor specific proprietary files, so we are using libs from stock rom and other devices
Audio Mods won't work as audio is still buggy
Thanks
SaMad SegMane for kernel
SnowCatPDA for rom
Saif UR Rehman for tesing
Contact US
Telegram Group Channel
Github
Nice rom for Lenovo vibe p1m.
The Oreo rom is very good but if you solve the audio problem in this rom then this rom is perfect for use
Which gapps package we have to download for Oreo ROM?
I have tried many rom for my p1ma40 but i got bootloop. i got bootloop on this rom too. is there any solution ?
Any development going on with this ROM?
Hello. I use google translator. Tell me, is it possible to decrypt the data section on this firmware, and in what way? Thanks you
Hello why i cant login to whatsapp, when i login i dont receive the code can you fix it
Any solution for audio??
Related
Hi,
Recently received my Redmi 4X, and went straight to Lineage OS (Treble). However, I noticed that my sensors (accelerometer, gyroscope, gravity) aren't working. I've tried flashing a few different firmwares (f. ex. Nougat firmware from MIUI ROM 9.5.5.0 NAMMIFA HM4XGlobal with baseband V037_PA and Nougat firmware from MIUI ROM 8.5.17 HM4XGlobal with baseband V037_PA) and also tried flashing persist.img from santoni_global_images_V9.5.10.0.NAMMIFD_20180615.0000.00_7.1_global_a08a39d350, but they still do not work.. Any idea what to try next? Huge thanks to anyone who can give me some pointers..
BR
3D
Same here with latest Resurrection Remix 6.1 - are we the only ones with this issue?
Me too
dastu said:
Same here with latest Resurrection Remix 6.1 - are we the only ones with this issue?
Click to expand...
Click to collapse
Here the same....
DehDehDeh said:
Hi,
Recently received my Redmi 4X, and went straight to Lineage OS (Treble). However, I noticed that my sensors (accelerometer, gyroscope, gravity) aren't working. I've tried flashing a few different firmwares (f. ex. Nougat firmware from MIUI ROM 9.5.5.0 NAMMIFA HM4XGlobal with baseband V037_PA and Nougat firmware from MIUI ROM 8.5.17 HM4XGlobal with baseband V037_PA) and also tried flashing persist.img from santoni_global_images_V9.5.10.0.NAMMIFD_20180615.0000.00_7.1_global_a08a39d350, but they still do not work.. Any idea what to try next? Huge thanks to anyone who can give me some pointers..
BR
3D
Click to expand...
Click to collapse
@Klecker
First I do not own a Mi4, I have a mi8. However, I stumbled upon this post while I was looking for something unrelated and since I have had the issue and resolved it I decided to help you guys. You can repay my time by clicking the Thanks button.
The reason that you are having a sensors issue is because somehow you have either damaged or corrupted your persist partition.
Method 1
The fastest path to fix this issue is to restore a Nandroid backup that you hopeful have. Ideally you only need to restore the persist images.
Method 2
Another option which may will take some trial and error and persistence by downloading a fastboot rom start with the most recently used. It has to be the fastboot version of a Stable rom, and not a modded stock version.
Unpacking the rom your desktop, It will unpack from a 2GB file into a larger 4GB file, now unpack the 4GB file.
You will be left with a rom folder that inside has many files including flashall.bat and a folder full of images.
Place phone into fastboot or EDL mode, and connect to the PC
Next, assuming that you have all ADB tools and drivers installed , double click flasall. bat file.
Now watch as your phone is fully erased, and restored to stock
Once you have restored the phone, and went through the setup process, including signing into to MiCloud. You will be back in business and running again without issues. Norte : Ensure that you backup any wanted files before taking these steps, Also,, you unl;ocked boot loader will remain unlocked.
3rd Method
Unpack the fastboot rom, and manually extract the persist.img and then place it into the sd folder of your phone using recovery file manager.
Boot to TWRP
Go to advanced , then terminal
type: dd if = / sdcard / persist.img of = / dev / block / bootdevice / by-name / persist
After its finished reboot to system, finished
Again If that helped you click thanks instead of saying it.
if it doesn't work for you, try the fastboot flashall method using different roms until it finally works, or better yet, get someone that has the expanded version of TWRP that allows persist partition backups, to make a recovery backup and then share it with you, this will absolutely work too.
Thank you.
I tried first and second method, not working.
Is there somebody with a Redmi 4x Global who is willing to share his working TWRP
persist-backup file?
Thanks in advance
Is there anyone here with a working Redmi 4x who can provide me with a TWRP backup of his persist partition? I tried everything, nothing works.
Thanks in advance
Klecker
Klecker said:
Is there anyone here with a working Redmi 4x who can provide me with a TWRP backup of his persist partition? I tried everything, nothing works.
Thanks in advance
Klecker
Click to expand...
Click to collapse
So I use AICP rom so I don't know if it will work( I don't really know this stuff), but here u go.
I hope I did everything correctly
@edit
And oh, i did it in wolf recovery so I hope it works in twrp as it is based off it
THIS IS NOT MY WORK , this is only for sharing purpose and to provide device specific guide.
the real developer of this is- https://forum.xda-developers.com/pr...vice-development/rom-oxygen-os-5-1-0-t3822987
WARNING :I‘m not responsible for any consequences at all. This is an OEM rom port, it may cause wrong behaviors including partition overwritting and may brick your phone or break hardwares. I strongly recommend you take a completely full backup of your device and know how to recovery firmwares in case of any problems.
WARNING:MAYBE FULL OF BUGS.DONT FLASH IF YOU ARE AFRAID OF THEM.
This ROM is ported from Android P-DP of ONEPLUS 6.
Requirements :
*TREBLE ROM :-[url]https://forum.xda-developers.com/xiaomi-redmi-4x/development/rom-resurrection-remix-t3783793[/URL]
*Redwolf recovery treble supported :-[url]https://forum.xda-developers.com/xiaomi-redmi-4x/development/unofficial-redwolf-recovery-t3776738[/URL]
*OxygenOS_5.1.0.7z :-[url]https://androidfilehost.com/?fid=5862345805528062126[/URL]
*Patchv1 :-[url]https://androidfilehost.com/?fid=5862345805528062110[/URL]
Instructions :
PLEASE BACKUP YOUR DATA
Extract Oxygen Os 7z file anywhere,
Reboot to recovery,
Wipe data,cache,dalvik cache,system,vendor,
Flash RR luis rom 6.1 and boot the rom,
Reboot to recovery,
Backup Rom again with different name,
Now move the extracted Oxygen OS files to WOLF/.BACKUPS/(serial number)/nameofbackup2/HERE,{You need to enable show hidden files in explorer},
In recovery restore only SYSTEM (uncheck everything else),
Flash Patchv1.zip
Wipe DATA,CACHE,DALVIK,
REBOOT SYSTEM.
After boot everything will be weird don't worry enable navigation gestures, hide notch from display settings ,
You can change display size as you want but change it to 350 (from setting/developer setting / small width ) works/looks best , font size as you like.
Getting rid of rounded corners and notch coming soon dev is working on it.
BUGS:
SurfaceFlinger crashes when open Camera, Chrome(use UC),
FingerPrint,
Can't Reboot(use poweroff),
Hotspot(?)
WIFI and bluetooth cannot open at the same time.
WORKING:
VOLTE
Playstore
WIFI
GPS
Navigation Gestures
other apps
Screenshots:[url]https://drive.google.com/drive/folders/1EbjU0H8q5o3vDXzRBo3Yul-gnKn6484F[/URL]
CHANGELOG:
v1review released for testing.
Credits and THANKS TO
@fxsheep for porting
@Swapnil Soni for Recovery
@8224Freak for RR
nice new rom for santoni I hope it would be develop some day keep it up!
JR Bautista said:
nice new rom for santoni I hope it would be develop some day keep it up!
Click to expand...
Click to collapse
It's just a port, so i don't thnik so
Wow . . android P Nice work dev . . tnx for sharing ?
Very nice
Hello,
I am currently using Pixel Experience 9.0 Pie official ROM on my Redmi 4X Santoni.
Is it compulsory to use the RR ROM mentioned in the Guide or As my ROM is already Treble enabled I can flash The Oxygen OS GSI Directly. Or I have to extract it to the Recovery Backup Directory and Then Restore it from the Recovery .
TREBLE COMPATIBILITY FOR YUREKA BLACK (Tinno p7201)
Guide and Vendor Zips Should work on Tinno p7201 clones - Wiko U feel prime , Blu Life One X2 mini, and Cect Digi U
Disclaimer:
WARNING, IT REPARTITIONS THE DEVICE SO DONT FLASH ON LOW BATTERY.
IF YOU DON'T KNOW WHAT UNLOCKING IS OR WHAT A PARTITION IS , BETTER NOT USE THIS.
!!! Whatever you do, it is at your own risk !!!
*************************************************************************************************************
How to Install
Flashing recovery
1. Flash Treble TWRP recovery given in downloads (important).
2. Reboot to recovery.
Re-partition & Treblize Device
Flash Treble Partitioner tool edited for Yureka Black in treble recovery. (Important Note: Only use the recovery given for download in next post (Twrp that has orange accents and splash) and the tool works properly only in it. Use this recovery whenever you use this tool. You can change recoveries later. Use of other recoveries to flash partition tool can put phone in a no-OS state).
Follow the on screen instructions while using tool.
Reboot to recovery.
Wipe System and Vendor.
If system or vendor aren't mounting change their filesystem to ext4.
Reboot to recovery.
From now you can flash Roms with Twrp or Any other recently built recovery ( Any treble twrp, Official twrp in twrp.me/ Pitch black recovery or (Twrp that has orange accents given after this post)).
GAPPS and MODS work properly only when flashed with latest recoveries and I don't maintain them.
All actions performed here are reversible.
As far as i know, everything here has been used > 100 times for several years and works.
If you want to flash GSI
Flash the Rom zip
Wipe system, Flash the GSI image to system & wipe data.
GSIs don't boot on android 11 right now. Please contact your Rom/Os maintainer for device and ask them to fix it.
*************************************************************************************************************
IMPORTANT:
For ERROR: 7 & in TWRP on flashing non treble roms.
Garlic was not released with treble ! Non treble Roms which are based on android 10 and prior for garlic CANNOT be flash after partitioning,
You need to remove vendor using partitioning tool again on partition tool required recovery.You can then flash non treble Roms like before or change recoveries.
*************************************************************************************************************
Credits----Source Maintainers & Co
Treble Party Tool:- @Oki - For TREBLE - PARTY TOOL --@someone755 for the keycheck binary--- @Zackptg5 for the V4A install script.
Recovery----Teamwin&Team
Give me a thumbs-up if it helped you
DOWNLOADS IN NEXT POST
DOWNLOADS
PARTITION TOOL
TREBLE TWRP
MORE HELP
Does it require Data Format?
No
What GSI can boot?
All GSI depending on Oreo or Pie depending on respective vendors along with Sgsi like MIUI,Zui, OOS and other Sgsi ports. No GSI will boot on Android 11 (Ask device maintainers).
Why are non treble custom roms no longer flashing?
Because custom roms are made for 4.7gb system , unless the dev mentions 3.7gb system , they cannot be flashed along with treble.
If you want to revert to non-treble custom roms..
Reflash the Party tool and choose option to remove vendor partition.
I'm on Android Nougat (7.1.1) and have a Wiko U Feel Prime.
Am I able to flash this treble or do I need a 8.0 custom ROM to enable treble.
Also can I flash any gsi I found out there or do I need a specific gsi for this since it isn't an originally supported treble device
Noobyguy said:
I'm on Android Nougat (7.1.1) and have a Wiko U Feel Prime.
Am I able to flash this treble or do I need a 8.0 custom ROM to enable treble.
Also can I flash any gsi I found out there or do I need a specific gsi for this since it isn't an originally supported treble device
Click to expand...
Click to collapse
Hello , there are standalone vendor zips in the post .First you need to repartition , after doing it you dont need a custom treble rom, flash my treble twrp, then just flash the vendor zip + bootimage and any GSI (pie GSI for pie vendor and Oreo GSI for oreo vendor) after wiping data.GSIs are not bug free. If you have any doubts/want to know the latest development going on the device, I strongly suggest you to join the telegram group, there are few wiko u feel prime users in our group.
Note:I did not make this vendor the credits go to dinolek from 4pda. I AM JUST SHARING IT HERE TO HELP OTHERS. IF YOU WANT ME TO DELETE IT GIVE ME A MESSAGE I'll DELETE IT.
YOU YOUR SELF ARE RESPONSIBLE FOR THE THINGS YOU DO TO YOUR SMART PHONE.I AM NOT responsible.IF YOU POINT YOUR FINGER AT ME I WILL laugh AT YOU.
A warning!!!
This vendor is not compatible with firmware on official vendors from Redmi 6 and 6A themes
Patches and various modifications for the official vendor will not work on the OSS vendor, sometimes have a negative effect!
Kernels from the official vendor will not work on the new vendor. When installing the kernel from the official vendor, the firmware will not start!
short info:
The author of an unofficial vendor is Dinolek
This vendor is based on the ALPS source code from MediaTek based on Android 10
This vendor has significantly fewer problems than all the official
This vendor has been thoroughly tested and has a stable status.
OSS vendor advantages over official:
Default data encryption is missing
- There is support for Api2Cam (You can download Google Camera from Google Play or use the Google Camera GO mod)
- No problem with codecs on Android 10 and 11
- No problems with ring volume control on CERTUS and GSI firmware
- There is support for the Vulkan API (some games and applications will work a little better)
- CERTUS and GSI work much more stable than on the official versions of vendors
- There is video stabilization
- Official YouTube client works great at 720p 60fps
- Kernel 4.9.190
- Based on Android 10 ALPS (AOSP from MediaTek)
Kernel -https://github.com/CertusRepos/android_kernEl_xiaomi_certus
Tree-https://github.com/CertusRepos/android_device_xiaomi_certus/tree/alps-10.0
Requirements:Unlocked bootloader
Need android pie miui
0.4 is for custom Roms and 0.5 is for
gsi
Don't use this vendor for android 9 custom roms
How to install it...I tried to install it twice but ended up with bootlooping...and is there any requirement to flash alps boot.img and where can I get the boot.IMG....by the way I am on crdroid 7.9, wulans kernel, vendor 1.0.8.0
havokelite said:
How to install it...I tried to install it twice but ended up with bootlooping...and is there any requirement to flash alps boot.img and where can I get the boot.IMG....by the way I am on crdroid 7.9, wulans kernel, vendor 1.0.8.0
Click to expand...
Click to collapse
Which twrp version and did you overwrite the vendor or deleted it first and then installed the alps vendor
Rom checker said:
Which twrp version and did you overwrite the vendor or deleted it first and then installed the alps vendor
Click to expand...
Click to collapse
Thanks for the reply, I am on OrangeFox Recovery and I deleted the vendor first & then flashed RevengeOS but got stuck in the bootloop and then flashed CorvusRom and a few other but nothing worked...So I flashed miui stock boot.img and salvaged my redmi 6a....Well I havent flashed vendor before so can u please give full instructions on how to flash the OSS vendor...I mean I have the zip file so can I just flash it or do I need to extract the zip and then select the boot.img file within the alps vendor 4.0 zip....
havokelite said:
Thanks for the reply, I am on OrangeFox Recovery and I deleted the vendor first & then flashed RevengeOS but got stuck in the bootloop and then flashed CorvusRom and a few other but nothing worked...So I flashed miui stock boot.img and salvaged my redmi 6a....Well I havent flashed vendor before so can u please give full instructions on how to flash the OSS vendor...I mean I have the zip file so can I just flash it or do I need to extract the zip and then select the boot.img file within the alps vendor 4.0 zip....
Click to expand...
Click to collapse
Use official twrp latest version and delete the vendor from advanced wipe and install alps vendor 0.4 for revenge os after that the ROM should boot, if it still doesn't boot give a try for 0.5 vendor bcz some people were saying that this vendor was helping them boot ROMs
Are these vendor images up-to date?
Asking because the numbers, 0.4 and 0.5, do not represent the tree version (10.0)
Did those images work for anybody?
I am trying to get back from 64-bit vendor for Android 12 and flashing those over ALPS-Vendor-0.6-ARM64-cactus just doesn't work. The phone is not bootlooping, rather is stuck on boot.
Interestingly enough 0.4 patches just vendor partition, while 0.5 patches both vendor and boot
HELLO THERE
Here's a list of all working roms, twrps, kernels and more for MediaPad T5.
If you want a guide of how to install, go to this post.
Report issues to T5 Support group from here
I'm making a MEGA folder with all specific (needed to work) and non-specific zips, kernels and twrps
N-S --> CAN USE NON-SPECIFIC ZIPS (may not work)
S --> NEEDS SPECIFIC ZIPS TO WORK ( can use non-specific compatible too)
PR --> Pre Rooted ROM
PRX --> Pre Rooted but doesn't work
UR --> Un Rooted ROM
U --> Untested ROMs (may work but I've not tested it yet)
M --> MODDED FOR T5 COMPATIBILITY
Modded roms are tested and proved to work. All the roms in the list are
compatibles, but newer versions may cause some installation errors.
Join the telegram group if you have any issue and I'll take a look as fast as I can.
PRX - LineageOS by @DarkJoker360 N-S
LeaOS by @AltairFR S U
PR - CrDroid by @Hami_Do N-S M
I tried the following roms on AGS2-W09
Did not boot:
lineage-18.1-20220224-UNOFFICIAL-iceows-pra
crdrom-v313+211013-arm64-avZ
crDroid_v7.10_11-WAS-21092021
Too large to install:
crdrom-v315+220202-iceows-pra
Works:
lineage-18.1-20211106-UNOFFICIAL-prague
CryptLoad said:
I tried the following roms on AGS2-W09
Did not boot:
lineage-18.1-20220224-UNOFFICIAL-iceows-pra
crdrom-v313+211013-arm64-avZ
crDroid_v7.10_11-WAS-21092021
Too large to install:
crdrom-v315+220202-iceows-pra
Works:
lineage-18.1-20211106-UNOFFICIAL-prague
Click to expand...
Click to collapse
crdroid should work. Go to the telegram grou chat to get the modded version until I release it. crdrom is about to get fixed. Lineage too.
crDroid_v7.10_11-WAS-21092021 does work
same for:
lineage-18.1-20220523-UNOFFICIAL-prague
LeaOS-20220616-UNOFFICIAL-iceows-pra.img (uploaded 1 day ago)
It took me more than a day to figure this out but if you have flashed Magisk in one of these custom ROMs then you need to restore the original KERNEL.img and RAMDISK.img form your stock firmware, otherwise everything will boot loop (even if you restore the initial custom ROM you have flashed first time). This is mostly because Magisk modifies the boot.img to apply the root patch.
As a side note here: you can install magisk.zip through TWRP immediately after reflashing your starting/initial custom ROM to be able to boot as before.
To do this I have used HuaweiFirmwareFinder (website + proxy app) to download update.app and then extracted the imgs with HuaweiUpdateExtractor and then used fastboot to flash the images.
It is useful if you have remembered your previous stock version as there can be conflicts with other images (like erecovery or recovery_ramdisk) if they have different versions.
Also I have never used TWRP to do the inital flashings, just fastboot because I see many threads here with people bricking their tablets.
denzelcris said:
crDroid_v7.10_11-WAS-21092021 does work
same for:
lineage-18.1-20220523-UNOFFICIAL-prague
LeaOS-20220616-UNOFFICIAL-iceows-pra.img (uploaded 1 day ago)
It took me more than a day to figure this out but if you have flashed Magisk in one of these custom ROMs then you need to restore the original KERNEL.img and RAMDISK.img form your stock firmware, otherwise everything will boot loop (even if you restore the initial custom ROM you have flashed first time). This is mostly because Magisk modifies the boot.img to apply the root patch.
As a side note here: you can install magisk.zip through TWRP immediately after reflashing your starting/initial custom ROM to be able to boot as before.
To do this I have used HuaweiFirmwareFinder (website + proxy app) to download update.app and then extracted the imgs with HuaweiUpdateExtractor and then used fastboot to flash the images.
It is useful if you have remembered your previous stock version as there can be conflicts with other images (like erecovery or recovery_ramdisk) if they have different versions.
Also I have never used TWRP to do the inital flashings, just fastboot because I see many threads here with people bricking their tablets.
Click to expand...
Click to collapse
This makes sense as flashing the boot also flashes the KERNEL and RAMDISK (correct me if I'm wrong). But do you know if you should do the same if you flash the system? I'm trying to flash a GSI but my device goes to a boot loop after flashing the system.
crDroid is working...just dont forget to unpack the x.z-file
Hi, anyone can help me?. I'm trying to install leaos on my Huawei Mediapad T5 (i'm not new on this), but everytime i reboot It when It finish installing, It keeps rebooting when It has to show the first configuration screen.
Nevermind, i finally got It to work