Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Quote:
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.
Click to expand...
Click to collapse
NOTE: This version of TWRP is intended to be used with the original unlock for karnak by xyz`.
If you unlocked or updated using amonet-3 it already contains an updated TWRP.
This version will still work, but it lacks support for features such as reboot to hacked BL.
Features:
amonet-aware
SDCard support
USB-OTG support
Backup/Restore support
Downgrade/Overwrite-protection for LK/PL/TZ
Autorestore of broken boot-patch
Also patches amonet-microloader when flashing images
Supports flashing stock-update bins (rename to .zip, no modification necessary )
NOTE: Your device needs to be unlocked.
NOTE: When backing up or restoring stock ROM (or any other ROM that has dm-verity enabled) make sure to select "System Image" instead of "System".
Many thanks to @Kaijones23 for testing!
Download: twrp-karnak-3.3.1-0.zip
XDA:DevDB Information
TeamWin Recovery Project (TWRP), Tool/Utility for the Amazon Fire HD 8 and HD 10
Contributors
k4y0z, xyz`
Source Code: https://github.com/chaosmaster/android_bootable_recovery
Version Information
Status: Beta
Current Beta Version: 3.3.1-0
Beta Release Date: 2019-07-17
Created 2019-07-16
Last Updated 2019-07-17
Changelog
17.07.2019:
Update TWRP to 3.3.1-0
Add support for vendor partition
16.07.2019:
Fix USB-OTG
Reserved #2
Reserved #3
Sent from my Pixel 3a XL using Tapatalk
@k4y0z @Kaijones23 good work guys!!
Great work!
Just flash from existing TWRP to update?
Michajin said:
Great work!
Just flash from existing TWRP to update?
Click to expand...
Click to collapse
Yup
Just uploaded a new build, that also fixes USB-OTG
Works great on my HD8 2018 that I just got today.
New build is up
Update TWRP to 3.3.1-0
Add support for vendor partition
k4y0z said:
New build is up
Update TWRP to 3.3.1-0
Add support for vendor partition
Click to expand...
Click to collapse
Wow very nice!
Does karnak has vendor partition??
Rortiz2 said:
Wow very nice!
Does karnak has vendor partition??
Click to expand...
Click to collapse
It has, but not used by stock as far as i can tell.
I added support in TWRP, so it could potentially be used by custom ROMS.
Working great on my brand new HD8. Installed 3.3.1 from your 3.2.3 release, rebooted to recovery, reflashed magisk, no issues. Thanks!
jibgilmon said:
Working great on my brand new HD8. Installed 3.3.1 from your 3.2.3 release, rebooted to recovery, reflashed magisk, no issues. Thanks!
Click to expand...
Click to collapse
Reflashing Magsik should not have been necessary if it was already installed
Quick question,
Can I just go to my existing TWRP, click Install, select the ZIP file attached here and flash or do I need to extract the image and install the Image file from within the current TWRP version?
Thanks!
agr8lemon said:
Quick question,
Can I just go to my existing TWRP, click Install, select the ZIP file attached here and flash or do I need to extract the image and install the Image file from within the current TWRP version?
Thanks!
Click to expand...
Click to collapse
You can do it either way, but just flashing the zip in recovery is probably the easiest way. You can reboot recovery while in TWRP to check that it flashed successfully, if you want to.
Hey, quick question
Can i install any .zips that i want? If not, what or which types of .zips should i try to avoid?
(In this case i just want to install YT Vanced)
Thanks
5442 said:
Hey, quick question
Can i install any .zips that i want? If not, what or which types of .zips should i try to avoid?
(In this case i just want to install YT Vanced)
Thanks
Click to expand...
Click to collapse
I just installed YouTube Vanced from Magisk.
nujak said:
I just installed YouTube Vanced from Magisk.
Click to expand...
Click to collapse
I'm not talking about magisk, as i will be flashing LineageOS, and it already has root so i wanna know about recovery, not magisk
5442 said:
I'm not talking about magisk, as i will be flashing LineageOS, and it already has root so i wanna know about recovery, not magisk
Click to expand...
Click to collapse
Flashing YT VANCED in TWRP will also work.
Related
So here is the deal folks,
**FOR SCREENSHOTS CLICK HERE!!**
I have updated my first supported ShoreDroid device using CM, AOSP and OmniROM to Android 4.4! This is a beta build and as such will come with a couple bugs - please report them here and not to CM, AOSP or OmniROM.
This build is the first and will not come with everything at once but right now it's a working build of KitKat. I have included the updated unofficial CWM Recovery you will need to flash this to your device. I have also included a flashable zip for those who just want to update recovery and flash with s-off and an installer script for those who have s-on using a windows machine.
Below are the instructions - please read them and understand I take no liability whatsoever with whatever may happen to your device. You take full responsibility from here.
Basics such as unlocking bootloader, rooting, fastboot and flashing should all be assets prior to beginning!
Flashable Steps
1. Download the current ROM and have it ready on your device -------->DOWNLOAD Updated!!!
2. Download my unofficial CWM Recovery and fastboot flash it to update your recovery ------->http://d-h.st/bSM
3. Boot into recovery and ensure you have a backup made
4. Factory Wipe, Wipe Cache, Wipe Dalvik and Format System prior to flashing or you'll end up unstable
5. Flash ROM
6. Flash Gapps found here ---------->http://forum.xda-developers.com/showthread.php?t=2397942
7. Reboot and voila!
*You can still do this method with s-on but you will have to first extract the boot.img for the zip and fastboot flash it right after updating your recovery and then flash the zip from step 4 down. Or you can use the installer script!
Update Script
1. Download the Installer Package here ---------> DOWNLOAD
2. Ensure the current ROM zip is on your phone as well!!!
3. Unzip the update script to your desktop
4. Reboot into recovery and flash ROM zip then go to advanced-reboot into bootloader
5. Run UPDATE.bat and follow instructions exactly or you will end up with boot loops!!!
6. Voila!
I would like to thank the following for their source code and amazing audio files:
CyanogenMod
OmniROM
AOSP Team
ViPER520
zhuhang
My device and kernels trees will be updated shortly!
ChangeLog:
11-20131215
-Merged ViPER Audio FX
-Removed Apollo and replaced with AOSP Music
-Updated to 4.4.2 and repo sync'd
-Changed default wallpaper
-Removed CM dependancies and media
-Started testing Active Display on test branch
-Lots of code cleanup and license change to Shore Holdings
11-20131210
-Removed CM Updater
-Added ShoreDroid changelog
-Removed Terminal app
-Added TWRP Support
-Tags complete for OTA and ROM Manager support
-Extensive kernel and device tree modification to stabilize ROM and improve WiFi - We will see what other bugs it squashes as well!
-Viper Audio Libraries added for future support in next nighly
-Repo Sync'd to the latest sources
11-20131204
-Initial Release
-New ShoreDroid boot animation
Past Releases
20131204 - http://goo.gl/X8ExpR
20131210 - http://goo.gl/h3V056
20131211 - http://goo.gl/CHo5Ma
Past Installer Scripts
20131204 - http://d-h.st/OVg
20131211 - ShoreUpdater.7z - 23.93 MB
XDA:DevDB Information
ShoreDroid 4.4 for Evita, a ROM for the AT&T HTC One X
Contributors
ShorelineDroid
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: New CWM Included
Based On: CM11, AOSP, OmniROM
Version Information
Status: Beta
Current Beta Version: 11-20131215
Beta Release Date: 2013-12-15
Created 2013-12-04
Last Updated 2014-02-14
ViPER4Android FX
Introduction
We have decided to leave BeatsAudio behind and start a new chapter of audio enhancement with KitKat. We are pleased to merge ViPER Audio into the ROM. You'll find the control panel is similar to DSP Manager and that all features are easy to use. I've personally tested the system out with urBeats headphones and it sounds great with the effects that you're able to manipulate. We will add continuously to this post as it will be our official ViPER support post so check back for more information later.
Click to expand...
Click to collapse
Official Website
The official website for the ViPER Audio project is ViPER FAQ here you can find a ton of information about the operation of ViPER and what's coming.
Click to expand...
Click to collapse
IRS Starter Pack
This is a collection of impulse response samples found on the Internet for users to begin with convolution feature. This pack does not include IRS by any individuals ---------> IRS Starter Pack
Click to expand...
Click to collapse
Hints and Tricks
* This absolutely has to be on compatibility mode with the other audio effect lib files included in this ROM
Click to expand...
Click to collapse
sd
I am loving the interest for this device. Proof that this device isn't dead
Sent from my HTC One XL using XDA Premium 4 mobile app
I did not find dbmenu at the top
haq.adnan said:
I did not find dbmenu at the top
Click to expand...
Click to collapse
Here.
haq.adnan said:
I did not find dbmenu at the top
Click to expand...
Click to collapse
You need to view it in a web browser.
Sent from my Evita
timmaaa said:
You need to view it in a web browser.
Sent from my Evita
Click to expand...
Click to collapse
5th! will use try rom
more and more 4.4 roms to choose from.
The ROM is running smooth. Flashed with torched kk 2.1.
Good job !!!
Hello,
I have twrp 2.6.0 and would that cwm recovery override it? thanks
Phoenixita's recovery should be fine, it is CWM after all. I agree about that Recovery Tools app too, it's a really valuable app if you want to switch recoveries easily.
Sent from my Evita
Scozzar said:
Yes it would. You can only have one recovery installed at a time. Lately, I've been using the Recovery Tools app on the Play Store. It allows you to flash recoveries without having to use your computer. It's nice if you're going between 4.3.1 and 4.4 ROMs because you can flash CWM and twrp.
EDIT: Also, can we use Phoenixita's recovery for this as well? I would prefer, just so I don't have 3 different recoveries all named "recovery.img". Can we rename the file, or would that screw things up?
Click to expand...
Click to collapse
which recovery tools are you referring to? Thanks
See link in my post above yours.
Sent from my Evita
timmaaa said:
See link in my post above yours.
Sent from my Evita
Click to expand...
Click to collapse
Thanks timmaaa you have been a BIG help on my journey of rooting, flashing etc...
Press the thanks button when someone helps you
Sent from my Evita
Scozzar said:
EDIT: Also, can we use Phoenixita's recovery for this as well? I would prefer, just so I don't have 3 different recoveries all named "recovery.img". Can we rename the file, or would that screw things up?
Click to expand...
Click to collapse
Yes. Its what i did
Scozzar said:
Yes to what? Renaming? Using Phoenxita's recovery? Both?
Click to expand...
Click to collapse
Lol. Recovery. My bad..
Scozzar said:
Yes to what? Renaming? Using Phoenxita's recovery? Both?
Click to expand...
Click to collapse
You can freely rename them. Not sure if recovery tools has anything in its scripting to load only recovery.IMG though. If you flash with fastboot, you will just have to alter your command to reflect the respective file name. i.e. fastboot flash recovery whateveryourenamedyourrecovery.img
Sent from my One X using XDA Premium 4 mobile app
installed the rom,and google apps..it works like a charm,thank you...but two issues:
1.the vibration is very much and there's no way to make it less
2.the wifi can not connect,i turn it on but it can't connect to my access point
Strong vibration is normal for aosp ROMs.
Sent from my Evita
Hello !
Currently i'm working in Le 2 kernel and device tree. My purpose is to make meaningful changes and additions so other ROMs can implement them.
Confirmed working with LOS, Carbon, LegendROM (latest releases)
This thread is all about the kernel. Currently the kernel features
sdcardfs support
cpu-input boost
power efficient work-queues
improvements to touchscreen driver, preparing support for dt2w
adj tree
low memory killer improvements
powersuspend driver
nvidia patches for energy efficiency
memory bus improvements
Adreno memory pools
and other small improvements in battery management and scheduler
Download: https://drive.google.com/open?id=0B4AOvCehd4v3OXBEX3dMSkdxQ3c
Source: https://github.com/mthomos/android_kernel_leeco_msm8976
To enable sdcardfs support just add this line in build.prop
Code:
ro.sys.sdcardfs=true
To be clear from the beginning: I will not answer to any feature requests and i respond to bug reports without logs. I hope to understand this
Cheers !
XDA:DevDB Information
Diades Kernel, Kernel for the LeEco Le 2
Contributors
marios199546
Kernel Special Features:
Version Information
Status: Testing
Created 2017-09-05
Last Updated 2017-09-07
What's the decryption key?
Good luck :good::good:
For which ROM?
Nice one.
Gonna try and report!
Its asking for decryption key!
OP updated with new link
Work on rom based in eui or only aosp rom ?
Sent from my Le X522 using XDA-Developers Legacy app
fmehdi said:
Work on rom based in eui or only aosp rom ?
Click to expand...
Click to collapse
Doesnt work on eui base
Only custom roms
What does sdcardfs mean?
bonsai.14 said:
What does sdcardfs mean?
Click to expand...
Click to collapse
https://www.xda-developers.com/divi...les-fuse-replacement-will-reduce-io-overhead/
I probably shouldn't be here this looks complicated but how do you flash the .img files? Are they even supposed to be flashed
billybobjoe512 said:
I probably shouldn't be here this looks complicated but how do you flash the .img files? Are they even supposed to be flashed
Click to expand...
Click to collapse
Sounds like you're new to this. When you boot your device into recovery (TWRP to be specific). You will see a option"Install", click over there then it will open up the local directory. And on the bottom right, you still see a option to select imgs file. Select that option and boom now you will see all your downloaded imgs files showing up there.
Note:- Make sure to choose a proper partition. For recovery. Img select recovery and so on. Taking a backup before you try something new is always recommended.
Njishi said:
Sounds like you're new to this. When you boot your device into recovery (TWRP to be specific). You will see a option"Install", click over there then it will open up the local directory. And on the bottom right, you still see a option to select imgs file. Select that option and boom now you will see all your downloaded imgs files showing up there.
Note:- Make sure to choose a proper partition. For recovery. Img select recovery and so on. Taking a backup before you try something new is always recommended.
Click to expand...
Click to collapse
So where would I flash these .img files? Or do I have to do something else before flashing
billybobjoe512 said:
So where would I flash these .img files? Or do I have to do something else before flashing
Click to expand...
Click to collapse
What else you can do? Like going for a walk is recommended!?
You just have to boot into recovery. And then flash them like the way i said.
Or else you can use this app.
https://youtu.be/6IMvOCUy2Wc
You can also flash .img via fastboot with this command : fastboot flash boot <file_name.img>
Also if you have magisk installed you have to flash again the magisk install every time you install a new kernel.
I am a bit of a noob so I'm probably doing a ton of things wrong here
So how long does it take to start up the device after flashing the kernel? I flashed to boot partition and I waited for about 10 minutes and I got impatient so I restarted and tried to take a logcat but it just said waiting for device so I just restored a backup that I had made
Did I mess up somewhere or do I need to have a logcat for this
Phone don't boot bro I waite d 20 min
Mine works perfectly, which rom do you use ? I have tested with LOS and Carbon and works flawlessly
marios199546 said:
Mine works perfectly, which rom do you use ? I have tested with LOS and Carbon and works flawlessly
Click to expand...
Click to collapse
Phone not booting. Stuck at Spash screen. Cant take logs (waiting for device).
About the Android Open Source Project
Android is an open source software stack for mobile devices and a corresponding open source project led by Google. This site and the Android Open Source Project (AOSP) repository offer the information and source code needed to create custom variants of the Android stack, port devices and accessories to the Android platform, and ensure devices meet the compatibility requirements that keep the Android ecosystem a healthy and stable environment for millions of users.
BUGS:
TELL ME.
sdcard that I will fix in next build.
GAPPS:
Click here to download this gapps.
Downloads:
09/05/2020
aosp-9-20200508-prague-haky86.zip
Fix gapps issue.
Fix hwc thanks to Flex1911.
I forget to include NFC fix, just flash Treble's module.
19/19/2020
aosp-9-20200716-hi6250-haky86.zip
Restart works.
Fix Google Play errors:
Go to Settings.
Open Apps.
Search for Google Play Store and Google Play Services.
Give the permissions especially to storages to get Play Store worked correctley.
XDA:DevDB Information
Android Open Source Project Pie for HI6250 Emui 8.x based, ROM for the Honor 8 Lite
Contributors
haky 86, flex1911
Source Code: http://github.com/hak86
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8.x
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2018-11-18
Beta Release Date: 2018-11-18
Created 2018-11-18
Last Updated 2019-11-14
** Note **
reserved:
topic will be reopened once download is uploaded
Edit: rom uploaded
Any experience with this?
dtrail1 said:
Any experience with this?
Click to expand...
Click to collapse
same as other roms, I simply remove kirin970 stuff.
I'm assuming Gapps are not included?
verntechguy said:
I'm assuming Gapps are not included?
Click to expand...
Click to collapse
Nope isn't included. I will use this thread as unique place for all my Pie ROMs.
haky 86 said:
Nope isn't included. I will use this thread as unique place for all my Pie ROMs.
Click to expand...
Click to collapse
Thanks for the info. So opengapps should work right? How about Magisk? Standard version should work?
verntechguy said:
Thanks for the info. So opengapps should work right? How about Magisk? Standard version should work?
Click to expand...
Click to collapse
for gapps I recommend pico, since it is "demo" build for nfc you have to flash magisk module, for magisk use 17.1 and up also don't forget to install the manager application.
haky 86 said:
for gapps I recommend pico, since it is "demo" build for nfc you have to flash magisk module, for magisk use 17.1 and up also don't forget to install the manager application.
Click to expand...
Click to collapse
My variant doesn't have nfc so I don't have to worry about that. Will try this out once I'm free. Thanks for your work!
** Breaking News **
AOSP Extended is HERE
08/11/2018:
AospExtended-v6.0-hi6250-20181108-1232-UNOFFICIAL.zip
Bugs: media works just via VLC application or similar, I will fix in next build.
Don't forget to do the following things:
1-)Reboot in TWRP and mount system, vendor and splash2 partitions.
2-)Run the following command from terminal: /sbin/sh /system/bin/releasetools.kirin970.sh
3-)Flash eRecovery and do factory reset to boot the rom properly. P.S: if boot with a fully worked twrp you don't need to flash stock eRecovery.
No screenshots? I forget to save them but see the one in the attached files
Telegram: https://t.me/HakyGSI
** Note **
AOSP has been updated
aosp-pie-9.0.0_r16-hi6250-090112018.tar.gz
Android 9.0.0 R16.
Hotspot fixed.
NFC fixed properly.
Don't forget run releasetools.kirin970.sh script via twrp to boot the whole rom.
cookremier said:
Dates doesn´t match to the files in the main post.
Look at this:
AOSP Extended:
18/11/2018:
AospExtended-v6.0-hi6250-20181108-1232-UNOFFICIAL.zip
Do you live in the future with a Flux Compensator ???
Click to expand...
Click to collapse
yes, I'm coming from the future .
it just a typo's error
Any other recommendation before flashing your Image? Tried it by coming from EMUI 8 but got sparse error after flashing system.img in fastboot.
pete80pro said:
By following your Tutorial I'm gettin error message on flashing System.img with fastboot.
I have to be on EMUI 8 before, any other needed things?
Click to expand...
Click to collapse
Flash phh's aosp 9 without wiping emui 8 system partition then try mine. in case not working wait next build then
I manage to boot LineageOS 16.0, I will fix error 7 here too and upload first beta in separate topic.
Good for daily use ? P10 Lite
cxyqqz said:
Good for daily use ? P10 Lite
Click to expand...
Click to collapse
Yes but I have to fix fastboot error first.
Anyways LineageOS 16.0 cancelled, sometime boot and some time doesn't boot. I'm start getting bored of from Emui 8.x and back to emui 5.x developments that are better in certain sense.
P20 Lite ane-lx support?
A_S_A113 said:
P20 Lite ane-lx support?
Click to expand...
Click to collapse
yes it is, the next image of AOSP 9 with fastboot fix will come out in next hours.
haky 86 said:
AOSP Extended is HERE
08/11/2018:
AospExtended-v6.0-hi6250-20181108-1232-UNOFFICIAL.zip
Bugs: media works just via VLC application or similar, I will fix in next build.
Don't forget to do the following things:
1-)Reboot in TWRP and mount system, vendor and splash2 partitions.
2-)Run the following command from terminal: /sbin/sh /system/bin/releasetools.kirin970.sh
3-)Flash eRecovery and do factory reset to boot the rom properly. P.S: if boot with a fully worked twrp you don't need to flash stock eRecovery.
No screenshots? I forget to save them but see the one in the attached files
Telegram: https://t.me/HakyGSI
Click to expand...
Click to collapse
What do you mean by flashing erecovery, you mean stock recovery right? (recovery ramdisk)
steven360 said:
What do you mean by flashing erecovery, you mean stock recovery right? (recovery ramdisk)
Click to expand...
Click to collapse
yes stock recovery, it is needed just to wipe data & cache. the releasetools.kirin970.sh can be flashed by twrp post rom installation by /sbin/sh in shell.
Introduction
This is an unofficial build of LineageOS 16 for Redmi Note 7 Pro. Differences from the one provided by Dyneteve include:
- Ported the CAF wrappedkey encryption stuff, which is what MIUI uses, over using patches from https://mokeedev.review/q/topic:%22fbe-wrapped-key%22+(statuspen%20OR%20status:merged), This requires an recovery with wrappedkey decryption support, e.g. this one
- Applied unmerged patch https://review.lineageos.org/c/LineageOS/android_build/+/247066 to mount system as /system_root properly on install. This makes addon.d scripts (e.g. Magisk / GApps survival script) work again on our device. This requires an recovery with proper system_as_root support, e.g. this one
- ROM includes its own vendor image instead of relying on one provided by MIUI. I intend to try to build as much of vendor image as possible from CAF source in the future.
Flash instructions
- Make sure you have the latest firmware images. If not, update them before flashing.
- Flash a TWRP recovery that supports mounting system as /system_root and supports wrappedkey encryption (the one provided above)
- Wipe data partition (without wiping /data/media). If you came from another non-CAF ROM (ROM that do not support wrappedkey mode) and had encryption enabled, you will need to format your data partition (including /data/media).
Note: If you decide to format your data partition, always format with 'advanced wipe' in TWRP recovery. DO NOT use fastboot -w or fastboot erase, even if you do, please format again in recovery, otherwise the system might not work.
- Install the zip in TWRP.
- Install whatever you want e.g. Magisk, OpenGapps
- DO NOT install the fcrypt disabler.
- Reboot and enjoy
Known issues
DO NOT remove screen lock passwords if you set one. You can change the password just fine, but DO NOT REMOVE IT. YOU WILL LOSE ACCESS TO ALL DATA IF YOU DO THIS AND REBOOT.
Removing screen lock passwords work after 20190528-1.
Downloads
20190609-1: https://mega.nz/#!PdRnxIia!Boh-a8e5JHt8YEBwbXKt8rWYj3PC56mdpEIXwDEY2ng
changelog: 1) Merged upstream LineageOS (June security patch) 2) Updated kernel to 4.14.123 3) Updated MIUI binary blobs 4) Some clean-up
NOTE: /proc/last_kmsg support is removed due to incompatibility. This feature is replaced by pstore, which you could find more information on through some Google-fu.
History versions:
20190528-1: https://mega.nz/#!nZRTQCbS!qf-RdT-ijayg8UBxyyz3Hoi2O_8ZtpWewgNv-eVDcqA
changelog: 1) merged upstream LineageOS; 2) fixed the bug of removing screen lock passwords, now it won't swallow all your data (this commit: https://github.com/PeterCxy/android...mmit/d2fe3434cddb98eeb414906e71a817559ade1b26; 3) merged LTS kernel 4.14.122, thanks to YaroST and aviraxp; 4) fixed potential charging problem; 5) some other kernel improvements
20190526-1: https://mega.nz/#!rRgwmY5T!2fQyDjukLoGmk7KRtas5n2Y_it9QS_s2noAItzNvFfY
Sources
Device: https://github.com/PeterCxy/android_device_xiaomi_violet
Kernel: https://github.com/PeterCxy/android_kernel_xiaomi_sm6150
Other changes and patches: see what is available on my GitHub https://github.com/PeterCxy/, everything is open-source for this ROM.
Contributors
PeterCxy, GuaiYiHu, aviraxp
Source Code: https://github.com/PeterCxy/android_device_xiaomi_violet
Thanks ?
Thank you for the ROM!
There's a Typo in the ROM os version description.
cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.
jyoti.id said:
cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.
Click to expand...
Click to collapse
If you can't boot to recovery at all you may need to flash a fastboot ROM of MIUI (of course in fastboot mode) and try to install twrp again.
jyoti.id said:
cant boot. installed as mentioned in instruction. its automatically rebooting to recovery (twrp, the given one). now whenever i try to flash other rrecovery its not booting into. stuck. please help.
Click to expand...
Click to collapse
Sorry I have no idea here.. What ROM you were on before flashing this?
Dwughjsd said:
If you can't boot to recovery at all you may need to flash a fastboot ROM of MIUI (of course in fastboot mode) and try to install twrp again.
Click to expand...
Click to collapse
iv flashed the stock rom, but now the internal storage is showing only 16GB of storage.
Edit: fixed everything. Thank you. I was curious about the battery backup of this ROM badly, so I just rushed in things so maybe I made some mistakes.
jyoti.id said:
iv flashed the stock rom, but now the internal storage is showing only 16GB of storage.
Edit: fixed everything. Thank you. I was curious about the battery backup of this ROM badly, so I just rushed in things so maybe I made some mistakes.
Click to expand...
Click to collapse
Just keep in mind that safety first
Download link not working
Edit: UC browser was the culprit
dwughjsd said:
just keep in mind that safety first
Click to expand...
Click to collapse
how u fixed storage issue
gsunil said:
how u fixed storage issue
Click to expand...
Click to collapse
It was @jyoti.id that faced and solved the issue, so let's call him for an answer
rom keeps rebooting into twrp , i did every step
gsunil said:
how u fixed storage issue
Click to expand...
Click to collapse
I just flashed the whole fastboot rom again & it fixed everything.
---------- Post added at 04:34 AM ---------- Previous post was at 04:33 AM ----------
King_Dinoco10 said:
rom keeps rebooting into twrp , i did every step
Click to expand...
Click to collapse
Same thing happened with me too
Device not charging above 86%. Anyone else facing this bug ?
PeterCxy said:
Sorry I have no idea here.. What ROM you were on before flashing this?
Click to expand...
Click to collapse
The phone does not charge more than 91%!
lapo_chel said:
The phone does not charge more than 91%!
Click to expand...
Click to collapse
now should be fixed, try today's new build
PeterCxy said:
now should be fixed, try today's new build
Click to expand...
Click to collapse
Safetynet does not pass.
lapo_chel said:
Safetynet does not pass.
Click to expand...
Click to collapse
It's because I used vendor files from MIUI beta. You can bypass it with a magisk module to reset the build fingerprint
Many thanks for your build! I like it much.
IMHO, SELinux should be enabled.
This is basically a tl;dr thread.
I don't want to make a thread that everyone will lazy to read.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. It's 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.
Disclaimer
Code:
/*
* Your warranty might not be void (thanks Xiaomi). However...
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this RECOVERY
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements
Xiaomi Mi 9 SE (of course)
Unlocked bootloader
Some knowledge on how to deal with your device... and patience.
Flashing InstructionsI assume you've done (very) basic steps on preparing to flash your device.
Reboot device to bootloader. If device is powered off, press and hold Power + Volume Down button until tinkering Mi Bunny with "FASTBOOT" text appears.
Optional: Flash stock vbmeta with the following command (attached if needed):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Under same directory as TWRP image and ADB/Fastboot executables (if ever required), type this command:
Code:
fastboot flash recovery twrp-3.x.x-y-KudProject-grus.img
Where x and y are version of TWRP you're going to flash.
IMPORTANT: After flashing, immediately press and hold Power + Volume Up for about 10 seconds to reboot to recovery.
Swipe the option to allow modifications. This will prevent stock ROM from replacing recovery, however be aware that you might need to reflash stock vbmeta with disabled verity after that to be able to boot stock ROM!
Downloads
Webserver | MEGA
Old releases only: OSDN | AndroidFileHost
Known Issues
/dev/null
Special Thanks
Dees_Troy and everyone behind TWRP
Everyone on Mi 9 SE community
Device Sources
TWRP repository fork
Device tree
Kernel source
Changelogstwrp-3.5.2_9-1-KudProject-grus
Merged TWRP source changes up to 25 April 2021 (UTC+8)
Updated kernel to MoeSyndrome kernel based on Android 10
Mount firmware partition as read-only
Added support for formatting Cust partition in GUI
twrp-3.4.0-0-KudProject-grus
Merged TWRP source changes up to 22 June 2020 (UTC+8)
Supports decryption of userdata on Android 10-based MIUI and custom ROMs using Android 10 crypto blobs (might not be backwards compatible)
Restored system and vendor (non-image) backup support
Added support for backing up persist (and the image)
Build some blobs from source
Updated remaining blobs from V11.0.2.0.QFBEUXM
Updated prebuilt kernel to latest Pie
twrp-3.3.1-3-grus-20190802
Switched to source-built kernel
Updated blobs from MIUI China developer 9.7.4
Added support for F2FS in kernel (tell me if decryption breaks on this file system though)
Added persist into fstab
Added vendor-side touch firmware
Get CPU temperature from proper thermal zone
Disabled vbmeta checks
Only allow image backups for system and vendor
Symlinked /system to /system_root/system for backward compatibility
Misc stuffs
TWRP and f2fs-tools upstream changes
twrp-3.3.1-2-grus-20190609
Fixed wrong USB-OTG mount point
twrp-3.3.1-1-grus-20190603
Updated prebuilt kernel and DTBO from MIUI China developer 9.5.30
Corrected vendor image flashing
Support for wiping /vendor
Support for flashing and backup up (as part of boot) DTBO
Defined TW_SCREEN_BLANK_ON_BOOT
(Properly) excluded TWRP app
Included private recovery configuration
twrp-3.3.1-0-grus-20190531
Initial build.
Notes
Don't use fastboot boot to boot the recovery; it'll proceed to boot system instead using recovery's kernel. If this happens with your current kernel's boot image security patch being older than recovery one, you're basically busted as FBE keys are upgraded the time newer combination of system + vendor + boot image security patches are detected.
If you're out of luck in this situation, the only way to resolve is to format data (just backup your data to somewhere safe before doing so).
If you flash disabled vbmeta, you can't flash stock MIUI zips until the original vbmeta is restored.
Wrapped key support is added into recovery just for anticipation, although not defined by default in fstab.
I can't test it since EEA device so far is on March ASB as of V10.2.5.0 stable.
Otherwise, basic functionalities including decryption should work.
Edit: grus doesn't have anti rollback enabled at this moment, but Xiaomi may enable it in the future...
it is save changed from wzsx150 twrp ? or must on fastboot ?
bonbibonkers said:
it is save changed from wzsx150 twrp ? or must on fastboot ?
Click to expand...
Click to collapse
If already on any version of TWRP, just flash it using Flash Image option to recovery partition.
ok, gonna test it out , many thanks great work ??
Thanks! working so far so good
krasCGQ said:
If already on any version of TWRP, just flash it using Flash Image option to recovery partition.
Click to expand...
Click to collapse
Working fine when flashing from wzsx150 twrp version.
krasCGQ said:
If already on any version of TWRP, just flash it using Flash Image option to recovery partition.
Click to expand...
Click to collapse
i already flash it, worked good. but the CPU Temps is little misreading, i think.... it can go up to 80° C lol
rzki03 said:
i already flash it, worked good. but the CPU Temps is little misreading, i think.... it can go up to 80° C lol
Click to expand...
Click to collapse
Just ignore it. That same CPU temperature glitch also happens on sirius.
Wow, finally an *actual* twrp
Sent from my Mi 9 SE using Tapatalk
krasCGQ said:
Just ignore it. That same CPU temperature glitch also happens on sirius.
Click to expand...
Click to collapse
okay then. thank you!
@krasCGQ
Hey, in next release can you add the option to backup and recover dtbo partion/image like with this recovery https://forum.xda-developers.com/mi-9-se/how-to/recovery-twrp-lr-team-wzsx150-v3-3-0-t3926219 ?
Thanks
denzel09 said:
@krasCGQ
Hey, in next release can you add the option to backup and recover dtbo partion/image like with this recovery https://forum.xda-developers.com/mi-9-se/how-to/recovery-twrp-lr-team-wzsx150-v3-3-0-t3926219 ?
Thanks
Click to expand...
Click to collapse
So this release doesn't have Backup/Restore working?
luisbelmont said:
So this release doesn't have Backup/Restore working?
Click to expand...
Click to collapse
Yes, it has. My request was a bit different.
denzel09 said:
Yes, it has. My request was a bit different.
Click to expand...
Click to collapse
Oh, perfect! Thank you. What advantages does your request have?
luisbelmont said:
Oh, perfect! Thank you. What advantages does your request have?
Click to expand...
Click to collapse
To backup and recover dtbo image before and after flashed this custom kernel: https://forum.xda-developers.com/mi...nel-okitakernel-v1-0-mi-9-se-27-2019-t3934029
Thanks for the work! Great seeing you here after ZenFone 2 and Redmi Note 4. Hopefully a KudKernel will be in the works(if not already).
puppetminds said:
Thanks for the work! Great seeing you here after ZenFone 2 and Redmi Note 4. Hopefully a KudKernel will be in the works(if not already).
Click to expand...
Click to collapse
Kinda off-topic, but well rebasing over CAF is a tough job...
Sent from my Mi 9 SE using XDA Labs