Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Mi Mix 4
USB OTG will not work
Decrypting Android 12 will only work if you remove pin/password
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
thanks to : @erfanoabdi @Cozzmy13
Send me a beer: Crypto (Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_xiaomi_odinx
https://github.com/TeamWin/android_device_xiaomi_sm8350-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomimimix4.html
Awesome! I'm gonna test it in 4-5 days when I'm able to unlock bootloader on my Mix 4.
I'm on unofficial TWRP now. Can I just flash this over the old TWRP?
Mrdream94 said:
I'm on unofficial TWRP now. Can I just flash this over the old TWRP?
Click to expand...
Click to collapse
Yes, let me know how it goes
Nebrassy said:
Yes, let me know how it goes
Click to expand...
Click to collapse
Thanks for the reply. So I have to flash this TWRP over the old, then should I do something special?
Great job!
I will have a try!
doesnt work for me.
it boots to twrp but cant click anything.
looks like that
{
"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"
}
I can confirm that I'm getting the same issue as above. The unofficial builds were working fine.
schlubbi said:
doesnt work for me.
it boots to twrp but cant click anything.
looks like thatView attachment 5487057
Click to expand...
Click to collapse
ifredwu said:
I can confirm that I'm getting the same issue as above. The unofficial builds were working fine.
Click to expand...
Click to collapse
Are you two on stock?
Nebrassy said:
Are you two on stock?
Click to expand...
Click to collapse
Mine is on Xiaomi.eu stable.
ifredwu said:
Mine is on Xiaomi.eu stable.
Click to expand...
Click to collapse
If you can test contact me on telegram
Hi, I'm getting the same result as above. I'm currently on xiaomi.eu weekly
cartwheelbob3 said:
Hi, I'm getting the same result as above. I'm currently on xiaomi.eu weekly
Click to expand...
Click to collapse
Same as above, pm me if you can test
cartwheelbob3 said:
Hi, I'm getting the same result as above. I'm currently on xiaomi.eu weekly
Click to expand...
Click to collapse
Im on weekly too, but thats based on Android 12 for me, so that could explain it.
calledJona said:
Im on weekly too, but thats based on Android 12 for me, so that could explain it.
Click to expand...
Click to collapse
Yes, same. Are you able to access internal storage in TWRP? I haven't found a way to. Removed pin/fingerprint etc. I'm using the panda version TWRP
No, im not using it, beacause im on weekly, as far as i know TWRP doesnt really work with android 12
calledJona said:
Im on weekly too, but thats based on Android 12 for me, so that could explain it.
Click to expand...
Click to collapse
cartwheelbob3 said:
Yes, same. Are you able to access internal storage in TWRP? I haven't found a way to. Removed pin/fingerprint etc. I'm using the panda version TWRP
Click to expand...
Click to collapse
Given that I still got no testers who had this issue, I'll just post the build here, this is just a test build that will be removed later, if it worked, official version will be updated shortly, please let me know if display works correctly here
https://host.erwanleboucher.fr/nebrassy/TWRP/odinx/TWRP-3.6.0-odinx-1640017542.img
Nebrassy said:
Given that I still got no testers who had this issue, I'll just post the build here, this is just a test build that will be removed later, if it worked, official version will be updated shortly, please let me know if display works correctly here
https://host.erwanleboucher.fr/nebrassy/TWRP/odinx/TWRP-3.6.0-odinx-1640017542.img
Click to expand...
Click to collapse
It boots fine now, but touchscreen is not responsive. I just booted using fastboot as I can't access internal storage to attempt the ramdisk method
cartwheelbob3 said:
It boots fine now, but touchscreen is not responsive. I just booted using fastboot as I can't access internal storage to attempt the ramdisk method
Click to expand...
Click to collapse
Touch takes about a minute after gui starts to start responding, please try again and wait for it to work
Nebrassy said:
Touch takes about a minute after gui starts to start responding, please try again and wait for it to work
Click to expand...
Click to collapse
I've waited several minutes and touchscreen is still not responsive. Hopefully someone else can try to see if it works for them.
Related
It's enough, don't hide TWRP inside a ROM thread!
Built from source inside cm-13.0 source tree, always sync to upstream TWRP
Trusted, completely open (recovery changes, device tree, kernel, etc)
Currently use the new default TWRP theme
Qualcomm encryption support (untested, have no plan to encrypt my device)
Properly run AROMA Filemanager 2.00b7
Compatible to both old KitKat and new Lollipop bootloader (since 20160201 build, use updated kernel source but CM known not boot with the new bootloader)
Download Links:
AFH: twrp-3.0.2-0-wt88047-20160513.img
Source Code:
Device tree: https://github.com/kumajaya/android_device_wingtech_wt88047/tree/cm-13.0-twrp
TWRP source: https://github.com/omnirom/android_bootable_recovery/tree/android-6.0
Kernel source: https://github.com/CyanogenMod/android_kernel_wingtech_msm8916/tree/cm-13.0
{
"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"
}
Which version is this?
You sr. Allow me to translate it for my people language and post it as an addition?
(No theming works included for now)
Lennoard said:
Which version is this?
You sr. Allow me to translate it for my people language and post it as an addition?
(No theming works included for now)
Click to expand...
Click to collapse
As latest upstream version, 2.8.7.0 android-6.0 branch.
Good for all room sir ? I use cm 12.1 never try cm 13 coz have a bug camera
wow good work dude... you are the hero here.. lol
@ketut.kumajaya
Code:
TW_EXCLUDE_MTP := true
I need MTP. Is it because MTP is broken you disable or what?
nick37332001 said:
@ketut.kumajaya
Code:
TW_EXCLUDE_MTP := true
I need MTP. Is it because MTP is broken you disable or what?
Click to expand...
Click to collapse
Previously broken but get compiled now.
ketut.kumajaya said:
Previously broken but get compiled now.
Click to expand...
Click to collapse
So I guess can remove it since its fixed?
nick37332001 said:
So I guess can remove it since its fixed?
Click to expand...
Click to collapse
Yes, I'll revert it.
Build 20160101 available for download:
- Upstream TWRP changes
- Upstream CM 13.0 changes
- Re-enable MTP and confirmed works
- Updated kernel source
@Kuma, Is there any reason that the new twrp is not working when pressing Vol UP+Vol Down+Power. I tried many times. I always flash through fashboot. And how can i permanently flash new twrp based on CM 13. I tired from adb folder, but recovery from phone is not working. Only one recovery working perfectly from phone is TWRP2.8.7.1. But you are saying use the proper recovery for better experience.
My device is Redmi 2 (2014818).
rkpg said:
@Kuma, Is there any reason that the new twrp is not working when pressing Vol UP+Vol Down+Power. I tried many times. I always flash through fashboot. And how can i permanently flash new twrp based on CM 13. I tired from adb folder, but recovery from phone is not working. Only one recovery working perfectly from phone is TWRP2.8.7.1. But you are saying use the proper recovery for better experience.
My device is Redmi 2 (2014818).
Click to expand...
Click to collapse
Working for me. After the Tux logo, still no idea why TWRP splash screen not appear but blank screen and then main TWRP menu shown. You can flash recovery via fastboot using "fastboot flash recovery twrp-2.8.7.0-wt88047-20160101.img" command.
<noob> Sorry, I'm new to Redmi 2 </noob>
Now the question: I am not able to permanently flash the recovery using fastboot, though the phone can hotboot one ("tethered"). Whenever I flash a recovery and reboot to it, only stock MiRecovery comes in.
Does anybody know solution?
Vynikal said:
<noob> Sorry, I'm new to Redmi 2 </noob>
Now the question: I am not able to permanently flash the recovery using fastboot, though the phone can hotboot one ("tethered"). Whenever I flash a recovery and reboot to it, only stock MiRecovery comes in.
Does anybody know solution?
Click to expand...
Click to collapse
Use the command "fastboot boot twrp-2.8.7.0-wt88047-20160101.img" next to "fastboot flash recovery twrp-2.8.7.0-wt88047-20160101.img"
zhtengw said:
Use the command "fastboot boot twrp-2.8.7.0-wt88047-20160101.img" next to "fastboot flash recovery twrp-2.8.7.0-wt88047-20160101.img"
Click to expand...
Click to collapse
So which one should I use? As I said, I want to FLASH the recovery, not to boot it.
Vynikal said:
So which one should I use? As I said, I want to FLASH the recovery, not to boot it.
Click to expand...
Click to collapse
Pay attention to the phrase "next to".
I mean use the commands both.
First, fastboot flash recovery ***.img, it will flash your recovery partition;
then, fastboot boot ***.img, it will override your boot partition, and your MiRecovery will be replaced.
Build 20160111 available for download:
- Upstream TWRP changes
- Upstream CM 13.0 changes
- Updated kernel source
ketut.kumajaya said:
Build 20160111 available for download:
- Upstream TWRP changes
- Upstream CM 13.0 changes
- Updated kernel source
Click to expand...
Click to collapse
Hi om kuma, is the TWRP Possible to read primary storage at ur cm13? Cuz I format my external storage as primary storage but its not detected anywhere in TWRP, so its need a little trick to flash ur update etc. From recovery with limited...
ketut.kumajaya said:
Build 20160111 available for download:
- Upstream TWRP changes
- Upstream CM 13.0 changes
- Updated kernel source
Click to expand...
Click to collapse
Can I use it for Oneplus One (bacon) CM13?
{
"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"
}
We’re really excited to announce the release of Paranoid Android Pie betas.
On first launch, you’ll notice a clean setup with a beautiful wallpaper from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. For those who are unfamiliar, Hampus is a multi-disciplinary artist whose design stands itself and we’re glad to have him onboard. We also added further UI touches that we believe enhances the overall user experience.
The beta builds include adjustments and improvements on top of the stock Android CAF base. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features.
Download
Suzu
Suzu_ds - coming soon
Changelogs
Paranoid Android Blog
Requirements
* Required * you must have the latest OEM image from SODP
Formatting data (all user data is wiped) is a must if coming from another ROM.
Instructions
Flash latest OEM Image for Loire from here
Reboot to recovery (TWRP recovery)
Format /system, /data and /cache
Install AOSPA zip package
Install [optional] a Google Apps package of your choice Open GApps is advisable, but stock and super variants are not recommended!!!)
Install Magisk (advisable otherwise GApps may not work)
Help us improve PA by submitting good bug reports possibly with a log attached. Learn how to take logs here.
Our device maintainer for Xperia X is @tomgus1 Mention (@) me if you need some assistance and/or when reporting bugs.
Cheers and #StayParanoid!
Source Code: [url]https://github.com/sonyxperiadev/kernel[/URL]
Changelog:
032019
- widevine support
- wireguard in kernel
- kcal in kernel
- v6 oem support
- enforced selinux support
- improved boot times
- power hal improvements
- many kernel optimisations
Click to expand...
Click to collapse
21022019
Initial Beta release
Click to expand...
Click to collapse
Reserved 2
Reserved 3
Wow... Wasn't expecting this at all
I still didn't unlock my F5121 but now I'll really consider doing it...
Is everything working? WiFi, BT, Camera, NFC etc.?
Thanks
Sent from my F5121 using Tapatalk
Th3 Ant said:
Wow... Wasn't expecting this at all
I still didn't unlock my F5121 but now I'll really consider doing it...
Is everything working? WiFi, BT, Camera, NFC etc.?
Thanks
Sent from my F5121 using Tapatalk
Click to expand...
Click to collapse
All functions are working well. Just get back to me if you notice anything ?
ROM Screenshots please.
Dope.
Looking forward to the final ROM.
Thanks for the work!
I would like to install this rom. I know that is still a beta, but...
How is the battery life?
Important bugs? Is it ready for a daily use?
Guys! Really? I'm stunned! Great to see. Will flash as soon as possible and report if something wrong happens!!
3 time flashed this rom and Gapps (pico,nano) doesnt appear after boot
I have the same problem. (Gapps Micro)
lookmanns14 said:
3 time flashed this rom and Gapps (pico,nano) doesnt appear after boot
Click to expand...
Click to collapse
dobby5 said:
I have the same problem. (Gapps Micro)
Click to expand...
Click to collapse
guys i think u must first install busybox , after this flashing gapps maybe worked
Xperia Mini said:
guys i think u must first install busybox , after this flashing gapps maybe worked
Click to expand...
Click to collapse
Its works thx you
Xperia Mini said:
guys i think u must first install busybox , after this flashing gapps maybe worked
Click to expand...
Click to collapse
Edited: It works here..first flash the rom&oem...let it boot,then go to twrp and flash magisk after that install busybox,go to twrp again and flash gapps,reboot to system,done:good:
Ah sorry guys, I'll add that to the OP.
Personally I've been running this for a few months as daily and I'm pretty happy with it. We just never got round to building for suzu as I'd put in a stupid flag that was causing a 4-5 minute boot time. ?*
I sucessfully installed this ROM, to install gapps you need to make a full wipe, reboot to recovery then flash ODM img, ROM and finally gapps
If you want root flash magisk after the first boot, in my case the app wasnt installed so ive do it manually and it works
Also i made a logcat, hope can help you
Search in setting doesnt work & keep FC...anyone has the same problem...that's all bug I've noticed so far
realthrash said:
I sucessfully installed this ROM, to install gapps you need to make a full wipe, reboot to recovery then flash ODM img, ROM and finally gapps
If you want root flash magisk after the first boot, in my case the app wasnt installed so ive do it manually and it works
Also i made a logcat, hope can help you
Click to expand...
Click to collapse
Thanks for the feedback, I'll look into it.
lookmanns14 said:
Search in setting doesnt work & keep FC...anyone has the same problem...that's all bug I've noticed so far
Click to expand...
Click to collapse
We noticed this ourselves today. We have a fix already and will be included in our next build.
OrangeFox Recovery
Replace TWRP with OrangeFox once and you won't go back
Last update: 22 November 2020. Build 2
Changelog:
- Updated Magisk to 21.1 (now clicking install magisk after rom installation will install magisk 21.1)
- Update Magisk uninstaller to latest build
- fixed a bug where some people couldn't use flashlight option inside recovery
- fastened things up for faster installations and backup
- minor bug fixes
Contents:
Overview
Why OrangeFox?
Features
Screenshots
Links
Installation procedure
OVERVIEW:
Probably the most beautiful recovery out there.
Synced with the latest Teamwin changes.
Designed with latest Material design 2 guidelines.
Included customization.
Inbuilt patches, like Magisk and password reset patch.
Password protection.
Fully open-source.
Frequently updated.
Why OrangeFox?
OrangeFox has been operating for over two years. In that time OrangeFox have improved the quality, stability, and device support of the recovery. Today OrangeFox is the leader in stability, UI design, and UX. Installing OrangeFox means being with the latest code and fastest fixes.
:good: Treble & Non-Treble Support
:good: No compatibility.zip error while flashing OxygenOS
:good: A lot of customisations
:good: Extremely beautiful UI ready to please your eyes.
:good: Dev team is always ready to fix your problems
:good: F2FS support
There were previously 10.1 builds for these devices for these devices and this is how current build is different from them:
New, more modern UI.
Fixed F2FS support
Upstreamed to R11
and many more...
Note: Official soon I've applied for it.
Screenshots
Screenshots at https://imgur.com/a/Ai8KWX9 and on Sourceforge
Links:
Support group: https://t.me/orangefoxop5t
Download: https://github.com/Maitreya29/OrangeFox-OnePlus-5-T/releases
Installation procedure:
There are two methods to install OrangeFox
A) Via a recovery (for those with TWRP installed):
1. To install an OrangeFox zip, flash it with OrangeFox (or any TWRP-compatible custom recovery) without any wipes.
2. Do the same thing if you want to upgrade OrangeFox
3. When you flash an OrangeFox zip, there is no need to flash any DFE or any other such thing
4.To install an OrangeFox img file, boot into fastboot mode, and run the command: fastboot flash recovery OrangeFox-xyz.img
B) Via Fastboot (For those without a recovery):
You need a PC for this. If you do not have a PC, or access to a PC, then you are stuck!
1. Unlock your bootloader (if not already unlocked)
2. Install adb, fastboot and the relevant USB drivers onto your PCs)
3. Download the correct OrangeFox zip file to your phone, and to your PC
4. Extract recovery.img from the OrangeFox zip file, and copy recovery.img to your PC’s adb directory
5. Reboot your phone into fastboot/bootloader mode
6. Open up a command line window / terminal emulator on your PC
7. Change to the adb directory on your PC
8. Flash OrangeFox Recovery by using the fastboot flash recovery recovery.img command
9. Reboot into OrangeFox by pressing the power + volume down keys, until you see the OrangeFox splash screen
11. After OrangeFox has booted up, check that everything is working – eg, that it has mounted the data partition successfully, and that the touchscreen works.
12. Find and select the OrangeFox zip on your phone, tap on it, and swipe to install it (because OrangeFox Recovery needs some files from the zip)
After installation, the phone will automatically reboot into OrangeFox
Enjoy!
The download link at SourceForge is broken. It keeps redirecting to the devices folder.
sukesh1090 said:
The download link at SourceForge is broken. It keeps redirecting to the devices folder.
Click to expand...
Click to collapse
Thanks. Download link fixed.
Last update: 22 November 2020. Build 2
Changelog:
- Updated Magisk to 21.1 (now clicking install magisk after rom installation will install magisk 21.1)
- Update Magisk uninstaller to latest build
- fixed a bug where some people couldn't use flashlight option inside recovery
- fastened things up for faster installations and backup
- minor bug fixes
Last update: 22 November 2020. Build 2
Changelog:
- Updated Magisk to 21.1 (now clicking install magisk after rom installation will install magisk 21.1)
- Update Magisk uninstaller to latest build
- fixed a bug where some people couldn't use flashlight option inside recovery
- fastened things up for faster installations and backup
- minor bug fixes
Love the effort put into this! Fantastic choices for new and old users. Good job on the recovery. Looks stunning I'm sure you already knew that though.
Mr.Conkel said:
Love the effort put into this! Fantastic choices for new and old users. Good job on the recovery. Looks stunning I'm sure you already knew that though.
Click to expand...
Click to collapse
Haha thank you
Hello, does password encryption work with Android 11? Do you know or I should try and let you know? Recovery seems very nice. First time I changed from TWRP and I think I'll stay. Good Job!!
Edit: I know it says "Password Protection" in the main post. What I meant is can it decrypt with password?
deneimainoob said:
Hello, does password encryption work with Android 11? Do you know or I should try and let you know? Recovery seems very nice. First time I changed from TWRP and I think I'll stay. Good Job!!
Edit: I know it says "Password Protection" in the main post. What I meant is can it decrypt with password?
Click to expand...
Click to collapse
I have not tried it with a pin code but for me pattern encryption works it decrypts your device just fine.
Maitreya29 said:
Haha thank you
Click to expand...
Click to collapse
I wanted to mention that when fully customizing the recovery things can get really laggy making it difficult to use. I can't exactly tell the setting I had because I set everything to default for fluidity. However please work on the speed and smoothness!
Appreciate the work.
Mr.Conkel said:
I wanted to mention that when fully customizing the recovery things can get really laggy making it difficult to use. I can't exactly tell the setting I had because I set everything to default for fluidity. However please work on the speed and smoothness!
Appreciate the work.
Click to expand...
Click to collapse
Did you try rebooting into the recovery after you customised? I should also point out the recovery doesn't utilise a phone's complete power. It's limited so there are always no animations and everything feels sudden, that's a limitation for twrp Ofox and everything else I've used.
Maitreya29 said:
Did you try rebooting into the recovery after you customised? I should also point out the recovery doesn't utilise a phone's complete power. It's limited so there are always no animations and everything feels sudden, that's a limitation for twrp Ofox and everything else I've used.
Click to expand...
Click to collapse
Well yes, of course. Everything seems to work fine after a few minutes but still very laggy at start and that can be a bit annoying for things like pattern lock and such. I'm not runny any customizations as of now things work good.
Tried PIN and it doesn't decrypt. It's no problem, got used to it(lol) but I'm just letting you know.
deneimainoob said:
Tried PIN and it doesn't decrypt. It's no problem, got used to it(lol) but I'm just letting you know.
Click to expand...
Click to collapse
Only patterns work on Android 11. That's normal
Maitreya29 said:
Only patterns work on Android 11. That's normal
Click to expand...
Click to collapse
I wanted to consult your team and members about a possible OrangeFox Recovery and a Rom A10 or A11 for a seperate device not OnePlus 5T. If you are interested, Pm me. Or message me on Telegram @MrConkel Payment is available for this project but is very limited. More details can be discussed after you pm or message me. Appreciate your time..
I like this recovery. It works with encryption in android 10. However, it did not work with encryption in android 11! Is it only me?
Hello!
Received an Oneplus 5T from China a few days ago, (still) running OxygenOS 9.0.9 A5010_43_191008. Gonna install some custom ROM as usual, so just unlocked its bootloader.
Saw this post about OrangeFox recovery, and considering what I've been reading in the [OFFICIAL][RECOVERY] [TWRP] TWRP for OnePlus 5T thread I feel like I'm going to put my faith in this recovery.
I have a question, though. According to what I read in the TWRP thread, the custom recovery gets killed by the stock ROMs. Is this serious?
{
"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"
}
Just
curiosity. I guess that means I should straight install my custom ROM of choice just after the recovery, period.
Merry Christmas and Happy New Year, by the way.
P.S.: Just saw there's a more recent thread about this recovery, [RECOVERY] [OFFICIAL] OrangeFox Recovery for OnePlus 5T. Will more properly repost this there, sry.
{
"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"
}
Released: 04/30/22
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
"This is a user friendly thread, all your suggestions are important to us and will be taken into consideration.."
"keep in mind this will wipe everything so always backup your stuff"
Instructions :
To flash any custom Rom to the moto g6 ali the first thing you need is to unlock the boot loader,
instructions in PTBR and ENG can be found HERE
Once you have your boot loader unlocked you will need to flash the 64bit version of TWRP recovery
as all custom ROM's for this device are 64bits except the stock Rom,
-> Download
To flash TWRP or OrangeFox recovery:
You will need adb and fastboot (and adb/fastboot drivers) installed to your PC
Put your phone in fastboot mode, plug it to the PC and use this commands:
To temporarily boot the recovery
fastboot boot recovery.img
To install permanently
fastboot flash recovery recovery.img
to reboot to recovery
fastboot reboot recovery
To flash lineage or any other custom ROM:
Format Data, type "yes" without quotes
then select everything except Micro SD card and USB OTG
and Swipe to wipe
keep in mind this will wipe everything so always backup your stuff.Download the latest Lineage build and gapps (ARM64-Version!) and place them ,
in your SD card,
tap on the ROM name, and "Swipe to confirm Flash",
Once that is done tap on "Wipe Cache/Dalvik" and Swipe to wipe, tap on back then select your gapps if you want gapps and flash it "Wipe Cache/Dalvik" again and reboot system.
* LineageOS
* Download-Vanilla
Changelog:
* April Security patch
* Signature Spoofing
* Donate
* Custom-Boot-Logos
Credits:
• @jeangraff30 For the source and much more
• All the people who helped me test
By @Broly
Follow @MotoG6update
Can't wait what gapps do you suggest?
raven.warsong said:
Can't wait what gapps do you suggest?
Click to expand...
Click to collapse
I'm using nikgapps core my favorite
Works pretty great so far. Thanks.
Cant get fingerprint navigation working though
zwackelmannnn said:
Works pretty great so far. Thanks.
Cant get fingerprint navigation working though
Click to expand...
Click to collapse
thanks for testing I'm working on it.
Is there anyway to upgrade from LOS17.1 and restore all Apps, Apps, etc?
orhan_drsn said:
Is there anyway to upgrade from LOS17.1 and restore all Apps, Apps, etc?
Click to expand...
Click to collapse
Unfortunately no way to upgrade it has to be clean install.
Updated the links with new build.
What sources are you using OP? I am trying to build 18.1 but failing, I need Signature Spoofing support, but first I am trying to build an unofficial stock build. Unfortunately, I believe I am using the wrong sources or lacking one or two.
Thanks in advance.
CENTSOARER said:
What sources are you using OP? I am trying to build 18.1 but failing, I need Signature Spoofing support, but first I am trying to build an unofficial stock build. Unfortunately, I believe I am using the wrong sources or lacking one or two.
Thanks in advance.
Click to expand...
Click to collapse
I'm using same source as pixelexperience ROM, https://github.com/Broly1/local_manifests/blob/lineage18.1/romservice.xml
Broly said:
I'm using same source as pixelexperience ROM, https://github.com/Broly1/local_manifests/blob/lineage18.1/romservice.xml
Click to expand...
Click to collapse
Ah, thank you! I just couldn't find a couple of them. No wonder why it was failing to build.
bootloop after flash
ironwolf115 said:
bootloop after flash
Click to expand...
Click to collapse
Worked OK for me.
I flashed this rom and android need password....And i found solution for bootloop, data and cache partitons only works with ext4 in 2021.... but RROS on 10 not have this problem...
Hi, I know it sounds stupid but I can't find the installation instructions to flash this rom. A long ago , I used to flash custom roms on my Galaxy Ace gts-5830i and there was step by step instructions for every rom like which recovery to use, which partition to wipe etc. Where has those instructions been moved??
puffedrice said:
Hi, I know it sounds stupid but I can't find the installation instructions to flash this rom. A long ago , I used to flash custom roms on my Galaxy Ace gts-5830i and there was step by step instructions for every rom like which recovery to use, which partition to wipe etc. Where has those instructions been moved??
Click to expand...
Click to collapse
Intructions are alway the same. Flash recovery. Flash the Rom and Gapps if you want them.
Any further experiences, reports, or updates for stock lineage?
B2Pi said:
Any further experiences, reports, or updates for stock lineage?
Click to expand...
Click to collapse
fixed
Broly said:
To be honest I gave up on lineage can't get the fingerprint gestures to work and there are other annoyance to it, right now I'm focusing on AEX and ArrowOS, also made a havoc build but won't even post them here.
Click to expand...
Click to collapse
That's unfortunate. I've been using resurrection, but that is now unsupported, and my recent button isn't working. I like the vanilla-ness of it.
Which do you recommend?
B2Pi said:
That's unfortunate. I've been using resurrection, but that is now unsupported, and my recent button isn't working. I like the vanilla-ness of it.
Which do you recommend?
Click to expand...
Click to collapse
Forget what I've said just updated the lineage Rom, finally learned how to fix the fingerprint gesture, the link already has been updated to the new one.
{
"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"
}
" #DroidOnTime "
dotOS is an Android ROM which focuses on performance and stability. We focus on making our rom look and feel great without struggling on Performance and Battery! So that one can get most out of his/her device.....
ROM Version:
5.0.1
Device: pine
Maintainer: AOiSPdev
Build Status: Unofficial
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
- You must be on a 64bit custom recovery
- Download latest dotOS build
- Format data
- Wipe /system , /vendor , /data , /cache
and /dalvik
- Flash ROM zip
- Flash GApps and Magisk (optional)
- Reboot and Enjoy!
Download
64bit custom recovery:
1) TWRP
2) OrangeFox
3) PitchBlack
Device Maintainer:
@AOiSPdev
Credits:
@YaAlex
Joel for 64bit OrangeFox and TWRP recovery
& all the testers
for personal questions and extra support join the telegram group I can't help on XDA Thread much as I am always busy...
Telegram Support Group
Like this thread, if you appreciate my work. Thanks in Advance!
Sources:
Kernel source
DotOS Source
Reserved.
Is it permissive or enforcing?
Would flashing an SD card as a internal memory mess with any functionality?
dalda123 said:
Is it permissive or enforcing?
Click to expand...
Click to collapse
Enforcing
TheyCallMeAnon said:
Would flashing an SD card as a internal memory mess with any functionality?
Click to expand...
Click to collapse
Setup SD card as external storage
Deep sleep seems to be broken.
Also howndo you pin apps so they don't get killed when you press 'clear all' in the manager?
The audio jack its not working for me
Edit: The problem was a modification on the mixer_patchs files that an app did.
Putting the backups files on the directory make that works again.
Any problems Wifi? or similar?
i tried all the other ROMs some time back and all of them after reboot straight didnt turn on wifi so im sticking with stock rom for now if someone can confirm this ill try it out thx
mike500005 said:
Any problems Wifi? or similar?
i tried all the other ROMs some time back and all of them after reboot straight didnt turn on wifi so im sticking with stock rom for now if someone can confirm this ill try it out thx
Click to expand...
Click to collapse
Right now, no problem that i casue xD, the wifi it's working well, the data i can't say because i didn't use, the speaker i think that it's a lite weak, that's why i try to use a mod to get a lite louder and get some problems xD
Always you can backup everything on your rom or stock with your prefer recovery and try other rom, if the rom doesn't seen enough for you, just restore.
Nice rom but I keep getting this internal problem every time I reboot my phone. Is this normal or I am missing something? Otherwise it seems to be functioning fine?
Giremo said:
Nice rom but I keep getting this internal problem every time I reboot my phone. Is this normal or I am missing something? Otherwise it seems to be functioning fine?
Click to expand...
Click to collapse
Just ignore that warning. I'll fix it on next build
any chance of including a stock calendar app?
also, the in-cable headphones control seems to be incomplete, only 1 buttons is working, I am able to play/pause only using the 'lower volumen' button, tried with multiple headphones.
AOiSPdev said:
Setup SD card as external storage
Click to expand...
Click to collapse
Sorry what does it mean? It is possible to use the SD card to extend internal memory? My son is on official firmware and the internal memory full messages are really annoying
Used this rom for quite a while with a couple of reboots. Now the phone somehow tells me that my SD card has an issue again. I tried setting it up as portable storage as usual but it won't let me without having to format it. The sd card itself still works fine tho in the recovery. Now the internal storage is also treated as full as well in play store and won't even let me access it in the file manager like as well.
Edit: False alarm It's just one of magisk module drm remover that causes this issue
Ranfiel said:
Right now, no problem that i casue xD, the wifi it's working well, the data i can't say because i didn't use, the speaker i think that it's a lite weak, that's why i try to use a mod to get a lite louder and get some problems xD
Always you can backup everything on your rom or stock with your prefer recovery and try other rom, if the rom doesn't seen enough for you, just restore.
Click to expand...
Click to collapse
Yea hasn't worked that well backup and restore with TWRP so maybe if I try another one out idnk why
mike500005 said:
Yea hasn't worked that well backup and restore with TWRP so maybe if I try another one out idnk why
Click to expand...
Click to collapse
You can try OrangeFox or PitchBlack recovery backup, maybe one of those work
does it work on redmi 7a 32 bit ?
itmasen1 said:
does it work on redmi 7a 32 bit ?
Click to expand...
Click to collapse
Well using this custom rom will automatically make your rom 64 bit mate. It just requires you to use those Custom Recovery Recommended above to have it successfully installed along with the instructions provided.
Giremo said:
Well using this custom rom will automatically make your rom 64 bit mate. It just requires you to use those Custom Recovery Recommended above to have it successfully installed along with the instructions provided.
Click to expand...
Click to collapse
thank you i will do my test after.