[10][OFFICIAL] CarbonROM | cr-8.0 [z3] - Xperia Z3 Original Android Development

{
"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.

Related

[Recovery] Official TWRP for Galaxy S6 edge+ (3.0.2-1)

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

[Recovery][J710F/FN/GN/MN/K] Official TWRP for j7xelte (Galaxy J7 2016 Exynos)

Team Win Recovery Project 3.0.2-0
This is for the Exynos SM-J710F, SM-J710FN, SM-J710GN, SM-J710MN, SM-J710K models only!
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/samsunggalaxyj72016exynos.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
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.
Make sure your don't have Factory Reset Protection enabled in your Google account or you may never be able to boot again!
More information: https://support.google.com/nexus/answer/6172890?hl=en
Extract Odin_3.10.7.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for j7xelte.
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, under Options tab disable Auto Reboot, then press [Start].
Once the flash is complete (Odin should tell you in the log, and progress bar on phone should stop), you can pull the battery then place the battery back in. Now hold [Volume Up] + [Home] + [Power] buttons until you reach recovery mode.
If you end up in stock recovery, start again from download mode step.
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/jcadduono/android_device_samsung_j7xelte (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_exynos7870 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
@jcadduono ,
Thanks for official TWRP.
Hello guy !
@jcadduono , thank you very much for great work ! It's fully working for my SM-J710FN
My internal storage doesnt mount. Requires to format data. And when i format the data, it becomes ok, and when you try to enter recovery again it doesnt mount the data, internal storage..
Sent from my SM-J710GN using XDA-Developers mobile app
Not sure if both are related but I had flashed this TWRP 4-5 days back. Last night after reboot (wasn't the 1st one after flashing certainly), phone didn't boot because of custom binary FRP lock. Had to reflash firmware.
@jcadduono why is the internal storage is not showing and why data is not mounting it gives always error
Amit.A said:
@jcadduono why is the internal storage is not showing and why data is not mounting it gives always error
Click to expand...
Click to collapse
jhampzkidoodle said:
My internal storage doesnt mount. Requires to format data. And when i format the data, it becomes ok, and when you try to enter recovery again it doesnt mount the data, internal storage..
Sent from my SM-J710GN using XDA-Developers mobile app
Click to expand...
Click to collapse
Normally on the newer Samsung devices we can flash https://idlekernel.com/fun-stuff-trust-me/no-verity-opt-encrypt/ and then go to the wipe page and use [Format Data] to turn off encryption.
It seems there is a bug with the Exynos 7870 devices that causes vold to encrypt the device regardless of whether or not boot image fstab actually calls for encryption, and I've tried removing all hints of encryption support from the boot image and yet still the system will start encrypting on the next boot.
TWRP does not support Samsung's closed off encryption as it relies on the Android OS frameworks.
I've tried submitting this issue to Samsung's Mobile Security team but they just shrugged it off and said you can't turn it off on purpose.
So pretty much you're SOL for data partition (internal storage is inside that) reading in TWRP until someone comes along with system modifications to disable encryption or a custom ROM.
Hi bro... @jcadduono
Thanks for making Official TWRP Recovery for our J7 2016. Really its great work Thanks again. :good:
I have a 2016 SM-J700P... with the Exynos processor. Will this TWRP work for me?
Guys, will the fact that I now have TWRP recovery (I have a J7 J700M Model, from Brazil), using Android 5.1.1 -> Android 5.1.1 (debloated) cause any harm if I try to install 6.0.1 Marshmallow (http://live.samsung-updates.com/index.php?device=SM-J700M) using ODIN??
Thanks!
@jcadduono with the custom kernel http://forum.xda-developers.com/galaxy-j7/development/recovery-samsung-galaxy-sm-j710f-t3380736 encryption can be turned off.
thewinelover said:
I have a 2016 SM-J700P... with the Exynos processor. Will this TWRP work for me?
Click to expand...
Click to collapse
I doubt it, it has different exynos processer
artssa said:
Guys, will the fact that I now have TWRP recovery (I have a J7 J700M Model, from Brazil), using Android 5.1.1 -> Android 5.1.1 (debloated) cause any harm if I try to install 6.0.1 Marshmallow (http://live.samsung-updates.com/index.php?device=SM-J700M) using ODIN??
Thanks!
Click to expand...
Click to collapse
Offtopic post you have. Shouldn't be a problem for flashing a firmware for your device via Odin, whichever ROM you are using.
Join us Samsung Galaxy J7 2016 users Samsung Galaxy J7 ? Official Group in Telegram
Here you can chat with anyone.
Here many xda developers are present.
Here you can share any kind of data and files in any size.
And the biggest thing is that here you will get instant solution to any problem. :good:
Telegram Group Link : https://telegram.me/joinchat/Cmh8LUAs6AFEJUfawPCiWg
Regard by @KeMii :good:
I Root the Device but After root there were many issues..... I Keep on getting an notification that unauthorized action ...
and also my device keeps lagging it lags just for a second but this games every 2-3 mins
I also freezed KNOX with lucky patcher but the problem still persists any meathod to solve the problem Thanks
Installed Xposed... Few Modules and Partition Crushed... It was my Brand NEW Phone :'(
Hello, TWRP backup not properly block set. The size of EFS equal to 4 MB in size, inside the reserve of zeros.
No IMEI as all zeros!
Need to fix, or put my. In my TWRP you can flash system.img from firmware.
Good luck to everyone! TWRP is correctly bekapit EFS.
Extract postcode to flash the IMG.
http://4pda.ru/forum/index.php?s=&showtopic=763247&view=findpost&p=51990201
Here you can find a lot of useful for this smartphone. Please forgive me for my English :laugh:
The Lord does not forget to thank! And then I see the downloading is not weak and thanks to zero.​
ermakovermakov7878 said:
Hello,your TWRP backup is not correct unit is specified. The efs size is equal to 4MB, inside backup zeros.
I took apart and tell it like it is. That's correct TWRP backup efs + setting backup System.img
Unpack the zip to flash the img.
http://4pda.ru/forum/index.php?s=&showtopic=763247&view=findpost&p=51990201
Here you can find a lot of useful for this smartphone.
Please excuse me for my English :laugh:
Click to expand...
Click to collapse
But it is all in russian :/
Will this work with J7-2016 with Snapdragon 617 ?
Skylinestar said:
Will this work with J7-2016 with Snapdragon 617 ?
Click to expand...
Click to collapse
No
will it work on Galaxy J7 prime ? it has same exynos 7870..
jcadduono said:
Team Win Recovery Project 3.0.2-0
FULL STEPS FOR OBTAINING ROOT
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
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.
Make sure your don't have Factory Reset Protection enabled in your Google account or you may never be able to boot again!
More information: https://support.google.com/nexus/answer/6172890?hl=en
Extract Odin_3.10.7.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for j7xelte.
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, under Options tab disable Auto Reboot, then press [Start].
Once the flash is complete (Odin should tell you in the log, and progress bar on phone should stop), you can pull the battery then place the battery back in. Now hold [Volume Up] + [Home] + [Power] buttons until you reach recovery mode.
If you end up in stock recovery, start again from download mode step.
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.
Click to expand...
Click to collapse
i have SM-J710FN. if I only follow below 3 steps, then will i b able to root my device ??
1. allow usb debugging and OEM unlock
2. flash official TWRP via Odin ... then re insert battery & reboot into TWRP
3. wipe data in TWRP and then falsh SuperSU via TWRP
is it enough.. Do I need to flash kernels first ??

[RECOVERY][TWRP 3.3.0][7.0/8.1/9.0] Galaxy J7 (2017) [17.04.2019]

{
"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 2017​Disclaimer
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

[RECOVERY][3.5.0_9-0][teak]Unofficial TWRP recovery for Sony Xperia XA1 Plus

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.
C:
#include <std_disclaimer.h>
/*
*
* 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.
*
*/
What working:
Normal and Encrypted backup and restore
Install flashable zip
ADB sideload
Mount almost every partitions
Turn off TWRP app promt because I'm not gonna make this offical build any way (Feel free to do so if you can and want to)
What not:
Time zone need to set manually
Can't decrypt /data (Hope some one who know vold decrypt can help me with that)
Usage:
To flash this twrp, run following command:
Code:
fastboot flash recovery recovery.img
To boot it, simply turn your device off and when you turn it back on, just hold power and volume down and wait for few second to enter recovery
P/S: Although this twrp was build for Xperia XA1 Plus specificly, it might work on other XA1 variants as well, for that I need some tester. The only different if exists is the build.prop which stop you to flash custom rom that not build for XA1 plus (which we don't have any as of yet) so just try it and give me some feed back
Source code:
https://gitlab.com/ndhai97/android_device_sony_teak/-/tree/twrp
Credits:
Big thank to @AlaskaLinuxUser who make great video series that give me a very good entry point to do this kind of work
Good job, just in case, put in my custom prop.default (for xperia g3123 xa1 simple) and I start without problems.
test: adb shell, backups, flash zip. Can't format/mount data, and it would be great if you add the fotakernel partition in recovery.fstab to make a recovery backup
If your /data being encrypted then I don't have any solution for that yet. I will add fotakernel later but could you also test mtp, it not working at my Archlinux setup, don't know if my setup has issue or mtp just broken on my twrp build I use adb sideload all the time so
Hi bro, I have an XA1 Plus with the last firmware version... Android 8.0 (48.1.A.2.122)
Do you think that this recovery.img could works on my phone?
Nice work! Glad to see you are making TWRP and sharing!
hello sir mine device (sm-615f) has same specs as this device ...and i tried porting it to my device( replaced kernel and kernel offset ) and in ramdisk replaced /etc/recovery.fstab and uevented.rc ....but not working... and reason being doing that is i see lot of gsi thing is also avail for your device ..can i port it if yes can you bit guide me there ( NOTE: already done research before bothering mentors here ) ..
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
format ur data then flash dis from ur sdcard
Wadhwa Saab said:
hello sir mine device (sm-615f) has same specs as this device ...and i tried porting it to my device( replaced kernel and kernel offset ) and in ramdisk replaced /etc/recovery.fstab and uevented.rc ....but not working... and reason being doing that is i see lot of gsi thing is also avail for your device ..can i port it if yes can you bit guide me there ( NOTE: already done research before bothering mentors here ) ..
Click to expand...
Click to collapse
For that matter you should PM me instead of comment in here, I see not much of react to my work and so I stop all development. about your question, our device (XA1) have no GSI so it not problem to begin with (GSI thread are fake, I do build from scratch so I know). Also I think it easier for you to build twrp than port it, you can take a look at my twrp device tree and create one for your device twrp tree. About how to build it watch Alaska Linux User youtube series here. It very easy to do than porting and it work correctly for your device, not to mention update twrp quite easy task too.
Hello there
I installed TWRP on my Sony Xperia XA1 Plus but could not start TWRP mode. The following error appears on the screen, then the phone boots normally.
{
"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"
}
To enter recovery, when booting hit vol down button. This is not an FOTA kernel so the flashlight won't go up to indicate you to enter recovery or normal boot, instead it sit in recovery partition of your phone (which mean with what ever kernel or boot image that you using, this recovery still work)
Hari Nguyen said:
To enter recovery, when booting hit vol down button. This is not an FOTA kernel so the flashlight won't go up to indicate you to enter recovery or normal boot, instead it sit in recovery partition of your phone (which mean with what ever kernel or boot image that you using, this recovery still work)
Click to expand...
Click to collapse
I have tried entering the TWRP mode multiple times. It is not happening. I'm already pressing the volume down button.
I am trying it on Android8 .122 ROM.
My device is g3421
Emirhan4646 said:
I have tried entering the TWRP mode multiple times. It is not happening. I'm already pressing the volume down button.
I am trying it on Android8 .122 ROM.
My device is g3421
Click to expand...
Click to collapse
Sorry for long time response, quite busy these day. How adb flash command output look like, if it successful then maybe you press it the wrong way, it should enter recovery when you boot up and hold the volume down. There are two other way to test this: the easy way is to run adb reboot recovery. The harder way is to install xposed and choose reboot to recovery from xposed manager, I'm quite sure this work on all Oreo based variant of XA1, my friend have XA1 ultra and it work just fine
I learned that the recovery mode cannot be entered with the buttons on this device, but I can enter the recovery mode with the buttons with the special kernel.
Here's how I enter recovery mode with stock kernel:
1- USB debugging must be turned on
2- I am typing the following command on adb and when it restarts, recovery is opened. ''adb reboot recovery''
Emirhan4646 said:
I learned that the recovery mode cannot be entered with the buttons on this device, but I can enter the recovery mode with the buttons with the special kernel.
Here's how I enter recovery mode with stock kernel:
1- USB debugging must be turned on
2- I am typing the following command on adb and when it restarts, recovery is opened. ''adb reboot recovery''
Click to expand...
Click to collapse
You should be able to enter recovery with power on + hold vol down at the same time (or when rebooting just hold the vol down button). If your special kernel mean kernel where it show light when booting, that recovery work independence with my recovery since they put it inside boot partitions. My recovery are being put in recovery partitions and should not be affected by any other boot.img
Hello, which firmware version does this need to work? I know with the older recoveries then installing them with the wrong firmware caused a bootloop.
I have an xperia XA1 Ultra G3221 with unlocked bootloader and ta backups. (I think using xa1 plus recovery on ultra is a bit sketchy to be honest but you say apparently it works)
Currently I am on 1306-6285_48.1.A.0.129 (yes it is old - I don't know why to be honest, Emma tool is really strange, it replaced my original updated O2 UK firmware with old nordic global firmware? what?)
I could use flashtool to update it if I need to I suppose, should probably factory reset first anyway.
Also this can be used to install magisk right? Thanks
Update: I updated to latest firmware and it didnt work, it just said "your device is unlocked and the boot image is not working" and shuts off. Thankfully that's only when I hold volume down though, powering on normally is fine.
Hi, My XA1 Plus (G3426) got some problem in starting fastboot. It just got bootloop when I try to make it fastboot with adb, and the situation only resolved after I relock it with Flashtool. The full recovery of Xperia Companion didn't change the situation, this machine always bootloop when it asked fastboot from adb if bootloader unlocked, and just can't detect as fastboot device if hard started with volume down, locked or unlocked.
Since I can't make it fastboot I think I can't flash this img. Any suggestions for this?

[ROM][SOFIAP][11][UNOFFICIAL][GAPPS][VANILLA] ArrowOS

{
"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"
}
ArrowOS​
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : via the Matlog app included or check how to
DOWNLOADS
08-04-21 Build - GAPPS/VANILLA
INSTALLATION - TWRP
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and copy to your external sd card
Download/Install Android 10 firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
Flash the ArrowOS zip
REBOOT TO RECOVERY!!
Reboot to system
Profit
INSTALLATION - FASTBOOTD
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and extract it to your adb/fastboot folder
Download/Install Android 10 firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
In TWRP reboot menu, select fastboot, wait for it to reboot
Open a cmd window where you extracted the files to earlier and flash the ROM with the below commands
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash product product.img
fastboot flash system system.img
Reboot to system
Profit
*** Dont install Magisk until you have booted the ROM once
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/Odin1101/Project-Sofia/tree/Upstream-plus
Device Source: https://github.com/whatthef84/android_device_motorola_sofiar-1
Vendor Source: https://github.com/whatthef84/android_vendor_motorola_sofiar-1/tree/android-11
Many thanks to @vache for the above device/vendor trees, the flash tool, and building TWRP. The guy's a legend!

			
				
Phone failed to run arrow OS. It just constantly going back to bootloader when restarting system. I'll figure it out later, luckily I've made backups so I have something to fall back on
You know what, I attempted an adb sideload as an "attempt", and it worked after fidgeting around TWRP for about 20 minutes. But for some reason, I'm on slot b. Weird, but it worked...
@Beetle84 Thanks for yet another one. But since you're dumping everything but this, may I ask what about arrow specifically made got want to switch to it alone?
Also, why do we need to go back to stock? Just to minimize errors? I don't understand. More precise and revelant debugging?
Thanks again I've been wanting to try this one but just had a couple questions lol
griz.droidx said:
@Beetle84 Thanks for yet another one. But since you're dumping everything but this, may I ask what about arrow specifically made got want to switch to it alone?
Also, why do we need to go back to stock? Just to minimize errors? I don't understand. More precise and revelant debugging?
Thanks again I've been wanting to try this one but just had a couple questions lol
Click to expand...
Click to collapse
Mainly the simplicity of it, and it has all the features I need.
Going back to stock first with the flash tool is mainly about prepping the b slot for TWRP flashable ROMs.
@Beetle84 is there a way to add the customization tool from the other 2 OS? I like this one based on Android 11 but I also like the customization from RR. I'm just curious.
ShadowWeasel said:
@Beetle84 is there a way to add the customization tool from the other 2 OS? I like this one based on Android 11 but I also like the customization from RR. I'm just curious.
Click to expand...
Click to collapse
Nah, not compatible, are you using telegram? I shared a build of Evo X there, that sounds like the sort of rom you are looking for.
Beetle84 said:
Nah, not compatible, are you using telegram? I shared a build of Evo X there, that sounds like the sort of rom you are looking for.
Click to expand...
Click to collapse
I just installed it
Beetle84 said:
Nah, not compatible, are you using telegram? I shared a build of Evo X there, that sounds like the sort of rom you are looking for.
Click to expand...
Click to collapse
Hey @Beetle84 where can I find the Evo X build
ShadowWeasel said:
Hey @Beetle84 where can I find the Evo X build
Click to expand...
Click to collapse
EvolutionX - 5.x - Google Drive
Beetle84 said:
EvolutionX - 5.x - Google Drive
Click to expand...
Click to collapse
Should I flash this thru stock or twrp version of fastbootd? also, gapps or vanilla?
Edit: I answered my own questions. I'll check out everything and let you know how things went. Too bad I don't know how to make roms, otherwise I'd help out
ShadowWeasel said:
@Beetle84 is there a way to add the customization tool from the other 2 OS? I like this one based on Android 11 but I also like the customization from RR. I'm just curious.
Click to expand...
Click to collapse
But he just said this ROM had all the features he needs. I like the adjustable purtiness of RR as well but I'm ready to give this a run after trying stag 11.
Theres still CR and Stag. Either way we're very fortunate to have the choices we have. I've been wanting to try my hand at building and just bought a new multi-purpose lappy but still haven't put in the time. These guys are essentially donating time, talent, and treasure (ITM) to what is a damn good cause IMHO.
I'm ready to try a no-bs os myself as my battery life is in the ditch.
Does Micro G work with this Rom?
@EpicSaga Not sure mate, ive never tried.
Absolutely it does! Microg works fine, as is or as a magisk module. I use the magisk module from the magisk app because you get basic installation and everything works. You only need to open the app and go to self test and click each item missiing their permissions for most everything to be added. Still need to get your nlp services added and enabled for network based location services.
I was just yesterday afforded the time to install and try the rom. I can definitely see the appeal of the minimalistic approach and I really like how the ROM specific settings are integrated into the existing categories instead of in a dedicated tab.
If I had only one wish it'd be for the long swipe long press options to kill apps and so on. Don't get me wrong it affords plenty of customizations and seems to be a fine ROM. I'm going to give it a go to see how things roll.
Beetle84 said:
ArrowOS​
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : via the Matlog app included or check how to
DOWNLOADS
08-04-21 Build - GAPPS/VANILLA
INSTALLATION - TWRP
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and copy to your external sd card
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
Flash the ArrowOS zip
REBOOT TO RECOVERY!!
Reboot to system
Profit
INSTALLATION - FASTBOOTD
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and extract it to your adb/fastboot folder
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
In TWRP reboot menu, select fastboot, wait for it to reboot
Open a cmd window where you extracted the files to earlier and flash the ROM with the below commands
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash product product.img
fastboot flash system system.img
Reboot to system
Profit
*** Dont install Magisk until you have booted the ROM once
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/Odin1101/Project-Sofia/tree/Upstream-plus
Device Source: https://github.com/whatthef84/android_device_motorola_sofiar-1
Vendor Source: https://github.com/whatthef84/android_vendor_motorola_sofiar-1/tree/android-11
Many thanks to @vache for the above device/vendor trees, the flash tool, and building TWRP. The guy's a legend!
Click to expand...
Click to collapse
Soon as I upgrade to the moto 5g ace u keep surprising us with your awesome work.
Hopefully you get the 5g ace and port this rom to it. If you don't get the phone thanks for all the fun you gave me on this phone and the moto g power..
Stay cool..
jhjhjhjhjhjh said:
Soon as I upgrade to the moto 5g ace u keep surprising us with your awesome work.
Hopefully you get the 5g ace and port this rom to it. If you don't get the phone thanks for all the fun you gave me on this phone and the moto g power..
Stay cool..
Click to expand...
Click to collapse
Thanks man, ive actually gone and bought the g 5g plus, awesome phone.
Beetle84 said:
Thanks man, ive actually gone and bought the g 5g plus, awesome phone.
Click to expand...
Click to collapse
Yes great phone only thing I wish it had dual speakers like the stylus but loving the 5G.
I already rooted it hours after I bought it lol.
I'll see you on the 5G Ace form then.. I'm happy you got the phone bro....lol my phone says 5G Ace yours 5G plus. Wonder what the differences are??..
How big is the battery in the g 5g plus? I live in the frigging hills and according to some coverage maps there's 5g close to home can't remember which cartier. T-mo/Sprint probably

Categories

Resources