Related
My English is very poor
http://www.miui.com/thread-1297535-1-1.html
- Based on Meizu forum qwerrazxs bottom package patchrom made available
- Supported phone models for the M030, M031, M032
- Recommended end package for the flyme 2.1.3
- Basically reached the level of everyday use, recommended updates
- Outgoing recent task approach: setting - button, and then according to their own preferences
note! Brush the first time, please make a backup
1 double clear brush back official flyme 2.1.3
2, upgrade the baseband MX baseband (V02.1201.01-248)
3, Flyme firmware must be root (Settings - login account - More - Open System permissions)
4, download MIUI ROM, on the sd card root directory
5, download MX Brush Kit miui recovery (mx2 mx generic). Install Open and grant it root privileges.
6, point reboot bootloader mode
7, the first double clear, and then put the brush directly rom, Meizu's brush with the same way.
http://pan.baidu.com/share/link?shareid=331361021&uk=1997143330
thanks for sharing.
its weird to find no reply in this thread.
Hey all, FYI the latest version of MIUI fo Meizu MX (M030, M031, M032) may be found here:
[Meizu MX] [合作开发组] MIUI V5 for Meizu MX_3.11.8 by helinchun (4.1.x JB)
I had success installing it from a prerooted Flyme 2.1.x ROM (3.0.39-oversea kernel). The package only modifies the /system and /data partitions, leaving the bootloader, kernel & recovery still intact. It means the device is still perfectly capable of reflashing an official update.zip, although I don't believe Meizu will ever release a newer one beyond the 2.4.1 "test firmware".
- MIUI has a built-in superuser management UI, you don't need to install your version of su+superuser/supersu
- Some applications are .CN specific. I recommend slipstreaming Google Play (vending) and a standard keyboard such as TouchPal X / LatinIme in the zip package (you may want to look at other MIUI V5 ROMs in the forum for examples)
MIUI Installation for Meizu MX:
0- ALL IMPORTANT DATA BACKED UP AND SECURED IN A SAFE PLACE. your current rom is rooted (HK, or CN with Flyme open system privileges), with RW access to /system. Copy your MIUI zip package to /sdcard/
1- Install RecoveryInstaller.apk, open it and grant it elevated privileges when requested
2- click first button with some chinese text to install files to /system (no other partition is altered)
3- click second button with some chinese text to complete & restart phone. After reboot you should land in the MIUI recovery program for MX and MX2
4- It is not touch-enabled, use Vol+/Vol- to navigate, Back/Menu to Cancel/OK
5- Factory Reset + Wipe Cache + Wipe Data
6- Install from ZIP on sdcard (not update.zip), let it operate for a while
7- After install, go up/back into "Power" menu and restart phone
8- Phone will remain on the MIUI logo for a long time on the first run (generating cache, I suppose). LEAVE IT ALONE, DO NOT INTERRUPT IT. It shall last 5 minutes or so.
9- ???
10- Profit!
Notes:
- You may continue to use the normal Meizu recovery mode (VolUp+Power) to flash a stock update or radio firmware.
- I cannot provide support for everyday use of the phone, as mine's been given away to another person.
- Apparently you don't need a Xiaomi account to use the ROM.
Unrelated remark:
- Android 4.4 (KK/KLP) has minimal specs of 512 MB RAM, thanks to improvements in Linux Kernel 3.8 - yet Samsung hasn't released a 4412 BSP with 3.8 AFAIK
TwoPointZero said:
Hey all, FYI the latest version of MIUI fo Meizu MX (M030, M031, M032) may be found here:
[Meizu MX] [合作开发组] MIUI V5 for Meizu MX_3.11.8 by helinchun (4.1.x JB)
Click to expand...
Click to collapse
Hey thanks! Seems to be updated weekly too!
Too bad the transfer speeds from China are horrendous (any chance for a mirror?). I'm on 1 gbps and still max out at a measly 30 kB/s. Oh well, i'll just wait for a few hours.
Hi man, thank you so much for your installation steps! Just installed it from flyme 2.1.3 .. I think the post says to install from 2.4.1, but I'm not sure.. Anyway, seems to be working ok. Do you think it will be an issue in the future?
---------- Post added at 04:16 AM ---------- Previous post was at 03:52 AM ----------
Long pressing the home button doesnt bring up anything.. solution?
dagbro said:
Hey thanks! Seems to be updated weekly too!
Too bad the transfer speeds from China are horrendous (any chance for a mirror?). I'm on 1 gbps and still max out at a measly 30 kB/s. Oh well, i'll just wait for a few hours.
Click to expand...
Click to collapse
I got distracted and never actually got to installing it, so now I'm back almost a year later.
AND IT WORKS!
MIUI V5 is still being updated each week for the MX, and the latest release works great. It made my phone feel alive again.
ALL the files i used:
RecoveryInstaller.apk: From OP of this thread.
Flyme OS 2.1.3 downgrade : http://meizufans.eu/forum/thread-m03x-flyme-2-1-3-official
Latest MIUI from official site: http://en.miui.com/download-188.html
Then just follow TwoPointZero's instructions.
If you want Gapps as well: http://en.miui.com/thread-3998-1-1.html
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
FEATURED ON THE PORTAL
Thanks @Doug Lynch for the mention!
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
TWRP 3.0.2-0 for LAVA Pixelv1, Tool/Utility for the OEM Cross Device Development
Contributors
MSF Jarvis, varun.chitre15
Version Information
Status: Stable
Created 2016-04-06
Last Updated 2016-04-20
Reserved
Credits
varun.chitre15 for his base trees
@DHARMESH17 for being a great tester
@arvinquilao for making me jealous!
Reserved
I would like you to recognize some misunderstanding.
On the official website of TWRP are 2 different Android One devices listed.
The first is "sprout" which stand for MTK powered devices
The other entry is called "2nd generation MTK (seedmtk)" which is simply wrong and might mislead some people. 2nd gen devices are powered by Snapdragon 410 CPUs.
You may want to change the listing on your website for a better understanding.
body150165 said:
I would like you to recognize some misunderstanding.
On the official website of TWRP are 2 different Android One devices listed.
The first is "sprout" which stand for MTK powered devices
The other entry is called "2nd generation MTK (seedmtk)" which is simply wrong and might mislead some people. 2nd gen devices are powered by Snapdragon 410 CPUs.
You may want to change the listing on your website for a better understanding.
Click to expand...
Click to collapse
@body150165, you might wanna do some homework now. Second gen devices are victim of fragmentation, causing two different variants to exist. The first, the Snapdragon 410-powered seed devices, have TWRP from @arvinquilao, and he's also running CM13 builds. The second one, the MT6582-powered Infinix Hot One and Lava Pixel v1, are classified as sprout by their manufacturers, which would have caused the confusion it somehow triggered in you. All said and done, as the only developer actively working towards CM13 and TWRP for the device, I took the liberty of renaming the device.
@body150165 thanks for bringing up your concern. Official TWRP build for the Snapdragon variant is already available via dl.twrp.me/seed, but the website is yet to be updated (probably in the next couple of days). As soon as it's updated I'll make a new thread here for the Snapdragon variant.
Second Partitiin (SD partition) working??
Sent from my SM-J500F using XDA-Developers mobile app
Nur_Alom said:
Second Partitiin (SD partition) working??
Sent from my SM-J500F using XDA-Developers mobile app
Click to expand...
Click to collapse
Who needs it?
I ported this TWRP 3.0.0-2 for my smartphone (Ulefone Paris, MTK6753), but I have 2 problems....I wrote here, because I want know if is a porting bug or also in others terminal there are the same bug:
1) I created in past a backup of my rom with TWRP 2.8.7.0 Version, and the 3.0.0-2 version isn't able to see my backup when I go on "restore" and choose my MicroSD, but if I navigate with file explorer, I can find it.
2) Battery bug: Always show me 50% of charge, no more, no less...
Are this common bugs, or porting bugs??? How can I fix it??
Thanks!!!
cuvetto said:
I ported this TWRP 3.0.0-2 for my smartphone (Ulefone Paris, MTK6753), but I have 2 problems....I wrote here, because I want know if is a porting bug or also in others terminal there are the same bug:
1) I created in past a backup of my rom with TWRP 2.8.7.0 Version, and the 3.0.0-2 version isn't able to see my backup when I go on "restore" and choose my MicroSD, but if I navigate with file explorer, I can find it.
2) Battery bug: Always show me 50% of charge, no more, no less...
Are this common bugs, or porting bugs??? How can I fix it??
Thanks!!!
Click to expand...
Click to collapse
I'll get back to you in a while after checking these. And this is TWRP 3.0.2-0, not 3.0.0-2.
I would like to know what steps have you taken to port it to determine whether I can source build for the device and make it official.
cuvetto said:
I ported this TWRP 3.0.0-2 for my smartphone (Ulefone Paris, MTK6753), but I have 2 problems....I wrote here, because I want know if is a porting bug or also in others terminal there are the same bug:
1) I created in past a backup of my rom with TWRP 2.8.7.0 Version, and the 3.0.0-2 version isn't able to see my backup when I go on "restore" and choose my MicroSD, but if I navigate with file explorer, I can find it.
2) Battery bug: Always show me 50% of charge, no more, no less...
Are this common bugs, or porting bugs??? How can I fix it??
Thanks!!!
Click to expand...
Click to collapse
@cuvetto : No, these bugs don't exist in my build. Tested as working fine by @DHARMESH17.
Will these work on 1st generation android one device i mean sprout 4 ?
DarkHeart Z said:
Will these work on 1st generation android one device i mean sprout 4 ?
Click to expand...
Click to collapse
It will not, sadly. TWRP seems to have not updated sprout devices for ages, so I'll run you guys a 3.0.2-0 build in some time and post it here.
MSF Jarvis said:
It will not, sadly. TWRP seems to have not updated sprout devices for ages, so I'll run you guys a 3.0.2-0 build in some time and post it here.
Click to expand...
Click to collapse
Then I am waiting for that
Bootloop
My device is lava pixel v1. After flashing this recovery from fastboot my device goes into bootloop. It always start with recovery and then says failed to mount /data etc and again reboots.
ashokvishnoi1994 said:
My device is lava pixel v1. After flashing this recovery from fastboot my device goes into bootloop. It always start with recovery and then says failed to mount /data etc and again reboots.
Click to expand...
Click to collapse
After fastboot flash recovery twrp-3.0.2-0-seedmtk.img, what exactly did you do?
You need to press both Volume Up + Power for about 15 seconds till device reboots back into bootloader mode and then go to recovery mode and open it. This has been tested as working. What steps did you take?
MSF Jarvis said:
@body150165, you might wanna do some homework now. Second gen devices are victim of fragmentation, causing two different variants to exist. The first, the Snapdragon 410-powered seed devices, have TWRP from @arvinquilao, and he's also running CM13 builds. The second one, the MT6582-powered Infinix Hot One and Lava Pixel v1, are classified as sprout by their manufacturers, which would have caused the confusion it somehow triggered in you. All said and done, as the only developer actively working towards CM13 and TWRP for the device, I took the liberty of renaming the device.
Click to expand...
Click to collapse
It should be Infinix Hot 2. Also I tried flashing via flashify and the recovery does not boot on Hot 2.
anarchtic said:
It should be Infinix Hot 2. Also I tried flashing via flashify and the recovery does not boot on Hot 2.
Click to expand...
Click to collapse
That's bad.... Can you provide me with your boot image? I will have to end up deunifying this recovery if it isn't booting :/
I would recommend that you also try a fastboot flash to see if it's a flashify thing.
MSF Jarvis said:
@body150165, you might wanna do some homework now. Second gen devices are victim of fragmentation, causing two different variants to exist. The first, the Snapdragon 410-powered seed devices, have TWRP from @arvinquilao, and he's also running CM13 builds. The second one, the MT6582-powered Infinix Hot One and Lava Pixel v1, are classified as sprout by their manufacturers, which would have caused the confusion it somehow triggered in you. All said and done, as the only developer actively working towards CM13 and TWRP for the device, I took the liberty of renaming the device.
Click to expand...
Click to collapse
MSF Jarvis said:
That's bad.... Can you provide me with your boot image? I will have to end up deunifying this recovery if it isn't booting :/
I would recommend that you also try a fastboot flash to see if it's a flashify thing.
Click to expand...
Click to collapse
I will when I get home, I am at work now which is why I used Flashify. Did you test using Hot 2?
anarchtic said:
I will when I get home, I am at work now which is why I used Flashify. Did you test using Hot 2?
Click to expand...
Click to collapse
Don't own one. I believed it would boot, just like it does for Android One first gen devices(One recovery for all devices)
Hi !
All i'm doing is sharing this piece of work of DarkJoker360 ! ALL Credits are on the main Thread .... I'M JUST SHARING !!!
Bugs :
Need further testing , please report your bugs in the original thread
- Audio output switching does not work ( example if you listen to music via speaker and plug in headphones , it does not switch to that output unless you change the rington stat ( from silent or vibrating to Ringing )
- Regular Magisk does not work , Please install magisk from original thread FAQ
What you need :
- A Hi6250 Device ( Check here : https://openkirin.net/devices/ )
- Fully Unlocked Device ( Bootloader AND FRP )
- Firmware Required : EMUI 8.X
- TWRP Recovery
- NotePad++
Download on original Thread Here
Before Flashing this rom !!!
We need to Modifiy the updater script
if you are on stock rom this shouldn't be a problem ( didn't test it ) but anyways , if we flash it right away there is a good chance to get an ERROR 7 Device not compatible or something on these lines , What we have to do is the remove the Assert checking on the updater-script :
-Please Check all the requirments and steps before executing this step , what we are doing is removing device verification and the zip will install no matter what on ANY Device which Can Result on a Hardbrick!
1/ Open The downloaded zip and navigate to Meta-INF/COM/google/android/updater-script
DO NOT OPEN IT USING NOTEPAD , Instead Use NotePad ++ Or some other text editing tool that does not change space Encoding
2/ After that you should see on first line "assert(get prop .....);" Remove all this line till the semi colon and save the file
3/ Copy rom to SD card !
4/ Reboot to recovery , Wipe Data / dalvik / cache
5/ Flash this rom and it should boot up flawlessly
6/ After rom Boots up , Go to setting / Developer options / Default USB configuration and chose file transfer so that your device would be recognized by your PC and other media hubs
GAPPS :
Here (ARM-64 Version 9.0 ) Pico is recommended : Google APPS
what difference from this than openkirin builds??
optionalmgrr.la said:
what difference from this than openkirin builds??
Click to expand...
Click to collapse
Openkirin provides stock EMUI camera with their build, and probably more stable ROMs
I really hope open kirin update their lineageos rom....
optionalmgrr.la said:
I really hope open kirin update their lineageos rom....
Click to expand...
Click to collapse
If they fix it patch something, they'll post it.
PalakMi said:
Openkirin provides stock EMUI camera with their build, and probably more stable ROMs
Click to expand...
Click to collapse
Not necessarily , as far as my experience this rom is as stable as the one provided by openkirin, i have to admit that i did not test their omnirom enough to judge .
I found this ROM to be much more stable and usable than the latest OmniROM from OpenKirin. I installed the Stock variant of OpenGApps and it ran flawlessly, even the Pixel Launcher. Nice work!
Google already announced a very early Android R Developer Preview I for Pixel and Essential devices. But no need to worry because our beloved device which is MI 8 SE a.k.a Sirus is able to try Android R with almost no major bugs All you need to do is just drinking a cup of coffee plus your big effort to read the whole steps that I'll provide to y'all bellow.
CAUTION: I AIN'T RESPONSIBLE IN ANYTHING IF SOMETHING GOES WRONG WITH YOUR PHONE :good:
Bugs ATM:
- Hotspot is completely dead (GSI SIDE ISSUE)
- Some apps on Play Store do not appear such as Telegram, Instagram, and so on
- And many other minor bugs that do not affect our daily use
Files:
- PBRP as recovery
MOD EDIT: Telegram link removed, please read the STICKY!
- Pixel port GSI by Erfan
- Fix brightness issue
- Fix notch
- Fix system UI freeze and lag as hell
- GMS
Steps:
1. I assume that you already installed PBRP. If yes, reboot to recovery first by pressing & holding the volume up and power off buttons together and if it's vibrate, take it off!
2. Format data then reboot to recovery.
3. Clear all except system, USB OTG, & SD Card.
4. Go to install section, then flash the vendor above. Please wait 'till the process is done.
5. After that, go to mount section, then checklist all of them.
6. Next, go to install section and press install image then choose the GSI file by Erfan then flash as system image.
7. Flash fix system UI crash and lag file and fix play store issue file.
8. Then move the fix notch file to /system/system/product/overlay by using TWRP file manager.
9. Remove EuiccGoogle on /system/system/product/priv-app.
10. Finally, reboot to system and thanks me later :fingers-crossed:
NOTES:
- TO HAVE ROOT ACCESS, PLEASE FLASH MOD EDIT: Telegram link removed, please read the STICKY! THROUGH RECOVERY. THIS ZIP FILE INCLUDES SU, PHH-SU, and SUPERUSER.APK.
- AFTER FIRST BOOT, YOU CAN ALSO FLASH MOD EDIT: Telegram link removed, please read the STICKY! BUT REMEMBER AFTER FIRST BOOT! YOU CAN ALSO IMPLEMENT F2FS (WHAT'S ACTUALLY F2FS?) IN INSTALLING THIS GSI BY FOLLOWINGMOD EDIT: Telegram link removed, please read the STICKY! !
- TO FIX SOME WEIRD ISSUES, YOU MUST INSTALL GMS MANUALLY OR BY USING ADB FASTBOOT TOOL.
- TO FIX BRIGHTNESS ISSUE, INSTALL THE APK THAT YOU'VE ALREADY DOWNLOADED AS USUAL.
Special thanks to:
Erfan who made Android R GSI
Carl who created fix system UI freeze and lag
Ramdani Akbar who found a way to fix brightness issue atm
Agung who found a way to fix sim card pop up issue
Mo9 for suggesting me the best vendor
And last but not least, special thanks to all my beloved Sirius Tester Group who always help me anytime
Seems the Step13 is Remove Euiccgoogle, because I don't found the Euiccpixel,
a05haiji28 said:
Seems the Step13 is Remove Euiccgoogle, because I don't found the Euiccpixel,
Click to expand...
Click to collapse
Thanks for reporting to me. I already edited in OP :good:
Thread updated to Android Developer Preview II And here are the screenshoots below:
Thread closed on OP's request.
strongst
Forum Moderator