Root Method
Root for all Exynos 850 devices.
Root for all Exynos 850 devices. A. Root part 1 - Preparing the file I accept no responsibility for bricked phones but I will help you to recover. 1. Download the exact firmware (including upgrade date) for your device from https://samfrew.com...
forum.xda-developers.com
Twrp and Kernel
Kernel and TWRP for a127f u2 (Exynos 850)
I have built a custom kernel for the a127f Exynos 850 I've also included a link to more custom recoveries in post#2 physwizz a12s kernel version 4 Based on a127f NOT for baseband u3 or higher For OneUI 3.1 ( also works for GSIs) Samsung...
forum.xda-developers.com
Latest twrp
Afaneh TWRP for a12s (Exynos 850)
Afaneh TWRP NOT for baseband u3 or greater (Working u3/u4 version on post #2) Download tar file. Extract recovery.img from tar file Method 1. If you have already installed recovery and decrypted. 1. Boot to recovery. 2. Install recovery.img 3...
forum.xda-developers.com
Root Method in post#2
afaneh92 TWRP in post #2
GSIs in post#3
Kernel Version 2 & 3 in post #5
Kernel version 4 in post #11
Install kernel without TWRP in post#21
TWRP (new) in post#6
Skyhawk recovery (new) in post #22
Orange Fox (new) post #24
Note
All of these procedures have been tested on the a127f with u2 baseband
They will probably all work on the m127f as well.
@physwizz
Recoveries for U2 baseband - Working
[RECOVERY][UNOFFICIAL] TWRP , OrangeFox and Skyhawk [Samsung-Exyons-850][m12s][a12s][SM-M127X][SM-A127X]
TWRP , OrangeFox and Skyhawk for Samsung A12/M12 Exyons850 * 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...
forum.xda-developers.com
Recoveries for U3 baseband - Still being tested
[RECOVERY][UNOFFICIAL] TWRP , OrangeFox and Skyhawk [Samsung-Exyons-850][m12s][a12s][SM-M127X][SM-A127X]
TWRP , OrangeFox and Skyhawk for Samsung A12/M12 Exyons850 * 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...
forum.xda-developers.com
All recoveries contain physwizz Kernel
Root Method for all Exynos 850 devices.
A. Root part 1 - Preparing the file
I accept no responsibility for bricked phones but I will help you to recover.
1. Download the exact firmware (including upgrade date) for your device from https://samfrew.com or https://www.samfirmware.net/ or https://www.full-repair-firmware.com/search?q=A20 or
Samsung Firmware Download - Lastest official firmware update
Samsung Firmware Download ⭐ Official and fast update ⭐ Lastest and old version ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
2. Download patched magisk
3. Use zarchiver to extract the apxxxxxx....md5 section from the firmware.
4. Use patched magisk to patch the ap section. Allow the extra files.
Click on install and select patch file.
The output will be a patched tar file.
B. To Unlock Bootloader
1. Activate developer options by going to settings, about phone, software information and tapping on build number 7 times.
On phone developer options in settings allow OEM unlocking and enable usb debugging by moving both
sliders RIGHT
If you don't see the OEM unlock
-Disable Auto System Update
-Then disable Automatic date and time (Found in General Management) > then set the time back 14 days
- Connect to the internet
-Go to software update then check for update and wait a long time till it registers the device on server
-Once it's registered the OEM Unlock should be visible in the Developer Options
then connect phone to PC
2. Reboot into download mode by holding down both Vol up and Vol down
(You might need to long press vol up to unlock bootloader)
then press vol up to continue
Reboot and skip through the setup process.
C. Root part 2
Reboot into download mode again
6. Flash the patched ap tar file using special Odin.
https://forum.xda-developers.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/
(Click on the ap button and choose the patched tar file. Press start)
7. Reboot.
8. Skip all the way through the set-up process.
D. TWRP installation for a127f and m127f (may not work for a127f/DSN)
Make sure your system has fully completed the installation process and all apps have been installed
1. Download the afaneh92 zip file.Unzip the tar from the zip.
2. Extract the recovery.img
3. Install TWRP app form the playstore
4. Choose Install TWRP
5. Choose file to flash.(don't select device)
6. Select recovery.img.
7. Reboot to recovery.
8. Mount system (Press mount then choose system)
9. Tap on Wipe, tap on format data, type YES. (Not just wipe data)
10. Tap on Advanced then terminal.
11. Type multidisabler. Wait for it to finish. Type multidisabler again. Go to main menu
Reboot to recovery (tap on reboot, tap on recovery)
Ignore the keyrefuge error message.
12. Reboot and go completely through the setup process. Wait for downloading to finish. This may take up to an hour. You can see the progress by pulling down from the top.
13. Reboot into recovery and Backup boot, data, super and dtbo
@physwizz
Installing a GSI
1. Unzip img file
2. Backup boot, data and super from TWRP.
Wipe data from twrp
3. Install IMG.
4. Install my kernel
5. Reboot
I have installed lineages and pixel experience
List of GSIs
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
@physwizz
deleted
physwizz a12s kernel version 2
Based on a127f
For OneUI 3.1
(May also work for GSIs)
Samsung securities disabled
More CPU governors
Conservative, On-demand, Userspace, powersave, performance, energy_step, shedutil
Optimised for performance
Overclocked for performance
Underclocked for battery
CPU: 247MHz - 2210MHz
Kernel
physwizz - Repositories
physwizz has 172 repositories available. Follow their code on GitHub.
github.com
@physwizz
physwizz a12s kernel version 3
Based on a127f
For OneUI 3.1
(May also work for GSIs)
Samsung securities disabled
More CPU governors
Conservative, On-demand, Userspace, powersave, performance, energy_step, shedutil
Optimised for performance
Overclocked for performance
Underclocked for battery
CPU: 247MHz - 2210MHz
lz4 compression added to zram
For Zram
Go to HKtweaks- virtual memory
Turn off zram
increase swappiness to 200
choose lz4
increase size to 4096
turn on Zram
Kernel
physwizz - Repositories
physwizz has 172 repositories available. Follow their code on GitHub.
github.com
@physwizz
TWRP
From @(Sri Lanka)
(MTP not working)
Installation
Unzip files
Extract recovery.img
Method 1.
If you have already installed afaneh92 TWRP and decrypted.
1. Boot to recovery.
2. Install recovery.img
3. Choose recovery partition
4. Reboot to recovery
Method 2.
From the start
1. Download firmware
2. Extract ap file.
3. Patch with magisk
4. Flash with Odin
5. Download recovery.img
6. Install TWRP app
7. Install TWRP
8. Choose file to flash.(don't select device)
9. Select recovery.img.
10. Reboot to recovery.
11. Format data
12. Install multidisabler zip
Or dmverity
13. Reboot to recovery
Done
@physwizz
physwizz said:
6. Install the TWRP tar file from patched Odin.
Click to expand...
Click to collapse
physwizz said:
9. Mount system etc
Click to expand...
Click to collapse
Hi,
I am quite noob, IT but not developer, with some knowledge of linux, rooted so far 3 devices with some imagination whats the process about. As far as I know, kernel and recovery are those special partitions, I should know exactly what am doing, because I can brick my phone almost permanently. So pardon me for basic question (I can of course study in another thread, but still will not be sure its 100% accurate for this device)....
6. Install TWRP - some detailed instruction will be welcomed (lasttime I saw TWRP, it was onetime run by adb/fastboot command with red colored mention DO NOT enable Write, stay read only) - BL, AP, CP?
9. Mount etc.... some details?
4. Install kernel .... some details?
And just to ensure myself understanding, TWRP become permanent in recovery partition, updated kernel comes with some optimizing - but no special changes has to be made for whole firmware. And A12s vs/aka A127F/DS versus my device A127F/DSN .... its not important difference?
Thanks
honzazkrumlova said:
Hi,
I am quite noob, IT but not developer, with some knowledge of linux, rooted so far 3 devices with some imagination whats the process about. As far as I know, kernel and recovery are those special partitions, I should know exactly what am doing, because I can brick my phone almost permanently. So pardon me for basic question (I can of course study in another thread, but still will not be sure its 100% accurate for this device)....
6. Install TWRP - some detailed instruction will be welcomed (lasttime I saw TWRP, it was onetime run by adb/fastboot command with red colored mention DO NOT enable Write, stay read only) - BL, AP, CP?
9. Mount etc.... some details?
4. Install kernel .... some details?
And just to ensure myself understanding, TWRP become permanent in recovery partition, updated kernel comes with some optimizing - but no special changes has to be made for whole firmware. And A12s vs/aka A127F/DS versus my device A127F/DSN .... its not important difference?
Thanks
Click to expand...
Click to collapse
Thanks for the feedback.
I'll add more detail shortly
honzazkrumlova said:
Hi,
I am quite noob, IT but not developer, with some knowledge of linux, rooted so far 3 devices with some imagination whats the process about. As far as I know, kernel and recovery are those special partitions, I should know exactly what am doing, because I can brick my phone almost permanently. So pardon me for basic question (I can of course study in another thread, but still will not be sure its 100% accurate for this device)....
6. Install TWRP - some detailed instruction will be welcomed (lasttime I saw TWRP, it was onetime run by adb/fastboot command with red colored mention DO NOT enable Write, stay read only) - BL, AP, CP?
9. Mount etc.... some details?
4. Install kernel .... some details?
And just to ensure myself understanding, TWRP become permanent in recovery partition, updated kernel comes with some optimizing - but no special changes has to be made for whole firmware. And A12s vs/aka A127F/DS versus my device A127F/DSN .... its not important difference?
Thanks
Click to expand...
Click to collapse
I hope the method is now OK.
please contact me if any further help is needed
Exynos 850 Resources
A127 M127 F127 A135 M135 A217 A047
t.me
Exynos 850 Testing & Development
A127 M127 F127 A135 M135 A217 A047
t.me
More detailed root and twrp instructions in post #2
physwizz a12s kernel version 4
Based on a127f U1 binary
For OneUI 3.1
( also works for GSIs)
Samsung securities disabled
More CPU governors
Conservative, On-demand, Userspace, powersave, performance, energy_step, shedutil
Optimised for performance
Overclocked for performance
Underclocked for battery
CPU: 130MHz - 2210MHz
lz4 compression added to zram
Ready for spectrum installation
Installation
Method 1
Install from TWRP
Method 2
Install adb tools on pc
Connect to PC
Copy zip file to adb folder on pc
Open terminal on pc
Navigate to adb folder
Type
adb sideload name.zip
For Zram
Go to HKtweaks- virtual memory
Turn off zram
increase swappiness to 200
choose lz4
increase size to 4096
turn on Zram
Kernel
physwizz - Repositories
physwizz has 172 repositories available. Follow their code on GitHub.
github.com
@physwizz
physwizz said:
Backup boot, data, super and dtbo
Click to expand...
Click to collapse
Thanks! I finally got the TWRP on my SM-A127F, though I cannot perform the last step: I get errors "Failed to mount '/data' (Invalid argument)" and "Failed to mount '/keyrefuge' (Invalid argument)". Any ideas?
UPD: not sure if it's OK, but I changed /data filesystem to ext4 and it worked well.
IchZerowan said:
Thanks! I finally got the TWRP on my SM-A127F, though I cannot perform the last step: I get errors "Failed to mount '/data' (Invalid argument)" and "Failed to mount '/keyrefuge' (Invalid argument)". Any ideas?
Click to expand...
Click to collapse
IchZerowan said:
UPD: not sure if it's OK, but I changed /data filesystem to ext4 and it worked well.
Click to expand...
Click to collapse
Format data
Type yes
Then GO to advanced
terminal and type multidisabler twice
Reboot to recovery
Ignore keyrefuge
IchZerowan said:
Thanks! I finally got the TWRP on my SM-A127F, though I cannot perform the last step: I get errors "Failed to mount '/data' (Invalid argument)" and "Failed to mount '/keyrefuge' (Invalid argument)". Any ideas?
UPD: not sure if it's OK, but I changed /data filesystem to ext4 and it worked well.
Click to expand...
Click to collapse
Can you post, how exactly you did it (changed to ext4)
Based on your mention, I tried TWRP, WIPE, Advanced wipe, Change or repair filesystem, Change, to EXT4. No luck.
IchZerowan said:
Thanks! I finally got the TWRP on my SM-A127F, though I cannot perform the last step: I get errors "Failed to mount '/data' (Invalid argument)" and "Failed to mount '/keyrefuge' (Invalid argument)". Any ideas?
UPD: not sure if it's OK, but I changed /data filesystem to ext4 and it worked well.
Click to expand...
Click to collapse
I didn't change mine to ext4.
I just left it as it was
honzazkrumlova said:
how exactly you did it
Click to expand...
Click to collapse
I tried exactly the same steps you mentioned, and it worked.
IchZerowan said:
I tried exactly the same steps you mentioned, and it worked.
Click to expand...
Click to collapse
Well, but...
In original physwizz instructions, there are steps and I would be greatfull to provide some details
Those key moments
0. "Install all apps, etc"
A. Wipe / Format Data / yes
B. Multidisabler twice
and your workaround C. Change FS to EXT4
My experiments was like>
0+A+B... system bricked (or 10min long bootloop)
0+A+B+C ..... bricked (but TWRP at least sees Internat storage with 50GB capacity)
Then, I said myself, well, C mean I wiped, never mind, lets alter it like
A+B+C+ call clean wipe (but on ext4 Data partition.... but how?)
Well, tried> A+B+C+ Wipe, Wipe Factory Reset.
no change, bricked.
I also tried/experiemnt
A+restart .... bricked
A+B+restart .... bricked
B+restart .... bricked
So, can you please write little bit details?
Thanks!
honzazkrumlova said:
Well, but...
In original physwizz instructions, there are steps and I would be greatfull to provide some details
Those key moments
0. "Install all apps, etc"
A. Wipe / Format Data / yes
B. Multidisabler twice
and your workaround C. Change FS to EXT4
My experiments was like>
0+A+B... system bricked (or 10min long bootloop)
0+A+B+C ..... bricked (but TWRP at least sees Internat storage with 50GB capacity)
Then, I said myself, well, C mean I wiped, never mind, lets alter it like
A+B+C+ call clean wipe (but on ext4 Data partition.... but how?)
Well, tried> A+B+C+ Wipe, Wipe Factory Reset.
no change, bricked.
I also tried/experiemnt
A+restart .... bricked
A+B+restart .... bricked
B+restart .... bricked
So, can you please write little bit details?
Thanks!
Click to expand...
Click to collapse
I currently wasn't able to run any GSIs on my phone, so not sure what to do next. I think, backing up /data is useless since it's empty (I tried ls from the terminal). Next attempt I gonna restore the state using backup or even odin, and back up only boot, super, and dtbo without changing the FS. At least, the default OneUI boots this way, so I hope one of the GSIs will boot as well. I gonna experiment on this a bit later.
IchZerowan said:
I tried exactly the same steps you mentioned, and it worked.
Click to expand...
Click to collapse
Well, I have had hope, when you written "worked". Hope that mounting /data is possible.
Well, backup /data ist not useless now, its not possible, because if you try, falls into error because unmountable.
Lets say, you wanna backup those special partition in case, your experiment with kernels go wrong, so far so good.
My intention was pretty less advanced, I wanna backup data for a reason - well, these days some apps goes way I dont want you, I would use /data backup in case, I want restore previous version of some app. That + regular backup, why backup data/files/setting, when I can backup whole system, lets say once a month.
Anyway, changing /data partition to ext4 DID something and CHANGED something (capacity of internal storage), so its maybe workaround about where the solution stays, I have found some older thread about similar problem in TWRP and solution that changing to EXT2, then EXT4 would help. Will experiment and let you know, if succeed.
Some screenshots from afaneh92 twrp.
Related
Here I will share all the info you need to know about using Treble on the Mi A1. Everyone is more than welcome to ask questions and clarification here, I am happy to answer and will update this thread over time. Thanks!
Contents
0. Key Terms
1. Restoring to Stock
-- 1.1. Requirements
-- 1.2. Full-device backup
-- 1.3. Stock restore process
2. "Treblize" (repartition) the device
3. Your first Treble ROM install
4. Installing AIO's, GSI's, Vendors and More
-- 4.1. Install a Treble AIO
-- 4.2. Install a Treble GSI
-- 4.3. Install/update a Vendor Pack
-- 4.4. Install a non-Treble ROM
-- 4.5. Restore a TWRP backup
5. Mods and Extras [Gapps, Magisk, custom kernels, etc.]
6. FAQ and Troubleshooting
----------------------------------------------
0. Key Terms
Throughout your Treble adventures, you may see lots of new terms. Here I will explain them all. This is essential reading!
Treble
Treble is the broad term of a new Android architecture model of splitting the system into two partitions:
System: where the Android OS goes, i.e. Oreo or later operating system;
Vendor, where the device-specific files go, such as drivers.
Before Treble, both the Android OS and device-specific files would live together on system. See below for a more detailed description of Vendor.
"Treblizing"
May also be called Treble-enable, Treble-conversion or some variation of that. This is the process of converting a non-Treble device to a Treble-capable one, unofficially, by changing the partition map of the device. This involves shrinking an existing partition - such as userdata or system in the case of the Mi A1 - in order to create a new vendor partition - or two vendor partition in the case for our Mi A1, one for each slot. Treblizing is just the preparation stage - you still need an AIO installation (see AIO below) before you are actually able to use a Treble ROM.
Vendor
Also known as Vendor Pack or Vendor Image. In the context of Treble, this is a standalone vendor image (either as a ZIP or usually as an IMG) that can be flashed to your Treble-enabled device for it to be compatible with a Treble system/ROM. These are similar to a kernel in the way that they are flashed to their own partition on your device and are compatible with many Treble ROM's. They are also similar to a kernel in that they are made specifically for one device to provide the low-level functionality of the system. It mostly includes drivers, but can also include apps and overlays that are automatically added at runtime to the Android OS that's living on System.
Treble developers for the Mi A1 may release standalone "vendor.img" for use on other ROM's - usually GSI's (see description of GSI below) but they are also part of an AIO (see description of AIO below).
GSI
Stands for "Generic System Image". This concept, introduced and developed by @phhusson is the creation of a System image that is device-agnostic - that is, it is a ROM that is designed to work with an existing Treble device, as long as the device has a GSI-compatible Vendor and kernel installation. For devices with official Treble support, phhusson makes the effort to try and adapt his GSI system for compatibility - but for unofficial Treble device like the Mi A1, it's our (tissot developers) responsibility to make a Vendor/Kernel that is as GSI-compatible as possible.
AIO
Stands for "All In One". This is a Treble firmware that includes a Kernel, System and Vendor image in the one ROM ZIP. This provides an all-in-one Treble experience through a device-specific Treble ROM. AIO's are designed to work well with their own ROM but should also strive to be compatible with a GSI.
An explanatory chart of Key Terms
{
"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"
}
Click here for full size image.
Ignore this spoiler (coded link to thumbnail because XDA thread edit breaks the IMG link)
Code:
https://img.xda-cdn.com/ic22y2zu5yi9EClrY11FS8FU5C0=/https%3A%2F%2Fimg.xda-cdn.com%2FU8u8IdA66PAFHOM4PsKNQbFHwSA%3D%2Fhttps%253A%252F%252Fimg.xda-cdn.com%252Fo1fMEJDyu5x7pv2B9KB323i8_IA%253D%252Fhttps%25253A%25252F%25252Fthumbs2.imgbox.com%25252Fd7%25252Fc2%25252FDxa93pOz_t.png
----------------------------------------------
1. Restoring to Stock
For the sake of consistency, I highly recommend everybody revert to a clean stock state. This ensures that as many of us are coming from the same place to eliminate inconsistency with reported bugs. If you're impatient or experienced though, feel free to skip this - but if you have issues, be sure to try again from here before asking for help.
Note that this will also restore you to the stock partition map, i.e. before "Treblizing".
1.1. Requirements
Unlocked bootloader and EDL access/drivers. See FAQ at bottom of this post for details on EDL.
Modern fastboot binary - it needs the "--set-active" option. Check with fastboot --help to see if it's listed in the usage.
Latest/recent official firmware package. Recommended "V.9.5.10.0.ODHMIFA" only because it's what I used, if you're not sure - but anything newer should be fine too.
Recent MiFlash version. I used 7.4.25 which can be downloaded from here.
1.2. Full-device backup
HIGHLY RECOMMENDED. While all this is relatively safe (as safe as device modding can be), I cannot be held responsible for any data loss or bricks. You can make a Low-Level backup with my tool here. You can use the "skip-systems-and-userdata" partition list to save time, since those can be backed up in TWRP anyway. This is here mostly as a failsafe.
Also backup your internal storage files. The Treblizing process may wipe your internal storage.
1.3. Stock restore process
Flash latest firmware (V.9.5.10.0.ODHMIFA at time of writing) in EDL mode with MiFlash. This will wipe your device (including Internal Storage) and restore stock partition map. This could take a while.
Optional: If Wifi is broken (you can check by booting ROM), flash the "tissot_images_V.9.5.10.0.ODHMIFA___persist-only" in MiFlash under EDL, attached. Just extract the ZIP and browse to the folder in MiFlash. You can replace the persist.img from official V.9.5.10.0.ODHMIFA or another ROM if you want to be sure it's genuine. Credits to @AlexAiS for discovering this.
Remember - you backed up your original persist.img in step 1 anyway, so this is not risky.
I am not sure how this works exactly. It seems MiFlash in EDL is able to re-build a MAC address while flashing the persist. I don't know where this MAC comes from though.
----------------------------------------------
2. "Treblize" (repartition) the device
If you looked at the chart, you'll know that this is just the first step. You will need to actually install an AIO ROM after this part. This is a ONE TIME PROCESS for getting Treble capability on your device.
Repartitioning is relatively painless ever since I created TWRP with Treble Manager. Read on for a walkthrough.
Fastboot boot to TWRP with mohancm's recovery img (i.e. recovery-3.2.1-1) if you don't already have TWRP installed. Do not get the installer - we're using the one with Treble Manager instead.
Install the latest TWRP with Treble Manager (v1.2 at time of writing, but of course latest version is best) then Reboot Recovery to actually load it. Be sure to read about TWRP with Treble Manager in that thread to understand how it works. If you have any questions specifically about the TWRP and Treble Manager, please ask in that thread.
Format Data in Wipe menu (to remove Stock encryption), then Reboot Recovery again (maybe not necessary but it can't hurt).
In TWRP, go to Advanced > Treble Manager and repartition the device by following the wizard. Userdata shrink is recommended, as per the in-menu description explaining this. Just try the Treble Manager and see yourself - it will ask you one last time before repartitioning so don't worry about it wiping without warning. Alternatively, you can just check the screenshots.
After finished it will reboot TWRP. You are now ready for installing a Treble AIO (and then a GSI, if desired), but be sure to still read on, especially the next section below (there is a known issue that you need to work around - otherwise a bootloop will occur).
----------------------------------------------
3. Your first Treble ROM install
THERE IS AN IMPORTANT STEP THAT MUST BE FOLLOWED HERE WHEN INSTALLING YOUR FIRST TREBLE ROM. FAILURE TO FOLLOW THESE INSTRUCTIONS WILL RESULT IN A BOOTLOOP.
Make a note of the current slot (in Reboot menu). If you followed this guide from Section 1, you should be in Slot A. If you're not, just swap any mention of Slot A and B in these steps.
Download a Treble AIO ROM (such as RR Treble Experimental) and flash in TWRP. This is required even if you want to use a GSI, since it has the required Vendor Pack and Kernel.
Immediately install TWRP with Treble Manager again, as you usually do, to re-inject TWRP into the new ROM boot image.
Reboot Recovery, NOT SYSTEM.
Confirm in Reboot menu that the device has successfully switched to Slot B. If it is still stuck in Slot A, this is a one-time bug that must be solved now - if you do not fix this then you will just bootloop.
If it is still stuck in Slot A, you must reboot to fastboot (make sure you have a current version, as explained in Section 1.1. "Requirements") and manually run the command:
Code:
fastboot --set-active=b
...after doing this once, slot switching should work fine in TWRP again. You should never have to do this again (unless you go back to stock then re-Treblize again).
In case you didn't know, all ROMs for our Seamless device actually install into the *other* slot that isn't currently active - that's why you always need to Reboot Recovery first before installing Magisk or Gapps and such.
I advise users from now on to keep an eye on their Slot switching whenever you install an AIO ROM to make sure it worked. If it happens again after these steps, please report it to me with as much details as possible (we're still trying to figure out this bug).
After following these steps, you should be able to flash Treble ROM's just as you would a normal ROM from now on. Your Treble transformation is complete. But read on for more help and walkthroughs if you need it.
----------------------------------------------
4. Installing AIO's, GSI's, Vendors and More
Assuming you followed Section 3 above, you are now ready to install anything as usual. But some users have expressed confusion about what they can and can't do from this point, so I will give you some example choices here.
4.1. Install a Treble AIO
At the time of writing this guide, currently the only Treble AIO is the RR Experimental build. If or when others come along, you can just install them like normal ROMs. We already did this in Section 3 above, but here is a simplified summary of that process:
Flash the AIO ROM in TWRP with Treble Manager 1.2+ - do NOT reboot
Immediately reflash TWRP with Treble Manager 1.2+ so you get the Treble-compatible TWRP back
Factory Reset if it's a different ROM, as you usually would in this case.
Make a note of which slot you are on right now
Reboot recovery
Make sure your device has now swapped to the other slot by checking the reboot menu. If it has not, you will need to repeat the fastboot --set=active step as explained in Section 3. (I don't know if this is necessary again - but I just want to warn users to be aware of this known bug)
Now that the slot has changed, you can install Gapps, Magisk and/or whatever other compatible additional mods you want.
4.2. Install a Treble GSI
You may remember from earlier that the Treble GSI's are just System images that use your existing Vendor and Kernel. We already have a Treble kernel and Vendor from an AIO (Section 3 or Section 4.1. above), so this is quite simple:
Download any GSI/Phh-Treble ROM's from the Treble-Enabled Device Development section and copy the IMG to device
Make sure your current slot is a Treble ROM slot (i.e. existing AIO or GSI working). Unlike AIO/ROM ZIP flashing, image flashing installs it to the CURRENT slot.
Flash the IMG to "System Image" in TWRP with Treble Manager 1.2+
Factory Reset if you're changing ROM's
Install any other mods (Gapps, GSI-compatible Magisk [i.e. 16.4 beta or later], etc.). You may need to boot the ROM once before installing any mods - this varies per GSI. Some existing mods may also be outright incompatible with the GSI.
Reboot
Note that since this is only a System image, there is no need to reinstall TWRP or Reboot Recovery.
4.3. Install/update a Vendor Pack
While you're on a current and working AIO or GSI slot, you can flash a vendor.img to update the driver/device level stuff for that ROM. This could be done to e.g. fix the Camera. This is useful if you're running a GSI.
Download a vendor.img from your AIO or Vendor Pack provider (e.g. RR AIO Experimental) and copy the IMG to device
Make sure your current slot is a Treble ROM slot (i.e. existing AIO or GSI working). Unlike AIO/ROM ZIP flashing, image flashing installs it to the CURRENT slot.
Optionally make a TWRP backup of Vendor (or more) if you want to be careful and it's your daily (I always do).
Flash the IMG to "Vendor Image" in TWRP with Treble Manager 1.2+
Reboot
Note that since this is only a System image, there is no need to reinstall TWRP, Reboot Recovery or install any Mods (Gapps, Magisk, etc) UNLESS it's a Vendor mod (as of time of writing, no Vendor mods exist yet).
4.4. Install a non-Treble ROM
This is simple, same as you're used to before Treblizing. But do note that this is only possible if you chose to resize Userdata when repartitiong with Treble Manager.
Download the ROM to your device
Optional - make sure the active slot is one with a Treble AIO/GSI ROM already - remember that ROM ZIPs install to the OTHER slot, not the currently active one; so this way you can easily switch back to the Treble ROM just by doing a Factory Reset (or TWRP restore of Data) and slot switch.
Factory reset
Install the ROM as per usual procedure (Install ZIP, reflash TWRP with Treble Manager 1.2+, reboot recovery to allow slot switch, install Gapps + Magisk + Mods, etc., reboot).
4.5. Restore a TWRP backup
There is nothing special about restoring a backup. Even if your backup was from a non-Treble ROM, you can restore that backup on a Treblized device. Obviously, though, any Treble ROM backup can only be restored on a Treblized device.
----------------------------------------------
5. Mods and Extras [Gapps, Magisk, custom kernels, etc.]
After you have confirmed that TWRP is booting in to the correct slot (see Section 3), you're ready to install other ROMs (see Section 4) followed by mods. I did briefly go over mods in Section 4, but I'll go into more detailed info about compatibility here.
Any usual Gapps should work fine, just as long as you flash after the slot is correctly set. Note that RR Camera (GCam) requires Gapps to be installed. I used Nano, they worked fine.
Also note that some GSI's will require you to boot the system first before installing Gapps.
Custom kernels must be marked Treble compatible for our device. Specifically (info for kernel developers) this means adding slotselect flag to vendor entry in DTB, and disabling dm-verity (so we can inject vendor changes to system).
It is reported that standard Magisk will work in RR Treble ROM, but it does NOT work on GSI. You need Magisk 16.4 beta or later for GSI's. Also see the FAQ section at the end for more info on the Magisk situation.
Some other ZIP's might need updating for Treble, really unsure. Experimentation is welcome. Just be sure you make TWRP backups before testing anything, of course!
--------------------------------
6. FAQ and Troubleshooting
Q) I get "cannot receive hello packet" in MiFlash
A) Just reboot EDL mode and try again. Usually only happens if you try to flash in EDL twice in a row. See the Low-level Backup/Restore/Unbrick toolkit thread for more info about EDL.
Q) How to Magisk with Treble? What is the TWRP and Magisk interaction?
A) Best to use Magisk 16.4 beta or later, it's reported as working on GSI's. Also note that Magisk is installed to the boot ramdisk (the same place as where TWRP goes) and this has the following implications:
Whenever you flash the TWRP installer, you will need to reinstall Magisk *after* you Reboot Recovery
TWRP installer will flash to BOTH slots, but Magisk will only flash to the CURRENT slot. So if you flash TWRP installer, it may erase any Magisk install on the inactive slot.
TWRP survival (in my recent TWRP builds) backs-up and restores the whole ramdisk. This will include Magisk, if it was already on the boot slot that it backs up.
Q) EDL mode? Eh?
A) EDL mode, or "Emergency DownLoad" mode, is a low-level mode for flashing devices. It is entered by the command:
Code:
fastboot oem edl
EDL mode is used to read/write to the eMMC more directly. It is used by this tool, as well as flashing with MiFlash.
Other important notes:
You will need good QDLoader drivers. These drivers gave me the best results.
You can exit EDL mode by holding Power button for ~10 seconds. Hold with VolDn to reboot into fastboot again, as one might expect.
Make sure you use a good USB-C cable.
Sometimes the flashing process can freeze. It will always report success when done. If it freezes, you need to reboot EDL mode. Try a different USB port or cable if you keep experiencing freezes.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
can i use this persist.zip inorder to solve the wifi issue in stock rom as well as some of custom rom too?
parasnarkhede said:
can i use this persist.zip inorder to solve the wifi issue in stock rom as well as some of custom rom too?
Click to expand...
Click to collapse
Yup. Just flash a stock persist.img in EDL mode. But backup your original in case, it could erase or change your BT MAC too.
@CosmicDan thank you so much for your work on this. Quite impressive if you ask me.
Tell me just something, every time you talk about "...do this or that in EDL mode..." you mean that we have to use your backup/restore tool, right?
I'm sorry for the noob question but, despite I'm quite familiar with Android, this is my first time using a device that has "slots" and that needs to boot to TWRP in order to flash it... there's some differences from all devices I had in the past and that's making doubt some stuff.
So, anyway, I'm currently using official BETA leaked by Xiaomi (Oreo 8.1 - OPM1.171019.019.8.5.11) so do I really need to reflash stock as you suggest? I mean...it's stock, beta but stock and I've never flashed any other custom ROM (since I've read that by doing it I could have issues with WiFi after returning to stock). So, what do you think? Is it really necessary to reflash stock? My partitions are all the original ones...the only thing different is system, right?
Thank you for your time and work.
Typhus_ said:
@CosmicDan thank you so much for your work on this. Quite impressive if you ask me.
Tell me just something, every time you talk about "...do this or that in EDL mode..." you mean that we have to use your backup/restore tool, right?
I'm sorry for the noob question but, despite I'm quite familiar with Android, this is my first time using a device that has "slots" and that needs to boot to TWRP in order to flash it... there's some differences from all devices I had in the past and that's making doubt some stuff.
So, anyway, I'm currently using official BETA leaked by Xiaomi (Oreo 8.1 - OPM1.171019.019.8.5.11) so do I really need to reflash stock as you suggest? I mean...it's stock, beta but stock and I've never flashed any other custom ROM (since I've read that by doing it I could have issues with WiFi after returning to stock). So, what do you think? Is it really necessary to reflash stock? My partitions are all the original ones...the only thing different is system, right?
Thank you for your time and work.
Click to expand...
Click to collapse
EDL mode is like fastboot mode, but even lower-level.
You enter into it with:
Code:
fastboot oem edl
It is needed by my backup tool yes, but it's also used to flash in MiFlash.
Will update the guide and FAQ with this info.
How to flash the persist file attached in the op in mi flash ?
You mean replace it with the one in the stock rom fastboot files and flash the whole rom again via mi flash ?
Ahmed Al-Sayed said:
How to flash the persist file attached in the op in mi flash ?
You mean replace it with the one in the stock rom fastboot files and flash the whole rom again via mi flash ?
Click to expand...
Click to collapse
Just browse to the folder with MiFlash....
CosmicDan said:
Just browse to the folder with MiFlash....
Click to expand...
Click to collapse
Oh, you mean choose only the persist.img file then mi flash will flash it automatically to the right partition ?
Ahmed Al-Sayed said:
Oh, you mean choose only the persist.img file then mi flash will flash it automatically to the right partition ?
Click to expand...
Click to collapse
No, you don't choose the persist.img. You choose the folder. You can't even choose a file in MiFlash, it's a folder browse.
It's the exact same method of flashing anything in MiFlash
CosmicDan said:
No, you don't choose the persist.img. You choose the folder. You can't even choose a file in MiFlash, it's a folder browse.
It's the exact same method of flashing anything in MiFlash
Click to expand...
Click to collapse
Which folder ?
The folder that i extracted the persist.img (attached in the op) in ? Or the srock rom folder after i replace the persist.img (attached in the op) with the one in the rom's folder and execute flash ?
Ahmed Al-Sayed said:
Which folder ?
The folder that i extracted the persist.img (attached in the op) in ? Or the srock rom folder after i replace the persist.img (attached in the op) with the one in the rom's folder and execute flash ?
Click to expand...
Click to collapse
DONT REPLACE PERSIST IN STOCK FIRNWARE. That does LITERALLY nothing, the persist is already from stock ROM!
Just extract the persist-only ZIP, and select it in MiFlash! Don't insert extra steps that I never said!
CosmicDan said:
DONT REPLACE PERSIST IN STOCK FIRNWARE. That does LITERALLY nothing, the persist is already from stock ROM!
Just extract the persist-only ZIP, and select it in MiFlash! Don't insert extra steps that I never said!
Click to expand...
Click to collapse
Thanks !
Dear sir,
I have few questions
1. Do we need any vendor image to flash with it?
2. How to revert back to stock rom (And erase vendor partition) from treble custom rom?
3. Can we revert back to stock partition map through mi flash tool in flastboot mode or edl mode?
Hopefully someone will make video soon, so that it becomes somewhat more easy to understand.
sudipta08sarkar said:
Dear sir,
I have few questions
1. Do we need any vendor image to flash with it?
2. How to revert back to stock rom (And erase vendor partition) from treble custom rom?
3. Can we revert back to stock partition map through mi flash tool in flastboot mode or edl mode?
Click to expand...
Click to collapse
1. I don't understand the question. The vendor image is part of the Treble ROM. You can get vendor from the RR Experimental thread for example.
2. By following Section 1.1.; Step 2 alone
3. By following Section 1.1.; Step 2 alone
CosmicDan said:
2. Flash latest firmware (V.9.5.10.0.ODHMIFA at time of writing) in EDL mode with MiFlash. This will wipe your device (including Internal Storage) and restore stock partition map. This could take a while.
Click to expand...
Click to collapse
Ritik99 said:
Hopefully someone will make video soon, so that it becomes somewhat more easy to understand.
Click to expand...
Click to collapse
Or you could tell us what part you're having trouble with so I can make it more easy to understand?
I don't understand how a video would make it easier. You need to be able to understand the process - not just copy what some guy is telling you to do.
CosmicDan said:
1. I don't understand the question. The vendor image is part of the Treble ROM. You can get vendor from the RR Experimental thread for example.
2. By following Section 1.1.; Step 2 alone
3. By following Section 1.1.; Step 2 alone
Click to expand...
Click to collapse
Ok I understand, but my query is, everytime I will flashing a new treble rom, will it flash vendor partition itself?
Congratulations, can't wait to test it on my a1.
One question, how about google play certified device status? Is still verified or not?
If i choose to shrink data partition, how much left for data? My a1 have 64 gb storage.
CosmicDan said:
Or you could tell us what part you're having trouble with so I can make it more easy to understand?
I don't understand how a video would make it easier. You need to be able to understand the process - not just copy what some guy is telling you to do.
Click to expand...
Click to collapse
Yup.. that what make people say "i do it the same as instruction and bricked my devices." It is because u just copy what other ppl do and dont know what exactly u do lol... Fir me, what in text is more worth.. because it explain everithing. And the video just a guidline of what u read.
sudipta08sarkar said:
Ok I understand, but my query is, everytime I will flashing a new treble rom, will it flash vendor partition itself?
Click to expand...
Click to collapse
Yes. Well, depends.
RR Treble has Vendor included, because it needs it. GSI's are just a system image that use your existing vendor.
squallbayu said:
Congratulations, can't wait to test it on my a1.
One question, how about google play certified device status? Is still verified or not?
If i choose to shrink data partition, how much left for data? My a1 have 64 gb storage.
Click to expand...
Click to collapse
If you.can tell me exactly what "Play Certified" actually is, then I might be able to answer that question.
The TWRP with Treble Manager tells you the size change.
Follow the instructions
Files required to be download:
Aosp 9:here
build.prop: here
Flash GSI with TWRP use this fix sd card not read in twrp here
reboot to twrp by pressing power + volume up
Perform a factory reset within TWRP. format data
Download and extract system-arm-aonly-gapps-su.img.xz and you will get system-arm-aonly-gapps-su.img
Transfer the system-arm-aonly-gapps-su.img from your PC to your device’s internal storage where TWRP can access it.
Tap on “Install
Change the type from “zip” to “image.
Find and select the system-arm-aonly-gapps-su.img you downloaded.
Choose to flash to the system partition
no need to flash modified vendor
Once that is done, reboot your device.
Fix : performance copy the build.prop to system/
Bugs: google certification (fix here) after registration clear the google apps data (framewrork/services)
XDA:DevDB Information
Aosp 9 Redmi Go, ROM for all devices (see above for details)
Contributors
samsungics1200, phhusson
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: Aosp 9
Version Information
Status: Testing
Current Beta Version: April 16 2019
Created 2019-04-17
Last Updated 2019-06-11
is there any bug?
Fix : performance copy the build.prop : here copy to system/
Click to expand...
Click to collapse
File needs permission to access - is there another link?
Thanks - the file is available for download now.
I have installed the ROM and it works well but do you know if it is possible to disable the forced device encryption?
Also, my SIM2 is not recognised. Any ideas?
Auto booting to fastboot after installing... (installed to redmi go, it is unlocked, followed instruction, tried minimum 3-4 times, tried several variants of 9.0 Pie GSI etc.)
If You installed 9.0 by the instruction above and it successfully started, it means there is some hardware difference between different region redmi go devices. Mine is Global version.
Stock 8.1 GO is installing and starting normally from TWRP. Problem occurs only with the rom from this thread.
I want to switch to 9.0 beacuse stock 8.1 GO have push notification issue. Believe me, I tried everything to fix it, but unsuccessfully...
Waiting for Your help.
Instructions
NOTE: Do not flash the vendor file from the OP, that causes bootloops on my device.
This is what I did - now happily running AOSP 9:
- Restore stock firmware (http://en.miui.com/download-365.html)
- Reboot then perform system update to get latest release
- Reboot to bootloader (fastboot mode)
- Download the GSI image from the OP
- fastboot flash system system-test-20190415-arm-a.img
- Boot to TWRP recovery
- Mount system partition
- Replace /system/build.prop with one from OP
- Reboot
Additionally, if you want to disable encryption:
- Format data partition (You will loose all of your data!)
- Download vendor image file from OP
- Extract default.prop and fstab.qcom
- Mount vendor partition
- Replace extracted files to phone
Update
Hello to my Russian friends who are following this thread from http://4pda.ru/forum/index.php?showtopic=939092&view=findpost&p=84933744
I have attached the files that need to be replaced to this post
hello guys. i have tried both procedures. it gets stuck on "android" logo (booting i guess).
shall i use vendor? shall not use vendor?
"
- Restore stock firmware (http://en.miui.com/download-365.html)
....
- Replace /system/build.prop with one from OP
- Reboot"
now it should boot?
i tried stopping here, and no luck. i tried doing those "additionally.." steps, same lack of luck.
You only need to touch vendor if you want to disable forced encryption.
These instructions worked when I posted them on 4pda:
- Unlock bootloader - there are instructions elsewhere
- Download: http://treble.phh.me/system-test-20190415-arm-a.img (system.img)
- Download TWRP from other thread (trwp.img)
- Download files.zip from my previous post and extract build.prop
- Power off the phone
- Press volume down and power buttons to go to fastboot bootloader
- Connect your phone to your computer via usb cable
- Type in terminal: fastboot flash system system.img
- Wait for process to finish
- Type in terminal: fastboot boot twrp.img
- Phone will reboot to TRWP recovery mode
- Select "Mount" then "System"
- Type in terminal: adb push build.prop /system/
- Type in terminal: adb shell chmod 600 /system/build.prop
- Reboot phone
If you need GApps, grab the latest pico from https://github.com/opengapps/arm/releases - ie https://github.com/opengapps/arm/releases/download/20190507/open_gapps-arm-9.0-pico-20190507.zip - and install from TWRP.
in locks every time in the "Encryption unsuccessful ... RESET PHONE"
/vendor issue
What process did you use? Did you touch the /vendor partition? Does formatting /data from TWRP help?
Restore stock formware (all partitions from fastboot) then follow steps here: post 10
Camera issue
Only issue I spotted on this ROM for now is - Camera quality became worse. Is it a driver or just app level issue?
This is a Project Treble device which means that the drivers remain untouched in the /vendor partition and the new GSI uses them, unlike older ROMs which contained their own drivers. Which version of firmware did you have before installing the GSI? On 4pda it was observed that camera2 api apps was the issue but I have not seen any such problem.
Just updated to the May 2019 build (v113) and all is good - just had to resize the image to fit the partition. I shall keep updating monthly as long as phh keeps making them.
The ROM from the original post is no longer available. If anyone is interested then I can make an updated GSI available.
Note: FM radio is missing
Kyuunex said:
Note: FM radio is missing
Click to expand...
Click to collapse
Indeed, but the developer is on it, follow progress here: Include FM Radio app
I can't find a gsi that will fit my system partition
need the smallest GSI possible for an obscure mt6580 device
EDIT: would love to try the outdated image that's no longer available ANYWHERE
First released twrp for BLU G90 phone.
Whats working:
Adb
Mtp
USb-OTG
MicroSD
Flash Image
Mount System , Vendor, product (contents of SUPER).... mount allows reading the partitions, but was not able to write to them
Back-Up/Restore to/from usb (or micro sdcard).... Due to size of super.img needed to format card ext4
Logcat
Screenshot
Known bug:
**Solved with new tree file**--data decryption is not working, so not able to read or backup internal storage.--
Built with Minimum Manifest _branch 10.0 :
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
Kernel source :
https://github.com/mrmazakblu/Blu_G90_G0310WW_stock_kernal
Device Tree :
New
GitHub - mrmazakblu/device_PBRP_BLU_G90_G0310WW at TWRP
Contribute to mrmazakblu/device_PBRP_BLU_G90_G0310WW development by creating an account on GitHub.
github.com
Download :
Releases · mrmazakblu/device_PBRP_BLU_G90_G0310WW
Contribute to mrmazakblu/device_PBRP_BLU_G90_G0310WW development by creating an account on GitHub.
github.com
Old
https://github.com/mrmazakblu/device_TWRP_BLU_G90_G0310WW
Download : https://github.com/mrmazakblu/device_TWRP_BLU_G90_G0310WW/releases
ADB Sideload is also broken.
Shananiganeer said:
ADB Sideload is also broken.
Click to expand...
Click to collapse
Most likely due to no able to read/ write to /data there is no place to temp store the zip.
Working on alternative options at the moment, as I am having trouble getting build correct to make decrypt.
Alternative is a modified /vendor.img, so device is not encrypted. But this of course is less secure.
I reformatted /data so it was unencrypted, but still couldn't use adb sideload. I was able to use adb push to put files onto the phone, but that didn't end up mattering as without rw to /system I can't install gapps XD. I'll have some time this weekend to take a look at things and try and help debug the decryption.
Appearently, this build is only missing data decryption.
Spoke with TWRP maintainer, they said this is working as intended. Super.img partitions are not currently meant to be mounted as r/w.
After I asked about flashing GApps, I was informed that there might be changes to TWRP source to allow mounting as r/w sometime sooner or later.
mrmazak said:
Appearently, this build is only missing data decryption.
Spoke with TWRP maintainer, they said this is working as intended. Super.img partitions are not currently meant to be mounted as r/w.
After I asked about flashing GApps, I was informed that there might be changes to TWRP source to allow mounting as r/w sometime sooner or later.
Click to expand...
Click to collapse
so it may seem we are waiting on how to affectively be able to modify the dynamic partitions before we can see a fully successful root. I am fairly new to these things so might be looking at it wrong.
Ivisibl3 said:
so it may seem we are waiting on how to affectively be able to modify the dynamic partitions before we can see a fully successful root. I am fairly new to these things so might be looking at it wrong.
Click to expand...
Click to collapse
To modify it "live" yes maybe.
You can modify the extracted system, as I did , using linux mount, and flash the system back modified, just like a gsi rom.
But for root, can't say.
On the latest build, was able to mount /system r/w. And successfully change the contents of it.
The patches in twrp source is not finished yet, so normal zip installs are not coded. But using adb shell (or TWRP terminal ) seem to be working.
This New build to be uploaded on github device source, as release "test build 9"
I have the G90 Pro and would love to be able to edit the build.prop file... the phone has a ridiculously low number of volume steps for media, 7.
Is there any way to boot into TWRP temporarily and edit the file, just to see if that will increase the steps? (by adding ro.config.media_vol_steps=30 for example)
johnsag49 said:
I have the G90 Pro and would love to be able to edit the build.prop file... the phone has a ridiculously low number of volume steps for media, 7.
Is there any way to boot into TWRP temporarily and edit the file, just to see if that will increase the steps? (by adding ro.config.media_vol_steps=30 for example)
Click to expand...
Click to collapse
Well, the first thing I'm concerned with here is , I'm not sure if THIS TWRP will work on the g90 pro.
But it might be possible. I was able to mount system as r/w on my g90 in TWRP.
You would need to fastboot flash --disable-verity vbmeta and vbmeta_system to prevent red state bootloader lockout.
Ok I've found one potential bug and have a question you may be able to answer. With your build of TWRP I cannot access fastbootd. Running adb/fastboot reboot fastboot just puts me back into recovery. To change images I've been doing the following:
1. Enter bootloader and flash stock recovery you provided in your other G90 thread
2. Enter fastbootd and flash the image
3. Re-enter bootloader and flash twrp
The question I have is, how can the super partition be increased? I tried to flash the LOSQ build with gapps, but the image is > half the size of the super partition. I want to take 1GB away from the userdata partition and add it to the super partition instead. Do I mount the stock super.img in Linux and modify it to be 5GB, adjust the partitions on the eMMC so the new img will fit, flash the new super.img from bootloader, and then go into fastbootd and flash LOSQ? Where does modifying BoardConfig.mk with the new size fit in? If you don't know or don't wanna bother answering that's cool, I've been doing some digging trying to get to the bottom and I'm just not understanding how to adjust the new dynamic partition scheme.
Shananiganeer said:
Ok I've found one potential bug and have a question you may be able to answer. With your build of TWRP I cannot access fastbootd. Running adb/fastboot reboot fastboot just puts me back into recovery. To change images I've been doing the following:
1. Enter bootloader and flash stock recovery you provided in your other G90 thread
2. Enter fastbootd and flash the image
3. Re-enter bootloader and flash twrp
The question I have is, how can the super partition be increased? I tried to flash the LOSQ build with gapps, but the image is > half the size of the super partition. I want to take 1GB away from the userdata partition and add it to the super partition instead. Do I mount the stock super.img in Linux and modify it to be 5GB, adjust the partitions on the eMMC so the new img will fit, flash the new super.img from bootloader, and then go into fastbootd and flash LOSQ? Where does modifying BoardConfig.mk with the new size fit in? If you don't know or don't wanna bother answering that's cool, I've been doing some digging trying to get to the bottom and I'm just not understanding how to adjust the new dynamic partition scheme.
Click to expand...
Click to collapse
The stock /product partition is not needed in non stock roms. Google gsi flashing guide tells show to delete logical partition product.
Code:
fastboot delete-logical-partition product
This is probably what is needed.
Don't know about your plan to increase stock super.img. no idea about why you mention boardconfig.mk
This TWRP is before the patch for TWRP fastbootd, so it is not included. I have resynced source, and will see if new build works, or not. If it does will post new release.
I mentioned BoardConfig.mk because the size of the super partition is listed there, but you were totally right about the product partition and I was able to flash LOSQ+gapps after deleting it. Thanks for the assist, and your work on porting TWRP to this awesome device! Will continue to keep an eye on your work as TWRP finalizes their support for Android 10.
Will this work for the G90 Pro? My guess is not but figured I'd ask
KryptekKnight said:
Will this work for the G90 Pro? My guess is not but figured I'd ask
Click to expand...
Click to collapse
I assume not. But if you send device stock recovery, I can try to bring it up. But cannot test it, I don't have the device.
mrmazak said:
I assume not. But if you send device stock recovery, I can try to bring it up. But cannot test it, I don't have the device.
Click to expand...
Click to collapse
Would you be able to compile a Gcam pretty for this phone? I would be willing to supply you with whatever is within my means to provide
KryptekKnight said:
Would you be able to compile a Gcam pretty for this phone? I would be willing to supply you with whatever is within my means to provide
Click to expand...
Click to collapse
I have no idea about gcam
johnsag49 said:
I have the G90 Pro and would love to be able to edit the build.prop file... the phone has a ridiculously low number of volume steps for media, 7.
Is there any way to boot into TWRP temporarily and edit the file, just to see if that will increase the steps? (by adding ro.config.media_vol_steps=30 for example)
Click to expand...
Click to collapse
Sorry OP.....
I need to get 01 post of your topic to report on custom recoveries on the G90 Pro.
For new users, you should know about the Android 10 permission structure.
In TWRP or PBRP, through the File Manager, it is not possible to copy files to the superpartition. But you can copy files from the superpartition to the internal SD card.
Therefore, to modify files from the super partition, it will be necessary to extract the super partition and extract system-product-vendor to then carry out the modifications and repackage.
Using Havocv3.11 the volume issue dissapears...........
Well all, thanks to @lopestom , we may soon have a new device tree to build recovery from , and data decryption is working on first test img. New recovery would be pbrp instead of twrp.
TWRP for m12 u3
(See post#2 for u2 version)
Built by Afaneh mod physwizz
Download tar file.
Extract recovery.img from tar file
Method 1.
If you have already installed recovery and decrypted.
1. Boot to recovery.
2. Install recovery.img
3. Choose recovery partition
4. Reboot to recovery
Method 2.
1. Download firmware
2. Extract ap file.
3. Patch with magisk
4. Flash with Odin
5. Download recovery.img
6. Install TWRP app
7. Install TWRP
8. Choose file to flash.(don't select device)
9. Select recovery.img.
10. Reboot to recovery.
Go to part B
Method 3.
1. Download recovery tar
2. Download vbmeta disabled tar
Exynos 850 Resources
t.me
3. Connect phone to PC
4. Go to Download mode
5. Flash recovery tar into ap with Odin
6. Flash vbmeta disabled tar into userdata with Odin
Part B
7. Reboot to recovery.
8. Wipe, format data, type YES.
9. Advanced, terminal.
10.Type multidisabler (twice).
11.Reboot to recovery
Reboot, setup phone
12. Flash Magisk for root(only for method 3)
13. Backup boot, data, super and dtbo
@physwizz
Afaneh TWRP modified by physwizz
For m12 u2
Download tar file.
Extract recovery.img from tar file
Method 1.
If you have already installed recovery and decrypted.
1. Boot to recovery.
2. Install recovery.img
3. Choose recovery partition
4. Reboot to recovery
Method 2.
1. Download firmware
2. Extract ap file.
3. Patch with magisk
https://t.me/a127f_res/4)
4. Flash with Odin
5. Download recovery.img
6. Install TWRP app
7. Install TWRP
8. Choose file to flash.(don't select device)
9. Select recovery.img.
10. Reboot to recovery.
Go to part B
Method 3.
1. Download recovery tar
2. Download vbmeta disabled tar
Exynos 850 Resources
t.me
3. Connect phone to PC
4. Go to Download mode
5. Flash recovery tar into ap with Odin
6. Flash vbmeta disabled tar into userdata with Odin
Part B
7. Reboot to recovery.
8. Wipe, format data, type YES.
9. Advanced, terminal.
10.Type multidisabler (twice).
11.Reboot to recovery
12. Flash Magisk for root(only for method 3)
13. Backup boot, data, super and dtbo
@physwizz
Installing a GSI
for a12s(a127f) and m12(m127f)
1. Unzip img file
2.Wipe data from twrp
3. Install IMG into system
4. Install my kernel
5. Reboot
If you need to install GApps
1. Wipe, advanced wipe
2. Select system, repair or change
3. Resize file system
4. Install GApps
GSI list
Exynos 850 Resources
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list
t.me
@physwizz
physwizz said:
You may need to swipe 6times to unlock
Click to expand...
Click to collapse
With this recovery, it's hard to call it a bug, since I stupidly disabled the screen timeout in the settings and everything is ok
physwizz said:
Installing a GSI
for a12s(a127f) and m12(m127f)
1. Unzip img file
2.Wipe data from twrp
3. Install IMG into system
4. Install my kernel
5. Reboot
GSI list
Exynos 850 Resources
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list
t.me
@physwizz
Click to expand...
Click to collapse
Thank you, as soon as you made the recovery, so now you can fully modify it, add hidden functions, so now also gsi, I'm just high, thank you very much, now there will be something else to occupy myself with
physwizz said:
Installing a GSI
for a12s(a127f) and m12(m127f)
1. Unzip img file
2.Wipe data from twrp
3. Install IMG into system
4. Install my kernel
5. Reboot
GSI list
Exynos 850 Resources
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list
t.me
@physwizz
Click to expand...
Click to collapse
It's a pity that there is no miui gsi firmware, well, okay, I will use what they give, thank you very much
physwizz said:
Installing a GSI
for a12s(a127f) and m12(m127f)
1. Unzip img file
2.Wipe data from twrp
3. Install IMG into system
4. Install my kernel
5. Reboot
GSI list
Exynos 850 Resources
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list
t.me
@physwizz
Click to expand...
Click to collapse
Hi, there's such a problem here, the touchscreen does not work on gsi firmware after the screen is locked, if the phone locks, or the screen just goes out, then the touchscreen stupidly no longer responds to clicks, and you have to restart, just like in twrp
KEMLEP said:
Hi, there's such a problem here, the touchscreen does not work on gsi firmware after the screen is locked, if the phone locks, or the screen just goes out, then the touchscreen stupidly no longer responds to clicks, and you have to restart, just like in twrp
Click to expand...
Click to collapse
I don't use GSIs
physwizz said:
I don't use GSIs
Click to expand...
Click to collapse
Are there any similar cores with a12 for m12 that can run gsi firmware?
KEMLEP said:
Are there any similar cores with a12 for m12 that can run gsi firmware?
Click to expand...
Click to collapse
I installed pixel experience and lineages ok
physwizz said:
I installed pixel experience and lineages ok
Click to expand...
Click to collapse
and there was no such thing that when unlocking the screen, the touchscreen does not work
Hi, I have such a question, I want to completely cut out all the system garbage from the firmware so that it can be installed via odin and there was no junk, since I just couldn't remove them from the off firmware, I think to do so, cut out all the garbage through the phone, delete all the extra folders, make a backup system and convert to img, and then flash through odin, will such an idea work?
Hi,
I tried the recovery in my m127g (u2). Though the recovery is actually for u3. As I haven’t yet found any working version for mine.
After I wipe, format data, it says, "Failed to mount '/data'." (attached photo 1)
After typing multidisabler in terminal, it says successful. (attached photo 2)
Any advice will be appreciated.
mdbshuvo said:
Hi,
I tried the recovery in my m127g (u2). Though the recovery is actually for u3. As I haven’t yet found any working version for mine.
After I wipe, format data, it says, "Failed to mount '/data'." (attached photo 1)
After typing multidisabler in terminal, it says successful. (attached photo 2)
Any advice will be appreciated.
Click to expand...
Click to collapse
No it won't work for u2.
If you send me your stock recovery.img I'll make one for u2
U3 version now in post #2
physwizz said:
U3 version now in post #2
Click to expand...
Click to collapse
Just installed this TWRP in my m127g (u2), worked just great. Thanks.
mdbshuvo said:
Just installed this TWRP in my m127g (u2), worked just great. Thanks.
Click to expand...
Click to collapse
Np
physwizz said:
Np
Click to expand...
Click to collapse
Just installed this TWRP in my m127g (u2), worked just great.
Click to expand...
Click to collapse
There was a problem I faced lately.
I had to flash my phone yesterday, tried to install the TWRP. The problem was internal storage not showing. Formatting and multidisabler doesn't help. Results in bootloop.
What works for me is installing OrangeFox (provided by you), formatting and typing multidisabler. Then use the method 1 here. Just for your information.
After installation it works fine.
mdbshuvo said:
There was a problem I faced lately.
I had to flash my phone yesterday, tried to install the TWRP. The problem was internal storage not showing. Formatting and multidisabler doesn't help. Results in bootloop.
What works for me is installing OrangeFox (provided by you), formatting and typing multidisabler. Then use the method 1 here. Just for your information.
After installation it works fine.
Click to expand...
Click to collapse
thanks for the feedback
Does this recovery work on sm-m127g/ds
Binary: u3
If yes what are the bugs for this model.
If no which one will work ?
{
"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"
}
Devices post#1
Root method post#2
TWRP post#3
Kernels post#4
Debloaters post #5
wizzROM creators post #6
Exynos 850 Devices
1. A12s
A127f & A127m
2. M12
M127f & M127g
3. A21s
A217f & A217m
4. F12s
F127g
5. A13
A135f & A135m
6. M13
M135f & M135m
7. F13
E135f
8. A04s
A047f
9. XCover5
G525f
10. A145f
Root for Exynos 850
1. Download the exact firmware (including upgrade date) for your device from https://samfrew.com or https://www.samfirmware.net/ or https://www.full-repair-firmware.com/search?q=A20 or
Samsung Firmware Download - Lastest official firmware update
Samsung Firmware Download ⭐ Official and fast update ⭐ Lastest and old version ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
2. Download delta magisk
3. Use zarchiver to extract the ap section from the firmware.
4. Use magisk to patch the ap section.(install, select file to patch)
5. Unlock the bootloader.
6. Flash the patched ap file using Odin.
Or with heimdall
7. Reboot.
8. Go all the way through the set-up process.
9. Don't upgrade your magisk of you won't see the online modules
@physwizz
Installing Custom Recoveries
A. Preparation.
1. Download firmware for your device
2. Extract ap file using Zarchiver and extract recovery.img from recovery.img.lz4 and compress it to recovery.tar
3. Patch the ap file with a magisk which will patch both boot.img and vbmeta.img (from magisk, choose install then select file to patch)
Alternatively you can extract boot.img.lz4 and vbmeta.img.lz4 from the ap file and compress them into a new tar file and then patch that file.
note: if you don't want root then just extract the vbmeta.img and use zarchiver to add it to my twrp.tar file.
You can flash this new file from odin at step 5
For Exynos 850 android 11 use a21s patched magisk.
For Exynos 850 android 12 and most other devices use delta magisk
4. Unlock OEM in developer options
5. Attach phone to pc and reboot to download mode
6. flash patched ap file.
Or..
Extract boot.img and vbmeta.img and add them to the TWRP zip.
7. Download the zip and extract the twrp.tar and extract recovery.img using Zarchiver.
B.Installation
Method 1.
1. Connect to pc and boot into stock recovery
2. Factory reset
3. Reboot into download mode.
4. flash twrp.tar into the ap slot
5. reboot to recovery from main menu (not just reboot)
be patient- It may take a while
6. Advanced, terminal. Type multidisabler (twice).
7.
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
8. Reboot to recovery from main menu (not just reboot)
Backup boot, data, super and dtbo
9. Reboot to system
Method 2.
If you have already installed recovery and decrypted.
Extract recovery.img
1. Boot to recovery.
2. Install recovery.img
3. Choose recovery partition
4. Reboot to system then reboot to recovery
Backup boot, data, super and dtbo
(For Pitch-black just install the zip)
Method 3.
1. Install TWRP app
Extract recovery.img
2. Install TWRP
3. Choose file to flash.(don't select device)
4. Select recovery.img.
5. Reboot to recovery.
6. (You may need to change data partition to ext4 first if format ruins your system)
7. Reboot to recovery.
8. Wipe, format data, type YES.
9. Advanced, terminal.
10.Type multidisabler (twice).
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
11.Reboot to recovery
12. Flash Magisk for root(only for method 3)
13. Backup boot, data, super and dtbo
Method 4
Using a second phone
C. Recovery Problems
Most recovery issues can be solved by attending to the following issues.
1. Did you root using the full ap file patched Magisk .
(This contains the patched boot.img and vbmeta.img)
Exynos 850 users must use the special a217 magisk?
2. Did you then go all the way through the setup process?
3. Did you download the recovery to match your device
4. Did you hold down power and volume up after Odin says pass?
5. Did you format data from stock recovery?
If you forgot to do this, just install stock recovery.img from TWRP and reboot.
6. Did you type multidisabler twice?
7. Did you reboot to recovery by choosing reboot from the menu and then choosing recovery?
8. To avoid touch issues go to settings and untick "allow time out"
D.To restore Stock Recovery
1. Attach phone to pc and reboot to download mode
2. flash patched ap file or stock recovery.tar
3. reboot
Or just flash stock recovery.img from twrp and reboot.
TWRP Building Guide
Guide to TWRP building
TWRP for a12s ============= 1. Setup -------- sudo apt update sudo apt upgrade sudo apt-get install git-all sudo apt install python-is-python3 git config --global user.email "your email" git config --global user.name "your name" 2...
forum.xda-developers.com
@physwizz
These TWRPs are all derived from my a127f device tree.
Code
physwizz - Repositories
physwizz has 172 repositories available. Follow their code on GitHub.
github.com
Kernels
Installing physwizz custom kernels
INSTALL AT YOUR OWN RISK
I AM NOT RESPONSIBLE FOR ANY BRICKED PHONES
But I will help any well-mannered person to recover.
Note: physwizz kernels work best with debloated stock or with wizzROM
Other custom ROMs may not be supported
A. Preparation
1. Root the phone
2. Compress your patched boot.img to make boot.tar
3. Copy boot.tar to PC
Note: If you have previously installed a custom dtbo, you may need to flash stock dtbo
Physwizz Collection
Dtbo installer Extract stock dtbo.img from your firmware. Add to the zip using zarchiver. Use stock dtbo.img from your baseband (not your kernel or your ROM)
t.me
B. Installation
Method 1
Install from twrp
Reboot to recovery
Backup boot and dtbo (if available)
Install kernel zip or boot.img
Wipe both caches
Reboot
Method 2
Install kernel from terminal.
1. Download magisk module (magic flash zip) https://github.com/Magisk-Modules-Alt-Repo/magic-flash
2. Install module and reboot.
3. Open terminal.
4. Navigate to folder containing kernel zip.
Use
ls to list contents
and
cd to change directories
5. Type su
6. Type flash kernel zip
7. Reboot
Method 3
Using ADB
Install adb tools on pc
Connect to PC
Copy zip file to adb folder on pc
Open terminal on pc
Navigate to adb folder
Type
adb sideload filename.zip
Method 4
Using boot.img
Install AIK Mobile from magisk modules https://t.me/physwizz2/82
Use rootexplorer to access
/data/local/AIK-MOBILE
Add patched boot.img and tap unpackimg.sh
Exit the folder and return to see the files.
Edit the files (eg to add a new Image
rename Image to boot.img-zImage and insert in split-image folder)
Tap repackimg.sh
Rename new_image.img to boot.img
Compress boot.img to boot.tar
Copy boot.tar to PC
Reboot phone to download mode
Install boot.tar from odin
Method 5
Using a second phone
1. Prepare boot.img as in Method 4.
2. Go here
Physwizz Collection
Installing boot.img using a second phone. You can install a new kernel without a PC by using patched boot.img from phone1 to phone2 Preparation 1. Download the exact firmware (including upgrade date) for your device from https://samfrew.com or https://www.samfirmware.net/ or...
t.me
C. Removal
Method 1
Reboot to recovery
Restore boot and dtbo
Reboot
Method 2.
Reboot phone to download mode
Install patched boot.tar or patched-ap.tar from odin
@physwizz
Kernel Properties
Samsung securities disabled
More CPU governors
On-demand, Userspace, powersave, performance, energy_step, shedutil
Optimised for performance
Overclocked for performance
Underclocked for battery
CPU: 130MHz - 2210MHz
lz4 default compression added to zram
Kernel source code
physwizz - Repositories
physwizz has 172 repositories available. Follow their code on GitHub.
github.com
physwizz debloat module v3
(Added a70 changes)
With physwizz-2 app
Fixed apps in system/product
Installing
Physwizz Collection
t.me
NOTE: you may still need to delete some apps from the app drawer.
Magisk module to debloat any Samsung phone to remove all the apps that slow down the phone
To debloat:
Install the module from Magisk and reboot.
To rebloat:
delete the module in Magisk and reboot
@physwizz
wizzROM Creator magisk module v4 Thermal
DO NOT INSTALL FROM TWRP
for all Samsung phones
Debloated ROM with Extras
Fixed apps in system/product
Extras:
Battery charge limit
Clean Master
ES file explorer
HKtweaks
SimpleReboot
Root Explorer
Zarchiver
physwizz-2
Thermal throttling removed
Make sure your OneUI ROM iis running befote you start
Installation
1 Backup system from recovery
2 Install the creator from Magisk
Physwizz Collection
t.me
3 Reboot
4 Enjoy
NOTE: you may still need to delete some apps from the app drawer.
Name your wizzROM (optional)
1. Use a root explorer to navigate to system/build.prop
2. Tap to Edit build.prop like this
ro.build.display.id=<your-name>
3. Tap disk icon to Save & Reboot
Xda post
wizzROM Creator
wizzROM Creator module v4 Thermal for all Samsung a-series phones OneUI 2.0 will become QwizzROM OneUI 3.1 will become RwizzROM OneUI 4.0 will become SwizzROM Debloated ROM with Extras Fixed apps in system/product Extras: Battery charge limit...
forum.xda-developers.com
@physwizz
Hi guys! I'm very new to this so sorry for mi lack of knowledge on this but i wanted to ask, i've an sma135m, exynos 850 but its stock kernel comes as 32bit forced. Is there any kernel which you provides that gives the capability to use the processor at full 64bit? Thanks in advance!
arieleoar said:
Hi guys! I'm very new to this so sorry for mi lack of knowledge on this but i wanted to ask, i've an sma135m, exynos 850 but its stock kernel comes as 32bit forced. Is there any kernel which you provides that gives the capability to use the processor at full 64bit? Thanks in advance!
Click to expand...
Click to collapse
No sorry.
But my kernel will make it better
physwizz said:
Root for Exynos 850
1. Download the exact firmware (including upgrade date) for your device from https://samfrew.com or https://www.samfirmware.net/ or https://www.full-repair-firmware.com/search?q=A20 or
Samsung Firmware Download - Lastest official firmware update
Samsung Firmware Download ⭐ Official and fast update ⭐ Lastest and old version ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
2. Download delta magisk
3. Use zarchiver to extract the ap section from the firmware.
4. Use magisk to patch the ap section.(install, select file to patch)
5. Unlock the bootloader.
6. Flash the patched ap file using Odin.
Or with heimdall
7. Reboot.
8. Go all the way through the set-up process.
9. Don't upgrade your magisk of you won't see the online modules
@physwizz
Click to expand...
Click to collapse
Hello! Thanks fpr the instruction, but I faced with issue that my SM-137F is also using Exynos 850 after installing the modified AP with ODIN (flashing full BL, AP, CSC, CP) using this version of Magisk Delta (like I've tried others as well) falls into Bootloop (don't even runs the system, just starts -> logo asking press power button -> new logo with warning of custom firmware -> reboot, and then again). So I've tried many different Magisk versions - result the same.
So the question is, what do I do wrong?
Firmware version SM-A137F_XSG_A137FXXU1AVH1 (Android 12)
And I haven't do patching using the phone, I've installed the Magisk on the Android Studio emulator and patching there, may be this a reason?
Sawery said:
Hello! Thanks fpr the instruction, but I faced with issue that my SM-137F is also using Exynos 850 after installing the modified AP with ODIN (flashing full BL, AP, CSC, CP) using this version of Magisk Delta (like I've tried others as well) falls into Bootloop (don't even runs the system, just starts -> logo asking press power button -> new logo with warning of custom firmware -> reboot, and then again). So I've tried many different Magisk versions - result the same.
So the question is, what do I do wrong?
Firmware version SM-A137F_XSG_A137FXXU1AVH1 (Android 12)
And I haven't do patching using the phone, I've installed the Magisk on the Android Studio emulator and patching there, may be this a reason?
Click to expand...
Click to collapse
1. A137 is Mediatek MT6769V/CU Helio G80 (12 nm)
2. You must patch using the phone
physwizz said:
1. A137 is Mediatek MT6769V/CU Helio G80 (12 nm)
2. You must patch using the phone
Click to expand...
Click to collapse
1. Oh my god, sorry... What version of Magisk for getting root do I need to use the, maybe you know?
2. Really? Why? I thought it's just changing the binary and doesn't matter when the Magisk launched, on this phone, emulator, or any other phone
Sawery said:
1. Oh my god, sorry... What version of Magisk for getting root do I need to use the, maybe you know?
2. Really? Why? I thought it's just changing the binary and doesn't matter when the Magisk launched, on this phone, emulator, or any other phone
Click to expand...
Click to collapse
If it doesn't work on the emulator try it on the phone.
I'll ask someone else who owns one
Sawery said:
1. Oh my god, sorry... What version of Magisk for getting root do I need to use the, maybe you know?
2. Really? Why? I thought it's just changing the binary and doesn't matter when the Magisk launched, on this phone, emulator, or any other phone
Click to expand...
Click to collapse
Yes he did it with patched ap file.
He also did it using official magisk apk and with twrp
physwizz said:
Yes he did it with patched ap file.
He also did it using official magisk apk and with twrp
Click to expand...
Click to collapse
Sorry, but maybe he has the right working twrp for my device? If yes, could you share with me? I cant find it as well anywhere, thanks a lot!
Sawery said:
Sorry, but maybe he has the right working twrp for my device? If yes, could you share with me? I cant find it as well anywhere, thanks a lot!
Click to expand...
Click to collapse
I'll ask him
Sawery said:
Sorry, but maybe he has the right working twrp for my device? If yes, could you share with me? I cant find it as well anywhere, thanks a lot!
Click to expand...
Click to collapse
Good morning,
Do have a semi-working TWRP. So far didn't have the time to fix FBE for /data partitions. But if you have a big enough SD Card it should be fine to use.
ZIP file holds just recovery.img (to flash direct if phone is rooted
recovery.tar.md5.zip can be used to flash on ODIN (AP slot). First extract zip to get tar.md5 file
edward0181 said:
Good morning,
Do have a semi-working TWRP. So far didn't have the time to fix FBE for /data partitions. But if you have a big enough SD Card it should be fine to use.
ZIP file holds just recovery.img (to flash direct if phone is rooted
recovery.tar.md5.zip can be used to flash on ODIN (AP slot). First extract zip to get tar.md5 file
Click to expand...
Click to collapse
I don't know, my only goal is to add root on my device somehow, but the only way as I understand is Magisk, I hoped to install it with TWRP as nothing works for me using ODIN flashing. Nothing works for me (SM-A137F_XSG_A137FXXU1AVH1 Firmware), the device endlessly reboots after this image on the screen (even if I'm trying to get to the recovery menu). But anyway thanks for the time and for the files.
physwizz said:
1. A137 is Mediatek MT6769V/CU Helio G80 (12 nm)
2. You must patch using the phone
Click to expand...
Click to collapse
The second point should be definitely added to README.MD in official Magisk github account, because there aren't any warning about using only the same phone for patching that you are going to root, as I understand that it is patching according to the type of processor in addition to other parameters.
Anyway thanks for help, it works for me, I've successfully rooted 2 different devices already (Samsung Galaxy A13 SM-A137F and Samsung Galaxy A03 Core SM-A032F if someone will be searching for).
Sawery said:
The second point should be definitely added to README.MD in official Magisk github account, because there aren't any warning about using only the same phone for patching that you are going to root, as I understand that it is patching according to the type of processor in addition to other parameters.
Anyway thanks for help, it works for me, I've successfully rooted 2 different devices already (Samsung Galaxy A13 SM-A137F and Samsung Galaxy A03 Core SM-A032F if someone will be searching for).
Click to expand...
Click to collapse
I don't think it needs to be the same phone but I don't think the emulator does a good job in that respect
A145f twrp now available