Problem with twrp - LeEco Le Max 2 Questions & Answers

Hello good afternoon!
I recently upgraded the ROM to this:
https://forum.xda-developers.com/le-max-2/development/rom-project-xtended-shakeme-t3794392
It ran all as expected, however, when I boot into recovery mode, to install the magisk and do root, I noticed that the twrp does not work as normal and does not allow the installation of zip or img. I went to "Mount" and was without the mark on "... read only".
When I click on "install" the storage folder appears empty ...
https://forum.xda-developers.com/showpost.php?p=77374349&postcount=473
The twrp is version 3.1.1-0, I think it is outdated, I do not know if that will be the problem.
How can I solve this problem?
How can I update twrp?

Heyyo, the instructions for that ROM start with "Verify that you're using the latest version of TWRP."
Now there's only these methods you can use to update TWRP so it'll work:
First method:
1. Download latest TWRP on your PC https://dl.twrp.me/x2/
2. Reboot phone to bootloader (hold power and volume down until the phone reboots and you see the bootloader screen pop up and then release the buttons)
3. Plug in a USB cable from your PC to your phone
4. Hopefully you have fastboot on your PC, otherwise please check Le Max 2 or any Android guide for fastboot and ADB utilities.
5. fastboot flash recovery twrp-3.2.3-0.img
6. If it completes successfully? Reboot to recovery (hold down power and volume up buttons until the phone reboots and you see the word "recovery" on the screen)
Method two:
1. Download latest TWRP onto your phone
2. Using an OTG adapter and a USB flash drive, copy the TWRP image to your USB flash drive using the file manager or download one from the Play Store (I recommend Amaze File Manager since it's free and open source software and works great).
3. Reboot to recovery
4. Mount > USB-OTG
5. Install > tap "install image" button > tap "select storage" button and select USB-OTG > select twrp image > select to install it to recovery > swipe to install.
6. Reboot to recovery and it should reload latest TWRP.
Method three:
1. Wipe > tap "format data" button > type yes > tap checkbox.
2. Reboot to recovery
3. Use a PC to copy latest TWRP image to your phone and ROM and Magisk and Gapps as your data will be reformatted.
4. Install all of it and reboot to system
Also, Magisk must be installed immediately after the ROM for SafetyNet to function properly, so I recommend wiping Dalvik, system, cache and data and then install ROM, Magisk and Gapps at the same time and then reboot to system.

Thanks for the super complete help !!
I will see then!

Related

[Q] Question about swapping Roms

Hi,
I have the ATT One X+ with ViperXL+ installed on it and TWRP as my recovery. I rooted it using hasoon's toolkit and followed his stpes. Now I would like to switch to Elegancia, just to try it out. Would I do this by simply loading it onto my phone, going into TWRP, and selecting flash ROM? Or is there a longer set of steps to follow? Do I have to flash another boot.img? Additionally, do I have to reinstall all my apps and redownload all my music?
Thank you for answering
Hi Killfire,
Switching between ROM is not that hard, but as for your apps and data you will need a third application like Titanium Backup or My Backup to transfer all your personal stuff from one to another. If you don't have that much application and personal data to restore it's not hard to do it manually.
Yes you have to flash the correspondent boot.img to the ROM you selected. They practically all have something different, so do flash the one recommended in the changelog.
As for your music, that should be safe if you don't wipe your SD card, if your music was transfer from your computer as well.
If you want to change from ROM A to ROM B
Put the ROM you wanna try to your virtual SD card
Reboot in Recovery
Do a full backup of your actual (excluding cache and recovery)
!! The following instruction are with TWRP Recovery installed !!
Select Wipe menu, then select Factory reset (swipe), select System (swipe)
Go back to the Install menu and select it.
Locate your ROM.zip and select it.
Swipe to confirm.
Probably Aroma installer will start, simply follow the on-screen instructions and complete the installation.
Complete installation
Reboot in bootloader mode.
Make sure the FASTBOOT USB is highlighted.
Use the provided tool to flash the appropriate kernel. Or simply do it like this throught SDK/ADB
At the prompt type >fastboot flash boot insert_your_boot_image_name_here.img (Enter)
If Success is achieved, type again at the prompt >fastboot erase cache (Enter)
You now have a customized boot.img installed.
Unplug your USB cable and hit Power button one time.
Select Reboot with your Volume rocker.
Hit Power button one time.
Your phone should reboot.

Samsung logo bootloop after flashing twrp 3.3.1-0

i was flashing a twrp using odin and after flashing it it keeps putting me in an infinite bootloop unless i go into twrp or download mode
My phone is a Samsung s9+ SMG695F
1. Activate unlock OEM in developer
2. Flash twrp
3. Go directly to TWRP recovery (do not reboot to android)
4. Select yes
5. Backup EFS
6. Format data
7. Flash custom ROM
Alternative:
4. Select no
6. Root phone
7. Install dm verity
8. Boot android

[info] guide: root stock rom with encryption enabled

hi
this is simple guide to show how you can choose to have encypted or decrypted status with rooted device
all the files you can found in this forum easily
to have for encypted rooted stock rom do this step wise step
install stockrom ( fastboot flash recomended)
fool boot
setup rom
reboot to fastboot
(by button)
flash recovery peters(by pc)
boot to recovery (by button)
go to mount and mount vendor and system
now
select file andflash mount system first and then emediatly select magisk file
flash magisk (do not use add more zip)
reboot system
now your fone will show as encrypted satus
rooted but not encrypted status
install stockrom ( fastboot flash recomended)
fool boot
setup rom
reboot to fastboot
(by button)
flash recovery peters(by pc)
boot to recovery (by button)
flash dm variety
go to formate
type yes
then ok( this will delete your all internal storege)
reboot
to recovery
goto
flash magisk
(you have to copy file with pc in internal storage
if internal storage not show then reboot to fastboot then again reboot to recovery then copy file from pc to mobile now in recovery select file)
note fone will not show as encrypted satus
downloads

How To Guide How to upgrade your rooted device to latest update (GT2 Pro Global)

Hi, here I bring you a small tutorial for upgrading your rooted Realme GT 2 Pro Global Version to latest update (RMX3301_11_A17), as you may know I am not responsible of any damage and I recommend you to back up your data.
First, uninstall all your modules from magisk (technically you could just deactivate them, I prefer uninstall though). Make sure Zygisk is deactivated and turn off all the super user permissions of your apps before the update step. You should deactivate Automatic system updates under developer settings as well.
Here the steps:
1. Go to settings and download the OTA, you´ll get the 200 mb one. Since what we need is the full OTA package, once it's been downloaded when it starts to be extracted force stop the Software Update app in your settings.
2. After previous step go to your file manager (in this case I use Mixplorer, for this you will need the app with root access) and go to the next directory: root/data/ota_package/OTA/ [a folder that starts like .ota], inside you are going to delete the ota file with .zip extension. This first two steps are a way to speed up the process of getting the full OTA.
3. Go again to your software update section in settings, you will see a notification from the app software update app, touch on continue. After that you will see a message of error, and you will see a button that says "Try again", keep clicking on try again several times. You'll see then that full OTA update will start automatically (about 5 gb in size).
4. From here you will have to wait until the "Install" button appears (it'll take a while). Next, you click install.
5. After reboot, transfer the boot.img file attached on this post to your device. Magisk patch it and transfer back to your PC.
6. Open your adb terminal, type the command adb reboot bootloader
7. Test recognition by typing fastboot devices
8. Next type: fastboot boot whatevernameofyourpatchedfile.img (it has to be in the platform tools folder)
9. Your device will boot with a temporary root, check everything is working ok in your device. After that you will go to magisk app, click on install, and in the Method section select "Direct Install", and then Let's go.
10. After reboot you'll have you magisk rooted device updated and working. Now you can install back your modules again.
boot
This method can be done on the phone with root preservation directly via Magisk. No need to copy/patch boot.img files manually, as long as you have restored image in Magisk at least once. This is explained below.
Important notes:
Do not restart the device or select "Install" in the OTA updater until Magisk is reinstalled to inactive partition. Otherwise it will boot into stock ROM, and patched boot.img must be flashed via fastboot to restore root.
In addition, after installing to inactive partition in Magisk, do not press restart on Magisk's prompt.
The auto-update should be disabled, including the "Auto Download" setting. Otherwise, the updater will attempt to download and install while Magisk is present, and show "Extraction Failed" error, and "Try Again". If that happens, the system will only allow to download a 5GB update instead. To reset it, you can clear Software Updater app data and cache via some root app manager.
When selecting "Restore Images" in Magisk, if a message shows in Magisk "Stock boot image not found", then you need to generate backup stock boot.img on the phone. This is only done once, but you will need a stock boot.img of your current ROM version.
- Copy current ROM version stock boot.img to storage
- Open Magisk and select install -> Patch file -> Select the stock boot.img
- Restart phone.
This will generate Magisk "backup image" folder where it will keep the stock, non-patched boot.img.
This is only done once, on any future update the error will not show.
Click to expand...
Click to collapse
The 300mb OTA update steps:
1. Go to updater and it should show 300-600mb update available. DO NOT press "Download"!
2. Go to Magisk, select to restore image. Do not restart when prompted by Magisk. If you get error, read note on top.
3. Go back to updater and select "Download". It will first download then extract. When it finishes extracting, DO NOT press Install!
4. Go back to Magisk and select install to inactive partition. Once it's done, do not restart via Magisk! Close Magisk.
5. Go back to updater, and press "Install" button
Click to expand...
Click to collapse
Extra notes:
1. If you press Download before removing Magisk, it will fail extracting and show "Try Again". Do not press try again. Go to a root app manager, and clear Data and Cache of com.oplus.ota Software updater. Then repeat the process by restoring images in Magisk first.
2. If you did press "Try Again", it will only allow you to download a 5GB update. Steps are similar as long as you restore Magisk. You might be also able to clear data and cache like in step above to reset it back to smaller update, but I haven't tested this yet.
3. If you restart by Magisk prompt, it will soft-loop. You can hold Vol Up + Power until it boots into non-root partition. Go to updater and press install. It will boot to rooted partition.
4. If you pressed Install in updater before installing Magisk to inactive partition, it will boot to updated partition without root.
5. I have tested the update methods with simply Uninstall -> Restore Images, while I had Magisk modules such as BCR, Shamiko, USF, LSPosed Zygisk. It works fine without the need of removing each module.
Extra side note: Update file is downloaded to: /data/ota_package/OTA/.otaPackage/mymanifest(...).zip
What is need of this lengthly process. Just wait for OTA to show in update. Only full package will show for rooted user. Let it download, Extract and verify. Before Pressing install Button, Go to Magisk and Install on inactive slot. Then Go back to updater and install button.
Phone will reboot and updated. Magisk working, All modules intact.
shivrajsingh said:
What is need of this lengthly process. Just wait for OTA to show in update. Only full package will show for rooted user. Let it download, Extract and verify. Before Pressing install Button, Go to Magisk and Install on inactive slot. Then Go back to updater and install button.
Phone will reboot and updated. Magisk working, All modules intact.
Click to expand...
Click to collapse
I know what you mean, in fact thank you for telling me that procedure is working well on our device hahaha, since there's no proper flashing tool and no TWRP yet, the idea behind that lengthy process is trying to reduce the risks to minimum n.n
Just confirmed that this works for a 300mb (before restoring images) update file instead of the full 5GB (after restoring images), updated the guide above.
vanya.ag said:
boot
Click to expand...
Click to collapse
now my fingerprint is broken
Quake94 said:
Notes:
When Magisk is removed using Restore Images, the Realme OTA updater will show a full 5GB update. If the Magisk is not removed, the OTA will be around 300mb. Both update files will work OK, there is just small difference in steps. The important part is to not restart the device or select "Install" in the OTA updater until Magisk is reinstalled to inactive partition. Otherwise it will boot into stock ROM, and a patched boot would need to be flashed via fastboot to restore root.
Click to expand...
Click to collapse
i followed your steps
it was an 5gb OTA update i dovnloaded it and extract it then i go to magisk and install to inactive slot after reboot now im in stock recovery what now?
Terrorigel97 said:
i followed your steps
it was an 5gb OTA update i dovnloaded it and extract it then i go to magisk and install to inactive slot after reboot now im in stock recovery what now?
Click to expand...
Click to collapse
What what? You post in multiple threads. In one of them you want to lock bootloader and keep it stock, but here you say you installed Magisk after OTA. You also talk about stock recovery that has nothing to do with bootloader.
Help yourself and read up, all the information is widely available.
Quake94 said:
What what? You post in multiple threads. In one of them you want to lock bootloader and keep it stock, but here you say you installed Magisk after OTA. You also talk about stock recovery that has nothing to do with bootloader.
Help yourself and read up, all the information is widely available.
Click to expand...
Click to collapse
I never said i will be on stock lol I was just asking if you can lock your bootloader again...
Terrorigel97 said:
I never said i will be on stock lol I was just asking if you can lock your bootloader again...
Click to expand...
Click to collapse
Lock only on clean, stock rom as per guide in the other thread.
Can't lock on rooted, but rooted can be reversed to stock clean.
EDIT: resolved, see bottom note.
A.19 update screwed something up for me.
I restored image in Magisk, installed a full 5GB update, reinstalled Magisk to inactive slot. Reboot via Magisk.
Phone went to softloop. I held Volume Up and Power, and at some point it switched back to previous slot with A18, works fine except no root.
Restarted to fastboot. Fastboot works OK.
When attempting to restart to bootloader, some "mascot" icon appears and chinese writing, and quits back to fastboot.
Manually switched active partition via fastboot --set_active to try to boot the A19.
Phone still softloops, again, restarted back to previous slot with A18.
Fastboot indicates unlocked bootloader.
Not sure what got messed up, and why bootloader mode refuses to start.
Not a big issue, because my old A18 works ok, so for anyone else reading this that got a softloop, I recommend simply holding Volume Up and Power to switch to old slot, instead of attempting to reflash and screwing both partitions up.
Anyone else in a similar situation?
EDIT: LOL I fixed it . I went to software updater, and "Install" button was displayed.
Pressing install restarted the phone into A19 with Magisk installed......
Very interesting! Because rebooting via Magisk or the --set-active command in fastboot resulted in softloop! So the "Install" must be doing some extra steps.
TLDR; after OTA update and reinstalling Magisk to inactive slot, do not reboot via Magisk, but via OTA updater "Install" button! My guide above was updated.
I confirm you have to reboot via the installer and not via Magisk, since I had to manually flash boot.img multiple times in the past.
Quake94 said:
EDIT: resolved, see bottom note.
A.19 update screwed something up for me.
I restored image in Magisk, installed a full 5GB update, reinstalled Magisk to inactive slot. Reboot via Magisk.
Phone went to softloop. I held Volume Up and Power, and at some point it switched back to previous slot with A18, works fine except no root.
Restarted to fastboot. Fastboot works OK.
When attempting to restart to bootloader, some "mascot" icon appears and chinese writing, and quits back to fastboot.
Manually switched active partition via fastboot --set_active to try to boot the A19.
Phone still softloops, again, restarted back to previous slot with A18.
Fastboot indicates unlocked bootloader.
Not sure what got messed up, and why bootloader mode refuses to start.
Not a big issue, because my old A18 works ok, so for anyone else reading this that got a softloop, I recommend simply holding Volume Up and Power to switch to old slot, instead of attempting to reflash and screwing both partitions up.
Anyone else in a similar situation?
EDIT: LOL I fixed it . I went to software updater, and "Install" button was displayed.
Pressing install restarted the phone into A19 with Magisk installed......
Very interesting! Because rebooting via Magisk or the --set-active command in fastboot resulted in softloop! So the "Install" must be doing some extra steps.
TLDR; after OTA update and reinstalling Magisk to inactive slot, do not reboot via Magisk, but via OTA updater "Install" button! My guide above was updated.
Click to expand...
Click to collapse
This sounds like what my phone is doing but maybe I am confused because you mention fastboot and the bootloader as two different things. Just to be clear, "adb reboot bootloader" is what you are calling the bootloader and "adb reboot fastboot" which goes into fastbootd mode is what you are calling fastboot?
If so then my phone is doing the exact same thing, I can boot to fastbootd mode but when I attempt to "adb reboot bootloader" then just like you said a little mascot with Chinese writing appears for a split second then it reboots back to the system. Did you get your bootloader working again by doing the install?
GIutton said:
This sounds like what my phone is doing but maybe I am confused because you mention fastboot and the bootloader as two different things. Just to be clear, "adb reboot bootloader" is what you are calling the bootloader and "adb reboot fastboot" which goes into fastbootd mode is what you are calling fastboot?
If so then my phone is doing the exact same thing, I can boot to fastbootd mode but when I attempt to "adb reboot bootloader" then just like you said a little mascot with Chinese writing appears for a split second then it reboots back to the system. Did you get your bootloader working again by doing the install?
Click to expand...
Click to collapse
There are four modes:
bootloader - adb reboot bootloader
fastboot - adb reboot fastboot (or the key combo)
fastbootd - fastboot reboot fastboot (from being already in fastboot)
recovery - adb reboot recovery (or the key combo)
EDL - adb reboot edl / fastboot oem edl / short testpoints or modify boot entry
In my case the fastboot mode would start ok, just not the bootloader mode.
I didn't try fastbootd, but it would probably start ok.
I don't understand the fastbootd mode well though. I read somewhere that it is fastboot in Data partition.
I haven't tested rebooting to bootloader after fix, but can let you know.
EDIT: Booting to bootloader from fastboot (fastboot entered with key combo) gives me the mascot again, then it goes immediately back to fastboot. So I think I am in same position as you
Running "adb reboot fastboot" started "Fastbootd" mode (the one with wipe data/reboot/power off)
Running "fastboot reboot fastboot" from the "Fastbootd" would restart to "Fastbootd"
Running "fastboot reboot recovery" from the "Fastbootd" showed success, but 1. phone stayed in "Fastbootd" and 2. The phone deauthorized ADB (but still showed in device manager as "ossi" device)
Running "adb reboot bootloader" from System, showed the mascot and started the regular Fastboot.
Running "fastboot reboot fastboot" while the regular Fastboot was on, started "Fastbootd"
My suspicions are:
1. Regular fastboot mode is the one with green "START" on top. Somehow it is the same as bootloader. This is confirmed by Realme guide for unlocking/locking bootloader - they ask to use adb reboot bootloader, and then run a fastboot command.
2. "Adb reboot fastboot" starts the "userspace" fastboot called "fastbootd" which is isolated from bootloader and kernel.
This would mean the modes are:
bootloader/fastboot -> adb reboot bootloader (or the key combo)
fastbootd - adb reboot fastboot, or fastboot reboot fastboot (from being already in bootloader/fastboot)
recovery - adb reboot recovery (or the key combo)
EDL - adb reboot edl / fastboot oem edl / short testpoints or modify boot entry
So you can get into the start menu (fastboot/bootloader) by using the button combo but if you try fastboot reboot bootloader it shows a mascot with chinese letters then goes right back to the start menu and adb reboot bootloader shows the mascot and goes into the start menu as well? I think your phone is fine. . . fastboot and the bootloader should both be the start menu right or is there a difference?
For me I get the realme logo then a screen glitch and boots to the system when I try the button combo. When I try adb reboot bootloader I get a mascot with Chinese letters then a screen glitch then boots into the system.
Added some extra notes in my guide. If Auto download was enabled in About Device -> Software Update, the updater will display "Extraction Failed" since it attempts to download and extract update while Magisk is present. It also locks itself out of "Local install". The updater will download 5GB update instead on a retry, and 5GB method would be used.
With the Auto download disabled, user can Restore Images via Magisk and then download and install the update.
I will test this on the next update rollout.
Revised guide after C.12 to C.13 update and testing the smaller update method. The process is much more straightforward than I initially thought. No need for "Local update".

Question Custom recovery???

Hi, I wanted to know if there is currently a working custom recovery for Redmi note 11s, if so which one and how to proceed ... thanks
https://forum.xda-developers.com/t/root-poco-m4-pro-4g-fleur-using-magisk.4449193/post-87460153
When you on Android 11 its working like charme, but when you on Android 12/13 it doesnt work, because of the encryption problem. you cant mount data...
when you will install (you need a sdcard):
1. boot to fastboot
2. fastboot flash boot "twrp.img"
3. fastboot reboot (reboots to twrp)
4. put the stock-boot.img on your sdcard and flash it with twrp to boot -> select both partitions (a/b)
5. go to advanced -> flash twrp
6. format data
7. reboot to recovery and test if you can mount data
8. reboot and enjoy!

Categories

Resources