{
"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"
}
Unofficial TWRP 3.3.0 For J7 2017Disclaimer
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.
Special features:
Code:
- built from Pie kernel source
- built in full 64bit mode
- updated TWRP source to 3.3
- Full F2FS Support
- fully compatible with all Oreo roms
Downloads:
J730x - Latest Release
Instructions:
Odin
Download Odin v3.13.1
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Home+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
Optional - Download and flash no-verity-opt-encrypt-6.0 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
J530x device tree - https://github.com/omnirom/android_bootable_recovery
Credits:
@corsicanu
@Dyneteve
@yshalsager
@TwrpBuilder
XDA:DevDB Information
TWRP_J730, Tool/Utility for the Samsung Galaxy J7 (2017)
Contributors
ananjaser1211, corsicanu
Version Information
Status: Stable
Current Stable Version: 3.3
Stable Release Date: 2019-04-17
Created 2018-08-30
Last Updated 2019-04-18
This TWRP is Android 8.1 Ready, when J7 officially receives Oreo this will be a direct flash either via .tar in odin or just update .img inside twrp itself.
This is also built on updated TWRP trees and all that good stuff. enjoy
sources are here if anyone wants to modify
**F2FS support is not there**
You are the best big thanks ?
Thanks @ananjaser1211 great job in making twrp for j7 specially this one is oreo ready. Too bad samsung crappy update is as late as ever.
flarestar123 said:
Thanks @ananjaser1211 great job in making twrp for j7 specially this one is oreo ready. Too bad samsung crappy update is as late as ever.
Click to expand...
Click to collapse
it will come eventually, lets hope it doesnt act like the current J5 update it broke multiple phone speakers so far :laugh:
ananjaser1211 said:
it will come eventually, lets hope it doesnt act like the current J5 update it broke multiple phone speakers so far :laugh:
Click to expand...
Click to collapse
Haha now even with dolby mod you will live in peace. No loud noise . And btw all those looking for the download link they are posted in github releases under assets
ananjaser1211 said:
[*]Based on Updated TWRP Tree
[*]Build with OMNI_8.1
[*]Support for 7.0/7.1.1/8.0/8.1
[*]ARM64 (2GB+ Zip)
[*]Working MTP (Windows/Linux)
[*]Propper System Mount/unmount
[*]EFS/Radio Backup enabled
[*]Aroma Support
[*]Disabled RED Debug Text
[*]Adjusted Partition Sizes
Click to expand...
Click to collapse
hey,
all is very fine.
NiceWork
plz can u disable Kernel warning line on boot to TWRP
Thanks
Thanks dev :good:
@ananjaser1211 Weird! Could not flash it. Odin FCs. (Win 10). twrp_3.2.1_1 works.
Greight said:
@ananjaser1211 Weird! Could not flash it. Odin FCs. (Win 10). twrp_3.2.1_1 works.
Click to expand...
Click to collapse
try to update twrp, not sure why it wouldnt work to begin with,flash 3.2.1 then download the twrp but .img , then flash it from twrp 3.2.1 as a workaround
What is different from Latest releases and Official TWRP Builder?
ananjaser1211 said:
try to update twrp, not sure why it wouldnt work to begin with,flash 3.2.1 then download the twrp but .img , then flash it from twrp 3.2.1 as a workaround
Click to expand...
Click to collapse
Thanks. Installed TWRP this way, but when I reboot to recovery, this message comes up in red:
recovery is not seandroid enforcing
Click to expand...
Click to collapse
Any ideas?
quanghuy226 said:
What is different from Latest releases and Official TWRP Builder?
Click to expand...
Click to collapse
Nothing, just wanted to keep twrp builder there as it gets auto updated every month, while mine would only be updated if im experimenting more stuff.right now they are on the same thing
Greight said:
Thanks. Installed TWRP this way, but when I reboot to recovery, this message comes up in red:
Any ideas?
Click to expand...
Click to collapse
Does it boot after ? that red msg is normal, if it stays on splash, what is your variant
ananjaser1211 said:
Does it boot after ? that red msg is normal, if it stays on splash, what is your variant
Click to expand...
Click to collapse
Yes and it works fine. BTW only appears on TWRP pre-boot screen. I have the G model.
Greight said:
Yes and it works fine. BTW only appears on TWRP pre-boot screen. I have the G model.
Click to expand...
Click to collapse
ok thanks for clarification, i thought it was stuck, ill add a patch to remove that red logo later.
New TWRP out:
Changes:
switched to TwrpBuilder official builds
included crypto for LineageOS software encrypted data, thanks to @Option58
made preload partition wipeable in recovery
included cpefs and m9kefs partitions in backup for safety reasons
Downloads:
J730x - https://github.com/TwrpBuilder/android_device_samsung_j7y17lte/releases
Instructions:
Odin
Download Odin v3.13.1
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Home+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
Optional - Download and flash no-verity-opt-encrypt-6.0 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
All the best!
I replaced my touch screen and your twrp is touch screen is not working and a8+ rom.....
EyuphanKundakci said:
I replaced my touch screen and your twrp is touch screen is not working and a8+ rom.....
Click to expand...
Click to collapse
Don't use fake displays. Done
ananjaser1211 said:
Don't use fake displays. Done
Click to expand...
Click to collapse
Other roms work excellent but your roms doesn't work please fix bro.
EyuphanKundakci said:
Other roms work excellent but your roms doesn't work please fix bro.
Click to expand...
Click to collapse
My ROMs work fine. And they are Oreo. Your device probably won't work with stock Oreo as well. Don't go cheap on a screen replacement
Related
Team Win Recovery Project 3.0.2-1
WARNING #1: 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.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy S6 edge+ stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Flash a root such as SuperSU or phh-superuser. You can also flash .
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:
[url]http://teamw.in/devices/samsunggalaxys6edgeplus.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 ROOTING YOUR DEVICE
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"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"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for your device variant.
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.
By swiping right, you will trigger dm-verity, and if you don't follow step 12 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
Only if you want your internal storage or data partition to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you only want a bootable system partition or readable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
** If your internal storage is encrypted, you will need to use adb sideload instead.
Go to [Reboot] -> [System].
Wait up to 5 minutes for your device to finish setting itself up.
* 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-1 - New device tree and kernel, support added for Marshmallow, f2fs, and MTP.
v3.0.2-0 - See here for the changes.
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)
NTFS file system support (read, write)
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_zenlte (android-6.0)
Kernel: https://github.com/jcadduono/nethunter_kernel_noblelte (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 S6 edge+, Tool/Utility for the Samsung Galaxy S6 Edge+
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/jcadduono/android_device_samsung_zenlte
Version Information
Status: Stable
Current Stable Version: 3.0.2-1
Stable Release Date: 2016-04-08
Created 2016-04-08
Last Updated 2016-12-18
Builds are coming soon guys, I just made the thread so that we have a reference when updating the site.
Bricked after flash, any suggestion? SM-G928F variant with audax plus 3.0 + audax kernel. Recovery not booting, tried reflash with odin old 3.0.0 recovery but the brick persist...
pmisun said:
Bricked after flash, any suggestion? SM-G928F variant with audax plus 3.0 + audax kernel. Recovery not booting, tried reflash with odin old 3.0.0 recovery but the brick persist...
Click to expand...
Click to collapse
Flash the twrp via Odin provided by the Audax rom, that note 5 recovery
Sent from my Darkside of Edge plus
Solved. Btw there is in repo of twrp dev which is linked by audax also 3.0.1 twrp working version. working as charm.
pmisun said:
Solved. Btw there is in repo of twrp dev which is linked by audax also 3.0.1 twrp working version. working as charm.
Click to expand...
Click to collapse
https://idlekernel.com/twrp/zenlte see 3.0.2-1, should be built soon on official, whenever someone confirms that everything is working ok
this includes:
adb shell
brightness slider
installing zips
formatting partitions (as ext4 and f2fs)
not crashing
backup & restore works for each partition
mtp
vibration
otg storage
whatever else you can think of checking
check on both L and M bootloaders, preferably quote my list with Y(working)/N(not working) in front of issues, and give recovery.log
jcadduono said:
https://idlekernel.com/twrp/zenlte see 3.0.2-1, should be built soon on official, whenever someone confirms that everything is working ok
this includes:
adb shell
brightness slider
installing zips
formatting partitions (as ext4 and f2fs)
not crashing
backup & restore works for each partition
mtp
vibration
otg storage
whatever else you can think of checking
check on both L and M bootloaders, preferably quote my list with Y(working)/N(not working) in front of issues, and give recovery.log
Click to expand...
Click to collapse
will try this evening.
pmisun said:
will try this evening.
Click to expand...
Click to collapse
welcome to xda, don't say you'll do things, just do things, it makes people think that they don't have to do it because someone else will do it eventually, slowing things down for everyone.
jcadduono said:
welcome to xda, don't say you'll do things, just do things, it makes people think that they don't have to do it because someone else will do it eventually, slowing things down for everyone.
Click to expand...
Click to collapse
will try and will do..make sense? ok i wont try this.
Why nothing for s6 edge + USC? Everything else except usc version :'(
Tokumei no said:
Why nothing for s6 edge + USC? Everything else except usc version :'(
Click to expand...
Click to collapse
read after first post, builds not up on the site yet, links available
jcadduono said:
read after first post, builds not up on the site yet, links available
Click to expand...
Click to collapse
But there has never been a custom recovery for the s6 edge + USC model. (SM-G928R4 US Cellular) Unless I have missed something then please point me in the right direction for a custom recovery for this specific model.
perfect update TWRP for G928F
https://idlekernel.com/twrp/zenlte/3.0.2-1/twrp-3.0.2-1-zenlte.zip
flash from CWM
It works perfectly fine! The only bug I've found is that vibration doesn't work but that's really not important
Sent from my SM-G928F using XDA-Developers mobile app
Can someone please work on a custom recovery for SM-G928R4? I mean come on now :'(
Works really great on my 928g only vibrations don't work but I don't care thanks a lot.
Guys help
I am using note 5 twrp-3.0.0-0-nobleltezt recovery for my G928C so how to flash this
I have the international SM-G9287 Duo variant on the latest firmware 6.0.1/MMB29K/G9287ZHU2BPC6 (marshmallow) and it's rooted. When I get to the step to press Home+Vol up towards the end of the flash it just reboots normal. Then when I turn of to boot into recovery Home+Vol up+Power I get "RECOVERY IS NOT SEANDROID ENFORCING" in red along the top with the Samsung GS6 logo. I have a tar file with the stock recovery and that boots fine. Any suggestions? Thanks in advance.
I can't find the download link to v.3.0.2-1 on the device page. Am I searching in the wrong place? (https://dl.twrp.me/zenlte)
fisk4rn said:
I can't find the download link to v.3.0.2-1 on the device page. Am I searching in the wrong place? (https://dl.twrp.me/zenlte)
Click to expand...
Click to collapse
Its link is in Post #6.
Powered by Elektrik
{
"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"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
What is PAX?
Our release of Android 10, titled CR-8.0, is codenamed PAX after the latin word for peace and Pax, the roman godess for peace.
PAX provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. PAX delivers a set of unique features, like a systemwide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Download
Join the CarbonROM Discord server
Meet us on Telegram
Homepage
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Sony Xperia Z3
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Nightly
Created 2020-02-08
Last Updated 2020-05-06
Reserved
@Myself5
Thx so so much for the first beta cr 8.0 build. I will check it out tomorrow.
One question:
Is possible to boot from this build directly into twrp?
I'm asking because the hardware buttons of my old z3 needs many pressure to work.
Restart to recovery
dhacke said:
Is possible to boot from this build directly into twrp?
Click to expand...
Click to collapse
All current Shinano ROMS derived from LineageOS16/17 should support restart to recovery. You may need to enable the extended restart menu under development options.
You can also trigger this via adb:
Code:
adb reboot recovery
Please report if that isn't working
Mr.Tom_Tom said:
All current Shinano ROMS derived from LineageOS16/17 should support restart to recovery. You may need to enable the extended restart menu under development options.
You can also trigger this via adb:
Please report if that isn't working
Click to expand...
Click to collapse
I can comfirm now that the boot into twrp works.
@Myself5
I believe i notice a bug: I couldn't secure the z3 with a password in the setup because after i entered the password it says 'success' but in the settings under the device security tab still stands 'swipe'.
When i try to change the display lock to the password option afterwards in the settings menu my z3 always asks me after a password and when i type in the password which i type in the setup it says wrong password.
New build uploaded just now has the SetupWizard fixed. The lockscreen bug is getting looked into right now.
Uploaded a new build. Contains some additional lockscreen clocks but more importantly, the PIN issue is fixed.
Code:
75ff1b7cd559ec1f61b196a831891142 CARBON-CR-8.0-PAX-UNOFFICIAL-z3-20200225-1425.zip
Can you support d6633 dual version please
Thanks for the awesome work. Flashing ASAP!
I am unable to successfully flash the 3.3.1 recovery. Android Stock marshmallow 6.0.1 build 291 installed. Rooted it by flashing 575 kernel and after root revert it back to 291 kernel file by flashing with flashtool.
Now my 6.0.1 is 23.5.A.1.291 means latest build. And flashing the recovery by typing the command "fastboot flash FOTAKernel recovery.img.
The recovery 3.3.1 which I downloaded from lineage 17.1 page. I renamed the file twrp_z3_2020-02-08.img to recovery.img
But after flashing the recovery when I enter into recovery it shows twrp 3.0.2
I downloaded the twrp 3.3.1 from different pages but same thing happened.
I'm a poor man ? and can't afford or buy android 10 device and I saw a dream that I opened xda and there someone launched mouth watering cr8.0 and lineage os 17.1
And I wish I could flash those os
But this twrp is hurdling me and that is proven a big hurdle to me which I couldn't cross
I'm on bed and doctor ? said you're guest of few days if you can't flash android 10
TWRP images flashed to the FOTAKernel partition can only be accessed by, starting with your phone completely powered off, holding both the power and volume down buttons. When the phone vibrates (as if it was being turned on), release the power button. When the screen lights up, release the volume down button. TWRP shall come up.
casouzaj said:
TWRP images flashed to the FOTAKernel partition can only be accessed by, starting with your phone completely powered off, holding both the power and volume down buttons. When the phone vibrates (as if it was being turned on), release the power button. When the screen lights up, release the volume down button. TWRP shall come up.
Click to expand...
Click to collapse
Finally someone who explains how to boot in the ( new ) recovery. I bet @KnowledgeSeekerPart2 had the correct recovery allready installed different times.
I didn't say that I couldn't enter into twrp. But whenever I flashed 3.3.1 on my 23.5.A.1 291 build I found 3.0.2 on my shinano.
Is it possible that if you flash 3.3.1 twrp, you ended up by having 2 different versions installed (3.3.1 & 3.0.2)
I simply wanna say that you mean which I understood that if you power on your device and when led light flashes then by pressing volume down button twice or thrice quickly you'll enter into 3.0.2 recovery and according to your mathod I'll enter into 3.3.1 (remember I just flashed 3.3.1 on fota kernel)
KnowledgeSeekerPart2 said:
I am unable to successfully flash the 3.3.1 recovery. Android Stock marshmallow 6.0.1 build 291 installed. Rooted it by flashing 575 kernel and after root revert it back to 291 kernel file by flashing with flashtool.
Now my 6.0.1 is 23.5.A.1.291 means latest build. And flashing the recovery by typing the command "fastboot flash FOTAKernel recovery.img.
The recovery 3.3.1 which I downloaded from lineage 17.1 page. I renamed the file twrp_z3_2020-02-08.img to recovery.img
But after flashing the recovery when I enter into recovery it shows twrp 3.0.2
I downloaded the twrp 3.3.1 from different pages but same thing happened.
I'm a poor man and can't afford or buy android 10 device and I saw a dream that I opened xda and there someone launched mouth watering cr8.0 and lineage os 17.1
And I wish I could flash those os
But this twrp is hurdling me and that is proven a big hurdle to me which I couldn't cross
I'm on bed and doctor said you're guest of few days if you can't flash android 10
Click to expand...
Click to collapse
Flash the recovery to recovery partition instead,
Code:
fastboot flash recovery (name of recovery).img
KnowledgeSeekerPart2 said:
I didn't say that I couldn't enter into twrp. But whenever I flashed 3.3.1 on my 23.5.A.1 291 build I found 3.0.2 on my shinano.
Is it possible that if you flash 3.3.1 twrp, you ended up by having 2 different versions installed (3.3.1 & 3.0.2)
I simply wanna say that you mean which I understood that if you power on your device and when led light flashes then by pressing volume down button twice or thrice quickly you'll enter into 3.0.2 recovery and according to your mathod I'll enter into 3.3.1 (remember I just flashed 3.3.1 on fota kernel)
Click to expand...
Click to collapse
Yes, that's right, it's possible, i had 2 different recoverys too in my Z2 or Z3C, don't remember exactly which device it was.
The " old way " was to press vol+ during boot process to boot in the recovery.
hey, same problem with @KnowledgeSeekerPart2
i tried all method around the web and unable to upgrade the crappy twrp 3.0.2 to shiny 3.3.1, the twrp 3.0.2 can't flash carbon, lineagos and will give you "unknown command" error....damn
let see what i tried so far
- upgrade through twrp app -> nope
- upgrade through flashing on current twrp recovery mode -> still nope
- upgrade through fastboot like "flash recovery" and "flash fota" -> still nope
i still boot to 3.0.2 with no change at all
and btw, @casouzaj recommended power+vol down combo not work too, because my z3 will not boot to recovery with that way, it boot the OS XD so i always have to : tap tap fast vol down few times to boot to recovery
very troublesome i admit
KoolKool993 said:
hey, same problem with @KnowledgeSeekerPart2
i tried all method around the web and unable to upgrade the crappy twrp 3.0.2 to shiny 3.3.1, the twrp 3.0.2 can't flash carbon, lineagos and will give you "unknown command" error....damn
let see what i tried so far
- upgrade through twrp app -> nope
- upgrade through flashing on current twrp recovery mode -> still nope
- upgrade through fastboot like "flash recovery" and "flash fota" -> still nope
i still boot to 3.0.2 with no change at all
and btw, @casouzaj recommended power+vol down combo not work too, because my z3 will not boot to recovery with that way, it boot the OS XD so i always have to : tap tap fast vol down few times to boot to recovery
very troublesome i admit
Click to expand...
Click to collapse
Again.
Download the required TWRP.
Place it in your " Fastboot and ADB " folder. ( PC ! )
Inside your " Fastboot and ADB " folder create an empty file, rename it to " flashFOTAKernel.bat "
Open ( edit ) the file, paste the following in the file :
fastboot flash FOTAKernel twrp-3.3.1-z3-20200212.img
Save the .bat file
Shut down your device complete. ( Press and hold vol UP and power until the device vibrates 3 times )
Now connect the device in fastboot mode to your PC ( press vol UP, hold the button ) and plug the USB cable in. LED should be blue.
Doubleclick the .bat file you've created before, and that's all.
Disconnect your device, press vol DOWN and power, HOLD the buttons until the boot logo appears, and your device boots in your new recovery.
0LDST4R said:
Again.
Click to expand...
Click to collapse
i appreciated your kindness highly
but sadly, your method not working for me
Shut down your device complete. ( Press and hold vol UP and power until the device vibrates 3 times)
Click to expand...
Click to collapse
i tried nothing vibrate
Now connect the device in fastboot mode to your PC ( press vol UP, hold the button ) and plug the USB cable in. LED should be blue
Click to expand...
Click to collapse
Yes, i tried this, i got blue light and into fastboot mode
Download the required TWRP.
Place it in your " Fastboot and ADB " folder. ( PC ! )
Inside your " Fastboot and ADB " folder create an empty file, rename it to " flashFOTAKernel.bat "
Open ( edit ) the file, paste the following in the file :
fastboot flash FOTAKernel twrp-3.3.1-z3-20200212.img
run the bat
Click to expand...
Click to collapse
yeah, i did, everything said file extractions are succesfully
Disconnect your device, press vol DOWN and power, HOLD the buttons until the boot logo appears, and your device boots in your new recovery.
Click to expand...
Click to collapse
i tried this, but it just boot straight into the OS
meanwhile, the "press vol down multiple time on green light logo boot up" method as i mentioned above is only the way into twrp recovery (but still old version), nothing less
my Z3 is Dual 6633, on right version, totally SuperU rooted and unlocked bootloader
tried it today... quite snappy... Better than cr 7, as fast as cr 6! Very impressed!
battery life excellent.
i ll use it for daily driver as soon as it passes beta phase!
passes safety net even with magisc!! (didnt have that with CR 6)
on the first install pixel launcher was present but force closes... quickstep worked all right.. after reinstall pixel launcher was absent.
camera did not work as well but somehow this fixed itself. (edit: the "cantt connect to the camera error returned unexpectedly)
i couldnt find how to connect to wifi with WPS push button, the setting seems to be absent.
much better than lineage (faster snappier) have to give you that.. thank you for all the work!!
excellent work for a beta build.
wishlist:
1. fm radio! pls pls pls !
2. shutdown/reset button on quick settings
I'm testing firmware on D6633. Faced with the fact that the SIM card is detected, but there is no connection. Tried to call - writes that you need to turn off flight mode. Even the APN is in place. Next, I tried to install the patch for SIM cards for the dual version, but this led to the fact that the firmware now does not see the SIM card at all. It would be nice to see a working mobile connection for D6633 in the following builds.
Team Win Recovery Project 3.4.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"
}
Exynos ONLY.
In NO way it is compatible with Snapdragon variants including but not limited to American(U/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. All apps that use KNOX like Samsung pay, Secure Folder and maybe more will no more work
Download: S20/S20+/S20 Ultra(Exynos variants)
Download
Sources:
Kernel source
TWRP source
Device Tree: Sorry are not under GPL License since are my own so they will not get released
Changelog:
06.12.2020
- Updated TWRP Source
- Adb Push works now without disable MTP in settings
- Fixed the bug where TWRP dont saved settings
- Updated DTB and DTBO for boot on One UI 3.0 (Use Magisk 21.1 for root One UI 3.0)
- Boot only with USB Cable or USB OTG connected (THX samsung for this stupid change in the bootloader)
- Removed decrypter from download folder (use Multidisabler 2.6 instead)
03.09.2020
- Twrp boots now without nulled Vbmeta.img
03.09.2020
- Fixed Optics and Prism Backup and Restore
- Brightness is now no more at max
- CPEFS error is gone
- Sec-EFS added in the FStab
19.08.2020
-Initial Release
Bugs:
-MTP and Encryption (ADB PUSH WORKS when you disable mtp in TWRP mount settings!)
XDA:DevDB Information
[RECOVERY] TWRP for Galaxy S20/S20+/S20 Ultra, Kernel for the Samsung Galaxy S20
Contributors
geiti94
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2020-08-19
Created 2020-08-19
Last Updated 2020-12-06
Guide:
Go to Developer settings and enable oem unlock
power off the device and boot in download mode with vol up+ vol down buttons and plug in the usb (make sure usb cable is connected to the pc)
in download mode you see the long press vol up option for unlock bl
unlock the bootloader (that will wipe your device so be sure you made a backup of your data)
after bootloader unlock boot up the phone and make sure it is connected to the internet or he triggers rmm prenormal
setup the phone without google account etc
reboot in download mode and flash twrp tar for your device with odin in the AP field
hold vol up + power button while odin is flashing until you are in twrp.
format data in twrp and install multidisabler (you find it here on xda!)
Flash Latest Magisk
press reboot to system in twrp.
Thank you.
Thanks ?
Awesome job bro you rock !!!! ???
You Legend
Thanks a lot great job.
Question:: If I'm already rooted with Linage recovery I can just flash TWRP in Odin skipping all the other steps , correct?
Will there be too for Snapdragon Variante of s20?
golfgtiedition30 said:
Thanks a lot great job.
Question:: If I'm already rooted with Linage recovery I can just flash TWRP in Odin skipping all the other steps , correct?
Click to expand...
Click to collapse
Yes then you cam flash only twrp. But remember that zips made for lineage recovery dont flashes in twrp since twrp mounts the partitions differently
golfgtiedition30 said:
Thanks a lot great job.
Question:: If I'm already rooted with Linage recovery I can just flash TWRP in Odin skipping all the other steps , correct?
Click to expand...
Click to collapse
Hi all
thanks for the great job
me it's the same, does it work if I just flash the zip?
geiti94 said:
Guide:
Go to Developer settings and enable oem unlock
power off the device and boot in download mode with power + vol down buttons and plug in the usb (make sure usb cable is connected to the pc)
in download mode you see the long press vol up option for unlock bl
unlock the bootloader (that will wipe your device so be sure you made a backup of your data)
after bootloader unlock boot up the phone and make sure it is connected to the internet or he triggers rmm prenormal
setup the phone without google account etc
reboot in download mode and flash twrp tar for your device with odin in the AP field (if you want to patch twrp byself patch the downloaded tar in magisk manager. patched tar is in downloads folder after patch)
hold vol up + power button while odin is flashing until you are in twrp.
format data in twrp and disable encryption! (i will post today or tomorrow a encryption remover made for twrp with super.img partition!)
Flash Latest Magisk
press reboot to system in twrp.
Click to expand...
Click to collapse
I am getting this error while formatting the data: failed to mount '/cpefs' (read-only file system)
LENO7 said:
I am getting this error while formatting the data: failed to mount '/cpefs' (read-only file system)
Click to expand...
Click to collapse
its normal since is a read only partition. you can ignore that error
Hi after flashing twrp with odin my galaxy s20 refuses to boot.
I see the warning that I have no offical samsung software and then I boots straigt to the entering fastboot screen.
Any idea how to fix that?
acocalypso said:
Hi after flashing twrp with odin my galaxy s20 refuses to boot.
I see the warning that I have no offical samsung software and then I boots straigt to the entering fastboot screen.
Any idea how to fix that?
Click to expand...
Click to collapse
on newest bootloader when you see s20 splash you need directly to release the buttons or he will boot in fastboot mode
thanks ... can you flash rom gsi?
Legend geiti right way for S20 Series
Jenanga said:
Legend geiti right way for S20 Series
Click to expand...
Click to collapse
this is coming soon too
Jenanga said:
Legend geiti right way for S20 Series
Click to expand...
Click to collapse
where you can search, in google I can't find it
Why am I banned from telegram?
Are we able to do a complete backup/restore? as per previous versions on other models?
Thanks
How to Root Samsung Galaxy A50 SM-A505F Android 11 with Magisk + OrangeFox ( OneUI 3.1 ). The OrangeFox Recovery ( Brought to you by @enzoaquino ) support Galaxy A50 One UI 3.1 Android 11, Android security patch level: 1 March 2021. It may be works for SM-A505F, SM-A505FN, SM-A505G, SM-A505GN. The OrangeFox R11.0 comes with Magisk Patched. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
LET US KNOW IF IT WORKS FOR:
SM-A505FN, SM-A505G, SM-A505GN ( NOT TESTED )
Manual Instructions:
Make sure the bootloader are unlocked, OEM unlock option is grey out
Enter Download Mode : Turn Power Off. Press and hold Volume Up + Volume Down key together, while pressing these keys, connect the phone to computer, then press volume up once.
Open ODIN, IMPORTANT!: Uncheck “Auto Reboot” in Options!
Flashing OrangeFox-R11.0-Stable-a50dd_magisk.tar as AP in ODIN, then click start.
DO NOT SKIP THIS STEP! Don't remove USB Cable, let it connected. Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key until OrangeFox Recovery Appears.
Format data
Install multidisabler-samsung-2.6.zip
Reboot to Recovery
When SAMSUNG logo appears wait for a few minutes or more then press and hold volume down + power key until the screen blank
Setup the phone
Connect Phone to Internet
Tap Magisk app: "Upgrade to full Magisk to finish the setup. Download and Install?" tap OK
Install and Open Magisk Manager, Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Done!
Video Instructions
Download
OrangeFox-R11.0-Stable-a50dd_magisk.tar
Credits to @Enzoaquino for OrangeFox A50 A11
Magisk patched and packed to .tar by me
The multidisabler isnt flashing it says zip file format errorhttps://drive.google.com/file/d/1-9UADSgWzPX2EHaaNOoMSd7_Thz_ft8b/view?usp=drivesdk
It worked just fine and got root with it but im curious about the multidisabler zip. What does it do and what is the fnction of it? It give me an eror while flashing both 2.6 and the latest version
{
"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 made it.
multidisabler-samsung-2.6 didn't work on SM-A505F
USE
multidisabler-samsung-3.1.zip
I tried both 3.1 and 2.6 but still failed to flash
Is it working or not?
redymedan said:
How to Root Samsung Galaxy A50 SM-A505F Android 11 with Magisk + OrangeFox ( OneUI 3.1 ). The OrangeFox Recovery ( Brought to you by @enzoaquino ) support Galaxy A50 One UI 3.1 Android 11, Android security patch level: 1 March 2021. It may be works for SM-A505F, SM-A505FN, SM-A505G, SM-A505GN. The OrangeFox R11.0 comes with Magisk Patched. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
LET US KNOW IF IT WORKS FOR:
SM-A505FN, SM-A505G, SM-A505GN ( NOT TESTED )
Manual Instructions:
Make sure the bootloader are unlocked, OEM unlock option is grey out
Enter Download Mode : Turn Power Off. Press and hold Volume Up + Volume Down key together, while pressing these keys, connect the phone to computer, then press volume up once.
Open ODIN, IMPORTANT!: Uncheck “Auto Reboot” in Options!
Flashing OrangeFox-R11.0-Stable-a50dd_magisk.tar as AP in ODIN, then click start.
DO NOT SKIP THIS STEP! Don't remove USB Cable, let it connected. Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key until OrangeFox Recovery Appears.
Format data
Install multidisabler-samsung-2.6.zip
Reboot to Recovery
When SAMSUNG logo appears wait for a few minutes or more then press and hold volume down + power key until the screen blank
Setup the phone
Connect Phone to Internet
Tap Magisk app: "Upgrade to full Magisk to finish the setup. Download and Install?" tap OK
Install and Open Magisk Manager, Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Done!
Video Instructions
Download
OrangeFox-R11.0-Stable-a50dd_magisk.tar
Credits to @Enzoaquino for OrangeFox A50 A11
Magisk patched and packed to .tar by me
Click to expand...
Click to collapse
send pls zip without magisk
Ok i worked around the "invalid zip format error"
i tried all the versions from v2.0 to 3.1.. none worked
then i extracted the version 3.1 on my pc, i went inside the folder and i created the zip file of the "META_INF" folder
then i copied META-INF.zip file to my mobile and it worked
Hope this helps everyone
This is my first time rooting a device btw.. lol
i was using twrp btw
msuroxy said:
Ok i worked around the "invalid zip format error"
i tried all the versions from v2.0 to 3.1.. none worked
then i extracted the version 3.1 on my pc, i went inside the folder and i created the zip file of the "META_INF" folder
then i copied META-INF.zip file to my mobile and it worked
Hope this helps everyone
This is my first time rooting a device btw.. lol
i was using twrp btw
Click to expand...
Click to collapse
Soo you only need meta-inf and compress it to a zip file??
PetiHun08 said:
Soo you only need meta-inf and compress it to a zip file??
Click to expand...
Click to collapse
yes extract the downloaded zip "multidisabler-samsung-3.1.zip"
go into folder "multidisabler-samsung-3.1"
right click "META-INF" folder and create Zip
Copy "META-INF.zip" file to mobile and flash
it worked for me!
msuroxy said:
yes extract the downloaded zip "multidisabler-samsung-3.1.zip"
go into folder "multidisabler-samsung-3.1"
right click "META-INF" folder and create Zip
Copy "META-INF.zip" file to mobile and flash
it worked for me!
Click to expand...
Click to collapse
Okay i'm going and try it cuz i have to fix my soft bricked a50 and root it( i have bricked it with no multidisabler after installing twrp cuz it failed)
do let us know if it worked or not..!
msuroxy said:
do let us know if it worked or not..!
Click to expand...
Click to collapse
Almost done...
PetiHun08 said:
It worked my phone booted properly with twrp and didn't replaced it. Thamks! :highfive:
Click to expand...
Click to collapse
My model: A505fn/ds eu model
wohoo.. cheers man!! now i have to figure out what i can do with a rooted device.. first time rooting a device.. any pointers??
msuroxy said:
wohoo.. cheers man!! now i have to figure out what i can do with a rooted device.. first time rooting a device.. any pointers??
Click to expand...
Click to collapse
Speed the device up with lspeed, Change boot animation, reset knox trip with triangle away, hack games with gameguardian(it works like cheatengine), install custom roms and lots of more!
PetiHun08 said:
Speed the device up with lspeed, Change boot animation, reset knox trip with triangle away, hack games with gameguardian(it works like cheatengine), install custom roms and lots of more!
Click to expand...
Click to collapse
thanks man.. i'll see you around
q1pa said:
I tried both 3.1 and 2.6 but still failed to flash
View attachment 5274351
Click to expand...
Click to collapse
My file flashed without error. u may try it.
Why does magisk dissappear when I reboot? I'm not talking about when Magisk asks to reboot, i get past that magisk is still good but if i have to reboot again it dissappears.
{
"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:
/*
*Disclaimer
*
* Your warranty is now void.
*
* 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.
*/
Introduction
OrangeFox Recovery is one of the most popular custom recoveries, with amazing additional features, fixes and a host of supported devices
OrangeFox version: R11.1
For device: a32
Maintainer: Ahnet ( @Captain_cookie_200 )
OrangeFox source:
OrangeFox Recovery · GitLab
OrangeFox Recovery | OFR
gitlab.com
Device tree:
GitHub - Epico-Bot/ofox_device_samsung_a32: Device tree for building OrangeFox Recovery for Samsung Galaxy A32 4G (MTK), based on A325FXXU2BVD6.
Device tree for building OrangeFox Recovery for Samsung Galaxy A32 4G (MTK), based on A325FXXU2BVD6. - GitHub - Epico-Bot/ofox_device_samsung_a32: Device tree for building OrangeFox Recovery for Sa...
github.com
Kernel Source: https://github.com/ahnet-69/android_kernel_samsung_a32-recovery
Features:
Code:
Synced with the latest Teamwin changes
Designed with latest Material design 2 guidelines
Implemented support for Flyme and MIUI OTA, and incremental block-based OTA in custom ROMs
Included assorted customizations
Inbuilt patches, like Magisk and password reset patch
Several addons
Password protection
Fully open-source
Frequently updated
Status
Stable-ish
Tested on:
SM-A325F (by me)
SM-A325M (by @filipedonato)
other models unknown. But should work.
Please report back so i can update the op
Downloads
Click here.
Bugs
1. TWRP cannot decrypt userdata if you set lockscreen. (someone said it works, other it doesn't, so I'll just leave it here, YMMV)
2. Flashing anything shows many "unlock" red lines. (They are currently harmless by our knowledge).
3.USB-OTG
4. Saving settings is fixed but for fixing settings such as theming resetting on reboot is by editing the bootable/recovery/twrp.cc and at line 396 (as of now) changing the bool to true. This makes the recovery load the themes twice. This should only be for encrypted devices but since it has fixed our issue we'll use this workaround until a proper solution has been found.
Installation
Code:
If you have TWRP or any custom recovery installed and bootable, you can upgrade instead; Look below.
<!> the installation will require WIPING DATA. You will also lose access to all Knox-based solutions like Secure Folder.
Backup every precious data you have on your phone.
<!> PC is required. Windows is preferred. (You probably know what you are doing when using Linux/Heimdall. We don't talk about Macs)
Unlock Bootloader:
1. Go to Settings > About Phone > About Software. Tap build number (10 times) until "you are now a developer" toast shows up.
2. Go back, go to Developer Settings.
3. Turn on OEM unlock toggle.
4. Turn off your phone, hold vol-up + vol-down, then plug in charging cable (please don't use 3rd-party charging-only cable, it must have data transfer capability).
5. Your device will boot into download mode with a warning. Accept it.
6. Hold volume-up until the phone shows the bootloader unlock panel "Unlock Bootloader?".
Press volume-up again. Now your phone bootloader is unlocked.
<!> It will now begin the process of wiping data. Let it do its job.
7. When it reboots to OS, finish setting up your device.
8. Double check to make sure OEM Unlock is still ON.
Preparing for the installation:
1. Download everything above onto your PC.
2. Rename OrangeFox recovery img file to recovery.img and add it to archive using any archiver and select gnu tar.
3. Install Samsung USB Driver.
4. Open Odin.
5. Connect your phone to your PC. There should be a COM entry on the top.
6. Make sure your phone is in Download Mode. (see step 4 of section Unlock Bootloader)
7. Make sure that OEM LOCK and REACTIVATION LOCK on your screen show "OFF". If it's not off, DO NOT PROCEED ANY FURTHER.
<!> For those with lock ON, use your device for 7 days without rebooting once. Then check the locks above again.
Installing:
1. Ensure phone is in Download mode.
In Odin:
Load in Userdata: VBMeta_disabler.tar file.
Load in AP: OrangeFox TAR file.
2. Prepare yourself. keep your hand on Volume-up and Power button (don't press yet).
3. In Odin, press Start. It will flash, then reboot. When the screen turned off, quickly press Vol-up and Power button to boot to recovery (this should take about 20~30 seconds).
<!> You should have OrangeFox up and running now.
Post-Installation:
MUST: Trigger Multi-disabler.
1. In OrangeFox, go to Terminal.
2. Type multidisabler, then enter. If it fails with something about vendor free space, run it again.
3. Run multidisabler again.
4. Go to main screen. go to Wipe > Format Data, type yes then swipe.
5. Reboot to Recovery. Now you can do other stuff.
Should: Backup all vital partitions:
1. In OrangeFox, go to Backup
2. Backup: EFS, Modem, NVRAM.
Enjoy: Reboot your phone to have a rooted stock, install custom stuff or do whatever you want.
Upgrade:
<!> Use when you already have any custom recovery installed (TWRP, SHRP, PBRP and the likes)
1. Download the recovery image.
2. Copy it to phone, then reboot to OrangeFox (Combo is Power + Volume-up)
3. Go: Install > select recovery.img file > select Recovery
4. Swipe to confirm flashing.
5. If success, reboot to recovery.
<!> You can also use Odin to upgrade, the steps similar to the Install section. All Post-installation, if already done, is unnecessary to do again.
Credits:
To the OrangeFox and TWRP team and everyone involved in making this all work.
@Long266 For his kernel and amazing work.
@ianmacd For multidisabler.
@afaneh92 For his a32x base tree and MTK-Samsung multidisabler.
@KrutosVIP For his experimental lineage kernel source from here.
reserved
reserved
I have tried to talk to various developers about the settings not saving issue. They have no idea. I have myself tried playing around with the tree but nope. So unless someone has a fix for this i have no idea
New Build!
Whats new?
Fixed the settings such as theming resetting on reboot by editing the bootable/recovery/twrp.cc and at line 396 (as of now) changing the bool to true. This makes the recovery load the themes twice. This should only be for encrypted devices but since it has fixed our issue we'll use this workaround until a proper solution has been found.
If you see the recovery trying to decrypt storage dont worry about it. its just because of this. It does nothing.
It's stable? I mean, i can install gsi's and zips?
ApiYoshi said:
It's stable? I mean, i can install gsi's and zips?
Click to expand...
Click to collapse
yes i use orangefox. flashing gsi works fine. same goes with zips
Captain_cookie_200 said:
yes i use orangefox. flashing gsi works fine. same goes with zips
Click to expand...
Click to collapse
Ok, i flashed it and is awesome!! Thanks for great work brother!
ApiYoshi said:
Ok, i flashed it and is awesome!! Thanks for great work brother!
Click to expand...
Click to collapse
You should make a telegram group
ApiYoshi said:
You should make a telegram group
Click to expand...
Click to collapse
i dont really know on how to maintain one. me and someone else made it but its sitting dead i'll see later on. and i'll post a thread abt it if there are any updates
Works in A32 A325M Brazil variant.
really nice you are keeping the a32 alive!
applesucksLmao said:
really nice you are keeping the a32 alive!
Click to expand...
Click to collapse
i did nothing tbh. all the credit goes to the people who put effort in making twrp work i just copied and built it. all the credit goes to them
Captain_cookie_200 said:
i dont really know on how to maintain one. me and someone else made it but its sitting dead i'll see later on. and i'll post a thread abt it if there are any updates
Click to expand...
Click to collapse
Ooh, i undertand
One question, you will update the recovery when an update came out?
ApiYoshi said:
One question, you will update the recovery when an update came out?
Click to expand...
Click to collapse
yes i will try
Where do I get the orange fox TAR, I see it in the steps but I don't see it to download it
Seth Ofc said:
Where do I get the orange fox TAR, I see it in the steps but I don't see it to download it
Click to expand...
Click to collapse
sorry i didnt include it. but i think i specified. rename OrangeFox recovery img file to recovery.img
then use 7zip or winrar or any other archiver and then add to archive. There select tar and compress. I'll include tar files in next builds by default
Thanks I already compressed the recovery.img to recovery.tar, do you know of any aosp rom for the a325m I was looking for but I can't find it
Seth Ofc said:
Thanks I already compressed the recovery.img to recovery.tar, do you know of any aosp rom for the a325m I was looking for but I can't find it
Click to expand...
Click to collapse
use a generic system image.
if you want heres a list: here