Related
All work belongs to @jesec - original thread here
All i have done is repacked with the required files for the G950.
@Jesec original OP is below.
Thread under construction.
Team Win Recovery Project 3.1.0-r1
Confirmed working on Korean and International variant. Should also work on other Exynos variants.
NOTE: YOU MUST ENABLE "OEM UNLOCK" (located in Developers options) BEFORE YOU DO ANYTHING.
As kernel source is not released, some features such as MTP are not available for now.
#include <std_disclaimer.h>
Download: (Flash via Odin)
dreamlteks (Korean version - SM-G950N) (compatiable with International version - SM-G950F/FD):
HOW-TO ROOT AND/OR DISABLE ENCRYPTION/DM-CRYPT:
I noticed that it could be really difficult to operate when /data partition is encrypted (can't view your internal storage from TWRP) and MTP/ADB is unavailable (can't transfer files from computer to phone).
So I included 2 flashable zips in recovery image itself.
They are located in /twres/flashables/.
To disable encryption/dm-crypt, just simply flash "no-verity-opt-encrypt.zip". It will disable dm-crypt and make /data encryption optional. Then you can go to Wipe menu to wipe your /data partition to finally disable encryption.
To root, just simply flash "Magisk-v12.0-arm64.zip". It will install Magisk on your phone.
XDA:DevDB Information
[RECOVERY] TWRP for Galaxy S8 (Exynos), Tool/Utility for the Samsung Galaxy S8
Contributors
mwilky, jesec
Version Information
Status: Beta
Created 2017-04-23
Last Updated 2017-04-23
As mentioned in the S8+ thread, I'm using the G950F and can get into TWRP fine. But once there, the touch-screen doesn't respond.
Kevin_R said:
As mentioned in the S8+ thread, I'm using the G950F and can get into TWRP fine. But once there, the touch-screen doesn't respond.
Click to expand...
Click to collapse
yup this fixes that
mwilky said:
yup this fixes that
Click to expand...
Click to collapse
Just tried it and it still doesn't work, unfortunately.
Just noticed, they both point to the exact same file despite the urls being different
Kevin_R said:
Just tried it and it still doesn't work, unfortunately.
Just noticed, they both point to the exact same file despite the urls being different
Click to expand...
Click to collapse
forgot to update link, now fixed
Thank you for your quick work.
I can't flash anything because my phone can't mount /data in recovery. I don't know why tried various methodes
EDIT: a full wipe made the job, working perfectly! Thank you
So how do you get into Download mode or Recovery mode in the S8 with no hard home button? Haven't seen that definitively answered anywhere.
norm2002 said:
So how do you get into Download mode or Recovery mode in the S8 with no hard home button? Haven't seen that definitively answered anywhere.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s8/how-to/youtube-guide-how-to-enter-exit-t3594947
This is why I regret getting the snapdragon variant. I'll make sure to get the exynos note 8 when released
Anyone tried Android Pay with Magisk to confirm it works?
Aside from that awesome work!
@mwilky I made a detailed tutorial on how to install TWRP and ROOT the Galaxy S8 on YouTube. It would be great if you could put it in the first post so people can easily see how to flash and root their device. Thanks a lot for your implication, I got my device 5 days ago and now it's completely ROOTED. Long live XDA Developers!
Just booted to Download mode, and it said: "rpmb fuse blown" Wonder what that is? Also the recovery looks a bit more useful and I entered a maintenance mode, looked like a slimmed down recovery
do I have to erase data or can I just install root?
Used the updated link and now it's working perfectly. Can even use my banking apps which used to always manage to detect root! Thanks for getting us root so quickly!
thanks
You can backup apps with data with Helium before wiping, saving some hours of manual restoration of app settings
Thread closed
Thread closed.
Official thread by jesec is now here: https://forum.xda-developers.com/galaxy-s8+/development/recovery-twrp-galaxy-s8-exynos-t3594756
INTRODUCTION
I posted my configuration before inside a couple of threads. After that, I have received a lot of questions about the same issues. I have also been asked to create a thread so newbies could have an easy way of having an Oreo system up and running in the Axon 7. So I am doing it. Newbies will have an easy entry point to the world of custom Oreo ROMs and a single point to clarify any question. We have a healthy and active Axon 7 scene here at XDA. This guide provides a path to have a custom Oreo system with the latest features available for this device requiring a minimum effort. It applies to any of the 3 Axon 7 flavors: A2017 (China), A2017G (Europe) and A2017U (Americas) with any memory and storage capacity. At this time there are 3 groups of ROMs depending on the Bootstack and GSI support:
1. B32+B10 ROMs use the reliable Nougat bootstack. They are very stable and battery efficient. On the other hand, none of them support dual SIM or HDR+ camera. However they support HDR and Camera2 API.
2. B12 without GSI support ROMs use the Oreo beta B12 bootstack. Full support for Camera2 API and HDR+ but very poor battery performance and stability issues.
3. B12 with GSI support ROMs also use the same Oreo beta B12 bootstack. They also require a separated vendor partition. They share the same benefits and limitations of the previous group. So far they are experimental and the Treble ROMs don't support yet all the Axon 7 Hardware when using them along with a GSI image. They are examples of a Work-In-Progress that is yet to be finished.
WHAT THE HECK IS TREBLE AND GSI?
Since Oreo, all the new devices must have a separated vendor partition to fulfill Google's Treble project requirements. This way the OS is structured in two parts:
1. Treble ROM: includes all the device drivers and vendor related files in the vendor and boot partitions. The Treble ROM is owned and updated by the device vendor or a custom ROM developer.
2. Generic System Image (GSI): Includes the Android OS, it is controlled by Google and allow generic and frequent security and system feature updates directly from Google. It uses the system partition.
So far, custom Android distributions such as LineageOS, Resurrection Remix, AOKP, Dirty Unicorns, AEX, etc... had to create specific ROMs for each supported device. This was painful and it all was depending on the willingness of a developer to maintain a version for each device. Thanks to Treble project, now Android distributions just release a single GSI able to be installed in any device using a Treble ROM. This way they can properly maintain all the devices with a single GSI image by focusing on frequent updates of a single GSI. These custom distributions will also deliver the security and feature updates by Google. So a fully Treble ROM for the Axon 7 will open the door to virtually all the Android distribution out there.
@NFound in the AEX ROM thread) is the only one working in developing a Treble ROM for our device. He has released some incomplete Treble ROMs coupled with non-generic system images. Others like @Kranoner in the Hellsgate Kernel thread or @OrdenKrieger in the LineageOS 15.1 are building and kindly sharing unofficial releases of several custom Oreo 8.1 ROMs that are used in the EDL packages below.
@Victor13f has also created guides on how to install the leaked Stock Oreo 8.0 Beta B12 ROM. I really advise to upgrade to any of the current Oreo ROMs since the current unofficial releases work way better than the previous Nougat versions. The custom AOSP Oreo 8.1 ROMs offer a wider spectrum for tweaking for better performance and battery. Custom kernels are adding full featured and optimized drivers for custom ROMs. They support almost everything, including backported drivers from the latest Linux 4.xx official kernel sources.
BACKUP:
Please note that a dirty flash won't work when coming from any non Treblerized Axon 7 (Axon 7 without the vendor partition). So, if you want to keep your information, then you should do a backup of your data before continuing with this guide. You can use the file manager to move your Documents, Downloads, Music, Pictures, Videos, etc... from your internal storage to an external SD card. You can upload them to a cloud service such as Google Drive, One Drive, MEGA, DropBox, etc. Or use the USB connection to move your information to your PC.
DEVICE UNLOCK:
Unlocking your bootloader will trigger a factory reset, and will delete the internal storage along with all the information in your phone. If your Axon 7 bootloader is still locked, you have to follow this guide before proceeding to the rest of this guide. It works for Marshmallow and Nougat stock phones. Please use that thread to ask any question related to unlocking your device.
INSTALLATION INSTRUCTIONS:
WARNING, THIS GUIDE WILL WIPE ALL THE DATA IN YOUR DEVICE, INCLUDING THE INTERNAL STORAGE.
IT REQUIRES YOUR DEVICE TO BE UNLOCKED, OTHERWISE YOUR DEVICE COULD BE BRICKED.
!!! Whatever you do, it is at your own risk !!!
In case you get stuck at any point in this guide, do not panic! There is a straightforward way to go back to stock. Just follow this Unbrick/Restore guide. I've tried to make things as easier as possible for everyone, specially newbies not used to deal with the Axon 7. So, I have created stable custom EDL packages. In order to reduce the risk and complexity, this one Stop ROM Shop performs all the following actions in a single flash:
- installs TWRP custom recovery
- installs my customized Bootstack
- removes unlocked bootloader annoying warning message.
- installs custom Oreo ROM.
- installs google apps.
- installs custom kernel.
- installs magisk root
- creates vendor partition to treblerize your phone, this way it will be futureproof.
- formats vendor partition as ext4 filesystem to complete the previous task.
- And the guide also helps you to format data and cache as f2fs in case you haven't done it already. It provides better battery, performance and extends the lifespan of the internal flash.
I provide here 2 basic EDL package options. Both of them include the vendor partition so you won't have to perform any additional formatting and backup when upgrading to treble roms. Both options are this way future proof, just choose one of them:
OPTION 1: B32+B10 based EDL Package if you prefer stability. It includes:
- N+O custom Bootstack (B32+B10)
- TWRP 3.2.1-7 recovery by NFound
- Resurrection Remix Oreo 6.0.0 2018.05.11 ROM By Kranoner
- Google apps (ARM64, 8.1, micro)
- HellsGate v3.0 Kernel by Kranoner
- Magisk root 16.7
OPTION 2: B12 based EDL Package If you require dual SIM or full support for HDR+ camera apps. It includes:
- O custom Bootstack (B12)
- TWRP 3.2.2 recovery
- AEX 5.7 20180711 ROM by NFound
- Google apps (ARM64, 8.1, micro)
- HellsGate X12 GClang Kernel by Kranoner
- Magisk root 16.7
Once you had chosen your preferred option then proceed with these steps:
Download and Un7zip the chosen package to a folder in your computer, ensuring there are no errors. I have an A2017U, so the American modem is the package default. If you have an A2017 or A2017G just copy your modem firmware, from the corresponding provided modem subfolder, to the main folder. Just overwrite the default American modem file.
Install MiFlash in your PC. It includes the Qualcomm Snapdragon SoC drivers, nonetheless you can always install the latest Qualcomm drivers.
Enter EDL mode using one of the following options:
by pressing VolUp+VolDn+Power until the power led flashes briefly
Installing a terminal app and typing reboot edl at the app prompt.
connecting your phone to your PC and typing adb reboot edl at your computer's command prompt.
While your phone is completely off, press VolUp+VolDn while connecting your phone to your PC.
If you haven't done yet, it's time to connect your phone to your computer.
Open MiFlash in your computer.
Click Browse button and select the folder you created with the firmware files.
Click Refresh button and your device will appear listed as virtual COM port.
Click Flash button and wait for a few minutes until it finishes. Note the bottom options are not applicable.
Wait a few seconds until the boot animation begins and press again VolUp+Power until the phone vibrates to enter again into recovery. Go to Advanced > Terminal and now type: reboot "dm-verity enforcing"
Press VolUp+Power until the phone vibrates to enter into recovery, then release both buttons. Go to Advanced > Terminal and type: reboot disemmcwp
Wait a few seconds until the boot animation begins and press again VolUp+Power until the phone vibrates to enter again into recovery for a 3rd time. To ensure everything is clean you should format the DATA partition, including internal storage. Go to settings and ensure "Use rm -rf instead of formatting" option is not selected. Then go to Wipe > Advanced Wipe, select Data partition and tap on Repair_or_Change_File_System button and then on Change_File_System button. Select F2FS and confirm action. Do the same to apply F2FS to the Cache Partition. Now, from the main menu > Wipe, select and clean dalvik.
NOTE: If you receive an error while formatting data, then go to Wipe > Advanced Wipe, select Data partition and tap on Repair_or_Change_File_System button and then on Change_File_System button. Format DATA as EXT4 first and, without leaving TWRP do it again as F2FS. That will fix the issue.
Go to main menu and reboot system.
Complete the setup process so you can continue with the rest of the customizations not included in the basic package:
SOUND EXPERIENCE:
The following steps will provide you with Dolby ATMOS and Viper4Audio pre-processors along with the HiFi DAC output. Please note that the activation of these features will drain your battery faster since both will use your CPU. Nonetheless the benefits are evident. if you want to fully enjoy the audio capabilities of the Axon 7 you should go ahead and use them. The steps are:
Download Mixer_AK4490.zip and Dolby-Oreo.zip to your phone.
Open Magisk Manager app, go to the Download section and Download (do not install yet) Ainur Sauron, Viper4Android FX and Audio Modification Library.
Reboot to recovery the same way you did during System installation, press install, navigate to /sdcard/MagiskManager folder and install Ainur Sauron, Viper4Android (I prefer 2.5.0.5 and traditional interface, however it is all up your personal preference) and Audio Modification Library zip files in that order. Do not reboot after flashing these files, just navigate now to the /sdcard/Download folder and flash Dolby-Oreo.zip and Mixer_AK4490.zip
SCREEN COLOR ENHANCEMENT:
Download and install KCAL Color Calibration/enhancement app. I only modify the Saturation to 62 to get amazing vibrant colors from this AMOLED screen, nonetheless this is a very personal configuration. At the end this has to please your own eyes. . This app optional since Kernel Adiutor and EX Kernel Manager apps can also configure Qualcomm SoC Color Control.
AVOID BATTERY DEGRADATION:
Install Battery charge Limit [ROOT] app. Open it and set Limit charge to 85% and recharge below 79%. Do you want to avoid your battery to wear as the time go by? do not miss this guide to understand why this step is so important for the health of your device.
BETTER CAMERA:
+ Snap Camera App
I am using, and heavily recommend the paid version of Snap Camera HDR. It supports Camera2 API with full manual and HDR support. Find recommended settings here.
Testing now GCAM v4.0. Nonetheless so far I am just starting testing.
Bacon Camera is another Camera I am now actively testing.
The next level of this guide will provide with instructions on how to change recovery, ROM, kernels and all the details and options you have. It is late today so I'll finish it later.
Hope it helps. I will be updating this guide in the future as soon my configuration changes or I find new technologies, apps or patches. If you know about a better option just post your suggestions!
Thanks and credits go to @NFound, @Kranoner, @Infy_AsiX, @roisuke, @Skrem339, @djkuz and you too for bringing up issues and valuable solutions.
Yes! I almost pm'd you like 3 times to ask if you would do exactly this. By far, I am not a noob, but honestly, i can finally take the plunge now knowing i have a place to look back and proper steps. I still have yet to flash TWRP 3.1.1-7 because of the [no bet removing inscription] bit on that thread, but reading over it like a dozen times, im fairly confident the only thing that will not work correctly on my a2017u is removing the warning that my bootloader is unlocked. Correct me if Im wrong on that one. Thank you, @Oki. Many thanks, brother.
kitcostantino said:
Yes! I almost pm'd you like 3 times to ask if you would do exactly this. By far, I am not a noob, but honestly, i can finally take the plunge now knowing i have a place to look back and proper steps. I still have yet to flash TWRP 3.1.1-7 because of the [no bet removing inscription] bit on that thread, but reading over it like a dozen times, im fairly confident the only thing that will not work correctly on my a2017u is removing the warning that my bootloader is unlocked. Correct me if Im wrong on that one. Thank you, @Oki. Many thanks, brother.
Click to expand...
Click to collapse
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Oki said:
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Click to expand...
Click to collapse
This was actually why:
NFound said:
TWRP Exclusive™
For "U" models pacth cleaning inscriptions bootloader NO BET!
Warning! "Del Inscription" - only for A2017 and A2017G !!!
Click to expand...
Click to collapse
^^^^^^^^This was actually why I thought it didn't work. Honestly, I don't mind the warning. I just had to ascertain if that was the only issue. Nfound had already confirmed it worked on a2017u. And removing that warning hasn't ever mattered to me that much.)
kitcostantino said:
This was actually why:
^^^^^^^^This was actually why I thought it didn't work. Honestly, I don't mind the warning. I just had to ascertain if that was the only issue. Nfound had already confirmed it worked on a2017u. And removing that warning hasn't ever mattered to me that much.)
Click to expand...
Click to collapse
Well NFound just tried to say that his solution was not tested at that time in an A2017U. Actually the 2017U is unbrickable thanks to the hardware EDL mode of the Qualcomm SOC.
By the way, I have updated the OP. Now it matches my current configuration. I have also mentioned my current testing efforts in the battery and camera areas.
Regards
Hi. Any fix for Dual Sim? I read through XDA and it seems dual sim is still not fixed. I am getting tired with nougat ROMs but without dual sim I have to stick with it...
@kitcostantino, there's also another method to get rid of that startup message that might work.
http://forum.xda-developers.com/showthread.php?p=74445757
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
Hello,
just a little question: Does this guide work on the Axon 7 2017G too? The RR Oreo Rom are for the 2017U....
Thx
Dave_XDA said:
Hello,
just a little question: Does this guide work on the Axon 7 2017G too? The RR Oreo Rom are for the 2017U....
Thx
Click to expand...
Click to collapse
Yes, the guide is valid for any Axon 7 flavor: Chinese, Euro and Americas.
marcdw said:
@kitcostantino, there's also another method to get rid of that startup message that might work.
http://forum.xda-developers.com/showthread.php?p=74445757
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
Click to expand...
Click to collapse
It is actually the same method. TWRP flashes that aboot image when selecting the option I mentioned. I still see the TWRP method a lot better since it doesn't require any extra download. You can see all the images and add-ons when exploring the filesystem while in TWRP Exclusive.
Thx for your answer.
I got this Axon 7 from my brother with the AEX Oreo Rom install'd. I wanne try out the RR Oreo because i use'd the RR on my old ASUS Phone.
Do i need to install the Bootloader you linke'd in your guide or can i install the RR Oreo with a clean install over the AEX Oreo Rom?
Thx again
Dave_XDA said:
Thx for your answer.
I got this Axon 7 from my brother with the AEX Oreo Rom install'd. I wanne try out the RR Oreo because i use'd the RR on my old ASUS Phone.
Do i need to install the Bootloader you linke'd in your guide or can i install the RR Oreo with a clean install over the AEX Oreo Rom?
Thx again
Click to expand...
Click to collapse
There is no problem as long you have an Oreo Bootloader. Since you are already running a custom Oreo ROM it means you already have a valid bootloader. Thus, you only need to flash the RR-O ROM. Should you find any problem you can just flash the latest bootloader I link in the OP or go back to AEX. It is important to do a clean install when switching Oreo flavors, as you plan, otherwise you will face problems.
Thanks for this. Been running stock since I got the phone, but missing the old phone days where I used to flash something new like once a week. Gonna try this out tonight I think. Really appreciate the concise directions
Are there known issues in returning to B35 Stock, should the RR(O) prove unsatisfactory?
amphi66 said:
Are there known issues in returning to B35 Stock, should the RR(O) prove unsatisfactory?
Click to expand...
Click to collapse
No issues, you can always go back to B35.
Oki said:
It is actually the same method. TWRP flashes that aboot image when selecting the option I mentioned. I still see the TWRP method a lot better since it doesn't require any extra download. You can see all the images and add-ons when exploring the filesystem while in TWRP Exclusive.
Click to expand...
Click to collapse
Thanks for the info.
Never used/explored TWRP Exclusive's extras really. In my environment I might break something [emoji39] but cool that everything is there.
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
How long does the first boot after flashing the bootloader take? I don't seem to get past the ZTE powered by android screen.
Never mind. Just hold Power + Volume Up at boot.
Thanks !! Oreo AND RR together !!
I will flash it tomorrow on my A2017G !!
(maybe you should write the A2017G compatibility on the first page because this :
RR-O-v6.0.0-20180422-axon7-Unofficial.zip
for the ZTE Axon 7(2017U), by Kranoner
on androidfilehost almost made me missed it )
EDIT : Does this ROM+kernel have the dualsim problem ?
Oki said:
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Click to expand...
Click to collapse
After doing this, I can't unlock my phone after restart by entering password. On A2017U and AEX Oreo latest. Any1 had this issue?
If anyone does, here's the fix: https://forum.xda-developers.com/axon-7/help/to-remove-screen-unlock-pattern-t3768575
ashishv said:
After doing this, I can't unlock my phone after restart by entering password. On A2017U and AEX Oreo latest. Any1 had this issue?
If anyone does, here's the fix: https://forum.xda-developers.com/axon-7/help/to-remove-screen-unlock-pattern-t3768575
Click to expand...
Click to collapse
What have you really done my friend? This guide requires a complete cleanup so it is impossible that you had any locksettings after a clean install. If you follow all the steps and follow the guide then you shouldn't have any problem.
The lock settings get corrupted after migrating to f2fs, and you can also find that problem when dirty flashing some roms or kernels. For that reason, to take care of that step, in the f2fs migration link, there is a link to a very detailed way to cleanup the lock settings. You can find that guide here: https://forum.xda-developers.com/axon-7/how-to/guide-access-locked-axon-7-how-to-t3525403 but, it shouldn't happen when following the steps of this guide. By the way, this guide requires RR Oreo ROM, and you mention you are using AEX Oreo...
Hi Everyone,
Just wondering if there has been any update about custom recoveries for pixel 6. I've been checking the TWRP website and what not but there no info on the subject that I can see.
Just curious to know if anyone else has heard anything about custom recoveries yet
I asked about on one Telegram, I think that TWRP is out-of-date for newest Android version (main dev is on hiatus)
Newrooter22 said:
Hi Everyone,
Just wondering if there has been any update about custom recoveries for pixel 6. I've been checking the TWRP website and what not but there no info on the subject that I can see.
Just curious to know if anyone else has heard anything about custom recoveries yet
Click to expand...
Click to collapse
TWRP for Android 11 only came out in late 2021. It should come soon for 12. No ETAs obviously but they have a chat here: https://rebrand.ly/teamwin-recovery-zulip-community and make announcements here: https://twrp.me/
Thanks guys, it's good to know that it might still be a while away hopefully not too long. It does have some good features so fingers crossed it's sooner rather than later.
TWRP has been dead for the Pixels for over two years.
You need to learn adb and fastboot if want to mod the Pixels.
If you are lazy, you can use this program to do what TWRP can do,
📳🔥PixelFlasher for Google Pixel 6 Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
nutzcase said:
TWRP has been dead for the Pixels for over two years.
You need to learn adb and fastboot if want to mod the Pixels.
If you are lazy, you can use this program to do what TWRP can do,
📳🔥PixelFlasher for Google Pixel 6 Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
Click to expand...
Click to collapse
Got any recomendations for getting shell access on a phone that doesn't boot normally? That's about the only use I have for twrp, its ability to be fastboot booted without an install.
adamf663b said:
Got any recomendations for getting shell access on a phone that doesn't boot normally? That's about the only use I have for twrp, its ability to be fastboot booted without an install.
Click to expand...
Click to collapse
adb reboot bootloader
fastboot boot boot.img (I think that's the syntax but if not then fastboot help will show you)
bobbarker2 said:
adb reboot bootloader
fastboot boot boot.img (I think that's the syntax but if not then fastboot help will show you)
Click to expand...
Click to collapse
That won't help on a system that has boot issues.
there was a custom recovery ( lineage recovery i think) that came with a custom rom. i was reading about the rom a few weeks back(forget where), but the developer would not release the recovery separately.
so really there is no reason why TWRP or some other custom recovery could not be developed.
but with the lack of roms on XDA and limited custom roms elsewhere, i feel that the pixel 6 will have very very little support.
nutzfreelance said:
there was a custom recovery ( lineage recovery i think) that came with a custom rom. i was reading about the rom a few weeks back(forget where), but the developer would not release the recovery separately.
so really there is no reason why TWRP or some other custom recovery could not be developed.
but with the lack of roms on XDA and limited custom roms elsewhere, i feel that the pixel 6 will have very very little support.
Click to expand...
Click to collapse
Statixos or staticos , something like that.
nutzcase said:
TWRP has been dead for the Pixels for over two years.
You need to learn adb and fastboot if want to mod the Pixels.
If you are lazy, you can use this program to do what TWRP can do,
📳🔥PixelFlasher for Google Pixel 6 Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
Click to expand...
Click to collapse
Only thing I ever really used it for was a nandroid
I have a question that is probably really stupid. Twrp and other custom recoveries allow installing custom roms, staticos and the like are out. How do they do it without a custom recovery?
alarmdude9 said:
I have a question that is probably really stupid. Twrp and other custom recoveries allow installing custom roms, staticos and the like are out. How do they do it without a custom recovery?
Click to expand...
Click to collapse
You push it as a zip file on fastboot. They're is dotos, deep, statixos, grapheneos, protons, crdroid etc for device
So basically bypassing the recovery altogether.
twrp lets you flash your device without needing a pc.
not to mention backup , on device formatting. amoung very many other useful tools
nutzfreelance said:
twrp lets you flash your device without needing a pc.
not to mention backup , on device formatting. amoung very many other useful tools
Click to expand...
Click to collapse
The feature I miss most is adb and having access to the decrypted file system. Decryption was always a problem for twrp; I used to unset my phone unlock method to get around that.
nutzfreelance said:
twrp lets you flash your device without needing a pc.
not to mention backup , on device formatting. amoung very many other useful tools
Click to expand...
Click to collapse
I miss having the ability to do a complegte image of your phone. Comes in handy when you get stuck in a boot loop and have to do a factory reset. Is there any other program that can do a full backup like TWRP?
I really do not see the need for a backup of andoid on the Pixel 6.
Backup your data.
There are several ways now days to restore the Pixel 6 with Android 12 and above.
adb and fastboot are your friends.
Kernel manager apps have a flash tool built into them.
vandyman said:
I really do not see the need for a backup of andoid on the Pixel 6.
Backup your data.
There are several ways now days to restore the Pixel 6 with Android 12 and above.
adb and fastboot are your friends.
Kernel manager apps have a flash tool built into them.
Click to expand...
Click to collapse
none of the ways you mention are possible with only a pixel6 and nothing else.
i cant tell you how many time when i was away for vacation or on a trip where i have flashed a rom on my S7. even a few times when some new software borked my phone and i could boot to recovery and RECOVER my device.
you can go to the custom kernel posts here and look at how many people have soft bricked their phone in April with a bad kernel. with a TWRP recovery they could have flashed a backup and never left their chair.
how can anyone say that more tools to fix things is in anyway a bad thing.
nutzfreelance said:
none of the ways you mention are possible with only a pixel6 and nothing else.
i cant tell you how many time when i was away for vacation or on a trip where i have flashed a rom on my S7. even a few times when some new software borked my phone and i could boot to recovery and RECOVER my device.
you can go to the custom kernel posts here and look at how many people have soft bricked their phone in April with a bad kernel. with a TWRP recovery they could have flashed a backup and never left their chair.
how can anyone say that more tools to fix things is in anyway a bad thing.
Click to expand...
Click to collapse
Why would you attempt to mod your cell while on vacation?
I was referring to the general user.
I updated my smartphone to A12 C10 and now it's impossible to enter BROM mode with MTKgui. Do you have a solution ? Why does OnePlus block this function? For me it was the ideal backup solution. Thanks for your feedback.
Quercy said:
I updated my smartphone to A12 C10 and now it's impossible to enter BROM mode with MTKgui. Do you have a solution ? Why does OnePlus block this function? For me it was the ideal backup solution. Thanks for your feedback.
Click to expand...
Click to collapse
They deactivated / removed it. Period.
OnePlus under OPPO converted user unfriended. Time to switch to others.
Who installed custom ROM before, made a wise decision, imho.
Maybe edl exploit for the C10 become available, but very improbable.
Btw, there is a app in play store which make backup of every partition ( some need root ) but cannot remember the name.
Cheers.
No, my smartphone is not rooted. I had too much bootloop with this Nord2. I relocked boot and removed root. With even more reason now that BROM mode no longer exists. There is no longer an easy solution to recover a broken phone
C.01 has BROM mode still active. Unfortunately keeping the preloader and lk while update to C.10 is not possible.
Rooted here from 1st day. More than year. No bootloop, neither rare behavior. Just need to know what is ok for this device and what is ko.....
So does that mean if I updated to C10, it is now impossible to root, custom rom or anything ? I cant access bootloader either...
If you have a solution please don't hesitate :/
Many thanks,
Julien
DPJulien said:
So does that mean if I updated to C10, it is now impossible to root, custom rom or anything ? I cant access bootloader either...
If you have a solution please don't hesitate :/
Many thanks,
Julien
Click to expand...
Click to collapse
Exactly.
The OPPO dev team decided to drop any possibility to customize as done with the other brands. C.01 Still has BROM enabled, not sure fastbootd.
To be able to customize further i stuck with A11 which has BROM and fastbootd and works just fine like old school Oxygen OS.
Cheers.
Hey found THE solution to have fastboot and BROM. There is a rollback package to OOS 11 here. It works for all versions after C.05
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
follow instructions from this video but use package from oneplus community
you need to have enabled developer options to see the local update button
Great share for those who trusted OP and upgraded to OOS12. Now is time to find the best working custom ROM, although almost all based a phh's build.
Hello! 'Know of any custom twrp for the XT2165-5 "Tonga" ???
My Moto G Power (2022) is a factory unlocked, North American Retail version.
I have rooted it with Magisk, but still have the default Recovery.
'Would like to have TWRP recovery as a convenience, but it's not a necessity
since I'm already rooted.
Thanks for taking the time to read this. Happy New Year 2023!
Unfortunately the dev scene for the Moto G "tonga" seems to be fairly inactive. I've been attempting to learn about ways to go about porting TWRP but I must admit my Android knowledge is fairly lacking since I came from the iOS jailbreak scene. Will definitely post a thread on XDA if/when I make progress.
With that said if anyone could point me towards any guides for porting TWRP I'd appreciate it as it seems a lot of what i find is fairly outdated?
Yes, I haven't seen much available for the Moto G Power "tonga", either.
There is a site on GitHub named "twrpbuilder" --
"Official site of the TWRP Builder Project"
Can't comment on it, 'only browsed the site ...
wc4usa said:
Hello! 'Know of any custom twrp for the XT2165-5 "Tonga" ???
My Moto G Power (2022) is a factory unlocked, North American Retail version.
I have rooted it with Magisk, but still have the default Recovery.
'Would like to have TWRP recovery as a convenience, but it's not a necessity
since I'm already rooted.
Thanks for taking the time to read this. Happy New Year 2023!
Click to expand...
Click to collapse
Hey,
Greetings to you. I, too, have a 2022 Motorola Tonga; I have the X2165DL, though, and it's not unlocked. I was wondering if you'd be willing to point me in the right direction with regards to HOW you managed to get it rooted? I have been met with no success at all in my search to root this phone. I would be appreciate your assistance very much.
I look forward to your response.
Thank you, I hope, in advance.
Will
Jetpac_HrtfdCT06120 said:
Hey,
Greetings to you. I, too, have a 2022 Motorola Tonga; I have the X2165DL, though, and it's not unlocked. I was wondering if you'd be willing to point me in the right direction with regards to HOW you managed to get it rooted? I have been met with no success at all in my search to root this phone. I would be appreciate your assistance very much.
I look forward to your response.
Thank you, I hope, in advance.
Will
Click to expand...
Click to collapse
Hi ... I believe that any Moto device with the letters "DL" at the end is a Tracfone model. They are very, very difficult to unlock. Sorry to break the news.
Otherwise, you might be able to find an unlock service (or hacker) -- and pay a fee to unlock the bootloader. It won't be cheap. ( Note: some that advertise that they can unlock a Moto xxxx- DL cannot really do it - they just take your money.
BTW: The Moto G (2022) Power is inexpensive to buy new --from Motorola or Amazon, etc. You want the "Retail US" model -- works on any network -- and then you can go to the Motorola website for the unlock code, for free.
You don't need the retail version, you can unlock the boost version. Mine was 40 bucks new from target. If it is unlockable, the OEM unlock switch will become toggleable after 72 hours of using the device. Even if it can't be through Motorola you can use mtk tools to root it, but you'll have to look that up and read about using it. I have not used it myself but there is a group by the name of A-team discussion on a certain popular messaging app that can help
wc4usa said:
Hello! 'Know of any custom twrp for the XT2165-5 "Tonga" ???
My Moto G Power (2022) is a factory unlocked, North American Retail version.
I have rooted it with Magisk, but still have the default Recovery.
'Would like to have TWRP recovery as a convenience, but it's not a necessity
since I'm already rooted.
Thanks for taking the time to read this. Happy New Year 2023!
Click to expand...
Click to collapse
Ever find anything? I did the same thing, rooting was easy compared to trying to find any software/mods that don't look dicey at best. Still just got the same apks i used before i rooted LOL
alphaGodfather said:
Ever find anything? I did the same thing, rooting was easy compared to trying to find any software/mods that don't look dicey at best. Still just got the same apks i used before i rooted LOL
Click to expand...
Click to collapse
No, nothing new .. As you mentioned, rooting is easy -- twrp is not a necessity.
IF YOU WANT TO UNLOCK YOUR PHONE READ THIS
had to ask moto for unlock code. waited 12 hours to receive reply, it went to spam folder (all previous did not)
oem unlock was not an option (there is an option in the developer menu to OEM unlock) . had to factory reset (using software of the OS itself, i did one with recovery and it did not unlock it....)
but wait .. it didn't unlock right away.. i had to unlock developer settings.. then go into developer settings... then TURN OFF DEVELOPER SETTINGS .. and OEM UNLOCK suddenly was selectable .. I CLICKED IT..
for root...
this is RETUS channel is retail us .. if you backup in the directory you can get all others
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
this appears to be an official repository, i was able to use the boot.img with magisk and root
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
i hear not doing this will boot loop, i just did it
and that command can only be entered in fastboot, not fastbootd
this was a 'factory unlocked' phone purchased from target
I Started to make a TWRP Recovery the files are on My gitlab and Mu github. I was able to make a tonga device tree for TWRP. That's a start.
Dana Silva / Tonga · GitLab
Tonga
gitlab.com
And
GitHub - 6thstring/android_device_motorola_tonga
Contribute to 6thstring/android_device_motorola_tonga development by creating an account on GitHub.
github.com
Now that you have a device tree for your device, it's time to build a TWRP recovery imageClone minimal TWRP environment
Follow the instruction in this page
GitHub - minimal-manifest-twrp/platform_manifest_twrp_omni: Minimal manifest for building TWRP for devices shipped with Android 5.1 through Android 9.0
Minimal manifest for building TWRP for devices shipped with Android 5.1 through Android 9.0 - GitHub - minimal-manifest-twrp/platform_manifest_twrp_omni: Minimal manifest for building TWRP for devi...
github.com
Remember to clone the correct version of TWRP based on what Android version your phone have! If your phone have Android 8.0, clone twrp-8.0 branch
Move device tree to TWRP sources
Copy working/(brand)/(device) folder to device/(brand)/(device) folder in TWRP sources
Example:
brand name: xiaomi
device codename: whyred
Copy working/xiaomi/whyred to device/xiaomi/whyred in TWRP sources
Building
Open a terminal with the current dir pointing to TWRP sources root
Then type
. build/envsetup.sh
to initialize the environment
After that, type
lunch omni_codename-eng
where codename is the codename of your phone
If that is successful, type
mka recoveryimage
to build the recovery.
If your device is A/B, use instead
mka bootimage
If also that is successful, congratulation!
Go to out/target/product/codename/ (codename is your device codename) and you will find your recovery.img
Go to [[5. Boot the recovery image]]
Good Luck
Can't believe this phone didn't get TWRP after all this time... Seems like a good phone for a custom rom.