{
"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:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About the project
Boot Bridge for Sony ELF is born out of an idea to create support
of systemless tools like SuperSU on the Sony ELF bootimages.
The structure being different from regular Android boot partitions,
these tools never worked to edit the content of the boot image
present on devices like the Xperia SP, T, TX, V, ...
Boot Bridge for Sony ELF allows you to choose the systemless zip
by simply replacing the file install/install.zip with the one to flash.
Warning: BootBridge for Sony ELF is meant to be used on custom ROMs.
For stock ROMs, you'd need to patch the ROM (bootimage securities) first.
Please refer to the currently supported devices list in the second post.
When you flash the Boot Bridge zip, a fake regular bootimage is created
with the contents of the original ELF partition, mapped in the fstab,
then the install.zip is automatically flashed as if you did yourself,
and finally the ELF partition is updated accordingly.
Boot Bridge for Sony ELF also supports being used with MultiROM secondary ROMs.
The project is an extension of the libbootimg originally created by Tasssadar,
that I then reworked to add Sony ELF boot support for Xperia MultiROM.
Downloads (Unlocked Bootloader only)
BootBridge-SonyELF.zip : https://github.com/AdrianDC/android_boot_bridge/blob/master/release/BootBridge-SonyELF.zip
Preview of the installation
OPTION 1) Root with Magisk by topjohnwu
Magisk (Latest version) : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Rename the downloaded zip to install.zip
Open the Boot Bridge zip with a zip manager
Replace the file install/install.zip with the new one
Flash the new Boot Bridge zip in the TWRP recovery
Reboot to Android
OPTION 2) Root with SuperSU by Chainfire
In order to get root access on AOSP based ROMs (2.78 SR5 or newer for 7.1.x),
you need to download the SuperSU project by Chainfire.
SuperSU zip (Latest version) : http://forum.xda-developers.com/apps/supersu
Rename the downloaded zip to install.zip
Open the Boot Bridge zip with a zip manager
Replace the file install/install.zip with the new one
Flash the new Boot Bridge zip in the TWRP recovery
Reboot to Android
OPTION 3) Root with phhSuperUser by phhusson
In order to get root access on AOSP based ROMs (7.1.1 included),
you need to download the phhSuperUser project by phhusson.
superuser.zip : http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Rename the downloaded zip to install.zip
Open the Boot Bridge zip with a zip manager
Replace the file install/install.zip with the new one
Flash the new Boot Bridge zip in the TWRP recovery
Reboot to Android
Install the phh's SuperUser application
Source code
Project sources - https://github.com/AdrianDC/android_boot_bridge (branch master)
libbootimg sources - https://github.com/AdrianDC/multirom_libbootimg (branch master)
MultiROM sources - https://github.com/AdrianDC/multirom_core (branch master)
Boot Bridge for Sony ELF created also thanks to :
- Tasssadar for the original libbootimg / MultiROM sources
- The XperiaMultiROM team for our evolution of MultiROM
- Chainfire for the flashable OUTFD export and boot detection
- Everyone involved in testing it
XDA:DevDB Information
Android Boot Bridge for Sony ELF, Tool/Utility for the OEM Cross Device Development
Contributors
Adrian DC
Version Information
Status: No Longer Updated
Created 2016-11-25
Last Updated 2020-08-29
Reserved
Changelog
Code:
Boot Bridge for Sony ELF - 26/12/2018
======================================
* Resolve compatibility with Magisk v17+ due to an
internal evolution of its boot partitions detection
Boot Bridge for Sony ELF - 28/05/2017
======================================
* Use android_boot as potential bridge to fix SuperSU
Boot Bridge for Sony ELF - 20/12/2016
======================================
* Fix the 32/64 bits dual support
Boot Bridge for Sony ELF - 18/12/2016
======================================
* Added support for Sony Stock ELF (64 bits) bootimages
* libbootimg changes from my recent updates
Boot Bridge for Sony ELF - 29/11/2016
======================================
* Fix the boot partition detection with symlinks
* Restore phhSuperuser support
Boot Bridge for Sony ELF - 27/11/2016
======================================
* Add support for newer Sony ELF partitions
* Allows to root Stock Sony ROMs on the Xperia Z2
* Updated in collaboration with Alexander Diewald
Boot Bridge for Sony ELF - 25/11/2016
======================================
* Initial public release on XDA
Devices supported
Code:
Sony Xperia SP (Huashan): Magisk, SuperSU, phhSuperSU
Sony Xperia T/TX/V (Mint, Hayabusa, Tsubasa): Magisk, SuperSU, phhSuperSU
Sony Xperia Z2 (Sirius): SuperSU on Stock ROMs
Sony Xperia X Performance (Dora): Stock ROM patching
...
It's great news! thanks a lot, will try it soon. :fingers-crossed:
hi @Adrian DC,
Thanks for your mail that pointing me on this thread.
As you now I'm maintaining a ROM for Xperia S and your project can be a good fit for it
For now I have a built-in support of root but no solution for those who wants SuperSU.
I'm generating the boot.img for Xperia S with the commandline :
python $(MKELF) -o [email protected] $(PRODUCT_OUT)/[email protected]$(BOARD_KERNEL_ADDR) $(PRODUCT_OUT)/[email protected]$(BOARD_RAMDISK_ADDR),ramdisk $(RPMBIN)@$(BOARD_RPM_ADDR),rpm
With parameters below :
# boot image
BOARD_KERNEL_ADDR := 0x40208000
BOARD_RAMDISK_ADDR := 0x41500000
BOARD_RPM_ADDR := 0x20000
Is your project compatible with the way I'm generating boot.img for Xperia S ?
If yes, I will test it with SuperSU (sepolicy for SuperSU systemless is already supported on the ROM).
Thanks for your feedback and work on that topic
mickybart said:
Thanks for your mail that pointing me on this thread.
Click to expand...
Click to collapse
No problem.
Normally the full port of Sony ELF partitions I made inside libbootimg for MultiROM
is compatible with all bootimages structures from these series of Sony devices.
I invite you to have your ROM's boot.img flashed into boot directly,
then flash my Boot Bridge as it is, even without a rooting zip, like in my screenshot,
and let it run to see the bridge creation then restore perform.
If anything goes wrong and the bootimage is not readable,
the process will stop and nothing will be done.
In the very worst case, the rebuilt boot image doesn't start
and you simply fastboot the image you came from.
Also recently I worked with Diewi (Alexander) to extend ELF support
to the newer version of Sony's last ELF devices, the 8974 (Z2) boot
that had ELF Stock images but also support for Android normal ones.
Once fully tested and confirmed, the update will be done on this project too.
On a side note, about root, SuperSU works fine on my devices on 6.0 & less,
for 7.1 the installation is fine too but the root features failed (with sepolicies totally fixed),
this is apparently common / randomly affecting some devices,
Chainfire is aware of it, so do not be surprised if that happens on yours,
and give phhSuperUser a go too as it is the fully working method on my AOSP 7.1 now.
Bye !
Amazing! Worked like a charm..no issues at all..thanks a [email protected] Adrian DC
Boot Bridge updated to support newer Sony ELF devices,
including the Stock Sony ROMs, allowing an easy SuperSU root process.
Hi Adrian, Sorry if is a noob question but im facing ERROR: 7 after instaling the BootBridge-SonyELF.zip, i've already replace the install.zip, it says in TWRP ------> Found bootimg @ /dev/block/platform/msm_sdcc.1/by-name/kernel ----> assert failed: run_program(''/tmp/boot_bridge/flash_zip.sh'', ''/tmp/boot_ brdge'', ''install.zip'') == 0 .... what i'm doing wrong? .. Im on AOSP 25/11 . Thanks for your time
Miggystar said:
Hi Adrian, Sorry if is a noob question but im facing ERROR: 7 after instaling the BootBridge-SonyELF.zip, i've already replace the install.zip, it says in TWRP ------> Found bootimg @ /dev/block/platform/msm_sdcc.1/by-name/kernel ----> assert failed: run_program(''/tmp/boot_bridge/flash_zip.sh'', ''/tmp/boot_ brdge'', ''install.zip'') == 0 .... what i'm doing wrong? .. Im on AOSP 25/11 . Thanks for your time
Click to expand...
Click to collapse
I've got the same error, did everything exactly according to instructions.
Where could the error be?
MichaBit said:
I've got the same error, did everything exactly according to instructions.
Where could the error be?
Click to expand...
Click to collapse
Thanks for reporting the issue.
It was introduced with the new update to support Z2 devices, and affected only phhSuperuser.
The issue is now fully fixed, please download the new version and try again.
Adrian DC said:
Thanks for reporting the issue.
It was introduced with the new update to support Z2 devices, and affected only phhSuperuser.
The issue is now fully fixed, please download the new version and try again.
Click to expand...
Click to collapse
Installation completed!
#root successfully :good:
Many thanks and greetings Adrian :highfive:
does it work with locked bootloader?
I have Xperia Z2 MM deodexed rooted with xposed
a.hamameh96 said:
does it work with locked bootloader?
I have Xperia Z2 MM deodexed rooted with xposed
Click to expand...
Click to collapse
This mod intervenes in boot image (kernel) so most probably it wont work. But I am not 100% sure
MichaBit said:
Installation completed!
#root successfully :good:
Many thanks and greetings Adrian :highfive:
Click to expand...
Click to collapse
Work for lbl???
vandiaz_sairavinz said:
Work for lbl???
Click to expand...
Click to collapse
dont try on lbl it will brick ur phone
nhicko95 said:
dont try on lbl it will brick ur phone
Click to expand...
Click to collapse
Ok, thank you
This is happening to me when I move App to system in link2Sd...
Greetings Adrian,
So nice that you still support our old Sony devices, particularly Xperia V. :good:
The thing is I used your Elf Bridge and succeeded to install Magisk 11.6. But then a new version of it came, 12.0. And I did all the same way as with 11.6 but failed. It was written that the boot image was so small. However, I flashed Magisk 12.0 with no Elf Bridge. And the weird thing that that time there was enough space. I knew that flashing without the Bridge would cause soft-brick, but I knew what to do next in that case, I flashed the proper boot image after all and the device started working again.
The question is following: is it possible to flash Magisk 12.0? I also forget to tell that the size of these two versions are almost similar. The log is attached here.
Thanks!
magisk 11.6 and above have elf support
Speed of a Puma, Brain of a Chicken
myxomop25 said:
Greetings Adrian,
So nice that you still support our old Sony devices, particularly Xperia V. :good:
The thing is I used your Elf Bridge and succeeded to install Magisk 11.6. But then a new version of it came, 12.0. And I did all the same way as with 11.6 but failed. It was written that the boot image was so small. However, I flashed Magisk 12.0 with no Elf Bridge. And the weird thing that that time there was enough space. I knew that flashing without the Bridge would cause soft-brick, but I knew what to do next in that case, I flashed the proper boot image after all and the device started working again.
The question is following: is it possible to flash Magisk 12.0? I also forget to tell that the size of these two versions are almost similar. The log is attached here.
Thanks!
Click to expand...
Click to collapse
Thanks.
Yes I got reports on that, but I think the faulty half-ELF support causes the issues you are having.
Better stick to the working version for the time being.
flipside101 said:
magisk 11.6 and above have elf support
Click to expand...
Click to collapse
Not really, it's faulty and breaks ELF bootimages (tunrs them back to regular bootimages,
which is where BootBridge plays a role to have proper read and write of the ELF bootimages
structures (32bits 8960 or newer 64 bits like 8996 Stock) without ELF support in the tools.
Related
Hello dear Lemon users!
I aquired this wonderful phablet a few weeks ago and started to tweak and experiment with it to get the most out of it.
I come from a ST25i (Xperia U) and am used to tweak and mod android phones.
But the only thread I've found was not organized or structured to aid and support those who know nothing about this phablet, mediatek or even android. Everything was spread around the massive number of posts, which always leads to users asking the same things over and over again.
So i decided to open this thread that i will keep updating with roms, recoveries, root methods, patches, tools, tutorials, etc...
ROMS
Flashable through SP FlashTools/Recovery
All Official ST/DEV/ROW Roms + OTA
ROW roms are flashable through SP Flash Tool, all the others are flashable through stock recovery or custom (you have to edit updater-script inside the meta-inf folder)
Flashable through SP FlashTools
VibeUI_Xancin
Source
A7000 137 ROW
Source
Flashable through CWM/TWRP
K50a40_S117_150706_ROW
Source
K3_Note_Xancin_Haier
Minimal GAPPS
Source
AOSP_CBT_HK_LIMITED
Source
SenSation_Rom
Source
AOSP_V4_XANCIN
Source
++LiMoNcHeLo 5.1 MDSTeam MoD++
PATCH
Source
++[LiMoNcHeLo NovAMoD MDSTeam VibeAosP]++
Source
Install this SMS app to fix the duplication of conversations due to incoming messages number having country prefix.
VibeUI_5.1_LTT_MDSTEAM
Source
VIBEUI_S137_ROW_LEMONADE
Source
Xperia_Mod_VibeUI_15_21
Source
Agujetas_vs_Reflex
Source
AOSP 5.1 by MDSTEAM (iOcean Rock Port)
Patch
Source
Carbon K3 Lite 2.5
Video Fix
Source
Lewa 6 (TCL M2M port)
Source
GACAMA AOSP v2.1_5.1
Source
Bestial Rom MDSTEAM
Ringtones patch
Source
Nexus ROM 5.1
Source
Haier 5.0
Source
360 Firmware OS from QIKU
Source
CoolUi 6.0 beta1 (Coolpad Dazen)
Source
Pekk3nDroid K3 1.0 AOSP (Androium 2.1.3 Based)
Source
Amigo OS 3.1.3
Source
VETA OS
Source
IUNI OS 5.18 pass: 092c
Source
SunRom V3.9
Patch
Delete Call Light Patch
Source
MIUI 7 6.1.30
Source
MIUI 7 7.1.1.0 Stable
Source
Flyme 5.6.2.1
Source
CM 12.1 Beta 3
Source
CM 12.1 PAC pass: 3361
Source
CM 12.1 SudaMod pass: 6f9f
Source
BlissPop v4.0.3
Source
Phoenix Rom 3 (Jiayu S3 Port)
Source
Vivo Funtouch 2.5
Source
EUI 5.5.037E
Source
VIBEUI_V3.5_1605_LTT_LEMONADE ANDROID 6.0 MM
Source
AOSP 5.1.1 LEMONADE V4
Contacts/Calendar Patch
Source
S205_VISNU_LEMONADE
Source
Androium 6
Source
LENOVO_K3_LOLLIPOP_5.0_S205_ROW_v1.17_CUOCO92
Source
04_K3_NOTE_5.1_1604_STABLE_ROW_004_CUOCO92
Source
Maremoto v2 (Jiayu Port)
Source
GReeNoiD v1.0
Source
K3_NOTE_MM_6.0_1610_3.40.1_v16_ROW_D_CUOCO92
Source
AOSP PURE BETA (Zopo Speed7 port) by pvkiniyan95
Source
OPEN SOURCE CODE
Android 5.0 Lollipop
Android 6.0 Marshmallow
Source
USEFUL LINKS
Lenovo Forum
Club Lenovo Forum
Mobile Uncle Forum
Loorin Forum
4PDA Forum
Movilesdualsim Forum
TUTORIALS
How to flash official VibeUI ST/DEV roms through custom recovery:
- You will need to edit the updater-script file inside the .zip
- Use 7zip to open the zip and go to \META-INF\com\google\android\updater-script
and drag the file out (same as copy/paste)
- Use Notepad++ to open it and edit the updater-script.
- Delete all the lines until:
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
- Save and replace the file dragging it into the 7zip window you left open.
- Flash the rom, ignore errors after the "Patching system image unconditionally..." message.
How to flash roms through SP Flashtool
How to flash recoveries through SP Flashtool
USB Drivers
USB Driver
Tools
ADB/Fastboot Automatic Recovery Install Tool
Extract folder, connect your phone to PC, run Recovery Install Tool.bat
You can flash any recovery, just replace the recovery.img file within the dir.
BaiduYunGuanjia VIP (English)
PC program to download large files from the chinese Baidu/Yunpan clouds. Run the self extracting file and afterwards run BaiduYunGuanjia.exe from within the extracted folder.
Root
Super SU
Flashable through recovery
SP Flash Tool
SP Flash Tool
Source
Recoveries
Recoveries Folder
Flashable through custom recovery, through SP Flashtool or directly through TWRP recovery using only the .img file.
Custom recovery - Just download any .zip, replace the recovery.img file within the .zip if you want another recovery using 7zip and flash it.
SP Flashtool - Just download the scatter.txt file and the recovery.img you want and flash it.
TWRP - Just download the recovery.img you want, select install in TWRP, install image, select the .img, mark the partition recovery and flash.
GAPPS arm64
Dirty Unicorns Gapps 5.1
OpenGapps
Source
Slim Gapps 5.0
Slim Gapps 5.1
Slim Gapps 6.0
Source
Flashable through TWRP/CWM recovery
XPOSED
5.0/5.1/6.0
Flashable through TWRP/CWM recovery
PATCHES/FIXES
Patched Boot Images
Flashable through TWRP recovery. Flash these to be able to boot in stock android 6.0 roms.
Patch for correcting offline charging screen in some roms
Flashable through TWRP/CWM recovery
Source
WiFi NVRam Error Fix
Copy the files in the zip to the same path, replace the ones there and set same permissions.
Invalid/Lost IMEI
Simply download this app, input your IMEIs, apply, reboot!
GPS Glonass Fix
Flashable through TWRP/CWM recovery (No wipes needed)
Source
MAXX Audio
Flashable through TWRP/CWM recovery (No wipes needed)
Source
Flashing removes Dolby Atmos and the toggle in the quick settings won't do nothing.
5GHZ Wifi Enabler
Enables the phone to pick up 5GHZ wifi frequencies.
MODEMS/RADIOS/BASEBANDS
Modems/Radios/Basebands All Versions
Flashable through TWRP/CWM recovery (No wipes needed)
Source
TWRP Backups
TWRP Backups Folder
Run the self extracting file and then copy the extracted folder to the dir of the backups of your TWRP recovery.
Enter recovery and restore. Reboot to system, enjoy...
All backups are rooted.
DUAL+ BOOT
Dual Boot Setup Procedure
Just in case...
2 other K3 Note resources:
http://forums.whirlpool.net.au/archive/2393953
http://www.needrom.com/category/lenovo/serial-k/k-50/
Guys get ready for AMIGO 3.5 from Gioneee Elife s7.. Really awesome rom.. uploading soon..
Can i flash the ROM directly on ROW version or i have to be on chinese Frirmware....?
hackerpower said:
Just in case...
Click to expand...
Click to collapse
which rom do you think is the best?(based on performance and minimal bugs)
How to port auto call record feature in limonchelo novamod ??
ifu said:
Can i flash the ROM directly on ROW version or i have to be on chinese Frirmware....?
Click to expand...
Click to collapse
The indian ROW rom has to be flashed via SP Flash Tool, so you can even format the whole phone before flashing it, no need to be on any rom prior to that.
daniel1112333 said:
which rom do you think is the best?(based on performance and minimal bugs)
Click to expand...
Click to collapse
The one i use, it's in my sig.
gurdeepsim said:
How to port auto call record feature in limonchelo novamod ??
Click to expand...
Click to collapse
Don't know, but i already saw that option in many other roms.
hello, can i flash the rom using FLASHIFY?? i think this is the easiest way to root and be in RECOVERY mode.
bitmappp said:
hello, can i flash the rom using FLASHIFY?? i think this is the easiest way to root and be in RECOVERY mode.
Click to expand...
Click to collapse
Which rom?
I don't know, ask the dev.
any rom under you Original post
bitmappp said:
any rom under you Original post
Click to expand...
Click to collapse
If it's possible it will only work with roms flashable through TWRP/CWM recovery, but i don't think it will work.
is there any way using wich we can chage wifi icon or hide wifi signal icon
gurdeepsim said:
is there any way using wich we can chage wifi icon or hide wifi signal icon
Click to expand...
Click to collapse
Gravity box module in Xposed.
Hi all, got my boy this today from gearbest uk, and I'm impressed with it so far. It came already rooted and with a couple of porn apps preinstalled lol, which i removed.
Anyway since it's already rooted i thought my plan of action would be to, install/run busybox, then install and use flashify to install custom recovery from the head post. Once done i would boot to custom recovery and install the recommended limochelli novamod rom, wiping off course.
Can anyone see any problems or am i good to go?
btw, great post, nice to see all needed info and files in one place
Which one is the best Rom for daily use....?
Added GPS Glonass Fix patch!! Now i catch russian sats Thanks AtlonX2
{
"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"
}
:good:
Checkout the before and after SS attached.
meangreenie said:
Hi all, got my boy this today from gearbest uk, and I'm impressed with it so far. It came already rooted and with a couple of porn apps preinstalled lol, which i removed.
Anyway since it's already rooted i thought my plan of action would be to, install/run busybox, then install and use flashify to install custom recovery from the head post. Once done i would boot to custom recovery and install the recommended limochelli novamod rom, wiping off course.
Can anyone see any problems or am i good to go?
btw, great post, nice to see all needed info and files in one place
Click to expand...
Click to collapse
You're good! TY. Any doubts holla!
ifu said:
Which one is the best Rom for daily use....?
Click to expand...
Click to collapse
It depends on what you want/like, but IMO Limonchelo Novamod.
I hope that this is the right thread to post that there is a new Dev-ROM made by Lenovo:
VIBEUI_V2.8_1530_7.131.1_DEV_K50-T5 大小：M 更新日期：2015/07/23
Click to expand...
Click to collapse
Source: http://www.vibeui.com/vibeui/rom?key=k3 note
Changelog: (Google translation)
Recommend
★ Security Center: privacy mode function optimization, more in line with privacy requirements
★ System: Solving the one-handed fast, the display application searches when there is no problem
★ Gallery: solved in some cases, appears to stop running when you click on the album set of problems
Security center
Optimization - adjust privacy mode logic, more in line with user habits
(Reminder: Due to compatibility reasons, this upgrade is complete guest password and a master password would be transferred, but please understand)
Optimization - perfect UI interface, adding more options
Optimization - In private mode, visitors can not open the Security Center
System Settings
Repair - resolved quickly with one hand, the problem does not exist display applications search
Repair - solved on the phone IMEI number SIM card status missing issue
Repair - to solve the problem if you're mode after opening not work properly
Repair - solved under fast boot state, charging not boot problems
Broadcasting station
Repair - to solve some cases, the program cache all operation failure problem
Notification Center
Repair - to solve some cases, flashlight can not open question
Repair - solved in some cases, stop long running problem appear in a multitasking application
Topic Center
Repair - to solve the English state, the theme central search interface layout irregular issue
Repair - solved in some cases, cause the phone Caton abnormal problems occur Topic Center
Repair - to solve the theme center, stop running problems downloading other users sharing wallpaper after
Repair - to solve the click history wallpaper unusual problems
Repair - solve appears to stop running after changing font problems
Repair - to solve the anomalies clicking topic I share a problem
Gallery
Repair - resolved after using the software to save the image, the picture can not find a problem in the album
Repair - solved in some cases, stop running problems click on the album is set
Lenovo Contacts
Repair - resolved in the English state, set the contact picture is not the first letter capitalized issues
Repair - to solve the problem of information recipients background color and text color conflict
Repair - solved in some cases, for a long time can not open the contact problem
Repair - can not solve the bright screen problem after call
Party applications
Repair - to solve the Postal Savings Bank, Agricultural Bank of mobile client can not properly use the
Repair - to solve the problem of incompatibility baby online
Click to expand...
Click to collapse
In the following Source of this changelog you will also find a little video about it in Chinese and I guess here you learn [HowTo] download the ROM.
I don't own a K3 Note, I am just reading because I am interested. But I hope this could help anybody.
MerenQue said:
I hope that this is the right thread to post that there is a new Dev-ROM made by Lenovo:
Source: http://www.vibeui.com/vibeui/rom?key=k3 note
Changelog: (Google translation)
In the Source you will find a little video about it in Chinese and I guess here you learn [HowTo] download the ROM.
I don't own a K3 Note, I am just reading because I am interested. But I hope this could help anybody.
Click to expand...
Click to collapse
Please don't make posts like this, i already know a new 1530 dev rom is out.
Thank you for your understanding.
If you would like to help me, tell me something i don't know via PM. The link you posted to learn how to download is the link to the tutorial how to use the OTA apk and switch from ST to Dev versions.
This thread has a Q&A thread, use it.
BTW here's the modem/baseband of the new 1530 dev: https://drive.google.com/open?id=0B5oTMOqjH0_TckpURFZPZ0xPVnM
I will post all the modems from all the versions in the OP asap.
Here's the link with all the ST/Dev versions to date and to the OTA apk: http://bbs.lenovo.com/forum.php?mod=viewthread&fid=921&tid=557109
{
"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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Nexus 7. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port.Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 2 parts you need to install:
MultiROM (multirom.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (recovery.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code
MultiROM - https://github.com/nkk71/multirom
Modified TWRP - https://github.com/nkk71/Team-Win-Recovery-Project
XDA:DevDB Information
MultiROM, ROM for the Xiaomi Mi 3
Contributors
vasishath
Source Code: https://github.com/nkk71/multirom
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Beta Release Date: 2017-03-27
Created 2017-03-16
Last Updated 2017-11-18
Download links:
https://www.androidfilehost.com/?w=files&flid=161749
Reserved
Latest Build: 19-Mar-2018
https://www.androidfilehost.com/?fid=746010030569962739
Supports MIUIv5 on the old partitions?
Where are saved the new systems?
The application from Google Play doesn't work.
thank you very much
my device os cyanogenmod 13 .working 6.0.1 system?
Working great Mi4Lte
Primary AICP secondary MIUI.EU
Just request If Recovery suport aroma will great to update primary costume rom
Thanks
does it work with otg?
I have Mi4 (cancro) with MIUI 8 (rooted) and app says : This is unsupported device (cancro)!..
Tr0NiX123 said:
I have Mi4 (cancro) with MIUI 8 (rooted) and app says : This is unsupported device (cancro)!..
Click to expand...
Click to collapse
Doesnt need the apps u can manage from recovery, select boot from start booting
Nicdeeee!!!!!
ubuntu touch os support mi3?
Haggiskop said:
ubuntu touch os support mi3?
Click to expand...
Click to collapse
No, it's not ported (yet), and noone seems to be interested in porting it.
annas_muslih said:
does it work with otg?
Click to expand...
Click to collapse
No, it doesn't. It was mentioned in the old thread, and for some reasons they forgot to add it here.
Haggiskop said:
my device os cyanogenmod 13 .working 6.0.1 system?
Click to expand...
Click to collapse
Yes
SnajperKRS said:
Supports MIUIv5 on the old partitions?
Where are saved the new systems?
The application from Google Play doesn't work.
Click to expand...
Click to collapse
It should afaik.
The new systems are saved at /data/media/0/multirom.
The app is not supported, just flash the TWRP from here and flash the multirom zip, it's not complicated
Working perfect on my Mi4w. Thx guys
Sent from my MI 4W using XDA-Developers Legacy app
Can this all be installed via twrp? Without using fastboot or anything?
sinz0000 said:
Can this all be installed via twrp? Without using fastboot or anything?
Click to expand...
Click to collapse
I have flashed the latest TWRP from my PC via fastboot, but you can flash it directly from TWRP or using flashify. The MultiROM you can also flash from TWRP like any other zip file. The single ROMs must be flashed from TWRP. Read post #1. Everything is described there.
Sent from my MI 4W using XDA-Developers Legacy app
ydd0ras said:
I have flashed the latest TWRP from my PC via fastboot, but you can flash it directly from TWRP or using flashify. The MultiROM you can also flash from TWRP like any other zip file. The single ROMs must be flashed from TWRP. Read post #1. Everything is described there.
Click to expand...
Click to collapse
Where can I get the patched kernel? It says in the first post that list of patched kernel is mentioned in the second post but the kernels arent mentioned
sinz0000 said:
Where can I get the patched kernel? It says in the first post that list of patched kernel is mentioned in the second post but the kernels arent mentioned
Click to expand...
Click to collapse
Multirom now works without any kexec kernel patch. I am using the no_kexec option, because I am coming from the previous version!
OP needs some changes
* you do not need app to install multirom. Just flash mutirom twrp and flash zip u will be fine.
* No kernel patch is needed. It works without kexec support
* Installing rom to USB otg doesnt work yet
{
"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:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What is Ubuntu Touch?
Ubuntu Touch is the touch-friendly mobile version of Ubuntu.
This operating system is developed and maintained by UBports: An international community of passionate volunteers.
This means Ubuntu Touch is 100% community driven and independent.
What is Halium?
Halium is the collaborative project to unify the Hardware Abstraction Layer for projects which run GNU/Linux on mobile devices with pre-installed Android.
How it is a GSI?
First of all, I should mention ubports GSI definition is different from android, but both are generic.
ubports root file system was always generic and works for most cases, but devs were porting halium system image to add device-specific (HALs and configs) support to ubports Android container.
But after project treble which introduced in android 8, all device-specific parts of android system image moved to vendor partition and we can use "Generic system images" over one vendor partition.
In halium version 9, we use this adventure and have a totally generic system image + root file system.
Requirements:
The only Requirement of booting this GSI is having Halium patched kernel.
Keep in mind having android 9 firmware installed on the device as GSI base is mandatory (GSI can be used on android 8.0 and 8.1 vendors but experimental and not supported yet)
How to install?
1. Boot TWRP and FORMAT data
2. Flash vendor image and halium-boot.img (Halium-boot.img confirmed working on DRG and PL2, B2N needs testing)
3. Flash GSI installer zip
4. Reboot
Note: if the device is stuck on the splash screen on boot, simply force reboot using the power/volume button combo meant for your device
Download:
GSI - built by @mrcyjanek (download ONLY target.zip)
Vendor images
Halium-boot
Whats suppose to work?
Bluetooth
Camera
Cellular Radio
Mobile Data
GPS
Graphics
Sensors
Sound
In-call Audio
Touch
Wifi
Vibration
Anbox
Media Playback
Known bugs?
Random (but rare) BSOD + reboots
no way to unlock using Fingerprint
Touching Fingerprint sensor can reduce media volume
oh and of course VoLTE
Camera (on B2N)
Supports:
Halium telegram group
UBports telegram group
UBports Porting telegram group
ErfanGSIs telegram group
Report Bugs:
Explain your bug in proper support telegram groups (from above)
Please don't ask about spoon-feeding or helping on building kernel or device specific builds.
Please don't ask about picking/reverting commits or any basic git commands.
bug reports without logs will be ignored
logs we need are: android logcat, kernel log, syslog
kernel log:
Code:
dmesg
syslog:
Code:
cat /var/log/syslog
logcat:
Code:
sudo -s
LD_LIBRARY_PATH=/system/lib64 lxc-attach -e -n android -- /system/bin/logcat
Taken with all due respect from Erfan's Thread
Appendix:
Anbox installation guide (by SevralTi on Github)
Code:
sudo mount -o rw,remount /
sudo apt update && sudo apt install -y anbox-ubuntu-touch android-tools-adb
mkdir ~/anbox-data
wget http://cdimage.ubports.com/anbox-images/android-armhf-64binder.img -O ~/anbox-data/android.img
touch ~/anbox-data/.enable
sudo chmod -R o+wrx /home/phablet/anbox-data/data
sudo start -q anbox-container
reboot, wait 2 minutes the reboot again
To symlink anbox files to system:
ln -s ~/anbox-data/data/media/0/Documents ~/Documents/android
ln -s ~/anbox-data/data/media/0/Pictures ~/Pictures/android
ln -s ~/anbox-data/data/media/0/Music ~/Music/android
ln -s ~/anbox-data/data/media/0/Movies ~/Videos/android
To make the QS panel occupy the whole screen, install UT Tweak Tool from the Open Store and increase device display scaling
Libertine containers can't be created from the settings app for now. To create a container, pass the command "TMPDIR=/tmp" in the terminal and follow documentation here
IMPORTANT
I take NO credit for the UBPorts community. All that I've simply done is patch our kernel to make it compatible.
Default password is "phablet" (without the quotes)
If you like my work, consider buying me a coffee and join our telegram groups
Cheers,
Sid
I would like to offer a special thanks to a bunch of people who've been with me through this ridiculous journey of mine:
@Sahil_Sonar - for all the help and advice he's given
@krushndayshmookh - for being a generally sweet guy and looking out for me
@CarbonGTR and @Nikhilkumar038 - for being solid friends and motivators throughout my struggle
@Catharsis007 - for being best boi
@ArcherTanu - for being extremely helpful
The UBPorts community
EVERYONE who's worked on the LOS sdm660 Kernel
and a special unnamed best friend who helped me power through the last couple of months.
Cheers,
Sid
Wonderful Work!! GBU!!
Pru
Updated #1 with a new GSI link that doesn't have the reduced storage bug
Awesome work!!! (though I can't try it out--I have a PL2)
Vedanth Padmaraman said:
Awesome work!!! (though I can't try it out--I have a PL2)
Click to expand...
Click to collapse
You can! Our kernel sources are unified and known to work on all 3 devices, DRG, PL2, and B2N
I've listed the bugs specific to DRG only because I own only a DRG, but in theory, you should be able to flash this on PL2 or B2N as well
Ok! Installing it soon
It works on the PL2, encountered nothing broken so far :good:. I received an SMS, downloaded some stuff, etc (but haven't tried calling yet). Once in while it does hang with a black screen while booting, but simply holding Vol. up + Power to force-restart does the trick, like mentioned in the OP. Set up whatsapp successfully on Anbox, but graphics on any anbox app are jerky and laggy at times, in a manner similar to that of the anbox installation on my Linux Mint, so this doesn't seem to be an issue pertaining to this GSI/Halium port. Still, would be nice to have an improvement
Updated kernel to fix media playback. Download from link in OP
Oh looks like really interesting. I'm downloading now. I'll test this for a few days. Question: It isn't Android totally. It's Ubuntu yes? Does it meant that other OS's can be ported as well like HarmonyOs? If that's true how it is can be ported.
SamandaR1112 said:
Oh looks like really interesting. I'm downloading now. I'll test this for a few days. Question: It isn't Android totally. It's Ubuntu yes? Does it meant that other OS's can be ported as well like HarmonyOs? If that's true how it is can be ported.
Click to expand...
Click to collapse
It isn't Android, it isn't exactly Ubuntu Desktop either. Canonical was working on Ubuntu Touch/Ubuntu Phone until 2017, and after they dropped the project, the UBports community was born and carried it forward. I'm not sure about HarmonyOS
#1 updated with halium-boot.img (confirmed working on DRG and PL2, B2N needs testing), new flashing method added
Which flashing method is prefered? Anybody who can tell a little on how it is in use? (Does it feel snappy or any lags)
Just about to flash to my B2N. The file B2N####-vendor.img needs to be set to a partition. "Select partition to flash image". I'm guessing boot or system, but honestly I have no idea. help?
---------- Post added at 11:43 AM ---------- Previous post was at 11:32 AM ----------
So.. I'm not exactly known for my patience.. Using method 1 I flashed the vendor image to system image, and boot image to boot partition. then changed to zip and flashed gsi. Twrp prompted me to install official twrp app, I was curious to see if it would work so I chose to do so. Then reboot turned me into a bootloop...
n00bDroid said:
Just about to flash to my B2N. The file B2N####-vendor.img needs to be set to a partition. "Select partition to flash image". I'm guessing boot or system, but honestly I have no idea. help?
---------- Post added at 11:43 AM ---------- Previous post was at 11:32 AM ----------
So.. I'm not exactly known for my patience.. Using method 1 I flashed the vendor image to system image, and boot image to boot partition. then changed to zip and flashed gsi. Twrp prompted me to install official twrp app, I was curious to see if it would work so I chose to do so. Then reboot turned me into a bootloop...
Click to expand...
Click to collapse
Code:
fastboot flash vendor <B2N####-vendor.img>
fastboot flash boot halium-boot.img # NOT B2N-0-354H-00WW-boot.img
Let the keyword "vendor" in <B2N####-vendor.img> serve as a reminder that it is meant to be flashed to the vendor partition.
Vedanth Padmaraman said:
Code:
fastboot flash vendor <B2N####-vendor.img>
fastboot flash boot halium-boot.img # NOT B2N-0-354H-00WW-boot.img
Let the keyword "vendor" in <B2N####-vendor.img> serve as a reminder that it is meant to be flashed to the vendor partition.
Click to expand...
Click to collapse
Immidiately after my post I made the same realization that vendor.img = vendor partition. So I did that, and it still didn't work.. But then again, I actually flashed B2N-0-354H-00WW-boot.img because I hadn't seen the halium-boot
So I went again. Now according to recipe. Then reboot system..I've been stuck on the "AndroidOne" logo for 15 minutes....after a forced reboot I see the Ubuntu Touch logo!!! thank you!
Camera isn't working. Any tips?
i did not thank you @Sid127 ! That's done !
Sorry for the recent inactivity
n00bDroid said:
Camera isn't working. Any tips?
Click to expand...
Click to collapse
I notice you're on B2N... System logs would be helpful from when you're trying to use the camera. That'd be the dmesg. Without that, I can't be of much help.
{
"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:
/*
* Your warranty is now void.
*
* Syberia Team not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications.
*/
Read the whole OP! Be respectful to each other and don't ask for ETAs, it's considered as being rude!
Syberia Project (aka Syberia OS) is a custom ROM for Xiaomi MI A3 that implements various features. This project was designed by our "Syberia Team" from scratch based on AOSP source code with some CAF fixes and improvements. Our team: @DennySPB, @blinoff82, @alexxxdev. Also many thanks to our designers @rlshukhov and @a18h for logos, wallpapers and bootanimations.
If you like our work you can buy us a cup of coffee or a glass of beer
Here
Code:
Monet
VoLTE, VoWiFi
LineageOS LiveDisplay
MicroG support
Pocket Judge
Call recording
Statusbar items switches
Three finger swipe to screenshot
Extended powermenu
...Settings and features will be gradually added.
SyberiaOS ROM Download
Recovery Download
Magisk Download
First time clean installation:
Code:
- Unlocked bootloader is required!
- You must have installed FW11 based ROM.
1 - Boot your device into fastboot mode:
adb reboot bootloader (or power off and power on again
while pressing Power + Vol Down)
2 - Flash Syberia recovery via fastboot
fastboot flash boot <name of the file>
3 - Reboot to recovery
4 - Perform factory reset (formatting data is important)
5 - Here you have 2 choices to install rom
1) Install > Sideload from ADB
on PC open terminal and type - adb sideload <rom zip name>
2) Install > install from sdcard or OTG
Just copy rom to the sdcard or OTG and install from it.
6 - Reboot to system, wait until rom booted, then reboot
in recovery again.
7 - Now you can install other zips (gapps, magisk etc) if needed by
using the methods described in the 5'th line of guide.
8 - If you flashed gapps, factory reset once more is a Must!
Updating:
Code:
1. Reboot into recovery
2. Here you have 2 choices to install rom
1) Install > Sideload from ADB
on PC open terminal and type - adb sideload <rom zip name>
2) Install > install from sdcard or OTG
Just copy rom to the sdcard or OTG and install from it.
3. Reboot to system
Code:
- You tell me only with logcat (screenshots)
Attention! We are not responsible for the operability of your device if you use third-party kernel, Xposed Framework or unverified Magisk modules.
Official website
Syberia Project Github
Syberia Project Gerrit
Device Source
Kernel Source
Official Telegram Group
Announcements Telegram Group
Development Telegram Group
Device Support Group
Code:
- LineageOS
- AOSPA (aka Paranoid Android)
- Nitrogen Project
- Benzo Rom
Update 11/07/2022
Changelog:
Fixed GPS logspam after caf update.
Updated GPS blobs to a12.
Updated GPS stack to LA.UM.9.11.r1-05600-NICOBAR.QSSI12.0
Ported DolbyAtmos from MOTO G PRO.
Implemented VPN tethering support.
Fixed QS clock size and placement.
Bring back "old" style QS brightness slider (temporary, until new style is fixed).
Spoiler: Archive
Update 30/06/2022
Changelog:
Removed mic boost.
VoiP changes.
Added keylayout for wired headphones.
Again increased haptics a bit.
Dropping prebuilt camera stack and building OSS camera stack.
Reworked Syberia UI Style.
Notes:
This build contains big changes for UI, so to avoid issues "clean flash" recommended
Update 01/06/2022
Changelog:
Implemented UDFPS dim layer (no brightness flicker)
Another VOiP fixes.
Added custom UDFPS animations and icons.
Added missing FM radio.
Increased haptics strength a bit.
Improved UDFPS scanning speed.
Update 17/04/2022
Changelog:
Improved boot time for ~3sec.
Fixed some system errors from log spam.
Added new NTP servers for faster Location.
Improved GPS stability and accuracy.
Enabled LiveDisplay HAL for picture adjustment.
Improved UDFPS callback delay’s.
Lowered size of UDFPS scan circle-point (theoretically this change should increase scanning speed but requires a good finger scan)
Imported from stock Health HAL (fixes charging calculations)
Upstreamed kernel to 4.14.275
Selinux Enforcing
Update 28/09/2021
Changelog:
Initial Build
Switched to ICE FBE encryption
Vendor updated to CAF LA.UM.9.11.r1-04500-NICOBAR.0 (except camera, audio, gps and DRM)
Switched to AOSP BT impl
Bugs:
Some modes in MIUI camera are not working
Reserved
This is fantastic!
But no matter what I do I can't install even core gapps. I flash them via adb sideload, perform a factory reset and nothing.. I feel like I've tried everything. There's no problem with Magisk tho. Can you please include some gapps in the rom?
Amazing news! Official ROM and latest Android version!
Hopefully the permissive SELinux can be sorted out with enough logs, but still, very nice work so far.
Does anyone can help me about the recovery via fastboot installation? I mean is there need to change slot e.t.c... And after recoverie's flashing, how we reboot to recovery, via a simple fastboot command?Thanks.
jeff.rey said:
This is fantastic!
But no matter what I do I can't install even core gapps. I flash them via adb sideload, perform a factory reset and nothing.. I feel like I've tried everything. There's no problem with Magisk tho. Can you please include some gapps in the rom?
Click to expand...
Click to collapse
Yeah, a12 not so fast at gapps bringup, we have limited chose to BitGapps, Nikgapps or FlameGapps, and Nikgapps with FlameGapps have some issues while flashing it on some devices (already reported to the dev), and only BitGapps works fine, but there are only Minimal package.
However i created a modified Nikgapps(stock) package - download
papafan said:
Does anyone can help me about the recovery via fastboot installation? I mean is there need to change slot e.t.c... And after recoverie's flashing, how we reboot to recovery, via a simple fastboot command?Thanks.
Click to expand...
Click to collapse
Generally speaking, IMHO doesn't matter how you got into recovery be it by command or power+vol+
maluus said:
Generally speaking, IMHO doesn't matter how you got into recovery be it by command or power+vol
Click to expand...
Click to collapse
And the slots? Is there any need to change them during flashing?
papafan said:
And the slots? Is there any need to change them during flashing?
Click to expand...
Click to collapse
When you flash something over fastboot you are to manage slots. When you do by recovery it manages slots. So up to flashing the recovery you'll manage slots. Afterwards flashes are done by recovery. Since recovery changes slots when you flash rom or update. Both slots should have the same firmware level (e.g. android 11 firmware.) If you have incompatible firmware on other slot it may cause problems on next update or full flash. IMHO op should explain a bit more about slot management. The same process is known to cause unwanted problems before. You can check the lineageos 18.1 oss thread for it.
Magicxavi said:
Update 28/09/2021
Changelog:
* Initial Build
* Switched to ICE FBE encryption
* Vendor updated to CAF LA.UM.9.11.r1-04500-NICOBAR.0 (except camera, audio, gps and DRM)
* Switched to AOSP BT impl
Bugs:
* Some modes in MIUI camera are not working
* Selinux Permissive
Click to expand...
Click to collapse
Hi,
Is it possible to safely install this ROM from android 10 stock EU version? (or, must I already be under A11 and in this case what should I do?)
I'm still stuck on A10 and the September 2020 security patch on my French version of the Mi A3
Sorry I'm a beginner
I think you must first update to a11. Do factory reset on your a10 first.
NikBos said:
I think you must first update to a11. Do factory reset on your a10 first.
Click to expand...
Click to collapse
Problem is that I still do not have the possibility to do OTA to A11...
In France we are literally blocked on A10 and the September 2020 security patch...
Then you can flash it with mi flash.
NikBos said:
Then you can flash it with mi flash.
Click to expand...
Click to collapse
I don't understand what to do in order not to lose my data, I would just like to update.
If I want to install the update without fear I have to make a backup. OK
To make a full backup I need TWRP. OK
To install TWRP to be able to make my backup and not lose any data I have to root my device with magisk. OK
If I root my device with magisk it makes me wipe all my data...
Hobbi1 said:
I don't understand what to do in order not to lose my data, I would just like to update.
If I want to install the update without fear I have to make a backup. OK
To make a full backup I need TWRP. OK
To install TWRP to be able to make my backup and not lose any data I have to root my device with magisk. OK
If I root my device with magisk it makes me wipe all my data...
Click to expand...
Click to collapse
If I were you I wouldn't rely on twrp for backup. Because once you update to A11 you ll have problem with twrp hence restoring it. On the other hand even if you are able to restore it somehow, probably you would end up with a bootloop anyway. Because when android version changes, data partition backup of other versions won't be compatible with newer one. I suggest you to have per app backup within os.
New update is out!
New update is out!
everything working fine, new icons and animations for udfps are pretty good and now it recognizes really fast. one thing i noticed is that the screen flicks when unlocking with figngerprint but just a little bit, its not something that really bothers as before. updating was fine without even needing to make a backup. anyways ty for, basically, the best rom for mi a3, if it wasnt that, i think we all would have already changed it. keep up the good work!
I just did the installation and the rom is fantastic!
Leaving Miui..
Everything seems to work very well.
Congratulations to those involved!!
Sorry for my english, I'm from Brazil
{
"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:
#include <std_disclaimer.h>
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Githup repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
Installation Instructions:
Backup your data and see the next post below
Recommended TWRP Image:
twrp-3.7.0_9-0-kuntao.img
ROM Download Links:
Google Drive | SourceForge
Recommended Google Apps Package:
NikGapps-core-13
NikGapps-SetupWizard
NikGapps-AndroidAuto
Root Access:
Magisk v25.2
Source Code:
https://github.com/LineageOS
ROM Firmware Required:
Any version of stock 6.0. Recommended P2a42_S251_171107_ROW
Acknowledgements:
Thanks to all Lineage OS developers
Special thanks to @Astridxx & @XiaoAk for the device tree sources and to @Astridxx for (once again) helping me out
Important Notes:
As you can see from my profile, I'm not an experienced developer. I've made some builds as a considerable amount of users showed interest in having their devices updated with latest LineageOS code. Therefore, my main objective here is to bring the latest Android security patches to kuntao making monthly builds.
To be clear, I'm more in a situation of "user became builder" than of "ROM developer". Please, understand this.
Long live to our beloved kuntao!
XDAevDB Information
[ROM][13][UNOFFICIAL] LineageOS 20 for Lenovo P2
Contributors
@Astridxx ,@XiaoAk
ROM OS Version: 13.x
ROM Kernel: Linux 3.18.x
Based On: LineageOS
Version Information
Status: Stable
Created 2023-03-05
Last Updated 2023-04-20
Installation Instructions
Remember, making a backup of your data before proceeding is recommended
If you are coming from Stock ROM, please refer first to the instructions below:
Install LineageOS on kuntao
If you are coming from any version of LOS18.1 or LOS19.1 or from any ROM that isn't android 13 based, you must perform a clean flash:
0- Make a backup (optional, but recommended)
1- Reboot to recovery
2- Format data (will delete all your data!)
3- Reboot to recovery again
4- Wipe > Advanced Wipe:
- Dalvik
- System
- Vendor
- Data
- Cache
- Internal Storage (optional, but recommended)
5- Flash ROM ZIP, Gapps, Gapps add-ons, Magisk add-on, etc
6- Reboot to system
7- Wait until it boots for the first time (may take some minutes)
8- If Magisk is missing after finishing the setup wizard, please reboot to system
Update Instructions
For updating from one of my builds to another (aka dirty flashing), please do the following:
1- Download ROM ZIP and copy it to the phone
2- Reboot to recovery
3- Flash ROM ZIP
4- Clean cache
5- Reboot to system
Known Issues
- Storage encryption is broken ( FDE was deprecated in a13 )
- Network traffic monitoring ( 4.9 kernel required for this )
- GPU monitoring ( 4.9 kernel required for this )
ROM Doesn't Boot After Flashing
Make sure you formatted /data partition (see installation instructions step 2)
SafetyNet Status Fix Instructions
1- Make sure Magisk was properly installed
2- Open the Magisk App
3- Open App settings (wheel on the top right side of the screen)
4- Enable "Zygisk"
5- Enable "DenyList"
6- Open "Configure DenyList"
6.1- On "Google Play services": Enable "com.google.android.gms" & "com.google.android.gms.unstable"
6.2- On "Google Play Store": Enable "com.android.vending"
7- Click on the back arrow (on top left)
8- Reboot your system
9- Test again (now it should pass)
ROM Change logs
Code:
03/05/2023
- Initial release
03/30/2023
- Fetch latest Device Tree
-- Sepolicy:
--- Address sensor hal denials
--- Address launcher3 denials
--- Allow some apps to access debuggable prop
-- rootdir:
--- Create STSensorHAL folder on data
--- Restore iio sensor device6 on boot
--- Add cpuset for the camera daemon
-- overlays:
--- Disable IMS features for Turkiye networks
--- Enable voWIFI support
-- prop:
--- Disable Bluetooth APCF Extended features
--- Enable ro.hwui.render_ahead and set it to 20 frames
-- Enable selinux ignore never allow flag
-- Don't force enable ims features
-- Remove aptX(HD) encoder shared libs
-- vendorsetup.sh: Add Trebuchet patch
- Update LOS components
-- Manifest:
--- Sync x86_64 webview prebuilts again
--- March 2023 Quarterly Platform Release and Security update
--- gs101 March 2023 Quarterly Platform Release and Security update
-- Update zlib source
- Sync latest LOS sources
- Update platform to android-13.0.0_r35
- Merge March security patch
04/20/2023
- Fetch latest Device Tree:
-- Set default livedisplay mode to 0
-- vendorsetup.sh: Add DeskClock patch
-- trebuchet:
--- Make overview scrim transparent again
--- Kill haptics in recents
-- nfc: Fix Mifare Classic reading
-- sepolicy:
--- Silence suspend_control_service neverallow denial
--- Silence tracingproxy_service neverallow denial
--- Silence fsck_untrusted neverallow denial
--- Allow system_app to access storaged via IPC
-- overlay: Allow gms to access persistent data partition
-- props:
--- Silence ResourcesCompat spam
--- Remove hwui skia atrace properties
--- Disable virtual displays writeback
-- Revert "sepolicy: Allow some apps to access debuggable prop"
- Sync latest LOS sources:
-- lineage: Track the FMRadio App and dependencies
-- Move Trebuchet to default.xml
-- overlay:
--- Disable immersive mode confirmation
--- Move default status bar height to no-rro
-- soong: Bring bootloader_message_offset back
-- envsetup: aospremote: Take .gitupstream into account
- Update platform to android-13.0.0_r41
- Merge April security patch
ROM Screenshots
Attached below.
Great work! Will test it when I have time, been waiting for this..
Hi all. I read these P2 forums for long time, but never participated. I love our P2 phone, riding a P2 since the release date and never changed. Now I got a message from my bank that the android version is too outdated to use their banking app, and they want me to switch to a newer OS. I could have ditched the P2, but couldn't. Therefore....easiest solution was to buy a second one xD I will test on the backup unit some of the roms available here, probably starting from the roms of @leo_97 . I need a stable daily driver, thus when I find something that works for me I will freeze it there for some time. But, in the meantime, I can help out with testing, starting from mid April onwards thus, feel free to contact me, and I will be a bit more active (and not passive) here in XDA for the coming months.
Cheers to all, and thanks @leo_97 , @Astridxx, @XiaoAk (and @mikeioannina for all the past efforts on P2!).
Hi
I just tested it on a P2 for a few hours and it works great! Thanks!
Is there any way to get full device encryption to work?
If I understand correctly, someone can access the phone's files even if you have a pin or password as it is now.
MKbis said:
But, in the meantime, I can help out with testing, starting from mid April onwards thus, feel free to contact me, and I will be a bit more active (and not passive) here in XDA for the coming months.
Click to expand...
Click to collapse
I'll PM you right away.
Draywen said:
Hi
I just tested it on a P2 for a few hours and it works great! Thanks!
Is there any way to get full device encryption to work?
If I understand correctly, someone can access the phone's files even if you have a pin or password as it is now.
Click to expand...
Click to collapse
You are welcome
So, IFAIK we don't have a way to make FDE work on A13 ROMs, A13 moved to FBE (File Based Encryption) which is not supported by 3.18.x kernel and we don't have rn a patch available that could enable it on our kernel version.
Regarding data access, I believe so. Without storage encryption, booting into recovery will already give access to the files. IIRC to this date encryption is fully working only on A11-based ROMs and maybe on some A12 ones.
Okay, so I'm stuck in a boot loop. I flashed the ROM from the link above but the phone won't start up. I just get the Lineage booting screen with the circle moving right to left. I've left it for 15 minutes just in case the first boot was slow but nothing else happens. I've tried to restore my original backup which was Lineage 17.1. It seemed to work, no errors from TWRP but now i just get the Lenovo screen and then it boots to fastboot mode. I flashed Lineage 20 for a second time but the same happened. I tried a different backup from August last year, again it just boots to fastboot.
Any ideas?
Cheers, Si.
EDIT: I've just noticed that I missed out step 3, reboot to recovery between Data wipe and flash ROM.
Now it boots no problem.
Cheers, Simon.
EDIT AGAIN: I still can't revert to either of my previous backups of Lineage 17.1. I would really like to be able to do this. Can anyone suggest why it will only boot to fastboot mode after a seemingly successful restore?
Thank you,
Simon.
@simes303
Don't know what the problem is, but I'd flash stock via fastboot. Then reinstall TWRP and restore LOS.
When things go wrong it's better to start from scratch rather than tinkering around and doing temporary fixes.
how is the battry life anyone?
eried1 said:
@simes303
Don't know what the problem is, but I'd flash stock via fastboot. Then reinstall TWRP and restore LOS.
When things go wrong it's better to start from scratch rather than tinkering around and doing temporary fixes.
Click to expand...
Click to collapse
Hi,
How is this different from flashing stock with TWRP?
Cheers, Si.
Used briefly but battery life seems worse, its like draining. Using 12L Lineage os and its way better.
mahmutpekkara said:
Used briefly but battery life seems worse, its like draining. Using 12L Lineage os and its way better.
Click to expand...
Click to collapse
how long does it last
laggy_boy said:
how long does it last
Click to expand...
Click to collapse
Didn't test much but its way waay noticable, you wouldn't want to use when you see the difference (didn't differ with or without gapps)
btw thx to all devs, using lineage os a12.1 and its good on battery
Battery life for me is considerably better than the Lineage 17.1 that I was using before, no question. I'd estimate almost twice the duration. I'm very happy with this ROM, thanks to all involved in developing it.
Simon.
I've actually just bought a brand new 64 Gb Lenovo P2 pretty cheap from eBay and I will definitely be flashing this Rom onto it.
Thanks again,
Simon.
Hi,
Does this ROM have USB OTG support? I can't get the phone to connect to either my external SSD drive or my bicycle helmet camera since I flashed this ROM. Both these things connected via OTG cable to my phone when I was running Lineage 17.1 and they also connect to the new P2 that I bought recently that still has stock OS. I've tried three OTG checker apps which all state that my phone is OTG compatible.
Thanks, Simon.
March 30th 2023 Release
Changelog:
- Fetch latest Device Tree sources
- Update LOS components webview & zlib
- Sync latest LOS source
- Merge March security patch
- Many more changes
Full change log available on the bottom of this post
Download URLs: GDrive | SF
Enjoy!
simes303 said:
Hi,
Does this ROM have USB OTG support? I can't get the phone to connect to either my external SSD drive or my bicycle helmet camera since I flashed this ROM. Both these things connected via OTG cable to my phone when I was running Lineage 17.1 and they also connect to the new P2 that I bought recently that still has stock OS. I've tried three OTG checker apps which all state that my phone is OTG compatible.
Thanks, Simon.
Click to expand...
Click to collapse
Hello Simon,
Yes, it does have OTG support. IFAIK it should work correctly with both FAT32 and NTFS partition types on external storage devices.