Related
Requirements:
1. Bootloader Must Be Unlocked.
2. Have a backup of your working Magisk Patched boot.img saved to your External SDcard.A little INFO:
The Sony L1 recovery seems to be disabled by SONY for some unknown and Probably stupid reason.
I have tried all ways to get the TWRP and Stock recovery to boot up from the fotakernel partition (recovery) but TWRP and even the stock recovery refuse to boot.
Anyway to cut a very long story short I am releasing this TWRP which is 95% functional and needs to be flashed to the boot partition
Working Method/flow:
Make sure you have a Back up of your working Boot.img "You know the one you used to root the device in the first place".
For ease of use You can use this app by XDA dev @wanam (Thread here) app on playstore Here You can also use this app to flash the v5-twrp-l1.img to your "boot" partition or you can go old skool and use dd (Via adb shell) or use the Magisk patched_boot.img you first rooted with..
Make SURE to Copy this working boot.img to your External SDcard.
When you require TWRP flash the downloaded TWRP to your boot partition using Fastboot (cmd's below) or the above app then reboot
You will now boot to TWRP.
Do what you need to do in TWRP.
IMPORTANT:
Remember Just before you leave TWRP go to INSTALL choose your external SDCard choose "image" from the install screen find your boot.img and select "boot" with the little radio button.
Once flashed choose reboot system.
Now when you boot you will be back to normal :good:
Things Not Working:
1. You will not be able to mount encrypted data therefore you would need to FORMAT your data and then leave it unencrypted.
SuperSU and Magisk will disable forceencrypt for you.
2. Does not Charge or show battery % so I don't know if it's actually charging. (Probably Qnovo battery module used by sony)
It will probably work on all variants but I am not able to test that.
It's use is for backups and restores wipes and installs for which it seems fully functional. :good:
Install Instructios.
Boot to the bootloader then
Code:
fastboot flash boot v5-twrp-l1.img
Then
Code:
fastboot reboot
Download HERE v5-twrp-l1.img
Hi @bigrammy!! I have it booting ok, obviously encryption is not working! I was able to do a backup but couldn't boot back into system, just keeps going back to twrp! I had to flashi the patched 3313 boot image from another post to get back into system! Good work though! Tested on g3311
Chronic2k13 said:
Hi @bigrammy!! I have it booting ok, obviously encryption is not working! I was able to do a backup but couldn't boot back into system, just keeps going back to twrp! I had to flashi the patched 3313 boot image from another post to get back into system! Good work though! Tested on g3311
Click to expand...
Click to collapse
:laugh:
Ok maybe I should update the OP as it seems it's not really clear enough that obviously the boot is replaced by the recovery.
Method would be make sure you have a Back up your working Boot.img You know the one you used to root the device in the first place.
You can also use dd (Via adb shell) or a app from the playstore or better still use the Magisk patched_boot.img .
Copy this working boot.img to your External SDcard.
When required flash the recovery to your boot partition using Fastboot then reboot
You will now boot to TWRP.
Do what you need to do in TWRP.
Then just before you leave TWRP go to INSTALL choose your external SDCard choose "image" from the install screen find your boot.img and select "boot" with the little radio button.
Once flashed choose reboot system.
Now when you boot you will be back to normal :good:
OP Updated let me know if it's clearer to understand now.
Thanks for reporting back. :good:
I'll give it a go! Many thanks! Just one question though. How do I enter recovery mode from then on? Is it still power down, power and volume down yeah?
Chronic2k13 said:
I'll give it a go! Many thanks! Just one question though. How do I enter recovery mode from then on? Is it still power down, power and volume down yeah?
Click to expand...
Click to collapse
I don't think you have really read or understood the OP
You are only ever flashing the "boot partition".
When you need to use TWRP you flash the TWRP.img to the boot partition and when your done you flash back your boot.img again to the boot partition as in the OP.
BTW Have you ever been able to enter the STOCK recovery using Power and Volume Down or using any commands
My phone could not enter the STOCK recovery at all let alone a custom one and since no one ever replied to my question about this I assumed this was the case for everyone as many sony devices from 7.0 had the recovery disabled?
I'm unable to get into stock recovery too!
So,
If we don't have a Recovery partition maybe we can
Create one...
Tutorial in here
https://iwf1.com/how-to-re-partitio...-all-options-included-change-size-fs-type-etc
I'll try it if i have time.
I tested twrp 2 times
Worked every time.
I've tried to install superSu.zip via twrp, looked all right, rebooted the phone and now it's in bootloop for over 2 hours...
It's getting hotter... i ca't turn it off
The only thing that works is keeping Power and Volume Up pressed and it looks restarting...
What can i do to revive it safely?
alegatorul said:
I tested twrp 2 times
Worked every time.
I've tried to install superSu.zip via twrp, looked all right, rebooted the phone and now it's in bootloop for over 2 hours...
It's getting hotter... i ca't turn it off
The only thing that works is keeping Power and Volume Up pressed and it looks restarting...
What can i do to revive it safely?
Click to expand...
Click to collapse
Mate you really need to be careful unless you really know what your doing
You will likely brick the phone if you continue to blindly mess with re-partitioning and the like.
If you were in TWRP which was flashed to the boot partition as directed in the OP then flashing the supersu.zip will simply modify your TWRP.img not your boot.img since TWRP is living in the boot partition at the time you run the .zip hence your looping.
This device has bootloader issues since it will not allow the booting of another partition except "boot" recovery, fotakernel, rdimage, all tested all failed to boot the TWRP recovery and stock recovery.
There is another method used by some sony devices but this will need to be heavily modified for this MediaTek SoC and will require a lot of study and script re-writes.
Spending all this time on a device that's pretty much obsolete before it was launched since it's not planned to receive oreo and Sony 90% locked down the bootloader is kinda futile so use the phone for what it is then throw it in the bin when done in a year or two.
Mate, you are right
Hi, please make recovery for L1 G3312 i hope you can do it.
tweak8 said:
Hi, please make recovery for L1 G3312 i hope you can do it.
Click to expand...
Click to collapse
I think this one may very well work for the dual SIM also so please try it and then report back with some actual details.
eg: bootloader status, firmware version, your region, etc etc.
Thanks.
Works great on the G3113 model, thank you for developing this! Now hoping to find a custom rom to install via .zip.
This "HERE v5-twrp-l1.img" is working in my Xperia L1 G3312.
But, after installing TWRP, phone does not get into boot normally. Everytime it boots into recovery mode. I think that it needs separate twrp partition. This twrp is overwriting the main boot. If anyone can make separate partition for TWRP recovery. This problem will be solved.
Hello. I ignored all your post like a retard and basically just went to the last step to flash the image. The twrp works but it wouldn't boot into normal mode but just boot to twrp everytime so I downloaded some random boot image I saw online and installed it. Now it's just stuck in the sony logo and won't even turn off. Is there anything I can do or is it rip for good?
dumb person said:
Hello. I ignored all your post like a retard and basically just went to the last step to flash the image. The twrp works but it wouldn't boot into normal mode but just boot to twrp everytime so I downloaded some random boot image I saw online and installed it. Now it's just stuck in the sony logo and won't even turn off. Is there anything I can do or is it rip for good?
Click to expand...
Click to collapse
No it's only the boot.img Flash the boot.img in this thread https://forum.xda-developers.com/xperia-l1/how-to/root-l1-g3313-magisk-t3693350 if you can get into fastboot that is.
If not then use FlashTool to flash the stock boot.sin and system.sin only. That should get you working again.
This "HERE v5-twrp-l1.img" is working in my Xperia L1 G3312.
But, after installing TWRP, phone does not get into boot normally. Everytime it boots into recovery mode. I think that it needs separate twrp partition. This twrp is overwriting the main boot. If anyone can make separate partition for TWRP recovery. This problem will be solved.
In twrp mode, I can do everything smoothly..... but phone does not get into boot normally..... After installing stock boot again, phone boot into normally, but twrp has gone completely..... So, it is clear that boot & twrp partition overwrites each other due to no separate partition.... So, we need separate partition for boot & twrp.... then everything will be solved...
bigrammy said:
No it's only the boot.img Flash the boot.img in this thread https://forum.xda-developers.com/xperia-l1/how-to/root-l1-g3313-magisk-t3693350 if you can get into fastboot that is.
If not then use FlashTool to flash the stock boot.sin and system.sin only. That should get you working again.
Click to expand...
Click to collapse
I downloaded the boot from the link you posted and flashed it. Now it phone works again. Many thanks!!
riadjblicd said:
This "HERE v5-twrp-l1.img" is working in my Xperia L1 G3312.
But, after installing TWRP, phone does not get into boot normally. Everytime it boots into recovery mode. I think that it needs separate twrp partition. This twrp is overwriting the main boot. If anyone can make separate partition for TWRP recovery. This problem will be solved.
In twrp mode, I can do everything smoothly..... but phone does not get into boot normally..... After installing stock boot again, phone boot into normally, but twrp has gone completely..... So, it is clear that boot & twrp partition overwrites each other due to no separate partition.... So, we need separate partition for boot & twrp.... then everything will be solved...
Click to expand...
Click to collapse
Yes but Sony Disabled the recovery partition (fotakernel) by design so you can not boot from it.
The OP is clear about the need to flash the TWRP to your boot partition and the reason I also give full instruction in the workflow/method but people simply don't read anymore it seems. :crying:
TWRP can be injected into the boot.img so you can boot normally or boot TWRP using the volume keys at boot time but I can't be bothered working on this since Sony are not going to update the Android Version.
While the phone is OK I have far better phones to spend my time on at the moment.
how to backup boot.img without root? if its impossible then how do i root this phone?
This TWRP recovery is compiled from source & not official yet
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.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Prerequisites
1. Unlocked bootloader.
Bugs
1. No bugs
2. If you have found a bug, please consider posting it to my GitHub Issues.
Instructions
1. Go to the fastboot mode.
2. Download the recovery.img and transfer it to the adb folder.
3. Open the cmd/terminal and change directory into the adb folder.
4. Now confirm/check that device is connected by typing:-
Code:
fastboot devices
If you got your device seriel number there then you are ready to continue otherwise try connecting device again and make sure USB debugging is on and you have granted permission to the PC to debug.
5. After that we will flash this TWRP recovery to the recovery partition by below command:-
Code:
fastboot flash recovery twrp-name.img
BooM ! TWRP flashed successfully.
6. Now unplug your device and then hold power button untill the phone turned off,after that press power button while holding vol down(-) button simultaneously and you will boot into TWRP recovery mode.
Enjoy !
Downloads
Official TWRP Website : https://twrp.me/umidigi/onemax.html
GitHub Release : Here (release name : TWRP-UMIDIGI-One_Max)
Version Information
ROM OS Version: 8.1.x Oreo
Source Code: Device Tree
Based On: TWRP
Credits
Omni Team for minimal TWRP source
@chankruze (myself) for device tree and compilation.
SUPPORT
Official Telegram Group
Official Telegram Channel
Hey ! Good job ! I tried building my own TWRP today but then noticed someone already did it ! Does encryption work ? I cant seem to decrypt the partition after flashing your TWRP.
EDIT : Couldn't wait, ended up formatting with encryption disabled via a zip + magisk
I've then proceeded to flash some GSI for Android 9 (even tried Q Beta 3) and if we want 9.0 one day, some heavy work will be needed : Cellular doesn't work; other than that, it all seems fine to me, camera is only 12mpx, front is 13mpx. Haven't tested more, i'm back to stock
EDIT 2: After comparing camera from stock and gsi, GSI wins easily. The camera is not as slow as stock.
Are there any decent ROMs yet for this phone? LineageOS would be fantastic.
@kgoerbig not to my knowledge. Maybe I'll try porting a 9.0 GSI soon.
I'm not sure if this is helpful or not, but Umidigi posts stock ROM on there forum. Can ROMs be ported based on there code? Or is it more complicated then that?
https://community.umidigi.com/m/?a=viewthread&tid=18692
_cab13_ said:
Hey ! Good job ! I tried building my own TWRP today but then noticed someone already did it ! Does encryption work ? I cant seem to decrypt the partition after flashing your TWRP.
EDIT : Couldn't wait, ended up formatting with encryption disabled via a zip + magisk
I've then proceeded to flash some GSI for Android 9 (even tried Q Beta 3) and if we want 9.0 one day, some heavy work will be needed : Cellular doesn't work; other than that, it all seems fine to me, camera is only 12mpx, front is 13mpx. Haven't tested more, i'm back to stock
EDIT 2: After comparing camera from stock and gsi, GSI wins easily. The camera is not as slow as stock.
Click to expand...
Click to collapse
I have tested LineageOS 16.0 GSI Android 9.0 (and many others ...) and it works well, even GSM and Camera.
The only thing I cannot have is a complete root : I install Magisk 19.3 correctly, but applications cannot get root permission (Titanium Backup cannot have su permission)
Hi to all!!!
I've unlocked bootloader, flashed twrp in post but when I power Off and On+Vol - my device doesn't power up...
Also if I make fastboot reboot recovery, my device reboot in fastboot mode again...
What's wrong??? I would test Descendant_ThreeDotZero_arm64_aonly rom!!!!
Pls Help me!!!!
silviuss82 said:
Hi to all!!!
I've unlocked bootloader, flashed twrp in post but when I power Off and On+Vol - my device doesn't power up...
Also if I make fastboot reboot recovery, my device reboot in fastboot mode again...
What's wrong??? I would test Descendant_ThreeDotZero_arm64_aonly rom!!!!
Pls Help me!!!!
Click to expand...
Click to collapse
If you use the stock boot.img with an GSI system image, it will not boot, you must first flash Magisk.zip before reboot!
It will disable dm-verity, and you can boot after.
If it continue reboot in bootloader mode, use spflashtool to flash a stock rom and all will be right
Or if you have a TWRP backup, restore all partitions except boot/recovery/cache/system/data and you can boot
@ dreambo Can you make a writeup of properly unlocking the bootloader/rooting? Or did you use these methods?
https://community.umidigi.com/forum.php?mod=viewthread&tid=17376
https://www.youtube.com/watch?v=xM_M5XP--Z8&t=176s
I should be receiving my Umidigi One Max in a day or so, and do not want to bork anything up! I have SPflash installed both on a Win10 laptop, and on a Ubuntu Linux machine.
dreambo said:
If you use the stock boot.img with an GSI system image, it will not boot, you must first flash Magisk.zip before reboot!
It will disable dm-verity, and you can boot after.
If it continue reboot in bootloader mode, use spflashtool to flash a stock rom and all will be right
Or if you have a TWRP backup, restore all partitions except boot/recovery/cache/system/data and you can boot
Click to expand...
Click to collapse
kgoerbig said:
@ dreambo Can you make a writeup of properly unlocking the bootloader/rooting? Or did you use these methods?
https://community.umidigi.com/forum.php?mod=viewthread&tid=17376
https://www.youtube.com/watch?v=xM_M5XP--Z8&t=176s
I should be receiving my Umidigi One Max in a day or so, and do not want to bork anything up! I have SPflash installed both on a Win10 laptop, and on a Ubuntu Linux machine.
Click to expand...
Click to collapse
You do not need to unlock you phone, mine is rooted with Magisk and have TWRP installed without unlock bootloader.
Just use spflashtool to flash a stock rom, but replace the recovery by TWRP and the boot.img by magisk_patched.img one.
Here how I do exactly:
1- in my running stock rom, I install MagiskManager and install Magisk by choosing the last option (patch existing boot.img)
2- give it your stock boot.img (extracted from stock rom) and it create for you /sdcard/Download/magisk_patched.img
3- use this to replace your stock boot.img and use also TWRP.img to replace stock recovery.img and flash the whole rom with SPFlashTool
Can you backup with TWRP with a locked bootloader? Isn't write access blocked with a locked bootloader?
dreambo said:
You do not need to unlock you phone, mine is rooted with Magisk and have TWRP installed without unlock bootloader.
Just use spflashtool to flash a stock rom, but replace the recovery by TWRP and the boot.img by magisk_patched.img one.
Here how I do exactly:
1- in my running stock rom, I install MagiskManager and install Magisk by choosing the last option (patch existing boot.img)
2- give it your stock boot.img (extracted from stock rom) and it create for you /sdcard/Download/magisk_patched.img
3- use this to replace your stock boot.img and use also TWRP.img to replace stock recovery.img and flash the whole rom with SPFlashTool
Click to expand...
Click to collapse
kgoerbig said:
Can you backup with TWRP with a locked bootloader? Isn't write access blocked with a locked bootloader?
Click to expand...
Click to collapse
If you can run the TWRP with a locked bootloader (and you can in case of umidigi one max) you can do any thing
dreambo said:
If you can run the TWRP with a locked bootloader (and you can in case of umidigi one max) you can do any thing
Click to expand...
Click to collapse
One last question. =)
Which boot file from stock did you use to patch with?
Downloadable from: https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
UMIDIGI One Max V1.0
or
UMIDIGI One Max E V1.0
kgoerbig said:
One last question. =)
Which boot file from stock did you use to patch with?
Downloadable from: https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
UMIDIGI One Max V1.0
or
UMIDIGI One Max E V1.0
Click to expand...
Click to collapse
I have used the European one, UMIDIGI One Max E V1.0
So I just received my One Max today. I was able to patch the boot image, and root the phone. I also, installed TWRP, but I'm running into an issue. From TWRP, I formatted with a normal wipe, It asked "Do you want to do this, it wipes data encryption Etc". I typed yes, and it did it's thing. Rebooted. Setup my basic settings on the phone. I rebooted back into TWRP, and it immediatly asked for a "decryption" password. It also won't allow me to mount internal partitions or sdcard. This even after I rooted via a patched boot file, and verified root access while booted in android (with root verify app). What am I doing wrong for TWRP to gain access to storage?
"Couldn't wait, ended up formatting with encryption disabled via a zip + magisk"
How did you format without encryption? I try to format from TWRP, type 'yes' , to verify, and encryption is still active. I'd like to disable encryption, so that I can properly backup everything from TWRP.
kgoerbig said:
So I just received my One Max today. I was able to patch the boot image, and root the phone. I also, installed TWRP, but I'm running into an issue. From TWRP, I formatted with a normal wipe, It asked "Do you want to do this, it wipes data encryption Etc". I typed yes, and it did it's thing. Rebooted. Setup my basic settings on the phone. I rebooted back into TWRP, and it immediatly asked for a "decryption" password. It also won't allow me to mount internal partitions or sdcard. This even after I rooted via a patched boot file, and verified root access while booted in android (with root verify app). What am I doing wrong for TWRP to gain access to storage?
Click to expand...
Click to collapse
Search in xda forum a zip that you can flash with TWRP before installing the Magisk zip from TWRP.
its name is disable_dm_verity????.zip, it disable in the boot.img the encryption.
After that format the data partition (format and not wipe, it's important!) and reboot normally, and your data partition will not be encrypted
dreambo said:
Search in xda forum a zip that you can flash with TWRP before installing the Magisk zip from TWRP.
its name is disable_dm_verity????.zip, it disable in the boot.img the encryption.
After that format the data partition (format and not wipe, it's important!) and reboot normally, and your data partition will not be encrypted
Click to expand...
Click to collapse
I eventually found all the correct files to remove encryption. I also installed AOSP. I'm kind of torn between the stock and AOSP. AOSP has better performance, but one annoying aspect is that I cannot find anywhere in the settings to switch the navigation buttons in AOSP (Back button is on the far left, I like it on the right side). Seems trivial, but it's annoying. I can now fully backup & restore in TWRP, which makes life a lot easier.
kgoerbig said:
I eventually found all the correct files to remove encryption. I also installed AOSP. I'm kind of torn between the stock and AOSP. AOSP has better performance, but one annoying aspect is that I cannot find anywhere in the settings to switch the navigation buttons in AOSP (Back button is on the far left, I like it on the right side). Seems trivial, but it's annoying. I can now fully backup & restore in TWRP, which makes life a lot easier.
Click to expand...
Click to collapse
Which AOSP ? where do you found it ?
dreambo said:
Which AOSP ? where do you found it ?
Click to expand...
Click to collapse
This thread:
https://forum.xda-developers.com/android/development/umidigi-one-max-custom-rom-modding-t3942521
This Rom
https://github.com/phhusson/treble_experimentations/releases
Do a complete backup of stock from TWRP onto microsd or USB first! System, data, modem, nvram partitions etc. That way you can restore from TWRP, and not lose os, data, or nvram (IMEI).
Specifically, system-arm64-aonly-gapps-su.img.xz
1. Download and extract file you downloaded, onto your phone.
2. Do a format (type yes)
3. Install from TWRP as "image".
Folks,
I wish to update to MIUI 12 but I also want to have ROOT and Magisk functionality.
Is it the same process as before where we:
1) fastboot boot recovery.img (this is twrp)
2) then flash Magisk?
has anyone achieved Root and Magisk functionality on MIUI 12 on Mi Mix 2S ?
I flashed MIUI 12 using fastboot then Magisk using Orange Fox and everything was fine. So the process is the same. I used Magisk v21.
dawidcx3 said:
I flashed MIUI 12 using fastboot then Magisk using Orange Fox and everything was fine. So the process is the same. I used Magisk v21.
Click to expand...
Click to collapse
Thanks bro,
Yea I flashed it the old TWRP/Magisk method and it works.
Placing my personal step by step instructions here in case anyone needs it. You can use Orange Fox in place of TWRP. Your choice.
Get latest Magisk Zip (Magisk-v21.0+) https://github.com/topjohnwu/Magisk/releases/
Copy Magisk-v21.0.zip to Phone Storage
Get latest TWRP (twrp-3.4.0-0-polaris+) https://dl.twrp.me/polaris/
Copy twrp-3.4.0-0-polaris.img to Phone Storage
Rename twrp-3.4.0-0-polaris.img to recovery.img (on local PC)
Go to bootloader mode (Power & Vol - )
CMD the following command: fastboot boot recovery.img
after starting TWRP on the phone flash twrp-3.4.0-0-polaris.img file again in TWRP by clicking Install then Select Image then Recovery Partition.
and after this, do not restart
flash Magisk-v21.0.zip
restart
and TWRP remains and you have root.
Regards..
Hi, I don't know if i have to start a new post but i have a inherent problem. I'm trying to install recovery, I've tried twrp and orange via fastboot. I successfully install both, but if i leave them and i reboot to system, next boot make my recovery disappear.... What i'm wrong?
Both at start aks me if i want to keep read only, but i swipe for allow modifications, i can do backups, install zip, Anything (i think, I've not tried this, but it seems fully working), no errors during flash and in recovery LOG also.... Dunno what to do
25agosto said:
Hi, I don't know if i have to start a new post but i have a inherent problem. I'm trying to install recovery, I've tried twrp and orange via fastboot. I successfully install both, but if i leave them and i reboot to system, next boot make my recovery disappear.... What i'm wrong?
Both at start aks me if i want to keep read only, but i swipe for allow modifications, i can do backups, install zip, Anything (i think, I've not tried this, but it seems fully working), no errors during flash and in recovery LOG also.... Dunno what to do
Click to expand...
Click to collapse
Stock rom has software that checks recovery and replaces it with stock if it detects changes. After you flash recovery in fastboot make sure you power off. Then boot to recovery with button combo and flash the recovery zip (orange fox). After flash it should reboot and automatically edit files to stop stock recovery install.
Is Google Pay working with rooted mi mix 2s?
howpathetic said:
Is Google Pay working with rooted mi mix 2s?
Click to expand...
Click to collapse
Yes it does. You have to use "hide magisk" option.
So i tried updating my phone and rerooting but as soon as i flashed the patched image something got corrupted and its only been pain now for the last few hours. Ive been super irresponsible in not backing up my phone away from the phone so I would rather not lose everything by flashing the factory image so anything and everything helps. for context it booted into 11 fine but as soon as I touched fastboot and the latest .img files is when stuff started going south.
edit: fixed the issue another way but an answer for that question would be nice to finally have on the internet.
I'm not very clear about what you did... The regular Magisk OTA process is:
1. Uninstall Magisk.
2. Install the OTA (do not reboot).
3. Install Magisk (after OTA).
The more involved process I've used (when the Magisk backup isn't valid) is:
1. Fastboot flash the vanilla boot.
2. Fastboot boot the patched boot.
3. Install the OTA (do not reboot).
4. Install Magisk (after OTA).
If you are doing a fastboot flash or boot you need to make sure the image you are using exactly matches your system. Which is especially important for the initial install. If you boot the wrong image, rebooting will fix it. If you flash the wrong image you have to flash the right image to fix it. That's why Magisk install has you fastboot boot and install from Magisk manager, less chance of a permanent issue
If you were going from Android 10 to 11 with Magisk 20, that will be a problem.
To answer the question in the title... You cannot access user data from fastboot. But you can probably fastboot boot TWRP and use that to access your data. I've done that before, but not on this phone.
Unfortunately the only build of TWRP that anyone has posted is unable to boot on Android 11 and I've not seen any other serious effort.
Assuming you were working entirely with stock ROMs, my best recovery from an unbootable state has been to reflash the stock boot.img, then boot into recovery, and apply over ADB the full downloadable OTA zip. No data wipe occurs.
I just tried to boot TWRP and it didn't work. Odd because it shouldn't depend on anything on the device... Looks like the bootloader is rejecting it
"Error verifying the received boot.img: Invalid Parameter"
a1291762 said:
I just tried to boot TWRP and it didn't work. Odd because it shouldn't depend on anything on the device... Looks like the bootloader is rejecting it
"Error verifying the received boot.img: Invalid Parameter"
Click to expand...
Click to collapse
It does depend on what's on the device because recovery is no longer its own partition. It's part of the kernel (boot.img). This unofficial TWRP was built against Android 10. And the entire partition layout changes around with the upgrade from 10-11. So it is just not valid and won't boot.
cmstlist said:
Assuming you were working entirely with stock ROMs, my best recovery from an unbootable state has been to reflash the stock boot.img, then boot into recovery, and apply over ADB the full downloadable OTA zip. No data wipe occurs.
Click to expand...
Click to collapse
I tried to access adb in stock recovery, and it didnt work. I made a new hread specific to it here.
Cant get ADB in recovery mode, but works in live mode, and so does fastboot
On my Rooted Pixel 4a, I can use: Fastboot - I flashed the latest update firmware as well as the rooted boot image ADB Over WiFi - This is the most comnon way I connect for ADB ADB While the Android OS is running What I cannoit get woirking is...
forum.xda-developers.com
Can you see what I a doing differently or have missed that made it work for you?
on a side note...
cmstlist said:
Unfortunately the only build of TWRP that anyone has posted is unable to boot on Android 11 and I've not seen any other serious effort.
Click to expand...
Click to collapse
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
DiamondJohn said:
...snip...
on a side note...
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
Click to expand...
Click to collapse
just came across this post, which may help explain why TWRP is problematic for our device. But the thread did hint about running twrp from fastboot. (Post by cmstlist)
TWRP 3.7.0-12 for Sunfish[Testing]
[RECOVERY] TWRP 3.7.0-12 - TeamWin Recovery Project 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...
forum.xda-developers.com
DiamondJohn said:
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
Click to expand...
Click to collapse
As a software developer that's been doing embedded Linux for 20 years, it saddens me that I haven't got past app development for Android
I'd love to help get TWRP going for the Pixel 4a but probably I'd get nowhere. I can certainly test TWRP builds though. My Pixel 4a is my daily driver but it's unlocked and rooted and I've got a solid off-device backup so I'm relatively fearless with hacking
DiamondJohn said:
I tried to access adb in stock recovery, and it didnt work. I made a new hread specific to it here.
Click to expand...
Click to collapse
I was not saying you can execute arbitrary ADB commands in stock recovery. However if you have a full OTA zip and can get into stock recovery, you can choose the option on-device to flash an update over ADB according to Google's instructions. This will only work with a signed official OTA zip. But if you happen to have corrupted your stock ROM to an unbootable state, it is a possible path to get it back to bootable so you can access the contents.
Just so that everyone is aware because no one here seems to be aware of anything...
TWRP version twrp-3.6.1_11-0-redfin.img from here: https://dl.twrp.me/redfin/
Works just fine if you just temp boot from fastboot with the most recent OTA SPA2A.220405.003
And you DO NOT HAVE TO INSTALL A KERNEL FOR IT TO WORK, THIS BUILD ONLY
With this build, you can indeed backup and restore your system. I have used this build since it was live, and it works no problem.
I cannot confirm it works with any other build, nor can I confirm you can install it to ramdisk and get it to work.
But it works just fine with temp booting from fastboot. Backup, Restore, etc works just fine for me. I have gone back and forth from my build to the OTA no problem whatsoever, and have been able to restore all userdata from the most recent OTA.
BIG THANKS TO TWRP, AND bigbiff for his work
and, btw, you have to reboot anywhere from 1 to 3 times after a restore for it to completely boot.
You'll see the old boot logo first and it will freeze, then the new boot logo and it could freeze, then the third time it boots just fine. They even have this listed on TWRP's site I believe.
So, if you're having trouble after a restore, just reboot a few times but wait until it hangs before you do. It will eventually come up.
Also, it is possible to install this same recovery to your boot.img ramdisk. You cannot flash this image directly or else you will end up in a boot loop.
In order to install permanently to the ramdisk, you have to disable verity and verification just like for root, then temp boot the twrp.img, then while in recovery adb push twrp.img /
Then go to install, and choose the twrp.img and it will ramdisk install it. Then wipe all userdata--must be done, no way around it.
Reboot to recovery, and backup the boot.img only. Then copy the boot.emmc.win to somewhere on your internal SD card as twrpboot.img.Then you need to boot into the system, install magisk app, and then patch twrpboot.img, then reboot to bootloader and flash the patched boot.
After all of that you will have both a rooted boot.img with permanent recovery in the ramdisk.
I do not know anything about safety net as I don't use any kind of banking apps at all so that will be your own responsibility to deal with.
That's so good to finally hear, looks like I'm going to have to do this. Thanks for the update, off topic but considering making a guide with as many links to projects, roms, kernels, etc that are being made or in process specifically for our phone and differentiating a11 and a12 support
stayboogy_Officially said:
Then copy the boot.emmc.win to somewhere on your internal SD card as twrpboot.img.Then you need to boot into the system, install magisk app, and then patch twrpboot.img
Click to expand...
Click to collapse
This worked for me. I have Magisk and TWRP installed on stock Android 12.1 version 220305.
I was worried because I did not actively Disable Verity or Verification , or unencrypt anything.
But I am able to make full backups, and restore them, which is what i care about
I updated to Android build SP2A.220505.002 (via TWRP 3.6.2, magisk 24.3, and the May 2022 ota update file).
No problems yet..
has anyone updated to Android13 ?