DISCONTINUED
Sorry .. due to limited time I have stopped all my AOSP projects.
Pls find the last AOSP downloads here ..
https://androidfilehost.com/?w=files&flid=289293
Thanks for understanding ..
It's AOSP time for Pixel C ...
Android Pie ..
AOSP_9.0.0_r31_PQ2A.190205.001_dragon-ota-eng.followmsi.zip
Known issues:
- Encryption seems not work - and has not been tested. -> Pls do not encrypt your data partition yet.
- Keymaster -> If you set Pattern, PIN or Password the Screen unlock may not work correctly.
Workaround for Pattern: On fresh boot you will need to wait a bit longer before you enter credentials.
The waiting time is required on fresh boot only, the following unlocks are working normally.
- The ROM does contain it's own vendor.img ! (If you go back to Oreo, pls reinstall stock vendor.img)
And big thanks to @NYCHitman1 (Dirty Unicorn) !
Without his work the Android Pie project would not have been possible !
Oreo ..
AOSP_8.1.0_r60_OPM8.190105.002_dragon-ota-eng.followmsi.zip
This ROM will require stock vendor.img - it's not part of the ROM installer !
You will find a copy inside the download folder.
Or just extract yourself .. https://developers.google.com/android/images#ryu
Pls install latest stock vendor.img via TWRP !
Installation:
1. Boot into TWRP (latest available version)
2. Wipe system, cache, dalvik and data partitions ! ( If you have encrypted /data partition - pls "format" /data via TWRP first ! )
3. Install latest ROM
4. Install Gapps (arm64) (optional)
5. install Magisk.zip (optional)
6. Reboot into system ..
- Please install Magisk.zip and/or SuperSu.zip yourself.
- If you face any strange issues, pls do a factory reset via TWRP first.
TWRP:
https://forum.xda-developers.com/pixel-c/development/twrp-3-0-2-0v16-t3400503
SOURCES:
https://github.com/followmsi/manifests/tree/dragon-aosp-pie
https://github.com/followmsi/manifests/tree/dragon-aosp-oreo
https://github.com/followmsi/manifests/tree/dragon-aosp-nougat
https://android.googlesource.com/
DOWNLOAD:
https://androidfilehost.com/?w=files&flid=289293
https://drive.google.com/drive/folders/0By6p5AdQfavBUTZmNWJoaU1iazg
Enjoy
Thank you for your work.
Its been a while since Pure Nexus was updated so will try this one when I'll get a free evening.
TheNamesJohn said:
Thank you for your work.
Its been a while since Pure Nexus was updated so will try this one when I'll get a free evening.
Click to expand...
Click to collapse
Pls give ist a try .. and report your feelings
Cheers
followmsi said:
Pls give ist a try .. and report your feelings
Cheers
Click to expand...
Click to collapse
Hello!!!
I want to try this. I´m on TWRP 3.1.0-0 (but I see newer versions in your OneDrive repo) and I have made a backup of my previous ROM.
I see that your ZIP it´s an OTA I must install it over...
Thanks in advance for everything.
Yes, the newer versions are for file based encryption (fbe) testing.
Pls install 3.1.0-1 .. Will work the same as the current one and maybe fbe is working too
No, pls wipe system the first time.
If you install update later on you can keep system.
Pls report if you like the ROM ..
Cheers
followmsi said:
Yes, the newer versions are for file based encryption (fbe) testing.
Pls install 3.1.0-1 .. Will work the same as the current one and maybe fbe is working too
No, pls wipe system the first time.
If you install update later on you can keep system.
Pls report if you like the ROM ..
Cheers
Click to expand...
Click to collapse
After update TWRP to 3.1.0-1 and make a factory reset I try to install your first zip and I get error 7 message. I´m missing something?
Thanks in advance.
Istvan_86 said:
After update TWRP to 3.1.0-1 and make a factory reset I try to install your first zip and I get error 7 message. I´m missing something?
Thanks in advance.
Click to expand...
Click to collapse
Wipe system is not included min factory reset
You need to do it manually .. Check system only and wipe.
Will be formated as ext4
Does it work for you ?
EDIT: .. We want to clean your system from all the stock google stuff .. And install AOSP only
Cheers
I am also getting an install error after manually wiping everything.
E3003: Can't install the package (Tue Mar 7 20:10:49 CET 2017) over newer build (Thur Mar 9 17:08:49 CET 2017)
Updater process ended with ERROR: 7
Error installing zip file /sdcard/AOSP_7.1.1_r24_N4F26T_dragon-ota-eng.followmsi.zip.
jeffyca said:
I am also getting an install error
E3003: Can't install the package (Tue Mar 7 20:10:49 CET 2017) over newer build (Thur Mar 9 17:08:49 CET 2017)
Updater process ended with ERROR: 7
Error installing zip file /sdcard/AOSP_7.1.1_r24_N4F26T_dragon-ota-eng.followmsi.zip.
Click to expand...
Click to collapse
What system do you have installed now ?
This "****ty" update script is checking your current build date ..Automatic google script.
Did you wipe system partition ?
We can remove this check manually .. if needed.
followmsi said:
What system do you have installed now ?
This "****ty" update script is checking your current build date ..Automatic google script.
Did you wipe system partition ?
We can remove this check manually .. if needed.
Click to expand...
Click to collapse
I manually wiped everything. Did not have a system installed. TWRP even yelled at me when i wanted to reboot to try again saying no OS was installed. I was coming from February image and an older TWRP before updating to the newest TWRP and trying this AOSP package before going to March image.
Strange indeed ...
Here is the relevant part ..
(!less_than_int(1488913849, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Tue Mar 7 20:10:49 CET 2017) over newer build (" + getprop("ro.build.date") + ").");
getprop("ro.product.device") == "dragon" || abort("E3004: This package is for "dragon" devices; this is a "" + getprop("ro.product.device") + "".");
ui_print("Target: Android/aosp_dragon/dragon:7.1.1/N4F26T/follow03072010:userdebug/test-keys");
Need to remove this and save the file and zip again ..
The script is the checking the date of the Recovery ))
Will remove this .. and make a new Upload ..
followmsi said:
What system do you have installed now ?
This "****ty" update script is checking your current build date ..Automatic google script.
Did you wipe system partition ?
We can remove this check manually .. if needed.
Click to expand...
Click to collapse
This is really funny ..
You are using already 3.1.0-1 from the download folder ... which is newer as the ROM ..
Look at the build date :
ro.bootimage.build.date=Thu Mar 9 17:08:49 CET 2017
Anyway ...
I already uploaded a new version .. same name !
Pls download again .. and install .. Thanks for your understanding !
The new update script looks like ..
Code:
getprop("ro.product.device") == "dragon" || abort("E3004: This package is for \"dragon\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: Android/aosp_dragon/dragon:7.1.1/N4F26T/follow03072010:userdebug/test-keys");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/700b0600.sdhci/by-name/APP", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/700b0600.sdhci/by-name/KERN-A");
show_progress(0.200000, 10);
set_progress(1.000000);
Sorry for this one
Will be fixed for the next month AOSP package ..
Cheers
followmsi said:
Wipe system is not included min factory reset
You need to do it manually .. Check system only and wipe.
Will be formated as ext4
Does it work for you ?
EDIT: .. We want to clean your system from all the stock google stuff .. And install AOSP only
Cheers
Click to expand...
Click to collapse
Sorry a hard day in the office and I go directly to bed.
I wipe everything and system is in ext4 but error 7 stiill stops the flashing process. Also my usb otg stop working in 3.1.0-1 and I must go back to 3.1.0-0 to restore my backup that iis stored iin a usb.
Istvan_86 said:
Sorry a hard day in the office and I go directly to bed.
I wipe everything and system is in ext4 but error 7 stiill stops the flashing process. Also my usb otg stop working in 3.1.0-1 and I must go back to 3.1.0-0 to restore my backup that iis stored iin a usb.
Click to expand...
Click to collapse
Pls re-download new OTA version .. same name - from the one drive folder again.
Removed the error 7 check now .. The OTA is older as the recovery you are using
Pls stay with TWRP 3.1.0-0 for now.
followmsi said:
Pls re-download new OTA version .. same name - from the one drive folder again.
Removed the error 7 check now .. The OTA is older as the recovery you are using
Pls stay with TWRP 3.1.0-0 for now.
Click to expand...
Click to collapse
Ok I´m back on TWRP 3.1.0-0 and downloading the new AOSP ZIP. I reinstall Pure Nexus just for testing and it installs and boots without problems with TWRP 3.1.0-0. So now with a booting rom installed what must I wipe before install the new zip?
Thanks for all your help.
Istvan_86 said:
Ok I´m back on TWRP 3.1.0-0 and downloading the new AOSP ZIP. I reinstall Pure Nexus just for testing and it installs and boots without problems with TWRP 3.1.0-0. So now with a booting rom installed what must I wipe before install the new zip?
Thanks for all your help.
Click to expand...
Click to collapse
Pls format system first .. to remove the pure nexus stuff ...
Have made dedicated version of the vendor.img too.
AOSP_Update.ZIP_PixelC_Ryu_vendor_N4F26T.zip
Oherwise you will get warning message at system start ..
All the small issues ... but now it's looking good.
I have moved as well ... I will stay on AOSP now .. no BETAs anymore !
Once they release the 7.1.2 code we will make a new AOSP
No problems on 3.1.0-1 in terms of USB.OTG ..
Just doing USB-OTG restore of my old data partition and will merge it "dirty" into AOSP now ..
All the google apps will cry
Takes 1-2 hours fixing stuff ... but not installing 150 apps and tons of other settings from scratch .. etc.
AOSP is coming
Cheers
followmsi said:
Pls format system first .. to remove the pure nexus stuff ...
Have made dedicated version of the vendor.img too.
AOSP_Update.ZIP_PixelC_Ryu_vendor_N4F26T.zip
Oherwise you will get warning message at system start ..
All the small issues ... but now it's looking good.
I have moved as well ... I will stay on AOSP now .. no BETAs anymore !
Once they release the 7.1.2 code we will make a new AOSP
No problems on 3.1.0-1 in terms of USB.OTG ..
Just doing USB-OTG restore of my old data partition and will merge it "dirty" into AOSP now ..
All the google apps will cry
Takes 1-2 hours fixing stuff ... but not installing 150 apps and tons of other settings from scratch .. etc.
AOSP is coming
Cheers
Click to expand...
Click to collapse
I repeat all the steps includiing downloading again all the files but when I end the process and try to reboot to boot in the rom TWRP says that OS isn´t installed.... We are missing something?
Istvan_86 said:
I repeat all the steps includiing downloading again all the files but when I end the process and try to reboot to boot in the rom TWRP says that OS isn´t installed.... We are missing something?
Click to expand...
Click to collapse
Just reboot .. ignore the message.
Sometimes TWRP has an issues if system is mounted before you install the zips.
After you have formatted system, just manually unmount system in mount menu.
I am running AOSP myself .. works like a charm !
Using Tapatalk from the old backup .. all was working directly.
But not all apps .. maybe 15 of 140 apps have to be reinstalled .. if you want to keep the settings, just install apk version over the existing installation .. works fine too
Fully burning AOSP
followmsi said:
Just reboot .. ignore the message.
Sometimes TWRP has an issues if system is mounted before you install the zips.
After you have formatted system, just manually unmount system in mount menu.
I am running AOSP myself .. works like a charm !
Click to expand...
Click to collapse
Ok, I install again pure nexus and boot it. After that I reboot in TWRP and wipe dallvik + cache + system and when this finish TWRP says "Unable to mount storage" Is this normal and I can now unmount system in order to flash the AOSP zip and the vendor zip + gapps and reboot?
Thanks.
Related
First of all i would like to thank ->Tsing Yi qingyi @http://weibo.com/1048297887 for his effort to make this possible!!
As some fellas request....I'm Just giving a detailed guide for the process to have Dual-System{Dual_Boot} in our little dragon @rmani :laugh:
DOWNLOADS:
1.HM1S-Sysrec.zip: http://pan.baidu.com/s/1jGzfP3o
2.M1S-System-Menu1.3-test.zip: http://pan.baidu.com/s/1qWDN5u8
if want it in a simpler way download 3
3.Mokke + Miui.zip: http://pan.baidu.com/s/1sjCyI3z
:good: @bhushan2k
MIRROR Link: https://drive.google.com/folderview...NrYmkzLTN3WmlONEczVnlzajg0emo3ZHM&usp=sharing
WARNING!! : Installation of Dual System is Complecated, include data loss and may brick your devices and i'm not responsible for any kind of Loss or Failure..!!
CAUTION!! : During this Process, Your Phone gets Factory Reset and all internal memory gets wiped!! Make a Backup of all internal data as well as a nandroid to extrnal sd!!
***//For Users coming from MIUI rom and want to have MIUI on one of the Systems continue from step 1-2 and read NOTE and in step 3 tick the checkbox promting special!
STEP1:
Flash HM 1S-Sysrec.zip...[after flashing, recovery gets rebooted].......In this Process Phones Intrernal Memory gets formatted and current ROM gets Factory Reset!
STEP2:
Flash HM 1S-System-Menu1.3-test.zip...Select English->Press Next->Accept and Press Next->Enter the function->Install and uninstall->Install the dual system.....This installs Dual-System and gets rebooted to recovery, meaning dual system got installed!!
**NOTE 1 : If you wish to install mokee+MIUI which was provided #3 in download section.....You can flash that mokee+MIUI.zip here, without proceeding further...and reboot!!
**NOTE 2 : Now we have two System partitions installed and we are on system1, which already have the previous Rom residual and System2 is Void!!
**NOTE 3 : If you want to have a fresh Installation of AOSP Rom on System1, you can directly flash a AOSP rom of your choice! or continue with previous rom!
STEP3:
Now that we have a Rom in System1 [MIUI or a AOSP]....so we need to install system switching software in it....
Flash HM 1S-System-Menu1.3-test.zip, Follow the prompts to enter the main menu -> enter the function -> Install switching software -> System I-> Next [check special for MIUI users]...and reboot system!!
STEP4:
After the completion of boot process you will see a system changing app....open the app ->give root permissions and the phone gets rebooted and gets stuck at mi logo indicating we are in System2....Now Enter Reovery (Powr+VolUp same time)
STEP5:
Flash a ROM of your choice...."and dont reboot!"....after flashing rom again flash HM 1S-System-Menu1.3-test.zip, Follow the prompts to enter the main menu -> enter the function -> Install switching software -> System 2-> Next....now reboot !!!.. which will take you to ROM installed in System 2 ....
STEP6:
After the completion of boot process, now that you are in System2, will see a system changing app as well ....open the app ->give root permissions and you will be able to switch to the other system/ROM........
////**Manual System switching process: **///
Flash HM 1S-System-Menu1.3-test.zip Follow the prompts to enter the main menu -> enter the function ->System Switching -> and select a System of your choice and proceed and Finally reboot !!!
***///Wanna change rom or try a new ROM keeping the other still///***
Stay on the System on which you want to try a new ROM....Reboot to recovery...
Flash HM 1S-System-Menu-Test1.3.zip and Follow the prompts to enter the main menu -> enter the function ->clear data->
Continuing which will wipes and factory Resets the current Rom....After proceeding further enter RECOVERY....
and Flash the ROM u wanna Try...and repeat #STEP5 and install switching software on new system!!(Hope U Understand)!!!
For reverting back...we need to flash Sysrec.zip once again and flash Sysmenu.zip and follow uninstall procedure...then everything will be normal...
...for further questions comment below...............Give :good: if useful!!!....
Happy Flashing!!!
If anything Goes wrong...How to revert Back ?
Sent From My Redmi
1.Does we need to follow a unbrick tutorial
To revert back OR just restore a backup
2.Should we install twrp and continue or
Continue with philz recovery
3. Can we access system partition of system 2 from system 1 and vise versa
Sent from my Redmi 1S using XDA Free mobile app
can we use rom??and can i install custom kernel for both roms??
as9333 said:
1.Does we need to follow a unbrick tutorial
To revert back OR just restore a backup
2.Should we install twrp and continue or
Continue with philz recovery
3. Can we access system partition of system 2 from system 1 and vise versa
Sent from my Redmi 1S using XDA Free mobile app
Click to expand...
Click to collapse
For reverting back...we need to flash Sysrec.zip once again and flash Sysmenu.zip and follow uninstall procedure...then everything will be normal...
2.cwm or twrp...u can try philz.. Dunno..
3.We can browse sys2 directories from sys1 & vice versa
how can i restore my data on my first rom? help me plz
chauhansonu104 said:
how can i restore my data on my first rom? help me plz
Click to expand...
Click to collapse
I don't think restoring nandroid data will work... Because....as u can see there are two two folders inside root/data/.......by restoring data from recovery will first wipes current root/data content and writes content from backup....so no dual-system!!! Hope you understand....tell me whether u have installed dual system? If so once see inside root/data /....u will get it!
sathyakaushik4 said:
can we use rom??and can i install custom kernel for both roms??
Click to expand...
Click to collapse
We can install gapps for system1 and system 2 separately....and can install custom kernels as well...!
very good tutorial.. thnx for this.. I tried on my own and couldnt manage.. will try again this time following ur simple steps..
Just a doubt if we install cm r18 and PAC ROM with custom kernel can we install kernel patch for both the ROMs
Will cm work
Can we boot into sys 2 within recovery
If sys 1 got bootloop
Sent from my Redmi 1S using XDA Free mobile app
Great, Thanks for info, will try after my exams, one again Thank You Very Much.
@as9333
i guess we can switch between system 1 & 2 from recovery itself.. just flash the zip and explore through its aroma installer and see theres that option to switch...
as9333 said:
Just a doubt if we install cm r18 and PAC ROM with custom kernel can we install kernel patch for both the ROMs
Will cm work
Can we boot into sys 2 within recovery
If sys 1 got bootloop
Sent from my Redmi 1S using XDA Free mobile app
Click to expand...
Click to collapse
Note 1: Two Roms will be installed with two separate system partitions....all u can do things like installing custom add-ons or patches either being on system1 or system 2..use switching software to switch between system partition 1or 2...
Note 2: U can switch to system of ur choice from recovery...by flashing HM1s-system-menu.zip...there u will c an option to switch system...hope u understand if u had read the procedure with a bit of pathence!
Thanx alot bro! now im running miui 6 and carbon rc6..
a small doubt.. in the dual boot system menu there are 2 options saying system change(install systemchange and direc system change or sumthing) whats the second one? what will it do?
had hard time downloading from chinese server... here is gdrive mirror link @pawanzZ
N-Gavin said:
Thanx alot bro! now im running miui 6 and carbon rc6..
a small doubt.. in the dual boot system menu there are 2 options saying system change(install systemchange and direc system change or sumthing) whats the second one? what will it do?
Click to expand...
Click to collapse
Read note2 of the above replied post...ur doubt will be clarified!!
bhushan2k said:
had hard time downloading from chinese server... here is gdrive mirror link @pawanzZ
Click to expand...
Click to collapse
Mk+miui is not mandatory to download!!!.... Remaining 2 are <30mb...any ways u made it easy ...tnx for mirror!!
internal storage
Thnx for the great tutorial
but i still have few question
First ,do external storage also wipe out?
Second ,are app installed in each rom are shared among them,includin data?
Hsmetric181 said:
Thnx for the great tutorial
but i still have few question
First ,do external storage also wipe out?
Second ,are app installed in each rom are shared among them,includin data?
Click to expand...
Click to collapse
figured it out myself,for everybody else
won't format external sd card
and apps will be installed separately
Maybe some mistakes in step 2. The dev recommended unmount system, data and cache before installed Dual-System (doesn't matter really). Some user may need install it twice to success for unknown factors. And as I know on earlier versions, after you installed Dual-System, both partitions are empty. You need to flash a rom to system 1. But I haven't try v1.3 yet so I don't know if anything changed.
The tutorial seems so long but it's very reasonable to proceed.
1. (unnecessary for the 1st time) recover your phone's status - flash sysrec.zip
2. install the dual-boot system - flash into aroma and choose the option
3. flash a rom to current (1st) system - flash it in recovery
4. (optional but recommended) install a switcher in the rom - install it in the aroma, caution the options, don't choose the wrong system
5. switch to system2 - switch directly in the aroma, or [ boot your phone to use the switcher app (after that plz press vol+ to enter recovery because system2 is empty now)]
6. flash another rom to current (2nd) system - just flash it in recovery, it will be in system2
7. (optional but recommended) install a switcher in the rom - install it in the aroma, caution the options, don't choose the wrong system
now you have dual system installed.
For changing between systems, use the switcher (if installed) or change in the aroma installer.
For replacing a rom, switch to the rom you unwanted, and reboot to recovery and flash the new one.
For clear data, don't use recovery,it will clear both. Use the aroma (change to the system you want to clear data and choose clear current).
For miui user, special for miui is actually for miui 6 because /system/app can't get root permission in miui 6.
For uninstall, do it in aroma and then flash sysrec.zip
@pawanzZ
{
"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"
}
LineageOS 19.1
Android 12
lineage-19.1-20230111-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- Camera is not working yet.
- SELinux is permissive.
- Our "old" Nivida codecs do have problems to play videos in Chrome-based browsers.
(Rename or remove /vendor/lib/libnvomx.so and reboot system to switch to
software video codecs.)
- Chrome browser starts slowly.
- As it looks like Widevine L1 has been revoked by end of August 2020.
- Maybe more issues ..
Installation:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions !
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (25.2)
6. Wipe CACHE and DAVLIK
7. Reboot into system
Enjoy 12
Android 11
lineage-18.1-20220216-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- SELinux is permissive.
- Our "old" Nivida codecs do have problems to play videos in Chrome-based browsers.
(Rename or remove /vendor/lib/libnvomx.so and reboot system to switch to
software video codecs.)
- Chrome browser starts slowly.
- Camera/Video may stops working after some time in use.
- As it looks like Widevine L1 has been revoked by end of August 2020.
Fresh Installation / Upgrade from any other ROM:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions ! (If you are encrypted, pls format DATA partition !)
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (21.x)
6. Wipe CACHE and DAVLIK
7. Reboot into system
Upgrade from previous lineage-18.x builds:
1. Boot into TWRP
2. Install ROM.zip
3. Re-Install Magisk 21.x
4. Wipe CACHE and DAVLIK
5. Reboot into system
Enjoy 11
Android 10
lineage-17.1-20201211-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- SELinux is permissive.
- Our "old" Nivida codecs do have problems to play videos in Chrome-based browsers.
(Rename or remove /vendor/lib/libnvomx.so and reboot system to switch to
software video codecs.)
- Camera/Video may stops working after some time in use.
- As it looks like Widevine L1 has been revoked by end of August 2020.
system-as-root (SAR)
For gapps installation issues and more information ..
Pls read first .. https://forum.xda-developers.com/showpost.php?p=80693701&postcount=1350
Fresh Installation / Upgrade from any other ROM:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions ! (If you are encrypted, pls format DATA partition !)
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (20.x+)
6. Wipe CACHE and DAVLIK
7. Reboot into system
Upgrade from previous lineage-17.1 builds:
1. Boot into TWRP
2. Install ROM.zip
3. Wipe CACHE and DAVLIK
4. Reboot into system
- The ROM does contain it's own vendor.img ! (If you go back to Oreo, pls reinstall stock vendor.img)
Enjoy TEN
Android Pie
lineage-16.0-20191017-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- Encryption seems not to work - and has not been tested. -> Pls do not encrypt your data partition yet !
- Keymaster -> If you set Pattern, PIN or Password the Screen unlock may not work correctly.
Workaround for Pattern: On fresh boot you will need to wait a bit longer before you enter credentials.
The waiting time is required on fresh boot only, the following unlocks are working normally.
In case of problems pls use Update.ZIP_TWRP_flashable_pattern_pin_remover_V2.zip to remove pattern/pin or password.
Installation:
1. Boot into TWRP (latest available version)
2. Wipe system, cache, dalvik and data partitions ! ( If you have encrypted /data partition - pls "format" /data via TWRP first ! )
3. Install lineage-16.0-201Yxxyy-UNOFFICIAL-dragon.zip
4. Install Opengapps
5. install Magisk.zip (tested with 18.x)
6. Reboot into system ..
- The ROM does contain it's own vendor.img ! (If you go back to Oreo, pls reinstall stock vendor.img)
And big thanks to @NYCHitman1 (Dirty Unicorn) !
Without his work the Android Pie project would not have been possible !
I have uploaded the last official Lineage Oreo build to androidfilehost.com ..
lineage-15.1-20200221-nightly-dragon-signed.zip - -> DISCONTINUED
SOURCES:
https://github.com/followmsi/manifests/tree/dragon-lineage-18.1
DOWNLOADS:
https://drive.google.com/drive/fold...oaU1iazg?resourcekey=0-4krcBcSF3tnMFvgcP4kMvw
https://androidfilehost.com/?w=files&flid=289293
Enjoy LineageOS on your Pixel C .. [/B]
RESERVED
Here you are ..
TWRP loop for me. Installs with no errors but won't boot into the os
I did a dirty (coming from AOSP 7.1.2) and then clean install. Haven't factory refreshed yet.
Tried wiping again and flashing back to aosp and having the same issue.
Any thoughts?
edit: now trying to pull some data off my tablet to do a full wipe, i dont NEED to do this, but would like to...but twrp wont recognize MTP on my system (win 10) ... problems problems today
minieod said:
TWRP loop for me. Installs with no errors but won't boot into the os
I did a dirty (coming from AOSP 7.1.2) and then clean install. Haven't factory refreshed yet.
Tried wiping again and flashing back to aosp and having the same issue.
Any thoughts?
edit: now trying to pull some data off my tablet to do a full wipe, i dont NEED to do this, but would like to...but twrp wont recognize MTP on my system (win 10) ... problems problems today
Click to expand...
Click to collapse
Did you format system ?
Pls do as first step.
If you boot loop install boot.img via fastboot.
No problems here.. it's quite fast !
Also dirty installation .. kept all my settings.
EDIT:
Mtp should work .. correct driver in Windows ?
We are using abd and mtp at the same time.
A Windows driver is on the share as well ..
Made a LineageOMS version as well ..
lineageOMS-14.1-20170418-UNOFFICIAL-dragon-followmsi.zip
Based on LineageOMS sources ...
https://github.com/LineageOMS
Enjoy
followmsi said:
Made a LineageOMS version as well ..
lineageOMS-14.1-20170418-UNOFFICIAL-dragon-followmsi.zip
Based on LineageOMS sources ...
https://github.com/LineageOMS
Enjoy [/QUOT
Is the nav bar laid out like stock
Click to expand...
Click to collapse
followmsi said:
Did you format system ?
Pls do as first step.
If you boot loop install boot.img via fastboot.
No problems here.. it's quite fast !
Also dirty installation .. kept all my settings.
EDIT:
Mtp should work .. correct driver in Windows ?
We are using abd and mtp at the same time.
A Windows driver is on the share as well ..
Click to expand...
Click to collapse
Hey follow
Yep did all of that. Formatted system, flashed boot.img, and no issues with mtp prior to the boot loops.
I went ahead and did a complete userdata reset and am sampling the O DP1 now ..I'm sure it'll work fine when (if) I come back to 7.x
Officialness
Thanks for building this. Hoping to try it out this weekend.
I'm hoping you intend to submit this build officially to LineageOS, so we continue to get updated builds. As you probably remember Cyanogen didn't accept the Pixel C. Hopefully with LineageOS things are better.
gaufres said:
Thanks for building this. Hoping to try it out this weekend.
I'm hoping you intend to submit this build officially to LineageOS, so we continue to get updated builds. As you probably remember Cyanogen didn't accept the Pixel C. Hopefully with LineageOS things are better.
Click to expand...
Click to collapse
You are not the first asking me this question ..
Here some more information ..
https://wiki.lineageos.org/submitting_device.html
Who is the maintainer ? .. me
- Changing vendor stuff .. monthly
- Applying kernel patches .. monthly
- Applying possible device tree patches and changes .. monthly
- Etc.
Here is the manifest for LOS ..
https://github.com/followmsi/manifests/tree/dragon-lineageos-cm-14.1
Also for the people who like to build their own verison
- As you may see we are removing 2 LOS repos today, due to build errors.
- This needs to be fixed on code level first - commited on LOS github.
- The stock google vendor.img needs to be integrated into the LOS Installer
Still not clear how this is done for "official" lineageos .. also from legal point of view.
Actually I need to get information here ... How is this done for other ROMs having a dedicated vendor.img ?
- The missing integrated kernel building was impemented a few minutes before
https://github.com/followmsi/androi...mmit/316a7e0e87b191bcf11b8de55778ddec83fac2f8
https://github.com/followmsi/android_kernel_tegra/commit/3e3e24c41db74693efc2fc74efaf6286b1c06013
You see there a few issues left ..
The ROM works perfectly but its not ready to be official yet.
Don't want to force and push a go live now .. No need to rush !
Hope you have a better understanding now ..
Cheers
Reuben_skelz92 said:
followmsi said:
Made a LineageOMS version as well ..
lineageOMS-14.1-20170418-UNOFFICIAL-dragon-followmsi.zip
Based on LineageOMS sources ...
https://github.com/LineageOMS
Enjoy [/QUOT
Is the nav bar laid out like stock
Click to expand...
Click to collapse
No !
The OMS version is the same like lineageOS but including OMS - to be ready to install substratum .. etc.
Made a version for Nexus 10 as well .. it seems to work fine.
Just have installed the ROM .. works fine - but did no special customizations or anything else.
Hope this helps ..
Click to expand...
Click to collapse
Debugging bootloop
followmsi said:
Did you format system ?
Pls do as first step.
If you boot loop install boot.img via fastboot.
Click to expand...
Click to collapse
Unfortunately this is also bootlooping for me. I've tried the steps above.
How can I help debug this? I was not able to use logcat. Does logcat work for you?
gaufres said:
Unfortunately this is also bootlooping for me. I've tried the steps above.
How can I help debug this? I was not able to use logcat. Does logcat work for you?
Click to expand...
Click to collapse
You did flash boot.img via fastboot ?
The ROM installation had no errors ?
What version of bootloader are you using .. .50 for 7.1.2 ?
Do you see the LOS logo (boot animation) when you boot-loop ?
Are you able to make a md5 hash ..Or similar to compare ?
File corrupt ?
Pls post a hash value to compare .. maybe onedrive is the problem.
Was not the first time a file was corrupted.
I am testing several ROMs and kernels in the last days .. no problems at all.
EDIT:
Which version of TWRP ?
EDIT2:
For your understanding.. logcat will start a short time after Android is booting.(boot animation)
But if you not pass the boot.img we have another issue. (Google logo)
Re: Debugging bootloop
followmsi said:
You did flash boot.img via fastboot ?
Click to expand...
Click to collapse
Yes. No errors.
followmsi said:
The ROM installation had no errors ?
Click to expand...
Click to collapse
None.
followmsi said:
What version of bootloader are you using .. .50 for 7.1.2 ?
Click to expand...
Click to collapse
I think so. Version 7900.50.0 from n2g47d.
followmsi said:
Do you see the LOS logo (boot animation) when you boot-loop ?
Click to expand...
Click to collapse
It doesn't get that far.
I see the unlocked bootloader warning. After thirty seconds it beeps, as expected. Then white "Google" text is then displayed for two or three seconds.
But after that it reboots into TWRP (blank screen, then unlocked bootloader warning, then beep, then white "Google" text, then TWRP).
followmsi said:
Are you able to make a md5 hash ..Or similar to compare ?
Click to expand...
Click to collapse
The update zip I'm installing from TWRP is lineage-14.1-20170417-UNOFFICIAL-dragon-followmsi.zip, which I downloaded from OneDrive. It has SHA256 hash
Code:
d124b4048f096317f593fa5dbf313ceaebbddd4352f0422276a86fd5f6707902
The boot.img I'm flashing with fastboot comes from the above zip. So it might be redundant for me to say the boot.img has SHA256 hash
Code:
cde8c7376d2d8d9d35ea5558473a669f91a27b0489f21b7a3cdb79af4a4ba931
followmsi said:
Pls post a hash value to compare .. maybe onedrive is the problem.
Was not the first time a file was corrupted.
Click to expand...
Click to collapse
I'm kinda hoping that is the problem, because otherwise this will be a pain to debug!
followmsi said:
I am testing several ROMs and kernels in the last days .. no problems at all.
Click to expand...
Click to collapse
Good. Weird.
followmsi said:
Which version of TWRP ?
Click to expand...
Click to collapse
Your build of 3.1.0-0.
followmsi said:
For your understanding.. logcat will start a short time after Android is booting.(boot animation)
But if you not pass the boot.img we have another issue. (Google logo)
Click to expand...
Click to collapse
Thanks for the explanation. So it might be boot.img given the boot sequence I described above?
I always get the TWRP bootloop if I boot before installing SuperSU. That happened with DU and with this.
I also had some issues with the setup wizard crashing. It was skipping the step of connecting wifi, and then it would crash when I tried to enter a Google account (which wouldn't have worked anyway without wifi.) I tried different gapps, same result. Finally I managed to swipe open settings and connect to wifi and now I'm set.
Now that I've got it running (OMS variant) it's great.
gaufres said:
Yes. No errors.
None.
I think so. Version 7900.50.0 from n2g47d.
It doesn't get that far.
I see the unlocked bootloader warning. After thirty seconds it beeps, as expected. Then white "Google" text is then displayed for two or three seconds.
But after that it reboots into TWRP (blank screen, then unlocked bootloader warning, then beep, then white "Google" text, then TWRP).
The update zip I'm installing from TWRP is lineage-14.1-20170417-UNOFFICIAL-dragon-followmsi.zip, which I downloaded from OneDrive. It has SHA256 hash
Code:
d124b4048f096317f593fa5dbf313ceaebbddd4352f0422276a86fd5f6707902
The boot.img I'm flashing with fastboot comes from the above zip. So it might be redundant for me to say the boot.img has SHA256 hash
Code:
cde8c7376d2d8d9d35ea5558473a669f91a27b0489f21b7a3cdb79af4a4ba931
I'm kinda hoping that is the problem, because otherwise this will be a pain to debug!
Good. Weird.
Your build of 3.1.0-0.
Thanks for the explanation. So it might be boot.img given the boot sequence I described above?
Click to expand...
Click to collapse
[HashChecker]
[File]/storage/emulated/0/download/lineage-14.1-20170417-UNOFFICIAL-dragon-followmsi.zip
[MD5]C79F1066186FF36C55643E264B3647E2
[SHA1]4DDD0A811FE22359D745335AA563023E95E808D3
[SHA256]D124B4048F096317F593FA5DBF313CEAEBBDDD4352F0422276A86FD5F6707902
At least the sha256 matches
Good bootloader
Good TWRP version ..
Do you install supersu at last step of your installation procedure ?
After you did install the ROM in TWRP, pls install supersu.zip (2.79 -sr3) as last step.
It will boot twice for the first time .. but then it should boot normally.
badwiring said:
I always get the TWRP bootloop if I boot before installing SuperSU. That happened with DU and with this.
I also had some issues with the setup wizard crashing. It was skipping the step of connecting wifi, and then it would crash when I tried to enter a Google account (which wouldn't have worked anyway without wifi.) I tried different gapps, same result. Finally I managed to swipe open settings and connect to wifi and now I'm set.
Now that I've got it running (OMS variant) it's great.
Click to expand...
Click to collapse
The SetupWizard is related to gapps .. the beans version seems to run perfectly.
Opengapps seems still to have issues on certain devices.
Will check supersu topic ..
Thanks for the feedback !
badwiring said:
I always get the TWRP bootloop if I boot before installing SuperSU.
Click to expand...
Click to collapse
followmsi said:
Do you install supersu at last step of your installation procedure ?
Click to expand...
Click to collapse
Thanks both. That's it.
No su: bootloops.
Lineage extras su: bootloops
SuperSU: boots OK
Magisk: boots OK
gaufres said:
Thanks both. That's it.
No su: bootloops.
Lineage extras su: bootloops
SuperSU: boots OK
Magisk: boots OK
Click to expand...
Click to collapse
Cool !
Found the issues as well ..
It's related to DM-verity .. even some config is missing.
Or the overwrite of build_fingerprint is related.
Need to investigate ..
Both supersu and magisk are removing the DM-verity checks in ramdisk.(boot.img)
As I always install supersu, I never realized.
Just compiling a new version .. changed the sources.
https://github.com/followmsi/androi...mmit/aae5804e75f4133ec82253cf6b2afbe39e46a56a
Removing DM-verity from fstab .. should solve this issue, also without supersu.
At later stage we can enable again, if it's working fine.
Thanks for your help testing ..
Cheers
New release ..
lineage-14.1-20170421-UNOFFICIAL-dragon-followmsi.zip
Changes:
- Integrated kernel compiling - using DU branch
- disabled DM-verity -> should fix proper booting even without supersu/magisk.
- General LineageOS changes -> fresh repo sync from today .. https://download.lineageos.org/
Installation:
1. Boot into TWRP
3. Install lineage-14.1-20170421-UNOFFICIAL-dragon-followmsi.zip
4. install SuperSU-v2.79-201612051815.zip (optional)
6. Reboot into system ..
- The ROM installer will keep your existing gapps installation.
- If you had SuperSu installed before you need to install it again - as we overwrite the boot.img completely.
A new OMS version will come later ..
Enjoy ..
I'm not the Author, the author is wzsx150 from LR.TEAM
WZSX’s TWRP is well-known as the Chinese version of TWRP due to the language default is in Chinese. However, you can switch to English within TWRP user settings it's easily. switched. You can follow the instructions on this link to change the language to English: https://miui.blog/any-devices/lr-tea...inese-english/
Xiaomi 8's LR.Team customized version of Twrp
Automatically decrypts data, Includes root functionality, clear the power-on password, multi-function restart.
Disclaimer: I have installed it and for me it works fine. However, it is not guaranteed to work for you especially if you currently have encryption. Use at your own risk
If you need help flashing TWRP : Follow instructions here: https://miui.blog/mi-8/flash-twrp-root-mi-8/
Downloads
Latest
Version for Miui 11 Android 10/Q : https://www.androidfilehost.com/?fid...26312261636230
MD5: 2f5f2e7dc8f32b5a999828c9370b7de2
Version for Miui 10 or 11 Android 9/P : https://www.androidfilehost.com/?fid...26312261636232
MD5: 4681f9bd6367f934218da71fd528e39b
Old Versions
TWRP-3.2.3.1-FireDance-Edition (English) ( img)
TWRP 3.2.3-1208 (English) ( zip - img )
TWRP 3.2.3-1110 (English) ( zip - img )
TWRP 3.2.3-1110 ( zip - fastboot - img )
TWRP 3.2.3-0918 (zip - fastboot - img)
TWRP 3.2.3-0908 (zip - fastboot - img)
TWRP 3.2.2-0703 (zip - fastboot - img)
TWRP 3.2.2-0611 (zip - fastboot - img)
TWRP 3.2.2-0609 (zip - fastboot - img)
Changelog (Google Translated)
2018.11.10 update Contents:
1. Update the new rom that supports the official Android 9.
2. Update and optimize some functions
3. Increase the option to restart after the automatic upgrade is completed. In the twrp setting, the default is automatic restart. Uncheck the box and you can not restart. After the automatic upgrade, some operations are performed to prevent twrp from being overwritten, etc.
4. Update the built-in root to magisk 17.1, and fix the problem that the module cannot be brushed. Other features are also updated and optimized
5. After the new version of the system root, restarting the system requires manual installation of the magisk app, the official system problem, this can only be so
. 6. If Kami may need the root system or remove the dm check operation.
7. Prevent the functions covered by the official rec: root system, signature boot, remove dm check, cancel forced encryption, etc.
2018.9.8 update:
1. Support the official Android 9.0 system, including automatic decryption data
2. About data decryption, this may not be particularly stable now, sometimes need to reboot into the system and then restart Twrp can be decrypted.
If the new version of twrp is not supported, you can try to use the old version of
2018.8.6 update:
1. Update twrp 3.2.3 source code
2. Built-in magisk16.7, temporarily build this version first
3. Optimize data decryption problem, fix some problems
4 Support the new version of miui10 data decryption
5. Decrypt the plaintext display input password, easy to check whether the password input is correct
6. Update to try to repair the decryption data scheme, set the lock screen password to the machine, enter twrp need to enter the lock screen Password, otherwise you cannot temporarily decrypt data.
7. After brushing in twrp, the first time you enter twrp may restart once. This is normal. If you restart repeatedly, or you can't decrypt data, please give me feedback on Weibo.
8. Regarding data decryption, this may not be particularly stable now. Sometimes you need to reboot into the system and restart into twrp to decrypt.
If the new version of twrp is not supported, you can try to use the old version of
Thanks. I was already using the EN version you posted in the Dogsly(that may be wrong) thread.
Great job
arifqur said:
Thanks. I was already using the EN version you posted in the Dogsly(that may be wrong) thread.
Great job
Click to expand...
Click to collapse
@gulp79 is to thank for the English version
mikefallen said:
@gulp79 is to thank for the English version
Click to expand...
Click to collapse
if you want to add to op, this is the img version of TWRP-3.2.3-1110-XIAOMI8-EN-wzsx150
(with a minor modifications of prop.default, and also with chinese language, in previous version chinese was removed, btw english is set as default).
https://mega.nz/#!MwQn3IgR!UmuuBk1OScPrHi_HUO1zA_Da0df3nexfrrWGEBGjJPg
gulp79 said:
if you want to add to op, this is the img version of TWRP-3.2.3-1110-XIAOMI8-EN-wzsx150
(with a minor modifications of prop.default, and also with chinese language, in previous version chinese was removed, btw english is set as default).
https://mega.nz/fm/M4oDgLxA
Click to expand...
Click to collapse
that link doesn't seem to work for me, just redirects to the home page of mega
mikefallen said:
that link doesn't seem to work for me, just redirects to the home page of mega
Click to expand...
Click to collapse
try this
https://mega.nz/#!MwQn3IgR!UmuuBk1OScPrHi_HUO1zA_Da0df3nexfrrWGEBGjJPg
gulp79 said:
try this
https://mega.nz/#!MwQn3IgR!UmuuBk1OScPrHi_HUO1zA_Da0df3nexfrrWGEBGjJPg
Click to expand...
Click to collapse
yup added to OP Thanks!
Help!!!
It works for mi 8 miui 10.0.3.0 global?, i cant figure out how install the eu rom, in the twrp show me only folders encrypted :C, somebody knows how ?
Looks like you will have to format Dara partition in recovery by typing yes
So, boot the img and then flash the zip for TWRP to stick permanently?
Can't use gapps Aroma installer using twrp .. any ideas ?
could this twrp support amora installer
could this twrp support amora installer?
On my MI 8, i restored a previous backup made with twrp, now the device does not accept my 4-digit password so I can't login to my phone!
please help!
cyaneo said:
On my MI 8, i restored a previous backup made with twrp, now the device does not accept my 4-digit password so I can't login to my phone!
please help!
Click to expand...
Click to collapse
in twrp go to file manager, data, system and delete locksettings file. reboot and you're good to go again
Hi!
Help me, please!
I can't exit from recovery mode on MI8
cyaneo said:
On my MI 8, i restored a previous backup made with twrp, now the device does not accept my 4-digit password so I can't login to my phone!
please help!
Click to expand...
Click to collapse
Go into recovery mode, format internal memory.
---------- Post added at 06:24 AM ---------- Previous post was at 06:22 AM ----------
Coolesha said:
Hi!
Help me, please!
I can't exit from recovery mode on MI8
Click to expand...
Click to collapse
You need to format your device.
bahuy2003 said:
Go into recovery mode, format internal memory.
Click to expand...
Click to collapse
ok, but doesn't this delete all my settings & personal files (aka reset to default)?
Thank you!
cyaneo said:
ok, but doesn't this delete all my settings & personal files (aka reset to default)?
Thank you!
Click to expand...
Click to collapse
If you device can't reboot, you can flash eu or global rom, format again and reboot system.
bahuy2003 said:
If you device can't reboot, you can flash eu or global rom, format again and reboot system.
Click to expand...
Click to collapse
Hu? never wrote it doesn't reboot etc. - It reboots, everything seems to be OK - I "just" can't login after restore a backup....
so, again: does "format internal memory" reset my phone, delete setting or personal files? If so, how does this solve the problem? After a fresh EU ROM install, everything works fine like a new install does.
cyaneo said:
Hu? never wrote it doesn't reboot etc. - It reboots, everything seems to be OK - I "just" can't login after restore a backup....
so, again: does "format internal memory" reset my phone, delete setting or personal files? If so, how does this solve the problem? After a fresh EU ROM install, everything works fine like a new install does.
Click to expand...
Click to collapse
Flash this zip in TWRP and your login password would be deleted, which by the way gets jumbled up after a restore.
Hi guys,
I'm about to sell my Mi 6 to upgrade to the K20 Pro and I would like to reinstall the latest MIUI 10 before giving my mobile away.
So as you read on the title I have the latest PE Pie CAF edition and I would like to be sure of all the steps to be done to install MIUI 10 without hassles. I have the latest TWRP 3.3.1-2
I have a Mac so the fastboot option is not my favourite one and I would prefer to use TWRP. I googled a bit and saw some youtubers reverting back to MIUI by entering TWRP and wiping
Dalvik / ART cache
Cache
System
Vendor
Data
Then install MIUI 10 ROM
wipe cache/dalvik
And then reboot system even if it says "No OS installed"
Some people installed lazy flash zip file as well. Some others didn't wipe Vendor and some wiped Internal Storage as well and installed the ROM via OTG. I couldn't find any guide/tutorial with a Mi6 and that's why I'm posting here.
What would you suggest? Do I need the lazy flash zip as well? Do I need to wipe Vendor partition and Internal Storage as well?
Thank you in advance for any experienced advice.
Install MIUI via MiFlash
worldwidegigio said:
Hi guys,
I'm about to sell my Mi 6 to upgrade to the K20 Pro and I would like to reinstall the latest MIUI 10 before giving my mobile away.
So as you read on the title I have the latest PE Pie CAF edition and I would like to be sure of all the steps to be done to install MIUI 10 without hassles. I have the latest TWRP 3.3.1-2
I have a Mac so the fastboot option is not my favourite one and I would prefer to use TWRP. I googled a bit and saw some youtubers reverting back to MIUI by entering TWRP and wiping
Dalvik / ART cache
Cache
System
Vendor
Data
Then install MIUI 10 ROM
wipe cache/dalvik
And then reboot system even if it says "No OS installed"
Some people installed lazy flash zip file as well. Some others didn't wipe Vendor and some wiped Internal Storage as well and installed the ROM via OTG. I couldn't find any guide/tutorial with a Mi6 and that's why I'm posting here.
What would you suggest? Do I need the lazy flash zip as well? Do I need to wipe Vendor partition and Internal Storage as well?
Thank you in advance for any experienced advice.
Click to expand...
Click to collapse
If you're on a mac, you can:
- download fastboot rom
- extract it
- run flash_all.sh (not really sure of the name right now but it's one of them ) file in the terminal
- done
Unfortunately Mi Flash doesn't work on a Mac ...
Thanks anyway
Ad3s12 said:
Install MIUI via MiFlash
Click to expand...
Click to collapse
I guess that's the way to go...But then I think I'll need to check if the adb/fastboot tools work on macOS 10.13
Thanks
xikz said:
If you're on a mac, you can:
- download fastboot rom
- extract it
- run flash_all.sh (not really sure of the name right now but it's one of them ) file in the terminal
- done
Click to expand...
Click to collapse
{
"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"
}
TWRP - 3.3.1-3 For Huawei MediaPad M3 Lite 8/10
The new TWRP 3.3.1-3 is required only for Android Q
Officially Supported Devices :
Huawei MediaPad M3 Lite 10 : ( code name Bach ) : BAH-AL00/BAH-L01/BAH-L09/BAH-W09
Huawei MediaPad M3 Lite 8 : ( code name Chopin ) : CPN-AL00/CPN-L0J/CPN-L09/CPN-W09
Instructions :
1. This new TWRP must be installed ONLY on your device running LOS 17.1 with TWRP 3.3.1-0 !
2. flash TWRP recovery using the following command : "fastboot flash recovery twrp-3.3.1-3.img"
3. reboot to recovery ( please check this info after TWRP was installed - and before take any actions )
Downloads :
twrp-3.3.1-2.img
twrp-3.3.1-3.img
Working/ Not working :
- adb shell & mtp
- wipe, backup & restore
- USB-OTG ( need to reboot device to be able to use USB-OTG )
- install Android 10 ROMs
- install GApps Android 10
- FBE /data decrypt support working !
Source :
kernel source : https://github.com/Huawei-Dev/android_kernel_huawei_bach
Credit :
TeamWin - TWRP
LuK1337 for his help !
Mention :
We need this new update of TWRP 3.3.1-3 in order to be able to install GApps on Android 10 & encrypt/decrypt your device !
There is no reason to update TWRP - if you don' use custom ROMs based Android 10 !
Best regards !
Reserved
*** reserved ***
Can't do anything with TWRP
Some help would be greatly appreciated, I have unlocked my mediapad m3 8.0 lite, flashed twrp 3.1.1-1 but when booting into twrp it just sits on the flash screen. Any help?
Roswellien said:
Some help would be greatly appreciated, I have unlocked my mediapad m3 8.0 lite, flashed twrp 3.1.1-1 but when booting into twrp it just sits on the flash screen. Any help?
Click to expand...
Click to collapse
Please, can you install twrp 3.2.0 ? And check to see if you have the same issue ...
surdu_petru said:
Please, can you install twrp 3.2.0 ? And check to see if you have the same issue ...
Click to expand...
Click to collapse
Installed 3.2.0, worked as expected, attempted to directly update to 3.3.1-1, issue returned. Went back to 3.2.0, worked again, flashed 3.3.1-0, issue came back. At a loss at this point. Is there something I am missing here?
Roswellien said:
Installed 3.2.0, worked as expected, attempted to directly update to 3.3.1-1, issue returned. Went back to 3.2.0, worked again, flashed 3.3.1-0, issue came back. At a loss at this point. Is there something I am missing here?
Click to expand...
Click to collapse
Yes, only 3.2.0 it's working with stock Huawei Rom. If you want to use the new twrp, please install LOS 16.0 in twrp 3.2.0 and from now you can update twrp without issues.
No luck.
surdu_petru said:
Yes, only 3.2.0 it's working with stock Huawei Rom. If you want to use the new twrp, please install LOS 16.0 in twrp 3.2.0 and from now you can update twrp without issues.
Click to expand...
Click to collapse
Got 3.2.0 installed and working. Wiped and flashed LOS 16.0, stuck in boot loop. Repeated and boot loop again. I've never had this many problems flashing ROMs before. And like an idiot I was in such a rush I didn't backup first. Gonna see if I can sideload a different room and get it running.
When I use the wipe in 3.2.0 there's a whole bunch of things in /data it fails to wipe saying access denied. Any ideas?
---------- Post added at 02:34 AM ---------- Previous post was at 02:21 AM ----------
Roswellien said:
Got 3.2.0 installed and working. Wiped and flashed LOS 16.0, stuck in boot loop. Repeated and boot loop again. I've never had this many problems flashing ROMs before. And like an idiot I was in such a rush I didn't backup first. Gonna see if I can sideload a different room and get it running.
When I use the wipe in 3.2.0 there's a whole bunch of things in /data it fails to wipe saying access denied. Any ideas?
Click to expand...
Click to collapse
Strike that. Did the wipe again when I got home. Didn't error out, flashed again and booted fine. Looks like I'm all good! Thanks everyone!
Update to 3.3.1-2 !
Hello !
There is a new update of TWRP to 3.3.1-2 !
Only minor updated, including new kernel for Android 10 & syncing with the last code source of TWRP to improve stability
Also was fixed FBE encryption !
4. flash TWRP recovery using the following command : "fastboot flash recovery twrp-3.3.1-1.img"
Click to expand...
Click to collapse
Hello
Any manual for regular people how and where to do this? I don't understand where and how type this command.
Instruction is not clear
Because your manual is useless I tried google and found Multi-Tool 8. I flashed img through it. If I tried load in TWRP device is stuck on this screen and nothing more
@surdu_petru, if you want donations then write usable manuals for real life regular people.
Yesterday I got unknown device and installed TWRP & Custom in 10 ninutes. Your manuals are not help at all. I spent hour+ and get nothing.
Looks like my device boots everytime in this TWRP now.
I donated your work even without using it. But no I'm so disappointed (
I made same with twrp_3.2.0-0. It works. Again 3.3.1-2 - nothing. Add notice about stock firmware to 1st message in topic. Time is killed (
pasha4ur said:
Because your manual is useless I tried google and found Multi-Tool 8. I flashed img through it. If I tried load in TWRP device is stuck on this screen and nothing more
@surdu_petru, if you want donations then write usable manuals for real life regular people.
Yesterday I got unknown device and installed TWRP & Custom in 10 ninutes. Your manuals are not help at all. I spent hour+ and get nothing.
Looks like my device boots everytime in this TWRP now.
I donated your work even without using it. But no I'm so disappointed (
I made same with twrp_3.2.0-0. It works. Again 3.3.1-2 - nothing. Add notice about stock firmware to 1st message in topic. Time is killed (
Click to expand...
Click to collapse
Hello !
Please do not panic ... the problem is that you didn't read everything or maybe you didn't understand everything like it should !
So, your device is still in Android N, because you are on stock ... so you need to use ONLY TWRP 3.2.0.0 !
Now, if you want to use LOS , you need to flash LOS 16.0 on this TWRP 3.2.0, and after that you are able to update TWRP/LOS as you like !
Good luck !
Warning !
Please be very carefully before to flash LOS 16.0 into TWRP 3.2.0 because there is no viable solutions to return to Huawei Stock Firmware !
Photo camera still not working and also the battery does not seem to hold as much as in stock ( maybe you can read some feedback of other users on LOS 17.1 or Pixel Experience) ... if these are not an impediment to you, than you can start format data into twrp-3.2.0 in order to decrypt /data, reboot device into twrp from twrp in order to be able to use data as twrp already recommend and flash LOS 16.0 ! Later you can update TWRP to the last version and install some Android 10 Custom ROMs !
If you want after all this to return to stock, then this is a problem because I already tried without success ... so, that's why this "warning!"
So, your device is still in Android N, because you are on stock ... so you need to use ONLY TWRP 3.2.0.0 !
Click to expand...
Click to collapse
Please be very carefully before to flash LOS 16.0 into TWRP 3.2.0 because there is no viable solutions to return to Huawei Stock Firmware !
Click to expand...
Click to collapse
You should write this in 1st message in topic. Not on 2nd page.
Don't worry. My device is already dead in bootloop.
I will look for a service center or buy a new tablet after removing the quarantine in my country.
Great job! (
pasha4ur said:
You should write this in 1st message in topic. Not on 2nd page.
Don't worry. My device is already dead in bootloop.
I will look for a service center or buy a new tablet after removing the quarantine in my country.
Great job! (
Click to expand...
Click to collapse
How is already dead ?? I see that you have installed LOS17.1, right ? ... So, I guess you re device it's ok !
So, I guess you re device it's ok !
Click to expand...
Click to collapse
After running encryption function it's in bootloop
Fix Data Partition Size !!!
Hello !
I will explain here how the partition /data should be resized in order to be able to Encrypt device on any custom ROM based Android 10 !
From the total of data size, we need to reserve 32768 bytes for encryption stuff.
First, your device should be running Android 10 with TWRP 3.3.1-2 installed ( if you are here, I guess this is already done - what follows is not for Android Pie or for another version of TWRP )
Connect USB cable and type : ( it doesn't matter if you are now on TWRP or a custom ROM based Android 10, btw, make sure you have already enabled "Android debugging" if you're not on TWRP )
adb reboot bootloader
Click to expand...
Click to collapse
You're now on bootloader mode, here only fastboot commands are allowed !
Determine total size of /data partition by typing this command :
fastboot getvar partition-size:userdata
Click to expand...
Click to collapse
Because there are three versions of data storage size : 16GB, 32GB & 64GB - the response to the above command will vary depending on the capacity of your device !
Something like this you'll see after above command :
partition-size:userdata: 0x5xxxxxxxx
finished. total time: 0.002s
Click to expand...
Click to collapse
Let's assign a name to this value, to make it easier to explain what to do next:
I'll call "sectors" the value "0x5xxxxxxxx" which means the total size of your data partition !
If you have any questions so far, then it's time to ask for help, before going any further: because we'll perform some operations with "sectors", and you should already understand what "sectors" mean ... basicly it's a value equale with the total size of youre data partition returned by fastboot !
How we actually interpret this generic number "0x5xxxxxxxx" :
The "xxxxxxxx" from "0x5xxxxxxxx" it's a base number 16 ( hexa) - and is made up of digits from 0 to 9 and also from letters from a to f !
This is just a random example in response to the above command :
partition-size:userdata: 0x5fb03abe0
finished. total time: 0.002s
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Convert "sectors" from hex to decimal using any converter online hex-to-decimal !
"sectors" it'll be now a number made up of digits from 0 to 9 !
Subtract now from "sectors", 32768 .... something like this : "new_sectors" = "sectors" - 32768
The new sectors "new_sectors" will be smaller by 32768 than the one convert from hex to decimal !
Now, this last value ("new_sectors") must be divided to 512 : "new_new_sectors" = "new_sectors" : 512
Let's go back to the "sectors", so we'll rename "new_new_sectors" to "sectors" , so the final value of "sectors" will be smaller by 32768 than the one convert from hex to decimal and also divided to 512 !
Finally, we can summarize all the above operations to this one :
"sectors" = (hex-to-dec(0x5xxxxxxxx) - 32768) : 512
Click to expand...
Click to collapse
As soon as you have the final value and everything went clarity, we need to format data under twrp with this final value of "sectors" !
Reboot device from bootloader mode :
fastboot reboot
Click to expand...
Click to collapse
Reboot device to TWRP :
adb reboot recovery
Click to expand...
Click to collapse
Warning : all data will be lose because we need to format /data :
In order to reformat data Unmount data & type those commands :
Unmount data : check "Mount" & under "Select Partitions to Mount:" deselect/uncheck "Data" !
adb shell
mkfs.f2fs /dev/block/mmcblk0p62 "sectors"
Click to expand...
Click to collapse
Instead "sectors" you"ll must introduce the value of "sectors" which is a number made up of digits from 0 to 9 !
Reboot your device again to TWRP in order to be able to use /data !
reboot recovery
Click to expand...
Click to collapse
That's ALL ... you can now install the new TWRP 3.3.1-3 ( please check OP for download ) with /data decrypt support and also the new LOS 17.1 ( released ) where you'll be able to Encrypt tablet without issues !
Warning :
Starting from now you should never format data again into TWRP in this way : Wipe -> Format Data !
This operation will remove "data" encrypt/decrypt support and your device will not be able to be encrypted under any custom ROMs Android 10 !
surdu_petru said:
Yes, only 3.2.0 it's working with stock Huawei Rom. [...]
Click to expand...
Click to collapse
Hi there,
Could anyone please point me at the right direction to download TWRP 3.2.0 for Huawei MediaPad M3 Lite ? It seems I can't find it anywehre :/
Thank you very much.
Oum said:
Hi there,
Could anyone please point me at the right direction to download TWRP 3.2.0 for Huawei MediaPad M3 Lite ? It seems I can't find it anywehre :/
Thank you very much.
Click to expand...
Click to collapse
Where else could TWRP 3.2.0 be if not in TWRP 3.2.0 thread ... logical, right ??
Roswellien said:
Some help would be greatly appreciated, I have unlocked my mediapad m3 8.0 lite, flashed twrp 3.1.1-1 but when booting into twrp it just sits on the flash screen. Any help?
Click to expand...
Click to collapse
The same thing's happened to me, but "twrp_3.2.0-0.img" worked on my device but the app does not recognize the recovery image (PixelExperience-10.0-HuaweiMediaPadM3Lite_2020-03-15.zip) which I copied it onto external SD card such as /sdcard/download folder.
---------- Post added at 04:49 PM ---------- Previous post was at 04:42 PM ----------
surdu_petru said:
TWRP - 3.3.1-3 For Huawei MediaPad M3 Lite 8/10
The new TWRP 3.3.1-3 is required only for Android Q
Officially Supported Devices :
Huawei MediaPad M3 Lite 10 : ( code name Bach ) : BAH-AL00/BAH-L01/BAH-L09/BAH-W09
Huawei MediaPad M3 Lite 8 : ( code name Chopin ) : CPN-AL00/CPN-L0J/CPN-L09/CPN-W09
Instructions :
1. unlock bootloader
3. unlock OEM on Developer options
3. enter on bootloader mode :
( switch off your device then keep pressed volume down key when plug to USB cable )
4. flash TWRP recovery using the following command : "fastboot flash recovery twrp-3.3.1-3.img"
5. reboot to recovery ( please check this info after TWRP was installed - and before take any actions )
Downloads :
twrp-3.3.1-2.img
twrp-3.3.1-3.img
Working/ Not working :
- adb shell & mtp
- wipe, backup & restore
- USB-OTG ( need to reboot device to be able to use USB-OTG )
- install Android 10 ROMs
- install GApps Android 10
- FBE /data decrypt support working !
Source :
kernel source : https://github.com/Huawei-Dev/android_kernel_huawei_bach
Credit :
TeamWin - TWRP
LuK1337 for his help !
Mention :
We need this new update of TWRP 3.3.1-3 in order to be able to install GApps on Android 10 & encrypt/decrypt your device !
There is no reason to update TWRP - if you don' use custom ROMs based Android 10 !
Best regards !
Click to expand...
Click to collapse
I cannot flash PixelExperience-10.0-HuaweiMediaPadM3Lite_2020-03-15.zip by TWRP 3.2.0.0. Do I need to flash LOS16.0 onto my device first and then update TWRP to 3.3.1.3 and then flash PixelExperience-10.0-HuaweiMediaPadM3Lite_2020-03-15.zip???
Hi guys i have no idea where i went wrong. When flashing TWRP, this message always comes up: "necessary to unlock frp! Navigate to settings> developer op)". Can you help me??
mc_simon88 said:
Hi guys i have no idea where i went wrong. When flashing TWRP, this message always comes up: "necessary to unlock frp! Navigate to settings> developer op)". Can you help me??
Click to expand...
Click to collapse
Yes, go to Settings->Developer settings->OEM unlock !