{
"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"
}
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.
Code:
* [B][U]Your warranty is now void.[/U][/B]
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Odin
- Odin3 v3.13.3
Heimdall
- Glass Echidna
TWRP for Samsung Galaxy Note 3 (Americas, China, Europe & Korea)
How to flash TWRP with Odin1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu. Alternatively, power it off and press the Power, Volume Down, and Home buttons simultaneously. When the blue screen appears, release all 3 buttons and press Volume Up.
2. In Odin, import the appropriate twrp.tar file for your variant with the "AP" and press the "Start" button.
3. Pull the battery as soon as your phone vibrates.
4. You can then boot directly into TWRP by pressing the Power, Volume Up, and Home buttons simultaneously. Release all three buttons as soon as you see the boot screen ("Samsung Galaxy Note3").
How to flash TWRP within a previous version of TWRP1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Recovery" from the Restart menu. Alternatively, power it off and press the Power, Volume Up, and Home buttons simultaneously. Release all 3 buttons when the boot screen appears ("Samsung Galaxy Note3").
2. In TWRP, tap "Install" then "Install Image".
3. Navigate in the folder structure to the location of the appropriate twrp.img file for your variant and tap it.
4. Select the "Recovery" radio button.
5. Move the slider to the right to flash the TWRP image.
6. Tap "Reboot System" or, alternatively, tap the back arrow 3 times to return to the main menu, then tap "Reboot" and "Recovery" to reboot into the TWRP image you have just flashed.
Changelog
- See post #2.
Bugs
- You tell me!
Credits
- JCrossleyBrook for feedback and screenshots.
- ashyx, jcadduono, haggertk, and every other open source developer and user who contributes directly or indirectly to the TWRP community in the development of and in providing feedback for the hlte and hltechn.
Sources
- hlte repository
- hltechn repository
- msm8974 kernel repository
- TWRP repository
XDA:DevDB Information
TWRP 3.5.2_9-0, ROM for the Samsung Galaxy Note 3
Contributors
ripee
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-0
Stable Release Date: 2021-04-06
Created 2018-02-08
Last Updated 2022-12-09
Reserved
CHANGELOG
3.2.1-1: The test build from TeamWin is here!
* My thanks to everyone who tested my attempts at resurrecting TWRP on the Note 3
* Please test both the IMG and TAR file, you can flash the test build over top of my unofficial build. Please report any changes in stability and functionality compared with my last build, formerly known as v4.
Reserved
Why new thread?
Sent from my Galaxy Note 3 using XDA Labs
banikgames said:
Why new thread?
Sent from my Galaxy Note 3 using XDA Labs
Click to expand...
Click to collapse
So that users can give me feedback more directly, and because I created my own source repo from which I build. The latest one on the TeamWin account is kind of outdated already, which could be why the official 3.2.1-0 is giving problems.
Have you tried my 3.2.1-1 build? Does it flash, boot, ...work? Does it recognize your SD card when formatted in NTFS, exFAT, and FAT32?
I flashed it but my phone cannot boot into system and recovery.
Must flash back old recovery through odin.
can i use aroma gapps using this twrp?
junio07 said:
aroma gapps can be flash using this
Click to expand...
Click to collapse
I don't see why not, please report back either way.
also does not work for me.
a newer TWRP version than 2.8.7.0 with aroma support. That's all we're waiting since years
MarkusOSx said:
also does not work for me.
a newer TWRP version than 2.8.7.0 with aroma support. That's all we're waiting since years
Click to expand...
Click to collapse
Thank you very much for mentioning that version 2.8.7-0 was the last known good one. I took a look at it's source branch and it seems that the partition sizes and bootimage arguments were way off compared with even the values in the lineage 14.1 hlte-common repo.
I just re-built so please try what's up now in the OP link.
Unless I provide different links, everything will be in the OP, and old builds will be overwritten by new ones.
ripee said:
Thank you very much for mentioning that version 2.8.7-0 was the last known good one. I took a look at it's source branch and it seems that the partition sizes and bootimage arguments were way off compared with even the values in the lineage 14.1 hlte-common repo.
I just re-built so please try what's up now in the OP link.
Unless I provide different links, everything will be in the OP, and old builds will be overwritten by new ones.
Click to expand...
Click to collapse
Doesn't boot.
Goes straight into Download mode saying "Could not do normal boot" when trying to access recovery.
Flashing back to the official 3.2.1.0 works fine. It's a tad slow and unresponsive and VERY slow in restoring a Nandroid backup but it works fine for me.
EDIT: I just remembered.. Jairus980 has a TWRP 3.1.1.0 with theme and all that works incredibly well. Shame he hasn't updated it to 3.2.1.0 or 3.2.1.1 yet. Maybe check out his recovery to see what he did different?
You can find it on his AFH. I don't really wanna link to it directly without permission lol.
same. dont boot with this.
m3rishor said:
same. dont boot with this.
Click to expand...
Click to collapse
you try install also via twrp?
vagenrider said:
you try install also via twrp?
Click to expand...
Click to collapse
off course. Both way. Twrp and odin. Revert with odin at 3.1.1.0 and after from twrp to 2.8.7.0 to flash AryaMod. Any Nougat dont detect SIM, and i flash diferent modem/efs
Dont work
Doesn't boot.
Goes straight into Download mode saying "Could not do normal boot" when trying to access recovery.
Same here
New attempt is up now.
How about what's under the link in the OP now? Any difference?
sorry late with this....
SM-N9005ZWEBTU
was on official 3.2.1.0
Kernel 34113 Xenial 26x
Bootloader GBQE1
Baseband GPQB1
Rom RR 585 01012018
Updated to 3.2.1.1 v1 (believe its on v3 now) and all is good. Phone feels faster
not work...
bootloader bqe1
modem boa2
JCrossleyBrook said:
sorry late with this....
SM-N9005ZWEBTU
was on official 3.2.1.0
Kernel 34113 Xenial 26x
Bootloader GBQE1
Baseband GPQB1
Rom RR 585 01012018
Updated to 3.2.1.1 v1 (believe its on v3 now) and all is good. Phone feels faster
Click to expand...
Click to collapse
You mean my current twrp 3.2.1-1 that's on my BasketBuild now? I'm not keeping track of revision numbers since the changes are minor, and anyway code that doesn't work won't serve as the basis for future development.
Can you please let us know if you are able to create and restore backups, both encrypted and unencrypted, on my twrp 3.2.1-1? Does your phone recognize your SD card when it's formatted in NTFS, exFAT, and FAT32?
On another note, thanks for referencing your bootloader and baseband, I didn't realize the ones I uploaded were outdated. I will update my .tar file as well.
Edit: latest bootloader and modem are up.
vagenrider said:
not work...
bootloader bqe1
modem boa2
Click to expand...
Click to collapse
Please try the latest bootloader and modem combination. will edit this post to let you know when they're available in my BL_CP folder on BasketBuild.
ripee said:
You mean my current twrp 3.2.1-1 that's on my BasketBuild now? I'm not keeping track of revision numbers since the changes are minor, and anyway code that doesn't work won't serve as the basis for future development.
Can you please let us know if you are able to create and restore backups, both encrypted and unencrypted, on my twrp 3.2.1-1? Does your phone recognize your SD card when it's formatted in NTFS, exFAT, and FAT32?
On another note, thanks for referencing your bootloader and baseband, I didn't realize the ones I uploaded were outdated. I will update my .tar file as well.
Please try the latest bootloader and modem combination. will edit this post to let you know when they're available in my BL_CP folder on BasketBuild.
Click to expand...
Click to collapse
It does exactly the same. Straight to DL mode with Could not do normal boot error.
Im on QD1 loader and QB1 baseband. The nordic ones that fix the Nougat SIM issues.
Related
Team Win Recovery Project 3.0.2-0
This is for the International Exynos SM-N900XX model only! Do not flash on Qualcomm models!
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxynote3internationalexynos.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
FULL STEPS FOR OBTAINING ROOT
Extract Odin_3.10.7.zip to your computer.
{
"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"
}
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for ha3g.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot without touching any other options, then press [Start].
Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery.
At this point, you will reach the screen asking you if you want to allow system modifications.
You will want to swipe to allow, otherwise the OS will replace TWRP once you boot!
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-0 - Initial build on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/TeamWin/android_device_samsung_ha3g (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_ha3g (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy Note 3 (Exynos), Tool/Utility for the Samsung Galaxy Note 3
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/jcadduono/android_device_samsung_ha3g
Version Information
Status: Beta
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-07-01
Created 2016-06-27
Last Updated 2016-07-01
Thank u very much for new twrp for our n900 device. Its the best recovery from all others & full compatible. You save my life. Thank you for great work .
jcadduono can you make kernel 6.0 for n900. Tks
Sent from my SM-N920K using Tapatalk
@jcadduono thank you. very good working.
Zip download:
http://turbobit.net/e20dbqyg7l12.html
chienduongvan said:
jcadduono can you make kernel 6.0 for n900. Tks
Sent from my SM-N920K using Tapatalk
Click to expand...
Click to collapse
sorry no interest in kernel dev on a device i don't own
thanks
bellal11 said:
thanks
Click to expand...
Click to collapse
Can you uploaf to MEGA?THANKS!!
rakee said:
Can you uploaf to MEGA?THANKS!!
Click to expand...
Click to collapse
seriously? it's 6 MB and direct download, what's the issue?
jcadduono said:
seriously? it's 6 MB and direct download, what's the issue?
Click to expand...
Click to collapse
I cant download it
rakee said:
I cant download it
Click to expand...
Click to collapse
rakee said:
Can you uploaf to MEGA?THANKS!!
Click to expand...
Click to collapse
https://mega.nz/#!1ttwgBYC!Hv-oU87LktSOPrxOsnceo31gRJfBNlpsjytoFsOSWog
mega link mate :good:
PaYDaY said:
https://mega.nz/#!1ttwgBYC!Hv-oU87LktSOPrxOsnceo31gRJfBNlpsjytoFsOSWog
mega link mate :good:
Click to expand...
Click to collapse
Thanks,mate:angel:
rakee said:
Thanks,mate:angel:
Click to expand...
Click to collapse
you are most welcome
Using this screen flicker, why??
Hello @jcadduono,
I am in Stock Lolippop and flashed this recovery without succeed.
Could you please help !
Now, I couldn't start my phone.
Thanks,
Thinh
lyduythinh said:
Hello @jcadduono,
I am in Stock Lolippop and flashed this recovery without succeed.
Could you please help !
Now, I couldn't start my phone.
Thanks,
Thinh
Click to expand...
Click to collapse
Are you flashing it on the correct device? Do you have ha3g? Following the instructions in the thread?
New official build is up on twrp.me now (3.0.2-0), it is 6.5 MB, if you have any other size then it's the wrong one!
@jcadduono Perfect. I downloaded another size of "twrp-3.0.2-0-ha3g.img.tar" (8.5MB).
I downloaded it in here.
Thank you very much. I got TWRP.
Thinh
@jcadduono I downloaded the .tar file but the format of file is .tar.md5 is it correct? ? I wanted to flash it whit Odin
آرین said:
@jcadduono I downloaded the .tar file but the format of file is .tar.md5 is it correct? ? I wanted to flash it whit Odin
Click to expand...
Click to collapse
twrp-3.0.2-0-ha3g.img.tar 6.5M This file guy.
BR,
Thinh
This is not the official file from twrp website? I downloaded one from the official, flash it, can not boot. Is it the different file? Thanks
xcal_tau said:
This is not the official file from twrp website? I downloaded one from the official, flash it, can not boot. Is it the different file? Thanks
Click to expand...
Click to collapse
They should be the same, only build fingerprint differs, both are 6.5 MB as of yesterday.
(official one was broken 2 days ago)
RYAN SHAY said:
@jcadduono I downloaded the .tar file but the format of file is .tar.md5 is it correct? ? I wanted to flash it whit Odin
Click to expand...
Click to collapse
tar is the same as tar.md5 for Odin. md5 just means it has a hash attached to the tar so Odin can make sure it's not corrupt (safer to flash than tar)
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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CHANGELOG for 3.0.3-0:
Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
Add Greek translation to some builds.
support new CM 13.0 pattern encryption (sultanqasim)
fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
libtar updated to latest upstream and fixes (jcadduono)
fixes for loading custom themes (_that)
TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
translation updates - added Italian, Czech and Polish and significant updates to Dutch
progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
fix input box text display (Dees_Troy)
reboot option after zip install complete (bigbiff)
other mostly invisible bug fixes and improvements
Install guide:
Install fastboot tools from google's sdk on your PC
Enter fastboot mode
Unlock your bootloader
Download recovery*.img and Lazyflasher
Copy lazyflasher In your internal Phone memory
Run fastboot flash recovery twrp-3.0.3-0-markw.img in command line
[*]Boot into recovery and flash Lazy flasher (Important for miui, else you can boot into system)
Reboot and enjoy it
Download:
twrp-3.0.3-0-markw.img
lazyflasher-no-verity-opt-encrypt.zip
Wow new TWRP build, btw I see you try to build LineageOS 13 (even msdx321 fork from your repo), thanks
Wow, this one is better than Cofface's TWRP.
Subscribe sir @Anik_khan...GIMEE !!!
Sent from my Redmi 3 using Tapatalk
@Anik_khan, thank God you're working for redmi 4 prime now! I was amazed by your redmi 3 ROMs. I hope you will create some ROM for R4P! Godbless you Sir!
Much better than before
Thanks, I am excited to see new TWRP for Redmi 4 Prime!
So, is this better than the one made by cofface? In what ways?
Can i flash this zip file to replace the twrp by cofface using twrp by cofface itself? And one more question.. When i want to go to recovery from off, when i press the up n power button it went to the stock recovery instead of the twrp and i need to select recovery for me to go to twrp.. .. Is there any solution for me to straight away go to twrp after pressing the combination button? Pleasee help... Im still using miui 8 and looking to try on lineage os.... Thanks in advance
nudgemodem said:
Can i flash this zip file to replace the twrp by cofface using twrp by cofface itself? And one more question.. When i want to go to recovery from off, when i press the up n power button it went to the stock recovery instead of the twrp and i need to select recovery for me to go to twrp.. .. Is there any solution for me to straight away go to twrp after pressing the combination button? Pleasee help... Im still using miui 8 and looking to try on lineage os.... Thanks in advance
Click to expand...
Click to collapse
Yes you can flash this TWRP.img straight using Cofface's TWRP(that's what i did before), but don't forget to reboot to recovery after flashing the img. After that flash the attached zip file lazyflasher and your good to go.. About your second question, i don't know if there's some kind of shortcut to go straight to recovery(a simple single tap wouldn't matter anyway), as for lineageos, i haven't tried it yet so no idea, but imo i still prefer stock rom over custom rom for less bug free experience.
Tapped from my Redmi 4 Prime using XDA Legacy
---------- Post added at 09:00 PM ---------- Previous post was at 08:56 PM ----------
brenyoka said:
Thanks, I am excited to see new TWRP for Redmi 4 Prime!
So, is this better than the one made by cofface? In what ways?
Click to expand...
Click to collapse
What i like about this new twrp is you can now mount/wipe system partition. Compare to cofface's twrp, you can't do those. [emoji3]
Tapped from my Redmi 4 Prime using XDA Legacy
nudgemodem said:
Can i flash this zip file to replace the twrp by cofface using twrp by cofface itself? And one more question.. When i want to go to recovery from off, when i press the up n power button it went to the stock recovery instead of the twrp and i need to select recovery for me to go to twrp.. .. Is there any solution for me to straight away go to twrp after pressing the combination button? Pleasee help... Im still using miui 8 and looking to try on lineage os.... Thanks in advance
Click to expand...
Click to collapse
You can flash directly from cofface by using install menu and press image button on right bottom to flash .img instead of zip
Just wanted to say that this is the best recovery for Redmi 4 Prime. No bugs, no problems with mounting partitions, no hassle. Thank you very much, Anik_khan
Sorry for the noob question, but why lazyflasher is necessary? I am using MIUI global (v8.1.2). What happens if I don't flash lazyflasher? Just curious. Thanks.
brenyoka said:
Sorry for the noob question, but why lazyflasher is necessary? I am using MIUI global (v8.1.2). What happens if I don't flash lazyflasher? Just curious. Thanks.
Click to expand...
Click to collapse
Likely wont boot since official firmware need to verify dex-opt (it supposed to be installed in official xiaomi recovery). However xiaomi eu rom will work just fine.
dels07 said:
Likely wont boot since official firmware need to verify dex-opt (it supposed to be installed in official xiaomi recovery). However xiaomi eu rom will work just fine.
Click to expand...
Click to collapse
Thanks. I am on official MIUI so I will flash lazyflasher as well.
any usb mtp bugs ?
azizkaka said:
any usb mtp bugs ?
Click to expand...
Click to collapse
MTP works great with no bugs in my case. I'm using xiaomi.eu btw.
Tapped from my Redmi 4 Prime using XDA Legacy
thank you
flash twrp done
now how to root ? plz links to download
no usb mtp after root
how to fix it ?
supersu v2.65 works without problem
In my opinion, this is the best TWRP for REDMI 4 Prime. Everything works.
Introduction
{
"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"
}
MultiROM is one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
You can install it either from MultiROM Manager app or from this guide:
MultiROM has 3 parts you need to install:
MultiROM - download the ZIP file from second post and flash it in recovery.
Modified recovery - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/vasishath/multirom/commits/android-8.1 (branch master)
Modified TWRP - https://github.com/vasishath/android_bootable_recovery/commits/android-8.1-mrom (branch master)
Thanks a lot to Tasssadar for creating this awesome utility.
XDA:DevDB Information
Multirom, ROM for the Xiaomi Redmi Note 5 Pro
Contributors
Shahan_mik3, vasishath
Source Code: https://github.com/vasishath/multirom/commits/android-8.1
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: Multirom TWRP
Version Information
Status: Alpha
Beta Release Date: 2018-03-28
Created 2018-03-19
Last Updated 2018-07-28
Download Link
https://androidfilehost.com/?w=files&flid=257990
Contents:
Multirom Zip
Multirom uninstaller
Multirom TWRP
NOTE: TWRP ZIP is not FLASHABLE. Extract the img and flash it.
One more for backup
Shahan_mik3 said:
One more for backup
Click to expand...
Click to collapse
@vasishath @Shahan_mik3
You guys are great.. thanks for greeting us with your amazing work and dedication..
It support oreo roms too??
@ki said:
It support oreo roms too??
Click to expand...
Click to collapse
ATM no. But will be adding soon
Thread cleaned up.
If you have an issue with a member or any source related please use the report button. No need to drag the thread off-topic please.
Also a quick read of XDA-Developers and the GPLhttps://www.xda-developers.com/xda-developers-and-the-gpl/ won't hurt
Regards,
The Arrow
The Arrow said:
Thread cleaned up.
If you have an issue with a member or any source related please use the report button. No need to drag the thread off-topic please.
Also a quick read of XDA-Developers and the GPL won't hurt
Regards,
The Arrow
Click to expand...
Click to collapse
Thanks appreciate it
@Shahan_mik3 ........switched from mi3/mi4 to note 5 pro huh?? :silly:
Tactical1997 said:
@Shahan_mik3 ........switched from mi3/mi4 to note 5 pro huh?? :silly:
Click to expand...
Click to collapse
Nah...we r using one device for development so it takes time to work and test on it.
May this guide will help others
EDIT: Nevermind, found my mistake, There IS an uninstaller zip
I dont want to be a spoilsport but think twice before installing multirom, If you want to remove it in the future you need an unistaller zip which never gets released for unofficial devices. I did this with my mi pad and i really regret installing multirom as i dont want it anymore but cant remove it. So just be sure that you really want it.
Please correct me if i have missed out anything or i am wrong in my statements.
robenn said:
I dont want to be a spoilsport but think twice before installing multirom, If you want to remove it in the future you need an unistaller zip which never gets released for unofficial devices. I did this with my mi pad and i really regret installing multirom as i dont want it anymore but cant remove it. So just be sure that you really want it.
Please correct me if i have missed out anything or i am wrong in my statements.
Click to expand...
Click to collapse
Let's say completely wrong. Chk op 2nd post
Shahan_mik3 said:
Let's say completely wrong. Chk op 2nd post
Click to expand...
Click to collapse
Oh sorry! Dont mind me, Great job on planning ahead !
Wip...miui 9 Oreo, aosp gsi, Los what more do u want in life :cyclops:
Shahan_mik3 said:
Wip...miui 9 Oreo, aosp gsi, Los what more do u want in life :cyclops:
Click to expand...
Click to collapse
A wish that everything I wish would be granted
Sent from my mido using XDA Labs
So can this works on redmi note5 China version？
It's based on Android 8.1
DukeG said:
So can this works on redmi note5 China version？
It's based on Android 8.1
Click to expand...
Click to collapse
After we release the update it should
Shahan_mik3 said:
After we release the update it should
Click to expand...
Click to collapse
Fine, I'll wait for it.
@Shahan_mik3
Thug pro
{
"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"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
https://drive.google.com/open?id=10i5ddHcV0lt8JJ7nV1bJjqc1XXjLCp8n
Note this is just a hobby, but feel free to report bugs.
Kernel source: Prebuilt stock kernel
Boot to fastboot ( volume down and power )
in fastboot type:
Link comes later when stable
fasboot reboot and hold power up and volume
Click to expand...
Click to collapse
Note: this twrp is working with the orginal system, when ota happens just flash twrp again.
BUGS:
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Contributors
@bassbounce ( Compiled )
@Manish4586 ( Device tree )
Device tree: https://github.com/Manish4586/android_device_xiaomi_jasmine-twrp
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information:
Status: testing
Created 17-9-2018
Last Updated 17-9-2018
Nice! So this is supposed to work without A/B conflicts - unlike the other TWRP project?
Edit: Awesome! This works great so far. I now have permanent TWRP on my device. It updates partition details perfectly and I was able to flash Magisk without an issue.
Thanks a lot for your work!
thedisturbedone said:
Nice! So this is supposed to work without A/B conflicts - unlike the other TWRP project?
Click to expand...
Click to collapse
U are right, this twrp just boots the stock android, the other did not do that.
bassbounce said:
U are right, this twrp just boots the stock android, the other did not do that.
Click to expand...
Click to collapse
Thank you. Edited my initial post with results. This would open our device to a lot of possibilities.
I have September update, can i install this?
ki69 said:
I have September update, can i install this?
Click to expand...
Click to collapse
I dont know, i didnt test it on the september .
bassbounce said:
Yes, it should be no problem.
Click to expand...
Click to collapse
Thanks man, can you build it for mi a2 lite (daisy) ?
Touch screen don't work
After flash twrp touch screen don't work
My device rooted and install magisk
s.arthit1993 said:
After flash twrp touch screen don't work
My device rooted and install magisk
Click to expand...
Click to collapse
Try flashing stock boot img
This is work for my Mi A2 Rooted Whit Magisk V17.1 ?
Unfortunately, I'm not a developer.
Can someone compile the code and make an available download for this image, please?
Many Thanks!
MMN said:
Unfortunately, I'm not a developer.
Can someone compile the code and make an available download for this image, please?
Many Thanks!
Click to expand...
Click to collapse
same problem here, I don't know how to download or install it, I would like to try it
Adairo said:
same problem here, I don't know how to download or install it, I would like to try it
Click to expand...
Click to collapse
Fastboot flash boot file.img
Restart phone and boot in to recovery volume up and power key.
If it works please report here,
I don't know if twrp works with the September update which is pulled back.
Also I need a 6gb 128 a2 to test this.
DOWNLOAD:
Some ppl reported touch problems we look in to that
Dont download yet
nvm
wi-fi does not work
bassbounce said:
Fastboot flash boot file.img
Restart phone and boot in to recovery volume up and power key.
If it works please report here,
I don't know if twrp works with the September update which is pulled back.
Also I need a 6gb 128 a2 to test this.
Click to expand...
Click to collapse
You have changed the file. The difference is enormous. Which one is correct?
-> twrp-jasmine-0.1.img (27.276kb) -> Link removed in the cited post
-> boot.img (37.252kb) -> Link in post #1
Mi A2 6/128GB is here.
dimaxxxxx said:
wi-fi does not work
Click to expand...
Click to collapse
And yes: wifi does not work on both images
WiFi not working, help please.
Testing without wifi:
* Magisk v17.1 (via TWRP/zip) -> works
* SuperSU (via Magisk) -> works
* SELinux-Manager (via TWRP/zip) and go to permissive mode -> works
* xposed (xposed-v90.2-sdk27-beta3, via TWRP) -> bootloop - I'll try direct installation through Magisk when wifi works.
What's about error message when deleting the cache in TWRP:
unable to find partition for path '/cache'?
To all restore the stock boot.img. To fix it
We need to find a solution. Don't flash the twrp.
{
"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"
}
Orange Fox custom recovery
What is Orange Fox?
This custom recovery is based off TWRP, but has added features and different styling.
For more information visit the official wiki - HERE
Features
* Updated with latest TWRP commits
* Built-in support for installing Magisk
* White Flashlight
* Password pretext your recovery
* Better language support
* Optimized versions of community scripts
* Fox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* Alternative lockscreen
Downloads
MEGA
Kernel - GitHub
OFRP Source - [URL="https://gitlab.com/OrangeFox]GitLab[/URL].
Thanks to the main OrangeFox contributors @MrYacha and @DarthJabba9
Also TeamWin for TWRP
--->
Installation
From existing TWRP or OrangeFox recovery
1. Download the OrangeFox zip to your device
2. Reboot to TWRP-based Recovery
3. Install the OrangeFox zip
4. Reboot recovery
From stock unrooted
1. Unlock bootloader
2. Download OrangeFox Odin installer .tar to PC
3. Boot device into download mode, and connect to PC
4. Uncheck auto reboot in Odin
5. Flash the OrangeFox .tar file to the AP tab
6. When flashed, and you are ready, force reboot into recovery.
7. Download Encryption disabler, and transfer to device.
8. Flash Encryption disabler, FORMAT data, reboot recovery.
9. Download Magisk and transfer to device. Flash.
10. Boot up, first boot may hang. After 3min waiting, hard reboot and you should boot straight into initial setup.
** Don't reboot device before going through initial setup and connecting to the internet. This is needed for KG status to read normal. If you don't do this, you may find yourself in a prenormal state.
** If installing OrangeFox through Odin, you will be missing the Fox add-ons, which aren't essential. But if so desired, flashing the OrangeFox zip from existing custom recovery will install the necessary files for Fox add-ons.
--->
Screenshots
Gallery
Mentalmuso said:
Screenshots
Gallery
Click to expand...
Click to collapse
Thanks for making an N9700 version.
Works great!!
Any chance you can get USB OTG to work?
Android detects my Sandisk Extreme, but TWRP does not.
Duh! Forgot to mount USB drive...now it works!
difference between this and mental?
best to start making custom roms instead
edit: i see this is by mental lol
weird
pretty cool, thanks. Theres a couple bugs: haptics dont work and the keyboard covers the input line in the terminal. Also, I don't know if this is intended for this recovery, but system apps are not shown in the app manager even though I have mounted system as rw. That would be really cool if they were.
Seems like this recovery has the potential to be a great tool for system-on-root modding. I'll keep for a little while, but not being able to use the terminal will end up being a deal breaker if not fixed. Why is it hidden away in menus too? Anyhow, know you didnt design it, thanks for the work in porting this!
AllanRSS said:
pretty cool, thanks. Theres a couple bugs: haptics dont work and the keyboard covers the input line in the terminal. Also, I don't know if this is intended for this recovery, but system apps are not shown in the app manager even though I have mounted system as rw. That would be really cool if they were.
Seems like this recovery has the potential to be a great tool for system-on-root modding. I'll keep for a little while, but not being able to use the terminal will end up being a deal breaker if not fixed. Why is it hidden away in menus too? Anyhow, know you didnt design it, thanks for the work in porting this!
Click to expand...
Click to collapse
Thanks, I'll take a look at those items. I haven't done much else since release, but I'll see if I can move the terminal to the front menus.
Is it really that easy to root a SnapDragon?
Eddie_Brock said:
Is it really that easy to root a SnapDragon?
Click to expand...
Click to collapse
Yes!
Mentalmuso said:
Thanks, I'll take a look at those items. I haven't done much else since release, but I'll see if I can move the terminal to the front menus.
Click to expand...
Click to collapse
That would be awesome if you could figure those things out. No pressure of course, I appreciate what you've done so far.
I do think if fixed up a bit this has the potential to be a great tool for our phones. System on root devices need a robust solution for modifying system files, and this recovery seems like a great start to achieving that. Adding system app management would be the obvious first choice for a feature many people would appreciate
flashed it in twrp and twrp keeps coming up. something is wrong
cylent said:
flashed it in twrp and twrp keeps coming up. something is wrong
Click to expand...
Click to collapse
Flashed what? Link me to the file you flashed
Mentalmuso said:
Flashed what? Link me to the file you flashed
Click to expand...
Click to collapse
https://mega.nz/#F!ng8WiCqD!AGERu9vO97A0YBnnmaXOaA?PxtiDASY
the zip
cylent said:
https://mega.nz/#F!ng8WiCqD!AGERu9vO97A0YBnnmaXOaA?PxtiDASY
the zip
Click to expand...
Click to collapse
Ok, assuming you have the n9750 device, I don't have much else to say. I just tested installing TWRP, then using the orangefox zip to flash OF. and it works fine for me.
I have twrp working and even have nemesis kernel installed.
When I flash orangefox zip in twrp items successful but when I boot into recovery it's twrp once again.
Should I flash it via Odin?
Also, I am on infinity rom...n975fds
cylent said:
I have twrp working and even have nemesis kernel installed.
When I flash orangefox zip in twrp items successful but when I boot into recovery it's twrp once again.
Should I flash it via Odin?
Also, I am on infinity rom...n975fds
Click to expand...
Click to collapse
This is for snapdragon phones only if your model is n975fds then you have exynos model which means this recovery won't work on your phone
minidude2012 said:
This is for snapdragon phones only if your model is n975fds then you have exynos model which means this recovery won't work on your phone
Click to expand...
Click to collapse
Now you tell me
Any chance of exynos version?
Post 14 above he said it works.
https://forum.xda-developers.com/showpost.php?p=81932681&postcount=14
cylent said:
Now you tell me
Any chance of exynos version?
Post 14 above he said it works.
https://forum.xda-developers.com/showpost.php?p=81932681&postcount=14
Click to expand...
Click to collapse
You might consider a different hobby...RTFM
Sent from my SM-N975F using XDA Labs
CAREFUL
I tried to boot into this recovery again yesterday and there was a verified boot problem. I went into a bootloop in download mode with the following error. I had to reflash twrp from odin to get the device back. I'm going to wait till this has been developed a little more to use it on my main device.
"partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0_INDIVLDVMT_EDRHS_IMTHSGAUEMSAC"
AllanRSS said:
CAREFUL
I tried to boot into this recovery again yesterday and there was a verified boot problem. I went into a bootloop in download mode with the following error. I had to reflash twrp from odin to get the device back. I'm going to wait till this has been developed a little more to use it on my main device.
"partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0_INDIVLDVMT_EDRHS_IMTHSGAUEMSAC"
Click to expand...
Click to collapse
This recovery is based off TWRP... vbmeta issues purely stem from root or more specifically magisk.