I have already unlocked the bootloader on my Micromax IN 1 E6746 and other than that it's untouched. How can I root my device and install custom recovery on it?
I have attached some screenshots from Treble check and Droid info app.
{
"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"
}
shah.meet6338 said:
I have already unlocked the bootloader on my Micromax IN 1 E6746 and other than that it's untouched. How can I root my device and install custom recovery on it?
I have attached some screenshots from Treble check and Droid info app.View attachment 5301995View attachment 5301997View attachment 5301999
Click to expand...
Click to collapse
For Magisk: Download the APK of the manager off of the official Github, and rip the boot.img from your ROM. Then: Use Magisk Manager to patch that boot image, and flash it to your boot using ADB commands while in fastboot mode.
For Recovery: I'm not sure. I do not own the device, and most devices have you do different things for flashing the recovery. Sorry that I can't help you in this regard.
OrthodoxOxygen said:
For Magisk: Download the APK of the manager off of the official Github, and rip the boot.img from your ROM. Then: Use Magisk Manager to patch that boot image, and flash it to your boot using ADB commands while in fastboot mode.
For Recovery: I'm not sure. I do not own the device, and most devices have you do different things for flashing the recovery. Sorry that I can't help you in this regard.
Click to expand...
Click to collapse
Any ideas on how to get the boot.img. This model is fairly new and hasn't been even 2 months since it was first released.
shah.meet6338 said:
Any ideas on how to get the boot.img. This model is fairly new and hasn't been even 2 months since it was first released.
Click to expand...
Click to collapse
You need to find a copy of the current stock ROM you are using. Then (since it will likely be in a .zip file): Extract it, and move it onto your device. Let Magisk do its job with the file, and then move the patched image onto your PC from your phone. Afterwards: Use ADB's "platform-tools" to flash the boot partition of your phone with the patched boot.img. You can find videos on how to do this, but the command should look like "fastboot flash boot x.img" - where x = the name of the file.
OrthodoxOxygen said:
You need to find a copy of the current stock ROM you are using. Then (since it will likely be in a .zip file): Extract it, and move it onto your device. Let Magisk do its job with the file, and then move the patched image onto your PC from your phone. Afterwards: Use ADB's "platform-tools" to flash the boot partition of your phone with the patched boot.img. You can find videos on how to do this, but the command should look like "fastboot flash boot x.img" - where x = the name of the file.
Click to expand...
Click to collapse
Found the recovery for my device.
Here is the link:
Thread '[RECOVERY][BETA][v3.0.0] Pitch Black Recovery [E7746][30/01/2021]' https://forum.xda-developers.com/t/...itch-black-recovery-e7746-30-01-2021.4210395/
The recovery works on Micromax in note 1 and Micromax in 1 ( as far as i know).
shah.meet6338 said:
Found the recovery for my device.
Here is the link:
Thread '[RECOVERY][BETA][v3.0.0] Pitch Black Recovery [E7746][30/01/2021]' https://forum.xda-developers.com/t/...itch-black-recovery-e7746-30-01-2021.4210395/
The recovery works on Micromax in note 1 and Micromax in 1 ( as far as i know).
Click to expand...
Click to collapse
Nice. You might need to flash a custom ROM to root your phone, as there doesn't seem to be any stock ROMs on the internet. You could maybe rip the stock ROM from your phone, but I'm not sure how to do that, nor how safe it is. If you use the custom ROM method instead: Just flash the ROM to your phone, then extract the .zip file of that ROM on your PC. Put the boot.img file on your phone, use the Magisk Patcher in the Magisk app, move the patched image to your computer, enter fastboot, and then flash your boot partition with it. Watch out, though. Depending on your phone: You may have A/B partitioning, which makes things a little harder for all flashing processes. I haven't had a phone with A/B partitioning for a while, so, I can't really help you there. But, I'm sure there are videos about it. The main process should still prove usefull regardless of which device you are using.
EDIT: You have an A-only system. Flashing the phone should be pretty easy.
OrthodoxOxygen said:
Nice. You might need to flash a custom ROM to root your phone, as there doesn't seem to be any stock ROMs on the internet. You could maybe rip the stock ROM from your phone, but I'm not sure how to do that, nor how safe it is. If you use the custom ROM method instead: Just flash the ROM to your phone, then extract the .zip file of that ROM on your PC. Put the boot.img file on your phone, use the Magisk Patcher in the Magisk app, move the patched image to your computer, enter fastboot, and then flash your boot partition with it. Watch out, though. Depending on your phone: You may have A/B partitioning, which makes things a little harder for all flashing processes. I haven't had a phone with A/B partitioning for a while, so, I can't really help you there. But, I'm sure there are videos about it. The main process should still prove usefull regardless of which device you are using.
EDIT: You have an A-only system. Flashing the phone should be pretty easy.
Click to expand...
Click to collapse
Flashed magisk zip through the custom recovery (PBRP) amd installed magisk manager app afterwards. Now i have a rooted phone with a custom recovery and stock rom.
If you have any suggestions for a good custom rom, please let me know.
shah.meet6338 said:
Flashed magisk zip through the custom recovery (PBRP) amd installed magisk manager app afterwards. Now i have a rooted phone with a custom recovery and stock rom.
If you have any suggestions for a good custom rom, please let me know.
Click to expand...
Click to collapse
I think that might be an out-dated version of Magisk. Some modules might not work. The newest update makesy ou install the app first. I think the latest is 22.1. As for a good ROM: Your phone supports project treble, which means that you can flash a GSI image if there isn't enough development for your device right now. I heard HavocOS is good. I'm personally a fan of crDroid, Pixel Experience, and Evolution X. LineageOS is also quite good. You can find treble ROMs here: https://forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/
Make sure to pick the appropriate GSI. If you don't already know: Flashing the wrong one can hard-brick your phone. You should download GSIs tailored around a-only arm64 architectures, because that's what your phone is built on. Happy flashing!
OrthodoxOxygen said:
I think that might be an out-dated version of Magisk. Some modules might not work. The newest update makesy ou install the app first. I think the latest is 22.1. As for a good ROM: Your phone supports project treble, which means that you can flash a GSI image if there isn't enough development for your device right now. I heard HavocOS is good. I'm personally a fan of crDroid, Pixel Experience, and Evolution X. LineageOS is also quite good. You can find treble ROMs here: https://forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/
Make sure to pick the appropriate GSI. If you don't already know: Flashing the wrong one can hard-brick your phone. You should download GSIs tailored around a-only arm64 architectures, because that's what your phone is built on. Happy flashing!
Click to expand...
Click to collapse
does pixel experience rom work for any treble device? If so, can you point me in the direction where i can find pixel experience rom .
shah.meet6338 said:
does pixel experience rom work for any treble device? If so, can you point me in the direction where i can find pixel experience rom .
Click to expand...
Click to collapse
1) It doesn't always work. While I'm not quite sure as to why, sometimes ROMs just won't work on some devices. That's not to say that other GSIs don't, though. The fun of flashing is finding out what works best for you.
2) https://forum.xda-developers.com/t/gsi-unofficial-11-pixel-experience-pixel-experience-plus.4269051/
OrthodoxOxygen said:
1) It doesn't always work. While I'm not quite sure as to why, sometimes ROMs just won't work on some devices. That's not to say that other GSIs don't, though. The fun of flashing is finding out what works best for you.
2) https://forum.xda-developers.com/t/gsi-unofficial-11-pixel-experience-pixel-experience-plus.4269051/
Click to expand...
Click to collapse
I tried the pixel experience plus from your link but when i select the .img file to flash, the recovery (PBRP) asks me to select a partition to flash from a list - nvram, uboot, boot, recovery, logo, tee1,tee2, super(product, vendor, system)
I am not sure which partition should i select here.
shah.meet6338 said:
I tried the pixel experience plus from your link but when i select the .img file to flash, the recovery (PBRP) asks me to select a partition to flash from a list - nvram, uboot, boot, recovery, logo, tee1,tee2, super(product, vendor, system)
I am not sure which partition should i select here.
Click to expand...
Click to collapse
You need to flash it to your system partition. Did you make sure to grab the correct GSI according to your architecture and partition(s)?
OrthodoxOxygen said:
You need to flash it to your system partition. Did you make sure to grab the correct GSI according to your architecture and partition(s)?
Click to expand...
Click to collapse
yes, i got the arm64 a only image. i don't see system partition mentioned separately on the list of partitions.
super(product,vendor,system) is one option. nvram is another option . uboot is another option and so on.
should i select super partition?
shah.meet6338 said:
yes, i got the arm64 a only image. i don't see system partition mentioned separately on the list of partitions.
super(product,vendor,system) is one option. nvram is another option . uboot is another option and so on.
should i select super partition?
Click to expand...
Click to collapse
Can you boot into fastboot mode? I believe you're meant to flash GSIs only to the system partition.
Follow this procedure:
1) Boot into recovery.
2) Click on "Wipe", go to the advanced section, and then select Dalvik/Art cache, Substratum Overlays, Magisk Modules, Cache, Data, System, and (If you want) Internal storage. Wipe them.
3) Boot into fastboot mode.
4) Open the "platform-tools" folder, and drop the GSI image inside. Then, open a console so you can use ADB. Enter "fastboot devices".
5) If your device is connected, enter: "fastboot flash system x.img" - "x" being the name of your image.
6) Hope that it works.
OrthodoxOxygen said:
Can you boot into fastboot mode? I believe you're meant to flash GSIs only to the system partition.
Follow this procedure:
1) Boot into recovery.
2) Click on "Wipe", go to the advanced section, and then select Dalvik/Art cache, Substratum Overlays, Magisk Modules, Cache, Data, System, and (If you want) Internal storage. Wipe them.
3) Boot into fastboot mode.
4) Open the "platform-tools" folder, and drop the GSI image inside. Then, open a console so you can use ADB. Enter "fastboot devices".
5) If your device is connected, enter: "fastboot flash system x.img" - "x" being the name of your image.
6) Hope that it works.
Click to expand...
Click to collapse
FAILED (remote: This partition doesn't exist)
i think it has something to do with the dynamic partitions. any ideas?
shah.meet6338 said:
FAILED (remote: This partition doesn't exist)
i think it has something to do with the dynamic partitions. any ideas?
Click to expand...
Click to collapse
How to Fix GSI System failed (remote partition table doesn't exist) fastboot
step by step guide to fix failed remote partition table doesn't exist, Most of the user face this issue during the Installation of GSI Firmware on dynamic
romprovider.com
Try this, maybe. I've heard about this tool on XDA, I believe.
OrthodoxOxygen said:
How to Fix GSI System failed (remote partition table doesn't exist) fastboot
step by step guide to fix failed remote partition table doesn't exist, Most of the user face this issue during the Installation of GSI Firmware on dynamic
romprovider.com
Try this, maybe. I've heard about this tool on XDA, I believe.
Click to expand...
Click to collapse
Here, too.
fastboot flash system: partition not found
Hi All, used my OP7T for a week before deciding to unlock. That went fine, but when I tried to flash a GSI (no custom ROMs available yet), it says partition not found?? Tried system and system_a. [email protected]:~/Downloads/Android$ fastboot flash...
forum.xda-developers.com
shah.meet6338 said:
I have already unlocked the bootloader on my Micromax IN 1 E6746 and other than that it's untouched. How can I root my device and install custom recovery on it?
I have attached some screenshots from Treble check and Droid info app.View attachment 5301995View attachment 5301997View attachment 5301999
Click to expand...
Click to collapse
Join this Telegram group for development of this device,
Telegram: Contact @MmxIn1_Official
t.me
shah.meet6338 said:
I have already unlocked the bootloader on my Micromax IN 1 E6746 and other than that it's untouched. How can I root my device and install custom recovery on it?
I have attached some screenshots from Treble check and Droid info app.View attachment 5301995View attachment 5301997View attachment 5301999
Click to expand...
Click to collapse
bro when gong to active on telegram,
we need testers like you to test custom roms and make our IN 1 Community better
Related
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel!
Click to expand...
Click to collapse
Images
Prerequisites
Unlocked Bootloader
Click to expand...
Click to collapse
Installation instructions
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
Code:
fastboot reboot
Alternate Installation Method (requires prior TWRP installation):
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed. NOTE: This will only flash TWRP to the active slot!
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select recovery from the partition list and swipe to flash
Click to expand...
Click to collapse
Device Changelog
Current version: 3.6.0_11-0:
Initial version
Click to expand...
Click to collapse
Older Device-specific versions:
N/A
Click to expand...
Click to collapse
Click to expand...
Click to collapse
TWRP Official Change Log
Frequently Asked Questions (FAQ)
Downloads
Download
Latest Official versions
Sources
TWRP
Device tree
Common tree
Kernel source
Click to expand...
Click to collapse
Known Issues
Device-specific
N/A
TWRP Upstream
N/A
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"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"
}
If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
Click to expand...
Click to collapse
Additional Help/Support
Live support is available on Zulip.
Click to expand...
Click to collapse
Frequently Asked Questions (FAQ):
How do I install an OTA while rooted and keep TWRP/root?
Full Firmware zip - in Android
Prerequisites:
Full Firmware zip for new software
TWRP installed to the current slot
Magisk Manager
Steps:
Put Full Firmware zip on root of internal storage
Reboot the device so that the update is detected
Install the update
After install completes BUT BEFORE REBOOTING, install "TWRP A/B Retention Script" module by @osm0sis in Magisk Manager
Install Magisk "to Inactive Slot (After OTA)" in Magisk Manager
Reboot and you're updated with TWRP and root retained
Full Firmware zip - Through TWRP
Prerequisites:
Full Firmware zip for new software
TWRP_Flash_tpposite_Slot-CPTBv2.zip
Magisk zip (optional)
Steps:
Reboot into TWRP
Navigate to Full Firmware zip and install, or sideload zip over adb
Flash TWRP_Flash_tpposite_Slot-CPTBv2.zip to retain TWRP.
(Optional) Reboot into TWRP and flash Magisk for root.
Incremental OTA package - Through TWRP ONLY
Prerequisites:
Current software stock boot.img
Current software stock recovery.img
Current software stock dtbo.img (only if modified by Magisk or custom ROM)
Incremental OTA zip for current software to new software
TWRP_Flash_tpposite_Slot-CPTBv2.zip
Magisk zip (optional)
Steps:
Ensure you have the latest version of TWRP installed. If you don't, follow the instructions in the OP to flash it.
Boot into TWRP.
Use the "Install Image" feature to flash the stock boot and recovery (and dtbo) images.
Flash the incremental OTA zip.
Flash TWRP_Flash_tpposite_Slot-CPTBv2.zip to retain TWRP.
(Optional) Reboot into TWRP and flash Magisk for root.
The key here is making sure the current slot is fully stock (including boot and recovery images) in order for the incremental OTA zip to install successfully.
What's the deal with these dynamic partitions?
Here's Google's explanation.
Why can't I write to system?
Dynamic partitions (see link above). See @topjohnwu's detailed explanation here.
How do I make modifications to system?
On the stock ROM, you don't. However, you can modify system "systemlessly" with Magisk.
Can I boot the recovery image without flashing it?
No. Fastboot boot isn't possible on this device, but since there's a separate recovery partition (two in fact), and ASUS provides full stock firmware, this isn't a big concern.
What is fastbootd?
Here's Google's explanation.
Can I back up the system/vendor partition separately?
No. Because dynamic partitions. The Super partition is backed up and restored in its entirety. If you need to flash the individual images, use fastbootd.
Why can't I restore X partition (read-only error)?
Some of the partitions that can be backed up in TWRP include sensitive device data which, if corrupted, backed up, and then restored, can irreparably damage the device. Therefore, while these partitions can be backed up in TWRP, only experienced users should restore them, which can be done manually via the dd command.
(I will not provide any additional details on this procedure)
Click to expand...
Click to collapse
Reserved
Big thanks to @Buffydamion for all his tireless testing and log-providing to get this TWRP in fully working order!!
Hopefully there aren't any bugs besides the upstream ones listed in the OP, but if there are, I'll do my best to figure them out.
Since I don't have the device, I'll have to rely on all of you for logs and feedback.
Enjoy!!
--Cap
How did you make it boot on this android 10 device? Official TWRP doesn't support android 10. Dees_Troy is still working on the solution.
Volski_ said:
How did you make it boot on this android 10 device? Official TWRP doesn't support android 10. Dees_Troy is still working on the solution.
Click to expand...
Click to collapse
@Dees_Troy isn't the only person on the TWRP team.
@bigbiff has been working tirelessly to add Android 10 support to TWRP, with help from @mauronofrio, @androiabledroid, myself and others. TWRP is open-source and a team effort. As you'll notice, there are still some upstream bugs that need to be fixed, which is why the official TWRP hasn't been updated yet. But it's working well enough to release it for devices that need it, and when the official TWRP is ready, these devices will have official support.
Works fine for me. Thanks!
The data partition was already partitioned to f2fs.
Flashed magisk and have a rooted phone now. Perfect!
Update - new 20200920 build with stock kernel with f2fs support thanks to a proper fix from @aleasto.
I've also unified the dtb & dtbo with the ROG3 build, so this one needs testing to confirm it's booting for everyone. Please report back here once you have a chance to update.
--Cap
Captain_Throwback said:
Update - new 20200920 build with stock kernel with f2fs support thanks to a proper fix from @aleasto.
I've also unified the dtb & dtbo with the ROG3 build, so this one needs testing to confirm it's booting for everyone. Please report back here once you have a chance to update.
--Cap
Click to expand...
Click to collapse
So I had to remove the above build as it didn't boot. Building a new one now and hopefully it'll work. I'll keep everyone posted.
New release 20200922-14
There's a new release available today, which I recommend everyone switch to at their earliest convenience. I've also added a zip attachment to the first post that will allow you to flash a TWRP installed to your current slot to the opposite/inactive slot after an OTA is installed, so that you keep TWRP (otherwise it gets replaced by the OTA/firmware zip). The zip can be flashed either in Magisk Manager after the OTA completes installing (but BEFORE rebooting) or in TWRP after manually flashing a full firmware update zip (but PRIOR to rebooting). The zip simply duplicates the recovery from the existing recovery partition to the opposite slot, so it will only work if TWRP is currently installed to the active slot.
Change Log:
Update prebuilt kernel to source built with @aleasto's patch for f2fs
Set data filesystem to f2fs in recovery fstab
Add TWRP flags to disable screen blank to ensure touchscreen gets initialized on boot and screen wake works
Hi guys, i tried on mine and worked smoothly...the only thing I still cant do is writing in system folder...I tried multiple app as Root explorer but still can't manage to write anything even with root permission...
Any thoughts?
luiscaproducer said:
Hi guys, i tried on mine and worked smoothly...the only thing I still cant do is writing in system folder...I tried multiple app as Root explorer but still can't manage to write anything even with root permission...
Any thoughts?
Click to expand...
Click to collapse
That is normal for dynamic partitions. The full super partition can be written but not the individual block devices.
Thanks Captain! So basically I will have to wait for the official release of the TWRP? Or it will just never happen to have a super partition...Excuse the ignorance
luiscaproducer said:
Thanks Captain! So basically I will have to wait for the official release of the TWRP? Or it will just never happen to have a super partition...Excuse the ignorance
Click to expand...
Click to collapse
That is unrelated to TWRP being official or not, lol.
TWRP upstream will soon be updated to allow read/write of the system partition, but keep in mind that verity will need to be disabled for you to change any of the content, unless you don't want your device to boot .
--Cap
P.S. If you need to make modifications to system, you should use Magisk - it's made for this exact situation.
Captain_Throwback said:
There's a new release available today, which I recommend everyone switch to at their earliest convenience. I've also added a zip attachment to the first post that will allow you to flash a TWRP installed to your current slot to the opposite/inactive slot after an OTA is installed, so that you keep TWRP (otherwise it gets replaced by the OTA/firmware zip). The zip can be flashed either in Magisk Manager after the OTA completes installing (but BEFORE rebooting) or in TWRP after manually flashing a full firmware update zip (but PRIOR to rebooting). The zip simply duplicates the recovery from the existing recovery partition to the opposite slot, so it will only work if TWRP is currently installed to the active slot.
Change Log:
Set data filesystem to f2fs in recovery fstab
Add TWRP flags to disable screen blank to ensure touchscreen gets initialized on boot and screen wake works
Click to expand...
Click to collapse
Works perfect for me. Thank you
Update 20201001-02
Changelog:
- Add support for installing incremental OTAs (requires flashing/restoring stock boot and recovery images while in TWRP)
- Add all relevant partitions to dynamic partition list and improve display of Super partition in Backup screen
- Add asusfw, EFS, Modem, & Persist partitions as backup options (USE WITH CAUTION!!)
Captain_Throwback said:
Changelog:
- Add support for installing incremental OTAs (requires flashing/restoring stock boot and recovery images while in TWRP)
- Add all relevant partitions to dynamic partition list and improve display of Super partition in Backup screen
- Add asusfw, EFS, Modem, & Persist partitions as backup options (USE WITH CAUTION!!)
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------
Hi,
I would like to install TWRP. if I understood correctly you have to do this:
1. Unlock Bootloader
2. Install TWRP on both partitions.
3. Install TWRP_Flash_tpposite_Slot-CPTB.zip
4. Install Magisk.
Is it right?
And the correct procedure to update OTA? can you remove magisk and module before?
Thank you for your answers.
[email protected] said:
------------------------------------------------------------------------------------------------------------------------
Hi,
I would like to install TWRP. if I understood correctly you have to do this:
1. Unlock Bootloader
2. Install TWRP on both partitions.
3. Install TWRP_Flash_tpposite_Slot-CPTB.zip
4. Install Magisk.
Is it right?
And the correct procedure to update OTA? can you remove magisk and module before?
Thank you for your answers.
Click to expand...
Click to collapse
You don't need #3, as you're flashing TWRP to both slots in #2. That zip is for keeping TWRP after flashing a full firmware zip.
To update with an incremental OTA, you have to have the stock boot and recovery images from the current firmware available to be flashed in TWRP. You have to boot to TWRP and flash both stock boot and recovery, and then you can flash the incremental OTA. Then reboot to bootloader and flash TWRP, then reboot to recovery and flash Magisk for root.
Great and thanks Captain T.
Just a clarification, if i flash a full OTA (not incremental OTA) i don't need flash the stock boot, right?
[email protected] said:
Great and thanks Captain T.
Just a clarification, if i flash a full OTA (not incremental OTA) i don't need flash the stock boot, right?
Click to expand...
Click to collapse
Correct.
And then you need to flash the zip that flashes TWRP to the opposite slot so you keep TWRP once you reboot. You'll have to reboot back into TWRP and flash Magisk if you want to keep root.
Hi everyone
My phone model is xt2075-3,I want to root
Can I directly flash the latest magisk(20.4) to get root permission after unlocking BL?
I've succeeded in getting root.The steps are as follows
1.Download the twrp for your mobile phone,and magisk20.4.zip,magisk 7.5.1.apk
2.Visit Motorola official unlock website to unlock BL
3.You have 2 choice,A.boot on twrp one time;B.flash twrp;I choose A
4.Whatever your choose,in the twrp,install magisk zip,after done,reboot system
Enjoy root!
If you use the Magisk Manager to patch the boot image manually, and then flash that through fastboot - will that work also?
(My phone has yet to arrive so can't test this just yet...)
Update : i got the 8gb ram 128gb varient and i could boot into twrp from fastboot but i cannot flash replacing stock recovery nor i can see the internal or external memory due to decryption error
However, i basically unlocked boot loader and booted in fast boot then i flashed the patched boot.img ( installed magisk apk and added the stock boot.img inside the phone to patch it) then copy it back to pc and flashed it in fastboot mode and now i got root access
NOTE : if you happen to do something wrong you cannot use rescue and backup software to restore your phone to stock again ... flash stock boot.img in fastboot first so the software will recognize the phone back again
sniper9911 said:
Update : i got the 8gb ram 128gb varient and i could boot into twrp from fastboot but i cannot flash replacing stock recovery nor i can see the internal or external memory due to decryption error
However, i basically unlocked boot loader and booted in fast boot then i flashed the patched boot.img ( installed magisk apk and added the stock boot.img inside the phone to patch it) then copy it back to pc and flashed it in fastboot mode and now i got root access
NOTE : if you happen to do something wrong you cannot use rescue and backup software to restore your phone to stock again ... flash stock boot.img in fastboot first so the software will recognize the phone back again
Click to expand...
Click to collapse
where did you find the boot.img and the patched one?
Thanks
Mr.Krulez said:
where did you find the boot.img and the patched one?
Thanks
Click to expand...
Click to collapse
Get the full stock image by downloading rescue and smart assistant app from lenovo which supports moto phones ... Do login and get the fastboot rescue option while plugging your phone in the pc in fastboot mode .. then it will download it full firmware for your varient
Becareful that continue to flash the firmware will wipe your phone completely
After that get a copy of the boot.img file ... Copy it to the internal memory and install magisk manager apk from its official github site ... Now patch the boot.img you copied in your phone inside the magisk app then copy it back to your pc
Lear how to flash it from fastboot
Flash it
Done .. you are now rooted by patched boot.img with stock recovery !
Sent from my moto g 5G plus using Tapatalk
View attachment 5143479View attachment 5143477View attachment 5143481
Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery
Hi Guys,
my device is a/b device, bootloader unlocked, could you please kindly advise to flash twrp
what is the fastboot command, i use fastboot flash recovery twrp.img and i get a bootloop . the command fastboot boot twrp.img runs twrp onece and its fine, but how do i flash it please?
thanks and kind regards
emanuel said:
what is the fastboot command, i use fastboot flash recovery twrp.img and i get a bootloop . the command fastboot boot twrp.img runs twrp onece and its fine, but how do i flash it please?
Click to expand...
Click to collapse
I think the flash method fails because there is no partition called "recovery" - as an A/B device it looks like there are two:
Code:
nairo:/ $ ls -l /dev/block/by-name/ | grep recovery
lrwxrwxrwx 1 root root 16 1970-05-20 07:34 recovery_a -> /dev/block/sdd20
lrwxrwxrwx 1 root root 16 1970-05-20 07:34 recovery_b -> /dev/block/sdf20
if you have the Magisk zip file on the internal storage you can use the "fastboot boot twrp.img" method to flash it from there (for some reason TWRP can't see the SD card on my device)
Now for my question... my rooted (UK Retail) device has indicated that there is an OTA update:
I've tried using the method described here to restore the boot partition to stock so that it doesn't interfere with the process, but it fails (see attached images).
Does anyone know of a working method? I have downloaded the full (2+GB) update so am prepared to flash that (and restore everything else from backups) if necessary - but would rather not if it can be avoided...
{
"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"
}
xth88312 said:
I've succeeded in getting root.The steps are as follows
1.Download the twrp for your mobile phone,and magisk20.4.zip,magisk 7.5.1.apk
2.Visit Motorola official unlock website to unlock BL
3.You have 2 choice,A.boot on twrp one time;B.flash twrp;I choose A
4.Whatever your choose,in the twrp,install magisk zip,after done,reboot system
Enjoy root!
Click to expand...
Click to collapse
Hi @xth88312 ,
can you give the link you used to download TWRP for Moto XT2075-3?
I unlocked my phone through the official Motorola site:
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
I downloaded the latest Magisk and MagiskManager in the same directory from
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
I downloaded the original firmware from https://mirrors.lolinet.com/ and extracted the boot.img in the same directory, then issued, through the ADB connection:
Code:
adb install ./MagiskManager-*.apk
adb push ./boot.img /sdcard/Download/
(Replace the star as needed)
I opened MagiskManager app (you need to be connected to the Internet) and in the Magisk card I tapped Install > "Select and Patch a File". I browsed for and selected /sdcard/Download/boot.img and tapped "Let's go". A patched image /sdcard/Download/magisk_patched_*.img is created. Then, through the ADB connection, I issued:
Code:
adb pull /sdcard/Download/magisk_patched_*.img
adb reboot bootloader
fastboot devices
fastboot flash boot magisk_patched_*.img
fastboot reboot
At reboot, the phone was rooted.
boringtech said:
Hi @xth88312 ,
can you give the link you used to download TWRP for Moto XT2075-3?
Click to expand...
Click to collapse
[RECOVERY][UNOFFICIAL] TWRP 3.5.0.0
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
thats the link for twrp for moto g 5g plus..
use at own risk as i havent tried it myself so im not responsible for bricked devices etc...FLASH AT OWN RISK....
Mr.Krulez said:
Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery
Click to expand...
Click to collapse
Mr.Krulez said:
Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery
Click to expand...
Click to collapse
youll have to patch bo
Mr.Krulez said:
Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery
Click to expand...
Click to collapse
you need to
Mr.Krulez said:
Thank you for the answer but if I want to just root my phone I only need to flash magisk right? i don't need the patched boot.img?
sorry to bother you but the last phone I used supersu withouth flashing anything else than the recovery
Click to expand...
Click to collapse
youll need the patched boot.img to gain root, thats how ive had to root all my moto phones ive had, never been able to just flash supersu etc, someone will jump in if im wrong but as far as i know you need to patch the boot.img....
Remember everything you do is at your own risk i take no responsibility for.what you do with your device
{
"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"
}
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
FEATURES AND FIXES:
No need to reboot TWRP after flashing ROM, to flash gapps or any other zips. All zips you flash after a ROM will automatically go to the new slot.
No need to flash TWRP everytime after flashing a ROM. TWRP automatically flashes itself after a zip (Controllable via a toggle)
Supports Hentai OS encrypted devices
Supports flashing MIUI zips
Supports Vibration
Supports wiping data without wrecking encryption.
BUGS:
On encrypted devices, if u unmount and remount /data, it will show garbage files in storage. This is because of metadata encryption and to fix it, reboot recovery.
SUPPORTS AND TESTED ON:
Mi11x (aliothin)
UNSUPPORTED (BUT MAY WORK):
Poco F3, Redmi K40 (alioth)
FLASHING INSTRUCTIONS:
Boot into attached boot.img using the following command:
Code:
fastboot boot twrp-aliothin.img
Once booted, go to Advanced -> Press "Flash current booted TWRP"
KNOWN LIMITATIONS:
The following are some known limitations due to either the design nature of Virtual A/B or a problem with ROM themselves. Please read carefully :-
You cannot format data after flashing a ROM zip (Limitation of Virtual A/B). If you want to format, then reboot recovery after flashing ROM. Additionally, if you are encrypted, the newly flashed ROM must be able to decrypt your device. If not, then you have to format data before flashing the ROM It appears, you can actually format data after reboot even if the new ROM cannot decrypt.
You can flash only one ROM in one boot. If you wanna flash another ROM, you must boot to system once. This is again a limitation of Virtual A/B.
Once you have rebooted after flashing a ROM, you cannot write to the data partition until you boot successfully to the new ROM. Android seals the data partition after a ROM flash to prevent any accidental brick since the newly flashed ROM is actually stored in /data. Only data format is allowed in this case. Once you successfully boot to the new ROM, your storage becomes ready for writing again.
Ideally, after flashing a new ROM, you should only need to wipe your data rather than format. But, due to a problem in the device trees current ROMs are using, you will have to format data if you are currently on miui and want to switch to a custom ROM. Specifically, the roms need this commit and to set vendor security patch level to fix this issue. Switching between custom ROMs should not need format, except for hentai OS.
If you are currently on hentai OS, then before using TWRP, you must flash vendor_boot from the link provided in every hentai OS release. Otherwise, you will get black screen. This is only needed when you boot to TWRP for the first time. Do not repeat this step again. Also, do not try this with beta version of the ROM. Use it only with stable.
If you reboot to older slot after flashing new ROM, the new ROM will be cancelled and you will have to reflash again. This is because of how Virtual A/B works.
If you must flash magisk via recovery (it's not recommended now), please uncheck "Inject TWRP after install" else TWRP will remove magisk.
Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.
Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.
CREDITS:
@Nebrassy for original TWRP and device tree. I also repurposed some of his commits from gerrit.
SOURCE CODE:
Kernel (Prebuilt): https://github.com/ArrowOS-Devices/android_kernel_xiaomi_alioth
DOWNLOADS:
https://drive.google.com/file/d/1oY5WxfXYPRLumCcaPPFGuq9OhtB3CM_X/view?usp=sharing
MD5:- 0909f61c83ce9876843dabba5bf1247e
TELEGRAM GROUP LINKS:
https://t.me/PocoF3GlobalOfficial
https://t.me/pocoF3GlobalUpdates
Reserved
Reserved
ayy pro <3
Yay Yahoo
Thx for your work, dev.
Quick question. Why is it not recommended to install magisk via TWRP now?
UPD: Flashed Magisk successfully with unchecked "inject twrp..."
I have the same question, how should we flash magisk now? I'm old school so for me it was allways the best and fastest way...
vasishath said:
Great work.
Click to expand...
Click to collapse
blinoff82 said:
Thx for your work, dev.
Quick question. Why is it not recommended to install magisk via TWRP now?
UPD: Flashed Magisk successfully with unchecked "inject twrp..."
Click to expand...
Click to collapse
Twrp reflashes itself after every zip flash, hence it removes magisk, you can uncheck inject twrp option to flash tho.
@vasishath
Hello,
First of all thank you for developing a version of TWRP.
I have a little problem with this one: failed to mount: system_root, vendor, odm
Unable to find partition for path storage
I can't install TWRP ...
I'm on the weekly xiaomi.eu
Here are the issues I'm currently having with your version of TWRP.
Shadowk1ller said:
I have the same question, how should we flash magisk now? I'm old school so for me it was allways the best and fastest way...
Click to expand...
Click to collapse
Patch the boot.img using the Magisk App and then flash the patched boot.img via fastboot
Shadowk1ller said:
I have the same question, how should we flash magisk now? I'm old school so for me it was allways the best and fastest way...
Click to expand...
Click to collapse
John Wu recommands direct install from magisk app
vasishath said:
John Wu recommands direct install from magisk app
Click to expand...
Click to collapse
TWRP not installed after installing custom ROM. Please check.
deif102 said:
Patch the boot.img using the Magisk App and then flash the patched boot.img via fastboot
Click to expand...
Click to collapse
To much work, when i can simply flash it in twrp after i flash the rom, it was that easy in past times...
But can i uncheck inject before flashing and then check it again and flash current booted TWRP as in the beggining?
Which rom did u flash ?
blinoff82 said:
TWRP not installed after installing custom ROM. Please check
Click to expand...
Click to collapse
vasishath said:
Which rom did u flash ?
Click to expand...
Click to collapse
My own ROM - Syberia OS (AOSP).
(Maybe after flashing ROM I can install twrp.img in recovery ramdisk?)
blinoff82 said:
My own ROM - Syberia OS (AOSP).
(Maybe after flashing ROM I can install twrp.img in recovery ramdisk?)
Click to expand...
Click to collapse
He is referring to use controllable toggle so I assume you should have enabled it before flashing rom. I still didn't tried this twrp so dunno where actually this toggle is..
NE0HP said:
He is referring to use controllable toggle so I assume you should have enabled it before flashing rom. I still didn't tried this twrp so dunno where actually this toggle is..
Click to expand...
Click to collapse
Of course this toggle was turned on before flashing (by default).
blinoff82 said:
My own ROM - Syberia OS (AOSP).
(Maybe after flashing ROM I can install twrp.img in recovery ramdisk?)
Click to expand...
Click to collapse
It appears to me that the ramdisk-files.sha256sum file was removed after u flashed the ROM. That caused the TWRP flashing to fail. Does your ROM's zip modify the current running ramdisk in anyway ?
Will future Miui builds now be using this version of twrp? if this is the case i wont need to flash it right now.
decryptionData
Spoiler: Old version
1. After flashing the ROM, you must make sure to inject TWRP, or install twrp ramdisk, or fastboot boot twrp.img, the bottom line is that you need to reboot into the reboot and not start the system
2. Before flashing DFE.zip, you need to check if the system is RW, if you are sure that it is RW, you can skip this step 3-6
3. We go into TWRP in it we mount the vendor section
4. Next, go to the terminal and write, "mount -o rw, remount /vendor", press enter
5. If nothing is written after execution, then the section in RW skips the next step
Or you can flash the zip file, go to the backupFSTAB folder and compare the "original" and move_to_move, if the second one weighs less and it exists at all, then the patch worked (it is advisable to manually remove it, before flashing the DFE, for the sake of convenience for verification)
6. If the terminal issued an error "/ dev / block / dm-3 'is read-only" or something similar, original and move to move are the same, then proceed to instructions 6.1-.6.3
6.1. Download the systemrw archive
6.2. flash in twrp, wait for the end of the process (you need about 10-12 free GB in memory)
6.3. restart TWRP
6.4 in the /data/
local/tmp/
systemrw_version/files/img section there will be a file after weighing about 8 gigs, you can delete it, or write a review, I will write automatic deletion in the DFE script
7. You can flash DFE.zip, if you removed the encryption for the first time, then you need to do "format data", if you update the ROM, you need to repeat steps 1-7, when changing the ROM, it is advisable to do "wipe date"
p.s Works on official miui, xiaomi.eu, and custom, not all tested, I do not know about hentai, since TWRP is not put on it
Tested on DerpFest (30.07), Xiaomi.eu (21.7.28), SyberiaOS (30.07), Official MIUI EEA 12.5.3
An example of how to flash
I have simplified patching for the end user as much as possible at the moment.
Instructions for ROMs based on MIUI (TWRP)
1. Flash ROM_MIUI.zip
2. Flash DFE_BETA_2.zip. Follow the instructions sent to the TWRP display.
3. If you are encrypted, you need to do "Format data".
If you Decrypted and change the ROM, after flashing the new ROM, you need to flash the DFE again, you are also advised to do "Wipe Data".
If you are upgrading the ROM you need to flash the DFE again
Instructions for "sideload" type ROM (TWRP / Recovery adb - PC sideload - "adb sideload ROM.zip) Has a payload.bin file inside the .zip archive
1. Flash Custom_ROM.zip (with the "Inject recovery" checkbox, or after installation, do "install recovery ramdisk"
2. Reboot TWRP (in case of flashing through a PC, flash a temporary TWRP (Fastboot boot twrp.img)
3. Flash DFE_BETA_2.zip. Follow the instructions sent to the TWRP display.
4. If you are encrypted, you need to do "Format data".
If you Decrypted and change the ROM, after flashing the new ROM, you need to flash the DFE again, you are also advised to do "Wipe Data".
If you are upgrading the ROM you need to flash the DFE again
Instructions for "Fastboot" type ROM
1. Open update.bat in a text editor or equivalent for your Operating System. Or Flash_all_exept_storage in case of miui, delete the last line like "fastboot reboot"
2. Run update.bat or use the mi flash tool in the case of miui, after selecting it to flash everything except the storage. At the end of the process, it will also boot into the temporary TWRP
3. Flash DFE_BETA_2.zip. Follow the instructions sent to the TWRP display.
4. If you are encrypted, you need to do "Format data".
If you Decrypted and change the ROM, after flashing the new ROM, you need to flash the DFE again, you are also advised to do "Wipe Data".
If you are upgrading the ROM you need to flash the DFE again
thanks for the Super RW patch https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/
Telegram support group Disable force encryption(DFE) for Poco F3 (alioth)
MFP, DFЕ, RO2RW, for Android 10+
Update channel @mfpupdate
t.me
Download https://drive.google.com/folderview?id=18NrZhttbyF-dHjM3VdfZdcPVrkmTeT_l
{
"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"
}
sorry bro , the procedure is confusing , i ended up with stuck in splash screen , can you describe it properly?
lawong said:
sorry bro , the procedure is confusing , i ended up with stuck in splash screen , can you describe it properly?
Click to expand...
Click to collapse
I'll record a video later for clarity
LeeGarChat said:
I'll record a video later for clarity
Click to expand...
Click to collapse
thanks you sir!
lawong said:
thanks you sir!
Click to expand...
Click to collapse
Sorry for my bad english, using a translator
I updated the patch, now everything is convenient and simple
It doesnt work with oneos (miui) and ends up bootlooping to fastboot mode?
i23u8 said:
It doesnt work with oneos (miui) and ends up bootlooping to fastboot mode?
Click to expand...
Click to collapse
maybe i fixed it. try 2.4 version
LeeGarChat said:
maybe i fixed it. try 2.4 version
Click to expand...
Click to collapse
It worked! Im on the latest oneos with tertis kernel v2 and it works!
Hi @LeeGarChat I'm happy that you like my script. Please keep in mind that
NO UNAUTHORIZED , UNOFFICIAL REUPLOADS OF MY SYSTEMRW / SUPERRW FEAT. MAKERW FILES ARE ALLOWED!
Instead, you can simply put a link to the official SystemRW / SuperRW feat. MakeRW by lebigmac project page to both your video description as well as to first comment of this and your other 2 threads. Thank you.
Your installation error in your video can be avoided if /data is decrypted and mounted properly. Apparently some recoveries still have trouble doing that... This error doesn't happen if script is launched from within Android because /data partition is decrypted/mounted properly in Android.
Before running my SystemRW script you can check free space in /data partition using this command in terminal:
df -h
You need at least 10+ GB to run the script properly.
lebigmac said:
Hi. Please feel free to add a link to official SystemRW script's project page to both your video description as well as to first comment of this thread. Thank you.
Also that installation error can be avoided if /data is decrypted and mounted properly. Some recoveries still have trouble doing that.
This error doesn't happen if script is launched from within Android because /data partition is decrypted/mounted properly in Android.
Maybe in next version of script I should use this path as project path:
/data/systemrw_1.32b
What do you think?
You can check free space in /data partition using this command in terminal:
df -h
Click to expand...
Click to collapse
good idea. I'm just learning "bash" for now
LeeGarChat said:
decryptionData
Spoiler: Old version
1. After flashing the ROM, you must make sure to inject TWRP, or install twrp ramdisk, or fastboot boot twrp.img, the bottom line is that you need to reboot into the reboot and not start the system
2. Before flashing DFE.zip, you need to check if the system is RW, if you are sure that it is RW, you can skip this step 3-6
3. We go into TWRP in it we mount the vendor section
4. Next, go to the terminal and write, "mount -o rw, remount /vendor", press enter
5. If nothing is written after execution, then the section in RW skips the next step
Or you can flash the zip file, go to the backupFSTAB folder and compare the "original" and move_to_move, if the second one weighs less and it exists at all, then the patch worked (it is advisable to manually remove it, before flashing the DFE, for the sake of convenience for verification)
6. If the terminal issued an error "/ dev / block / dm-3 'is read-only" or something similar, original and move to move are the same, then proceed to instructions 6.1-.6.3
6.1. Download the systemrw archive
6.2. flash in twrp, wait for the end of the process (you need about 10-12 free GB in memory)
6.3. restart TWRP
6.4 in the /data/
local/tmp/
systemrw_version/files/img section there will be a file after weighing about 8 gigs, you can delete it, or write a review, I will write automatic deletion in the DFE script
7. You can flash DFE.zip, if you removed the encryption for the first time, then you need to do "format data", if you update the ROM, you need to repeat steps 1-7, when changing the ROM, it is advisable to do "wipe date"
p.s Works on official miui, xiaomi.eu, and custom, not all tested, I do not know about hentai, since TWRP is not put on it
Tested on DerpFest (30.07), Xiaomi.eu (21.7.28), SyberiaOS (30.07), Official MIUI EEA 12.5.3
An example of how to flash
I have simplified patching for the end user as much as possible at the moment.
Instructions for ROMs based on MIUI (TWRP)
1. Flash ROM_MIUI.zip
2. Flash DFE_BETA_2.zip. Follow the instructions sent to the TWRP display.
3. If you are encrypted, you need to do "Format data".
If you Decrypted and change the ROM, after flashing the new ROM, you need to flash the DFE again, you are also advised to do "Wipe Data".
If you are upgrading the ROM you need to flash the DFE again
Instructions for "sideload" type ROM (TWRP / Recovery adb - PC sideload - "adb sideload ROM.zip) Has a payload.bin file inside the .zip archive
1. Flash Custom_ROM.zip (with the "Inject recovery" checkbox, or after installation, do "install recovery ramdisk"
2. Reboot TWRP (in case of flashing through a PC, flash a temporary TWRP (Fastboot boot twrp.img)
3. Flash DFE_BETA_2.zip. Follow the instructions sent to the TWRP display.
4. If you are encrypted, you need to do "Format data".
If you Decrypted and change the ROM, after flashing the new ROM, you need to flash the DFE again, you are also advised to do "Wipe Data".
If you are upgrading the ROM you need to flash the DFE again
Instructions for "Fastboot" type ROM
1. Open update.bat in a text editor or equivalent for your Operating System. Or Flash_all_exept_storage in case of miui, delete the last line like "fastboot reboot"
2. Run update.bat or use the mi flash tool in the case of miui, after selecting it to flash everything except the storage. At the end of the process, it will also boot into the temporary TWRP
3. Flash DFE_BETA_2.zip. Follow the instructions sent to the TWRP display.
4. If you are encrypted, you need to do "Format data".
If you Decrypted and change the ROM, after flashing the new ROM, you need to flash the DFE again, you are also advised to do "Wipe Data".
If you are upgrading the ROM you need to flash the DFE again
thanks for the Super RW patch https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/
Download https://drive.google.com/folderview?id=18NrZhttbyF-dHjM3VdfZdcPVrkmTeT_l
View attachment 5381831
Click to expand...
Click to collapse
The new guide still need to flash RW Patch for first time ?
Jadugd said:
The new guide still need to flash RW Patch for first time ?
Click to expand...
Click to collapse
my DFE patch will tell you if you need to flash a separate SystemRW patch. in my patch there are commands to try to transfer memory to RW, but it does not always work. on the official miui does not work. need to flash systemRW, on xiaomi.eu my patch translates the system to RW
So far it works successfully in: oneos (with tertis v2 kernel), derpfest, syberia, spark, evo x, miui vn, miui vna.
It doesnt work with: arrow os
I am using twrp vishash (wont switch slots or boot using nebrassy)
i23u8 said:
It doesnt work with: arrow os
Click to expand...
Click to collapse
Copy error in TWRP, I will try to fix it
LeeGarChat said:
Copy error in TWRP, I will try to fix it
Click to expand...
Click to collapse
It actually flashes successfully in twrp and then just bootloops.
Btw, additional, works with mi-globe with stock kernel.
i23u8 said:
It actually flashes successfully in twrp and then just bootloops.
Btw, additional, works with mi-globe with stock kernel.
Click to expand...
Click to collapse
As for the Arrow ROM, it's strange that the file becomes zero size when copied. and I have not yet understood what it is connected with. conducted tests yesterday. in some conditions it is zero size, in some it normally copies. no idea at all yet what this is connected with. in the latest version 2.4b there is still no check for zero size files. I will rewrite it on the weekend, I hope I will fix the installation in the ROM arrow
Additional: works with mimix
new version 2.5
fixed work on ArrowOS
completely changed the logic of the script
now the script checks if fstab has gone to zero size
i23u8 said:
So far it works successfully in: oneos (with tertis v2 kernel), derpfest, syberia, spark, evo x, miui vn, miui vna.
It doesnt work with: arrow os
I am using twrp vishash (wont switch slots or boot using nebrassy)
Click to expand...
Click to collapse
LeeGarChat said:
new version 2.5
fixed work on ArrowOS
completely changed the logic of the script
now the script checks if fstab has gone to zero size
Click to expand...
Click to collapse
Omg awesome! Let me test it in 30 minutes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <not_my_phone.h>
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
TWRP 3.7.0_12.1 - Samsung Galaxy A32 4G
Current Status: Stable-ish
Supported Models:
SM-A325F: tested by @Long266 .
SM-A325M: tested by @Melky777 .
SM-A325N: not tested.
Bugs known so far:
TWRP cannot decrypt userdata if you set lockscreen. (one said it works, other it doesn't, so idk I'll just leave it here, YMMV)
Flashing anything shows many "unlock" red lines. (They are currently harmless by our knowledge).
USB-OTG
<!> There can be many more bugs unknown to me and testers. Report as soon as you face problem.
<!> PSA: I don't have the device to verify some of these bugs.
Download:
TWRP (3.7.0): https://github.com/almondnguyen/twr...a32-20230208/TWRP-3.7.0_12.1-a32-20230208.tar
Samsung USB Driver: https://developer.samsung.com/mobile/android-usb-driver.html
Odin (3.14.4): https://samfw.com/Odin/Samfw.com_Odin3_v3.14.4.zip
Disable VBMeta: https://forum.xda-developers.com/at...236537/?hash=f7249adaefe16f3aeac3256a63063f0a
(Optional) Root using Magisk: https://github.com/topjohnwu/Magisk/releases/
Install:
If you have TWRP or any custom recovery installed and bootable, you can upgrade instead; Look below.
<!> the installation will require WIPING DATA. You will also lose access to all Knox-based solutions like Secure Folder.
Backup every precious data you have on your phone.
<!> PC is required. Windows is preferred. (You probably know what you are doing when using Linux/Heimdall. We don't talk about Macs)
Unlock Bootloader:
Go to Settings > About Phone > About Software. Tap build number (10 times) until "you are now a developer" toast shows up.
Go back, go to Developer Settings.
Turn on OEM unlock toggle.
Turn off your phone, hold vol-up + vol-down, then plug in charging cable (please don't use 3rd-party charging-only cable, it must have data transfer capability).
Your device will boot into download mode with a warning. Accept it.
Hold volume-up until the phone shows the bootloader unlock panel "Unlock Bootloader?".
Press volume-up again. Now your phone bootloader is unlocked.
<!> It will now begin the process of wiping data. Let it do its job.
When it reboots to OS, finish setting up your device.
Double check to make sure OEM Unlock is still ON.
Preparing for the installation:
Download everything above onto your PC.
Install Samsung USB Driver.
Open Odin.
Connect your phone to your PC. There should be a COM entry on the top.
Make sure your phone is in Download Mode. (see step 4 of section Unlock Bootloader)
Make sure that OEM LOCK and REACTIVATION LOCK on your screen show "OFF". If it's not off, DO NOT PROCEED ANY FURTHER.
<!> For those with lock ON, use your device for 7 days without rebooting once. Then check the locks above again.
Installing:
Ensure phone is in Download mode.
In Odin:
Load in Userdata: VBMeta_disabler.tar file.
Load in AP: TWRP TAR file.
Prepare yourself. keep your hand on Volume-up and Power button (don't press yet).
In Odin, press Start. It will flash, then reboot. When the screen turned off, quickly press Vol-up and Power button to boot to recovery (this should take about 20~30 seconds).
<!> You should have TWRP up and running now.
Post-Installation:
MUST: Trigger Multi-disabler.
In TWRP, go to Advanced > Terminal.
Type multidisabler, then enter. If it fails with something about vendor free space, run it again.
Run multidisabler again.
Go to main screen. go to Wipe > Format Data, type yes then swipe.
Reboot to Recovery. Now you can do other stuff.
Should: Backup all vital partitions:
In TWRP, go to Backup
Backup: EFS, Modem, NVRAM.
Enjoy: Reboot your phone to have a rooted stock, install custom stuff or do whatever you want.
Upgrade:
<!> Use when you already have any custom recovery installed (TWRP, SHRP, Ofox and the likes)
Download the tar recovery image, then extract it to get recovery.img
Copy it to phone, then reboot to TWRP (Combo is Power + Volume-up)
Go: Install > Install image > select recovery.img file > select Recovery
Swipe to confirm flashing.
If success, reboot to recovery.
<!> You can also use Odin to upgrade, the steps similar to the Install section. All Post-installation, if already done, is unnecessary to do again.
GSI and related stuff:
GSI should be directly flashable now. Big credit to @Long266
Install TWRP, do all the instructions.
Download a GSI. Phh's is a good start.
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
If downloaded a compressed file (the extension is not .IMG; e.g: `gsi.img.gz` ), extract it to get an IMG file. Copy the IMG file to your phone.
Reboot into TWRP.
Tap Install > Install Image > Select your GSI .img file.
Select System Image, then flash.
If previously you were on stock, Wipe > Format data.
Reboot System.
Profit.
Source codes:
Kernel: https://github.com/long266/android_kernel_samsung_a32/tree/s
TWRP device: https://github.com/almondnguyen/twrp_device_samsung_a32/tree/twrp-12.1
Credits:
Devs involved in the making and maintaining of TWRP, twrpdtgen, Magisk and base software.
All the Testers.
@Long266 as tester, collab-dev.
@ianmacd for multidisabler.
@afaneh92 for a32x base tree and MTK-Samsung multidisabler.
@dronkit and @Mighty_Rearranger for Magisk-IMEI fix on MTK devices.
@klfld for GSI installation guide.
Older Release(s):
TWRP 3.6.2_12.1-20220703: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/tag/TWRP-3.6.2_12.1-a32-20220703
TWRP 3.6.2_12.1-20220528: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/twrp-3.6.2_12.1/
TWRP 3.6.1_11: https://github.com/almondnguyen/android_OTA/releases/TWRP-3.6.1_11-a32-B20220324
Footer Infos:
Status: Beta
Current Stable Version: 3.7.0_12.1
Created: 2022-03-24
Last Updated: 2022-07-03
chmod 550 /mnt/vendor/nvdata/md/NVRAM/NVD_IMEI must run on OS, not TWRP, since TWRP cannot mount /mnt
I can't install large IMG files to internal memory? For example a gsi?
Melky777 said:
I can't install large IMG files to internal memory? For example a gsi?
Click to expand...
Click to collapse
I should clarify that I don't own the device and all the testing was/is done by @Long266 .
These specific questions should be inquired to him instead (on his thread here: https://forum.xda-developers.com/t/...hawk-recovery-project-3-1-2021-03-24.4420469/ ).
Anyways, the bug that you are mentioning means that you can't flash images FROM internal SD card. GSI and image stuff should be flashable from other places like external SD or cache. Zip files are so far working as intended (as is they are flashable from anywhere).
To be fair, there could be flaws in his testing methodology and you should try it yourself.
Thanks Bro
I will owe the test of the A325M. I have no SD card at the moment.
Build 2022-03-25 changes:
Add backup entry for NVRAM, so in case Magisk messes up you still have a working copy intact.
Fix flashing image causing file size exceeded limit.
Updated TWRP Link, previously pointing to dead end.
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
can u send recovery.log ?
Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
just skip NULL errors
How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?
YellowSM said:
How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?
Click to expand...
Click to collapse
You can use the "install Image" under TWRP.
From the <!> For more info part, download .img file instead, copy it to your phone. Then go to TWRP > Install > Install Image > select TWRP img > select Recovery to flash.
If you've done, Post-installation steps are unnecessary to do again.
edit: upgrade section added to main post.
How to deactive KC Client and
Knox Enrollment Service?
Hi, I wanted to try a GSI with this, is it safe to try it? Thanks for developing this TWRP, I can help with testing too.
Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.
klfld said:
Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.
Click to expand...
Click to collapse
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22
Long266 said:
can u send recovery.log ?
Click to expand...
Click to collapse
On the same day I removed the twrp and blocked the bootloader.
Melky777 said:
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22
Click to expand...
Click to collapse
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
To flash the GSI you have to rename the .img file to system.img, put it in the same location than the zip and flash the zip. I have the scripts inside the zip to check if it didnt do anything weird and the source code seems safe, tried two GSIs today.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
For file transfer i'm using ADB with this tool, it's even faster than MTP somehow Python ADB File Explorer
EDIT: Uploaded vendor.img with the overlay for this device, ill push the changes to github later.
Download here: vendor.img
klfld said:
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
Click to expand...
Click to collapse
Very good job!!!
Makes a topic, I think I'm not the only one who wants to install a GSI.