Related
It appears my A100 decided that it wanted to nearly 100% brick itself last night.
I'm stuck with only recovery at the moment and it is reporting that /dev/block/mmcblk0p4 and /dev/block/mmcblk0p8 are not found. I've tried plugging it into usb while in recovery to see about using ADB shell to recover the partitions but I cannot seem to get the USB drivers to recognize the device.
Anyone have ideas on what I can do as a next step?
Thanks to pio_maski and linuxsociety for helping us all out. For those just joining the thread:
pio_masaki said:
For everyone having the missing partitions error in this thread, once it starts its done, it began when the first freeze occurred.
At this point you have 2 choices, neither is fun and both involve Acer.
1 send it now and get charged for repair, they'll know its modded.
2 try to trigger fail safe and just plug it in, turn it on and let it sit and try to boot into android. After a set amount of failed /system or /boot reads it'll go into fail safe mode. Sending it under warranty in this state will have it repaired at no code aside from shipping to Acer.
You'll know fail safe is happening when you turn it on, blue or orange light comes on but the screen is off and there is no vibration on power on.
Both ways:
Get onto the Acer site and start a chat with a rep, tell them what happened. They'll ask you to hard reset after verifying warranty is still in effect time wise. After it fails this, they'll give you the info on sending it in. For me it took 10 days to get it back from sending it out.
Edit: for anyone that can still boot but hangs up, recovery may still be possible but its a very small window.
Click to expand...
Click to collapse
linuxsociety said:
If you have the brick, then there isn't any options left except to send it in to Acer for repair. They won't say anything about your ROMS/Kernels, however you need to find out if the stock bootloader needs to be re-flashed, and this will pretty much lock them out of recovery and everything when you do. They'll just end up replacing the board in the tablet and sending it back. I'm not 100% sure if anyone has sent their tablet in to acer with the a200 bootloader still intact and received their repaired tablet without a hassle, really that's the main thing you may want to check into.
Click to expand...
Click to collapse
I had the same thing happen to me last night.
Curious to know if you all were using stock kernels or a custom one? if custom which one?
linuxsociety said:
Curious to know if you all were using stock kernels or a custom one? if custom which one?
Click to expand...
Click to collapse
I believe mine was a stock kernel. I was using an unlocked boot loader, clockwork recovery 5.5.0.4 (I believe) and CM9 from 2012/07/08. Unfortunately that is about all the information I can provide. I was unable to use adb with CWR so I couldn't pull up more information on the nature of the problem. I ended up sending it back to Acer for warranty and got it back not 24 hours ago.
kemonine96 said:
I believe mine was a stock kernel. I was using an unlocked boot loader, clockwork recovery 5.5.0.4 (I believe) and CM9 from 2012/07/08. Unfortunately that is about all the information I can provide. I was unable to use adb with CWR so I couldn't pull up more information on the nature of the problem. I ended up sending it back to Acer for warranty and got it back not 24 hours ago.
Click to expand...
Click to collapse
The reason I asked was because I have been working on custom kernels and recoveries for the A100 to help in preventing this from happening, so I just wonder if anyone has had the mmc brick bug to occur while using one of my kernels in combination with my twrp recovery that also has userland mmc brick bug prevention patches.
linuxsociety said:
The reason I asked was because I have been working on custom kernels and recoveries for the A100 to help in preventing this from happening, so I just wonder if anyone has had the mmc brick bug to occur while using one of my kernels in combination with my twrp recovery that also has userland mmc brick bug prevention patches.
Click to expand...
Click to collapse
What causes the bug? Is it something preventable in terms of software run? I just got my A100 back from warranty and would prefer it not die in the same spectacular fashion again...
I actually just finished unlocking the bootloader, flashing CWR 5.5.0.4 and re-installing CM9. Would prefer not to do this dance again.
kemonine96 said:
What causes the bug? Is it something preventable in terms of software run? I just got my A100 back from warranty and would prefer it not die in the same spectacular fashion again...
I actually just finished unlocking the bootloader, flashing CWR 5.5.0.4 and re-installing CM9. Would prefer not to do this dance again.
Click to expand...
Click to collapse
The exact cause is unknown, however we do know that parts of the information the GPT partition table contains is wiped. There is no exact cause that we are aware of yet.
I wonder why so many people choose to use CWR over twrp? It would make sense to use CWR on devices that don't have TWRP support, but this one does and has for a while. I've never figured that out as the interface is much more trickier and when I have used it in the past i just seem to easily accidentally do the wrong thing with it. I dunno I guess people get accustomed to using one product and just never switch to something else.
linuxsociety said:
The exact cause is unknown, however we do know that parts of the information the GPT partition table contains is wiped. There is no exact cause that we are aware of yet.
Click to expand...
Click to collapse
Do the more recent recoveries include a good way to re-write the GPT partition table via an adb shell? Seems like if you can re-write the GPT partition table you'd be able to recover the device from mostly dead. Also, does the bug affect data stored on the various partitions? If so, are there images of the various partitions floating around?
linuxsociety said:
I wonder why so many people choose to use CWR over twrp? It would make sense to use CWR on devices that don't have TWRP support, but this one does and has for a while. I've never figured that out as the interface is much more trickier and when I have used it in the past i just seem to easily accidentally do the wrong thing with it. I dunno I guess people get accustomed to using one product and just never switch to something else.
Click to expand...
Click to collapse
Speaking for myself, I find that I can mash the hardware keys more efficiently via muscle memory than touch about a touch screen. Probably my old graybeard keyboard ways shining through...
I considered moving over to TWRP but the last I looked the information was a little lean (~1-2 months ago now probably). I planned on looking closer at it once the JB port is further along for the A100. Figured I'd jump to TWRP when I jump over to JB. I am aware the CM9 versions for the A100 are a bit out of date and I'm working on a build to address that (running repo sync while I'm at work).
kemonine96 said:
What causes the bug? Is it something preventable in terms of software run? I just got my A100 back from warranty and would prefer it not die in the same spectacular fashion again...
I actually just finished unlocking the bootloader, flashing CWR 5.5.0.4 and re-installing CM9. Would prefer not to do this dance again.
Click to expand...
Click to collapse
At this point its an unknown trigger, however the research on it shows Samsung and kindle fire devices with the same emmc we have are prone to the same issue.
As it stands now Linux society has patched the issue for Samsung devices in his kernel for Android and his kernel for twrp, its about the best protection we have at this time. While I may not agree to the trigger with him, its still a step taken against it that may well prove to be what prevents future bricks. Better safe then sorry kind of thing and I would suggest his recovery and kernel for this reason. Plus his kernel has a lot of extra goodies to play with
It works with all existing roms from ICS to JB, stock or modified or CM.
Tapatalked from my Galaxy S II.
pio_masaki said:
At this point its an unknown trigger, however the research on it shows Samsung and kindle fire devices with the same emmc we have are prone to the same issue.
As it stands now Linux society has patched the issue for Samsung devices in his kernel for Android and his kernel for twrp, its about the best protection we have at this time. While I may not agree to the trigger with him, its still a step taken against it that may well prove to be what prevents future bricks. Better safe then sorry kind of thing and I would suggest his recovery and kernel for this reason. Plus his kernel has a lot of extra goodies to play with
It works with all existing roms from ICS to JB, stock or modified or CM.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
You just had to sweeten the deal.... I will definitely add this higher on my ToDo list than I planned. I really don't want to go through the hassles of another warranty.
If it helps right before my device's GPT table died, I saw a massive CPU spike that caused my device to get quite warm. 2 or 3 hard power-offs and power cycles later my device was going out for warranty. After each boot before it went dead the CPU spike problem was still present and the device wouldn't even unlock from the lockscreen.
kemonine96 said:
You just had to sweeten the deal.... I will definitely add this higher on my ToDo list than I planned. I really don't want to go through the hassles of another warranty.
If it helps right before my device's GPT table died, I saw a massive CPU spike that caused my device to get quite warm. 2 or 3 hard power-offs and power cycles later my device was going out for warranty. After each boot before it went dead the CPU spike problem was still present and the device wouldn't even unlock from the lockscreen.
Click to expand...
Click to collapse
That is actually different from normal for emmc bricks, though makes sense too. If the file system is corrupt or missing then it would hog CPU time trying to find the data or fix the damage, if it even could.
Tapatalked from my Galaxy S II.
i think my a100 died just now for the same reason. i was running cm10 preview with 1.5 custom kernel for JB. Is there a way to restore the tablet? any help?
icomar said:
i think my a100 died just now for the same reason. i was running cm10 preview with 1.5 custom kernel for JB. Is there a way to restore the tablet? any help?
Click to expand...
Click to collapse
You need to give more details about what exactly your tablet is doing and what all was you doing when this happened? Can you still get to recovery? When you try to boot does it ever show boot animation? After turning the tablet on does the distorted Acer image still appear? Can you get adb connection at regular boot? Recovery adb? If you can get to recovery can you please give us your recovery.log file also? Thanks
Sent from my A100 using Tapatalk 2
linuxsociety said:
You need to give more details about what exactly your tablet is doing and what all was you doing when this happened? Can you still get to recovery? When you try to boot does it ever show boot animation? After turning the tablet on does the distorted Acer image still appear? Can you get adb connection at regular boot? Recovery adb? If you can get to recovery can you please give us your recovery.log file also? Thanks
Sent from my A100 using Tapatalk 2
Click to expand...
Click to collapse
you are right, so:
1) my tablet was charging, i unlocked it, it freezed. So i pressed the reset button under the tablet. Then it showed boot animation for ever.
2) i can access recovery (clockworkmod recovery) so i flashed cm9 instead of cm10, but the result is always the same, stuck on bootanimation after the distorted acer image that appears. Sometimes the tablet finishes boot, say "upgrading android" but never finishes.
I will try with adb later at home, and if you can tell me how to take the recovery.log i will provide it.
In this case what can i do?
icomar said:
you are right, so:
1) my tablet was charging, i unlocked it, it freezed. So i pressed the reset button under the tablet. Then it showed boot animation for ever.
2) i can access recovery (clockworkmod recovery) so i flashed cm9 instead of cm10, but the result is always the same, stuck on bootanimation after the distorted acer image that appears. Sometimes the tablet finishes boot, say "upgrading android" but never finishes.
I will try with adb later at home, and if you can tell me how to take the recovery.log i will provide it.
In this case what can i do?
Click to expand...
Click to collapse
That's not a brick. backup your apps with titanium backup, reboot wipe data, cache, dalvik, and system. Install your rom, gapps, kernel, etc.. Boot to android and install titanium backup, restore apps + data (only user apps not system!)
Sent from my A100 using Tapatalk 2
hello there, i did what you said (except for the titanium backup thing, i dont care about apps) that is the procedure to flash roms. after flashing the recovery freezed after saying "install completed" so i had to reboot manually the tablet from the power button.
still rom does not work (now the boot animation does not even show up).
PLUS if i try to wipe again the recovery says what you see in the attachment.
It is worse than before, am i right?
linuxsociety said:
That's not a brick. backup your apps with titanium backup, reboot wipe data, cache, dalvik, and system. Install your rom, gapps, kernel, etc.. Boot to android and install titanium backup, restore apps + data (only user apps not system!)
Sent from my A100 using Tapatalk 2
Click to expand...
Click to collapse
He's bricking. If he wipes cache then he will finish the job.
Edit: never mind I didn't see his update.
Tapatalked from my Galaxy S II.
pio_masaki said:
He's bricking. If he wipes cache then he will finish the job.
Edit: never mind I didn't see his update.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
now what? too late?
icomar said:
hello there, i did what you said (except for the titanium backup thing, i dont care about apps) that is the procedure to flash roms. after flashing the recovery freezed after saying "install completed" so i had to reboot manually the tablet from the power button.
still rom does not work (now the boot animation does not even show up).
PLUS if i try to wipe again the recovery says what you see in the attachment.
It is worse than before, am i right?
Click to expand...
Click to collapse
Well it definitely doesn't look good now. So the boot animation was appearing before you tried to do all the wipes and install from CWM? I just wanted to verify that this DID in fact take place while booted into recovery. You may want to discuss this with pio_masaki since he had a brick happen to him recently, and he is quiet knowledgeable with the procedures to try to recover from lost partitions or to verify that you are indeed bricked (lost GPT partition info ) .
stock rom
my tablet(a100)is doing much the same, its stock except for crosix swap-mod ,i plug into pc(win 7) and it says apx not installed..last nite it locked up while reading,..and well..i rebooted it and all i saw was the android..
As topic says, is there a custom recovery available for R819 ?
I found TWRP for Chinese R819T version, but is it compatible also with the R819 ?
samusalo said:
As topic says, is there a custom recovery available for R819 ?
I found TWRP for Chinese R819T version, but is it compatible also with the R819 ?
Click to expand...
Click to collapse
Not yet. Dees_Troy is working on it now, he got an R819 a day or two ago. (Edit: oops, he doesn't have his yet, he was just working with someone else.)
I just got mine earlier today. Right now I am trying to get a complete return-to-stock package from Oppo. Yeah, I could extract everything and eventually build one myself, but it's SO much easier when the manufacturer provides it for you. Unfortunately it's the weekend and the Oppo guys are in a complete different timezone than I am. I think that was the main reason Dees_Troy is halted too - Trying to boot the image using "fastboot boot" doesn't work, and he's (understandably) nervous about flashing a recovery when he doesn't have a return-to-stock image.
Edit: FYI, motochopper works for rooting. It's a royal pain to get it working with this device on Windows machines, but on Linux, you only need to get ADB running by adding 0x22d9 to ~/.android/adb_usb.ini
Entropy512 said:
Not yet. Dees_Troy is working on it now, he got an R819 a day or two ago. (Edit: oops, he doesn't have his yet, he was just working with someone else.)
I just got mine earlier today. Right now I am trying to get a complete return-to-stock package from Oppo. Yeah, I could extract everything and eventually build one myself, but it's SO much easier when the manufacturer provides it for you. Unfortunately it's the weekend and the Oppo guys are in a complete different timezone than I am. I think that was the main reason Dees_Troy is halted too - Trying to boot the image using "fastboot boot" doesn't work, and he's (understandably) nervous about flashing a recovery when he doesn't have a return-to-stock image.
Edit: FYI, motochopper works for rooting. It's a royal pain to get it working with this device on Windows machines, but on Linux, you only need to get ADB running by adding 0x22d9 to ~/.android/adb_usb.ini
Click to expand...
Click to collapse
What about Kernel SOurces and Other Trees ?
GuneetAtwal said:
What about Kernel SOurces and Other Trees ?
Click to expand...
Click to collapse
https://github.com/oppo-source/R819-Kernel-Source-4.2
MediaTek's kernel build system gives me a headache... It's a mess. Also, there are some nasty licensing conflicts between various files there. It's better than no source at all, but there are some issues a few of us are in contact with Oppo to resolve. (Oppo has been EXTREMELY cooperative so far.)
The biggest problem is that right now fastboot won't allow you to flash or boot any kernel images, whether normal boot or recovery. This means that if you hose up a device by flashing a bad recovery or kernel, you've got a brick. Supposedly Oppo is also working on fixing this too.
I successfully wrote a test TWRP image that Dees_Troy provided me, but I'm not going to make it public for the following reasons:
1) MTK's dumchar driver used to read/write kernel and recovery partitions does not do any size enforcement. Backing up a kernel in recovery will result in a 4GB backup image at the moment... I've figured out how to fix the driver, however:
2) Being unable to recover from bricks using fastboot means that this thing is extremely dangerous
3) The fstab is probably still not right for the device
The biggest blocker is 2) above - once that's resolved it should be a matter of only a few days.
Edit: I was partially wrong. It's not possible to flash recovery from fastboot, but you can flash replacement boot images.
Entropy512 said:
https://github.com/oppo-source/R819-Kernel-Source-4.2
MediaTek's kernel build system gives me a headache... It's a mess. Also, there are some nasty licensing conflicts between various files there. It's better than no source at all, but there are some issues a few of us are in contact with Oppo to resolve. (Oppo has been EXTREMELY cooperative so far.)
The biggest problem is that right now fastboot won't allow you to flash or boot any kernel images, whether normal boot or recovery. This means that if you hose up a device by flashing a bad recovery or kernel, you've got a brick. Supposedly Oppo is also working on fixing this too.
I successfully wrote a test TWRP image that Dees_Troy provided me, but I'm not going to make it public for the following reasons:
1) MTK's dumchar driver used to read/write kernel and recovery partitions does not do any size enforcement. Backing up a kernel in recovery will result in a 4GB backup image at the moment... I've figured out how to fix the driver, however:
2) Being unable to recover from bricks using fastboot means that this thing is extremely dangerous
3) The fstab is probably still not right for the device
The biggest blocker is 2) above - once that's resolved it should be a matter of only a few days.
Edit: I was partially wrong. It's not possible to flash recovery from fastboot, but you can flash replacement boot images.
Click to expand...
Click to collapse
WEll it is same as Xperia C's Source and other Leaked Source :/ i Don't know why Mediatek don't make a Simple Filesystem like that of Nvidea and Qualcomm
i think it comes with cwm right,thats what a developer told me:fingers-crossed:
Zpik said:
i think it comes with cwm right,thats what a developer told me:fingers-crossed:
Click to expand...
Click to collapse
No, it does not. Stock Android "3e" recovery.
There's a TWRP image nearly ready, but who knows when it will be fully ready for public consumption. I won't be working on it (or anything else) at all this week for various reasons.
Not tested on nougat.
I use adb and fastboot , twrp, supersu.
Files We need:
TWRP: It's bogus, in my phone the screen flips upsidedown: Connect a mouse thru female usb or try to figure out how to tap in a rotated screen with a non rotated touch panel.
TWRP Download -> https://drive.google.com/file/d/0B0XMYw0cbs_cdm5FZW1DQXl4MFU/view
SuperSU file - > https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
For ADB access thru MAC:
1.- First of all we have to get open USB debug mode to get adb acces to the phone by going to Settings -> About -> Software Information -> Tap 7 times over Build number.
2.- After we get Developer options available we have to put the phone on usb debugging by goig to "Settings-> Developer Options" Activate USB Debugging.
3.- Install android platform-tools on your PC/Linux/MAC , in my case had work on MAC and no devices acces thru ADB on PC :silly: .
platform-tools -> http://www.androidpolice.com/2017/0...ble-without-full-sdk-android-studio-download/
Here you have the 3 options to download ADB and FASTBOOT
4.- Connect your phone to the PC (USB) and copy SuperSu to the root of your phone, a place that its easy too acces, cause TWRP, for the moment flips the screen.
5.- Copy TWRP3.0.XXX.zip to the folder where you have platform-tools installed.
6.- Reboot your phone to bootloader and in Linux could work too:
./adb reboot bootloader [./ is placed cause I don't put platform-tools on the my PATH]
After the boot, then we have to boot on TWRP
./fastboot boot twrp-3.0xxxx.zip (you don't flash anything) If you want to flash TWRP, at your awn risk, ./fastboot flash recovery twrp-3.0xxxx.zip".
Well, now you have to see TRWP on your phone screen.
My recomendation is to play a little bit with the flipped screen if you don't have a female USB to plug a mouse.
7.- Trying to make a complete backup of the phone could be a good practice to move on TWRP with the flipped screen . Tap backup option and make a Backup. Always recomended!
8.- After Backup, you can go to INSTALL SuperSU.zip file. "Install -> look for your SuperSU.zip file "
9.- Go to Playstore and install supersu app.
Now you can test your root, after reboot for example tryin to install some APP that requires root. Fast move:
./adb shell
su root
It has to appear a screen to grant root access to the phone.
10. Done!
Well I think thats my second post at all, hope can help someone to root the phone.
I placed In Questions and Answers cause XDA says want to protect us from SPAM.
Feel free to correct me anything.
Kronen_75
Your links do not work.
jnmacd said:
Your links do not work.
Click to expand...
Click to collapse
Links are corrected. Thanks!
You can also substitute Magisk instead of Supersu if you need to use any of the pay apps or have root sensitive apps...
Without the right Twrp, many benefits to rooting are missing such as removing stock rom applications. Seems without being able to boot to a recovery, even Titanium cannot remove apps because it needs to clean the dalvic.. Can't do it without a recovery
Sent from my ASUS_Z016D using XDA-Developers Legacy app
Download the right twrp here: https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
You should change your title !!
Tested on nougat.
The variant ZS550KL can be rooted with same method on latest firmware with nougat
Very nice guide, Thank you. Could you please provide updated links to both TWRP and SuperSU. I am currently using TWRP 3.1.1-0 and it functions properly after hanging for approximately 45 seconds on boot. This may be due to the fact my phone is encrypted. I initially rooted without installing TWRP (fastboot boot twrp.img) but have since flashed it. Both ways work well. The posted version of SuperSU did result in root but caused me to lose cell service! The phone could "see" the sim card but not use it. Updating to SuperSU 2.82 solved that issue. This was all done on my finally rooted ZenFone 3 Deluxe Special Edition (Z016D)!!!
I unfortunately figured something out the other day. Using TWRP 3.1.1-0 I am able to install zip files, complete wipes, make & restore backups. The issues only arise after you restore your nandroid image. Everything works except for two things.
1. The ability to hear audio during phone calls. The phone is actually able to place calls but you are unable to hear or record any phone audio. Oddly enough I was able to play music and use voice dictation. It was only in-call audio that seemed to be affected.
2. If you have a pin set when you create your nandroid image your pin will no longer work once restored. You will be locked out of your own phone!!
Fortunately both are fairly easily resolved and keep TWRP relatively useful, although a bit bothersome!
To resolve the pin issue it is necessary to use the TWRP file manager or ADB to delete 5 files (listed below) and regain entrance to your phone. Once deleted simply reboot the phone and reset your pin. If you remove your pin before creating a backup this issue is averted completely.
/data/system/gatekeeper.pattern.key
/data/system/gatekeeper.password.key
/data/system/locksettings.db
/data/system/locksettings.db-wal
/data/system/locksettings.db-shm
To re-enable call audio use TWRP (install zip) to reflash the same version firmware from the Asus website over your current install without wiping. This will restore any system apps you may have removed but you should still have root and can easily remove them again. There will be two errors when performing the flash, which is why I believe root is retained but the system image will be reflashed. Reboot and enjoy
I sincerely hope I have not caused anyone any issues! Or that someone else finds this information useful. I have tested everything in this post at least three times. All testing was done on the most recent Android 7 firmware on my ZenFone 3 Deluxe Special Edition (SnapDragon 821/6/256).
Sandman45654 said:
I unfortunately figured something out the other day. Using TWRP 3.1.1-0 I am able to install zip files, complete wipes, make & restore backups. The issues only arise after you restore your nandroid image. Everything works except for two things.
1. The ability to hear audio during phone calls. The phone is actually able to place calls but you are unable to hear or record any phone audio. Oddly enough I was able to play music and use voice dictation. It was only in-call audio that seemed to be affected.
2. If you have a pin set when you create your nandroid image your pin will no longer work once restored. You will be locked out of your own phone!!
Fortunately both are fairly easily resolved and keep TWRP relatively useful, although a bit bothersome!
To resolve the pin issue it is necessary to use the TWRP file manager or ADB to delete 5 files (listed below) and regain entrance to your phone. Once deleted simply reboot the phone and reset your pin. If you remove your pin before creating a backup this issue is averted completely.
/data/system/gatekeeper.pattern.key
/data/system/gatekeeper.password.key
/data/system/locksettings.db
/data/system/locksettings.db-wal
/data/system/locksettings.db-shm
To re-enable call audio use TWRP (install zip) to reflash the same version firmware from the Asus website over your current install without wiping. This will restore any system apps you may have removed but you should still have root and can easily remove them again. There will be two errors when performing the flash, which is why I believe root is retained but the system image will be reflashed. Reboot and enjoy
I sincerely hope I have not caused anyone any issues! Or that someone else finds this information useful. I have tested everything in this post at least three times. All testing was done on the most recent Android 7 firmware on my ZenFone 3 Deluxe Special Edition (SnapDragon 821/6/256).
Click to expand...
Click to collapse
The second issue happens in all the phones/twrp.
It's possible to install the firmware from asus website with twrp?? To update i flash the stock recovery, install the firmware, then reflash twrp and supersu. Didn't know that! It updates successfully with twrp??
Thank you Ryder for confirming my suspicion that the pin issue may have been a more common one with TWRP. This is the first phone I actually cared enough about to use a pin. I was thrown for a loop when I first booted my fresh nandroid restore and the pin I know I've been using was incorrect!
As for installing firmware, with the two errors that occurred during I don't know that you would be able to do full scale upgrade to a higher version. To reinstall the system partition however it does seem to work quite well. I tested this part four times. To do so download the correct device/version firmware to the phones storage, click install, and select that file. After it completes I like to wipe both the cache and the dalvik cache before restarting the phone. The audio issue was unfortunately easily reproduced on my phone, but thankfully equally easy to resolve. This worked for me each time without fail.
Sandman45654 said:
Thank you Ryder for confirming my suspicion that the pin issue may have been a more common one with TWRP. This is the first phone I actually cared enough about to use a pin. I was thrown for a loop when I first booted my fresh nandroid restore and the pin I know I've been using was incorrect!
As for installing firmware, with the two errors that occurred during I don't know that you would be able to do full scale upgrade to a higher version. To reinstall the system partition however it does seem to work quite well. I tested this part four times. To do so download the correct device/version firmware to the phones storage, click install, and select that file. After it completes I like to wipe both the cache and the dalvik cache before restarting the phone. The audio issue was unfortunately easily reproduced on my phone, but thankfully equally easy to resolve. This worked for me each time without fail.
Click to expand...
Click to collapse
You said that the two issues occurred when you restored the nandroid backup and to fix one of them by installing the zip firmware from asus website with twrp... I don't understand. I can install zip firmware with twrp or i have to flash the stock recovery and install with it? Errors may occur using the twrp? Sorry
Everything done in my post so far has been in TWRP. Honestly I didn't even back up the recovery image. TWRP seemed to work flawlessly so I bit bullet and flashed it.
On a sidenote I am currently testing the usability of FlahFire on this device. It appears to create a very nice fastboot installable recovery image! I have yet to restore the image however. I will post my findings here once I have thoroughly tested it.
Sandman45654 said:
Everything done in my post so far has been in TWRP. Honestly I didn't even back up the recovery image. TWRP seemed to work flawlessly so I bit bullet and flashed it.
On a sidenote I am currently testing the usability of FlahFire on this device. It appears to create a very nice fastboot installable recovery image! I have yet to restore the image however. I will post my findings here once I have thoroughly tested it.
Click to expand...
Click to collapse
Ok. I'm interested in flashing zip firmware to update. Never tried that. I thought that firmware can be installed only with stock recovery. The stock recovery can be downloaded in an asus forum website
This is the first time I have flashed anything in almost a year. I got to thinking and this is the most success I have had was flashing a stock image with TWRP! I doubt it will perform a full flash. I believe the errors are most likely for the boot and recovery partitions. As a save my butt reflash the system partition it does work. It sounds like it's time to find some TWRP changelogs!
Sandman45654 said:
This is the first time I have flashed anything in almost a year. I got to thinking and this is the most success I have had was flashing a stock image with TWRP! I doubt it will perform a full flash. I believe the errors are most likely for the boot and recovery partitions. As a save my butt reflash the system partition it does work. It sounds like it's time to find some TWRP changelogs!
Click to expand...
Click to collapse
I don't care about stock images... If i can't flash the zip with twrp to update successfully then i reflash the stock recovery and after the update root again with twrp and supersu. By the way, the zip firmare contains factory images? I thought it contains different kind of files
Ryder. said:
By the way, the zip firmare contains factory images? I thought it contains different kind of files
Click to expand...
Click to collapse
I lack the knowledge to answer that with enough certainty to even call it an answer! This is my foray into the insides of this phone and I don't want to start posting my hunches.
What I do know is you can flash the system partition using TWRP. I have done it several times. Asus's zips run as a script based zip install. You are offered no options during install. When the script runs you will see two errors quickly scroll past.
Ryder. said:
Download the right twrp here: https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
Click to expand...
Click to collapse
Are you creating these TWRP builds? If so thank you very much! TWRP-3.1.1-0-Z016-20170826 seems to work flawlessly! No lag on boot and no known issues after restoring a backup unlike before.
I wanted to post my finding about FlashFire by Chainfire. I have had great success with the fastboot backup! It is the only option I have tested extensively however. I have been running the same fastboot restored phone since soon after my last post on this topic with no issues discovered.
Sandman45654 said:
Are you creating these TWRP builds? If so thank you very much! TWRP-3.1.1-0-Z016-20170826 seems to work flawlessly! No lag on boot and no known issues after restoring a backup unlike before.
I wanted to post my finding about FlashFire by Chainfire. I have had great success with the fastboot backup! It is the only option I have tested extensively however. I have been running the same fastboot restored phone since soon after my last post on this topic with no issues discovered.
Click to expand...
Click to collapse
No. It's not me. It's another user which i don't remember the nickname
Ryder. said:
No. It's not me. It's another user which i don't remember the nickname
Click to expand...
Click to collapse
Okay thank you. If you happen to find out/remember please let me know. I would like to give credit with my project and thank them for their hard work.
First, let me say I have been using rooted phones with twrp for several years and never had the slightest problem with them, so I generally know what I am doing, but the Mi A2 Lite is just a disaster area for me, not with Magisk, that works fine, but twrp seems impossible for me to install on 10.0.3.0 without soft bricking ( I had twrp installed on 10.0.2.0 and 10.0.1.0 so I am not unfamiliar with the method, but on 10.0.3.0 - no way). I have done so many factory resets now I have my own parking space at the factory! (That is humour btw).
So I wondered if a different approach to the problem might work. I am not a coder or phone guru, so what I propose might be nonsense, if it is I am sure somebody will tell me.
We are all used to the concept of the 'patched_boot.img' created by Magisk and if you don't want to produce your own version the forum usually has a link to it. Magisk though is not the problem, twrp is, so what I am proposing is that somebody provides a link to a 'double_patched_boot.img' ie a flashable boot image that contains both twrp and magisk and that can directly replace the stock boot via fastboot.
Apparently there are some folks that have managed to install both twrp and magisk on 10.0.3.0, so if one of them could extract the 'double_patched_boot.img' from their phone it might help out a lot. How do you achieve that? Well there is probably more than one way, but the way that I would choose (if I could manage to install them both in the first place) is to boot into twrp, connect to pc, take a miflash backup of the phone and then unzip it with the following command (this is a linux command I am sure someone can provide a windows equivalent):
Code:
tar -xzf ********.tgz
where ********.tgz is the name of your miflash backup.
Then extract the boot.img from the resulting folder, rename it to something like 'double_patched_boot_10.0.3.0.img' and provide a link to it on the forum. Then some brave soul could try it out (probably not me as I am sick of doing factory resets and don't have any backups because I don't have any recovery to make them from).
OTOH this might just not be practical, I don't know enough to be sure.
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
Interesting. I have certainly thought of jumping ship to a custom rom, but I would like to wait a little before I do so, ideally until someone fires up a Lineage rom for the A2 Lite. But if things continue as badly as they have done so far with stock roms then I might well join you on RR.
viking777 said:
Interesting. I have certainly thought of jumping ship to a custom rom, but I would like to wait a little before I do so, ideally until someone fires up a Lineage rom for the A2 Lite. But if things continue as badly as they have done so far with stock roms then I might well join you on RR.
Click to expand...
Click to collapse
also because of the new ARB thing, custom is much safer, i think i bricked my last device rolling back from ota 9.0 software to ota 8.1. that's a non-issue with custom. just something to be wary of. the current RR pie gsi is near flawless for he so far. hope that helps a little
12:121390 said:
also because of the new ARB thing, custom is much safer, i think i bricked my last device rolling back from ota 9.0 software to ota 8.1. that's a non-issue with custom. just something to be wary of. the current RR pie gsi is near flawless for he so far. hope that helps a little
Click to expand...
Click to collapse
Anti roll back is disabled and not an issue if bootloader is unlocked
Nice thread. Tried it as well but no chance 10.0.3.00 + twrp + magisk. And you are right the problem is twrp.
Sent from my Phh-Treble vanilla using Tapatalk
12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
Does RR Pie have any issues on Mi A2 Lite? Whichever GSI I'd tried, I had lags :/
12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
brother i also want to install RR PIE Rom can you please give me the guide link?
hossman said:
Anti roll back is disabled and not an issue if bootloader is unlocked
Click to expand...
Click to collapse
correct it is not. what happened was.. lol. i thought i was crafty and did some file swapping and made miflash setups that would flash so the stock files as usual , but with gsi's like RR and/or bootleggers for the system image. and it works, up until i flashed from RR to bootleggers with those setups described previously . there is where my genius was flawed. lol. lesson learned
---------- Post added at 06:43 AM ---------- Previous post was at 06:38 AM ----------
marstonpear said:
Does RR Pie have any issues on Mi A2 Lite? Whichever GSI I'd tried, I had lags :/
Click to expand...
Click to collapse
for me, i have not come across anything caused by the GSI. any issues I've faced are purely self inflicted.
I don´t get your problems... Just boot twrp, and install it as described in original thread.
After that flash back aboot from 9.6.11.0 and the message "your system got destroyed" will disappear!
Voodoojonny said:
I don´t get your problems... Just boot twrp, and install it as described in original thread.
After that flash back aboot from 9.6.11.0 and the message "your system got destroyed" will disappear!
Click to expand...
Click to collapse
You might not get my problem, but likewise I don't get your solution. Firstly aboot has never been touched during the attempted twrp install so why flash it at all, it has not been changed, and secondly you suggest I flash it with something that is how many versions old 4?, 5?, I'm not sure, when just about every post you ever read stresses that you should not mix old and new partitions at the same time.
I hope you forgive my scepticism, but can you actually suggest the slightest reason why this might work?
Or is it all just voodoo johnny (sorry, couldn't resist that).
viking777 said:
You might not get my problem, but likewise I don't get your solution. Firstly aboot has never been touched during the attempted twrp install so why flash it at all, it has not been changed, and secondly you suggest I flash it with something that is how many versions old 4?, 5?, I'm not sure, when just about every post you ever read stresses that you should not mix old and new partitions at the same time.
I hope you forgive my scepticism, but can you actually suggest the slightest reason why this might work?
Or is it all just voodoo johnny (sorry, couldn't resist that).
Click to expand...
Click to collapse
Aboot is the bootloader. Since Pie the aboot was modified to check wheather there are modification on your boot.img. So everytime you modify something (like installing twrp), you get the message "your system got destroyed".
9.6.11.0 is the last version of Oreo. Here the bootloader didn´t check boot.img.
That´s why you need to flash 9.6.11.0 - maybe the older verstions will work too. Didn´t check. But I guess only 9.6.11.0 will work becouse it was the latest oreo version and it had to have a bootloader which can boot up pie (to have ota working).
Here you can find the aboot.img I use... and which works without any problem on pie - right now I´m running 10.0.3.0...
Just flash it via fastboot.
Voodoojonny said:
Aboot is the bootloader. Since Pie the aboot was modified to check wheather there are modification on your boot.img. So everytime you modify something (like installing twrp), you get the message "your system got destroyed".
9.6.11.0 is the last version of Oreo. Here the bootloader didn´t check boot.img.
That´s why you need to flash 9.6.11.0 - maybe the older verstions will work too. Didn´t check. But I guess only 9.6.11.0 will work becouse it was the latest oreo version and it had to have a bootloader which can boot up pie (to have ota working).
Here you can find the aboot.img I use... and which works without any problem on pie - right now I´m running 10.0.3.0...
Just flash it via fastboot.
Click to expand...
Click to collapse
OK that makes sense now - thank you for the explanation. I will probably give that a try sometime, but not right now as I have a stable working phone for the first time in ages and I don't want to jeopardise that.
Just one question though. When I had twrp installed on 10.0.2.0, it was fine at doing backups, but on the two occasions I tried to restore with them they failed, by which I don't mean that the restore didn't repair the phone, but that it was impossible to even carry out the restore, it started but did not complete - just ended with 'Restore Failed' message.
Have you tried any restores with twrp installed in the manner you suggest and if so did they work? No point in installing it otherwise.
viking777 said:
OK that makes sense now - thank you for the explanation. I will probably give that a try sometime, but not right now as I have a stable working phone for the first time in ages and I don't want to jeopardise that.
Just one question though. When I had twrp installed on 10.0.2.0, it was fine at doing backups, but on the two occasions I tried to restore with them they failed, by which I don't mean that the restore didn't repair the phone, but that it was impossible to even carry out the restore, it started but did not complete - just ended with 'Restore Failed' message.
Have you tried any restores with twrp installed in the manner you suggest and if so did they work? No point in installing it otherwise.
Click to expand...
Click to collapse
There seems to be some bugs restoring system and vendor... Some users talked about... I usually only save and restore the data and boot partition and I never had any problems with that. For all other partitions you can use miflash or fastboot...
Yeah all my twrp full backups don't work after a fresh stock installment either, that's very annoying.
The twrp version for daisy is bugged. Backups are not working, the wifi with GSI Roms on pie stock is not working anymore as soon as twrp is installed as well.
Sent from my Phh-Treble vanilla using Tapatalk
Thanks for the replies above. @voodoojohnny
In my case it was the data partition that caused the restore to fail, vendor and system and boot all seemed to go through normally. @cd492
Based on what you say along with my own experiences and those of voovoojohnny, it looks like twrp is more trouble than it is worth at the moment. I think I will make do without it for now and hope for a better version in the future.
viking777 said:
First, let me say I have been using rooted phones with twrp for several years and never had the slightest problem with them, so I generally know what I am doing, but the Mi A2 Lite is just a disaster area for me, not with Magisk, that works fine, but twrp seems impossible for me to install on 10.0.3.0 without soft bricking ( I had twrp installed on 10.0.2.0 and 10.0.1.0 so I am not unfamiliar with the method, but on 10.0.3.0 - no way). I have done so many factory resets now I have my own parking space at the factory! (That is humour btw).
So I wondered if a different approach to the problem might work. I am not a coder or phone guru, so what I propose might be nonsense, if it is I am sure somebody will tell me.
We are all used to the concept of the 'patched_boot.img' created by Magisk and if you don't want to produce your own version the forum usually has a link to it. Magisk though is not the problem, twrp is, so what I am proposing is that somebody provides a link to a 'double_patched_boot.img' ie a flashable boot image that contains both twrp and magisk and that can directly replace the stock boot via fastboot.
Apparently there are some folks that have managed to install both twrp and magisk on 10.0.3.0, so if one of them could extract the 'double_patched_boot.img' from their phone it might help out a lot. How do you achieve that? Well there is probably more than one way, but the way that I would choose (if I could manage to install them both in the first place) is to boot into twrp, connect to pc, take a miflash backup of the phone and then unzip it with the following command (this is a linux command I am sure someone can provide a windows equivalent):
where ********.tgz is the name of your miflash backup.
Then extract the boot.img from the resulting folder, rename it to something like 'double_patched_boot_10.0.3.0.img' and provide a link to it on the forum. Then some brave soul could try it out (probably not me as I am sick of doing factory resets and don't have any backups because I don't have any recovery to make them from).
OTOH this might just not be practical, I don't know enough to be sure.
Click to expand...
Click to collapse
THIS HAS NOT BEEN TESTED ON GSI'S YET
I'm currently in the process of RR with TWRP but having extreme Encryption errors
Grab these two files (Big Thanks to Zerovoid, Seryioo, and mac12m99)
Fixed SDCard Support TWRP Image File (Put this on your SDCard and Computer)-
https://forum.xda-developers.com/mi...unofficial-twrp-daisy-mount-sd-fixed-t3889390
Fixed SDCard Support TWRP Installer Zip (Put this on your SDCard)-
https://androidfilehost.com/?fid=11410963190603893418
But I got TWRP on 10.0.3.0 with magisk, and Justic Kernel.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA
Start with the phone being on with USB Debugging enabled correctly
Type adb reboot bootloader
So flash the 10.0.3.0 ROM through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
After it is done flashing it restarts, go ahead and hold power and volume down right back to the Bootloader
Type: fastboot boot twrp-3.2.3-0-daisy_zero.img
It would boot into TWRP, if you see something about decryption hit cancel this may mean you haven't followed directions so far
Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
Hit the home button back to TWRP home screen and tap reboot >>> bootloader
Download this to your computer - https://androidfilehost.com/?fid=11410963190603884024
Type: fastboot flash aboot aboot_9.6.4.img
Then type: fastboot reboot
Afterwards your phone shall boot up to Android if it does hold power and volume up and release power and keep hold volume up when the screen turns back on to go-to recovery, if TWRP boots up you have successfully completed the task.
Now flash Magisk zip (optional)
Hopefully this helped kind of my first tutorial, this was my process.
InfinityXDA said:
THIS HAS NOT BEEN TESTED ON GSI'S YET
I'm currently in the process of RR with TWRP but having extreme Encryption errors
Grab these two files (Big Thanks to Zerovoid, Seryioo, and mac12m99)
Fixed SDCard Support TWRP Image File (Put this on your SDCard and Computer)-
https://forum.xda-developers.com/mi...unofficial-twrp-daisy-mount-sd-fixed-t3889390
Fixed SDCard Support TWRP Installer Zip (Put this on your SDCard)-
https://androidfilehost.com/?fid=11410963190603893418
But I got TWRP on 10.0.3.0 with magisk, and Justic Kernel.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA
Start with the phone being on with USB Debugging enabled correctly
Type adb reboot bootloader
So flash the 10.0.3.0 ROM through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
After it is done flashing it restarts, go ahead and hold power and volume down right back to the Bootloader
Type: fastboot boot twrp-3.2.3-0-daisy_zero.img
It would boot into TWRP, if you see something about decryption hit cancel this may mean you haven't followed directions so far
Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
Hit the home button back to TWRP home screen and tap reboot >>> bootloader
Download this to your computer - https://androidfilehost.com/?fid=11410963190603884024
Type: fastboot flash aboot aboot_9.6.4.img
Then type: fastboot reboot
Afterwards your phone shall boot up to Android if it does hold power and volume up and release power and keep hold volume up when the screen turns back on to go-to recovery, if TWRP boots up you have successfully completed the task.
Now flash Magisk zip (optional)
Hopefully this helped kind of my first tutorial, this was my process.
Click to expand...
Click to collapse
Thank you very much for posting this process in such detail, unfortunately I think you must have missed my last post where I said:
it looks like twrp is more trouble than it is worth at the moment. I think I will make do without it for now and hope for a better version in the future.
Click to expand...
Click to collapse
I meant it, at least for now, but maybe your post will help somebody else.
viking777 said:
Thank you very much for posting this process in such detail, unfortunately I think you must have missed my last post where I said:
I meant it, at least for now, but maybe your post will help somebody else.
Click to expand...
Click to collapse
Yes I didn't see that post but understand I didn't give you links to the official TWRP, I gave you the unofficial fixed TWRP which actually features SD Card Support and trust me it works completely fine I haven't had a problem yet. This took me hours upon hours to figure out what I was doing wrong.
The only specific reason you are not successfully getting TWRP is because you didn't flash the aboot.img after installing the zip.
I hope this helps you in the future!
thanks InfinityXDA for the tutorial, you should create a post just for it~
I am grateful and I bought this because next tk Samsung s22 yktra this phone is definitely #2 in my opinion, which is saying a lot.
However the root process is tedious because I am not around a computer I am just lazy to get ito do flashing etc.
My question is, why do. We not have a a real recovery and ability to back up and restore various roms we or flash zips senselessly.
So my question is (since I just bought this) do you guys rhibj we will have to dastboir flash everything or at least much harder then with cwmod or twrp recovery. Is it not possible to have a recovery like those on t his phone?
Is there a better phone in the us that is unlockaable but has the quality like this phone and screen or the Samsung s22 yktra phone?
Thanks
Without a PC you can't run fastboot commands to unlock bootloader and root it. Twrp isn't available for stock a12, let alone the upcoming release of a13
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
jgrimberg1979 said:
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
Click to expand...
Click to collapse
I don't think that you will find too many phones from the primary companies (Google, Samsung, etc) nowadays that will have TWRP builds. As time progresses, the technology (and what is available) progresses as well.
jgrimberg1979 said:
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
Click to expand...
Click to collapse
This is the most recent news about Android 12 compatibility for TWRP:
TWRP 3.6.2 Released
TWRP 3.6.2 is out now for most currently supported devices.
twrp.me
We are continuing work on Android 12. There is no ETA currently. You can follow our status on Zulip
Click to expand...
Click to collapse
Disclaimer: I am not advocating signing up for "Zulip", and I won't be doing so myself. When/if TWRP for Android 12 becomes available, I'll hear about it whether I sign up on there or not. It's also likely Android 13 will be stable by then.
Supposedly, the Official TWRP App (not itself updated since 2020) will notify when there's a new version - but I don't know if that applies to when there's no current version of TWRP Recovery already installed.
The reality is that for any device that actually has full working FASTBOOT, there is really no need for these types of recovery systems (i.e. twrp).
Screwing around with different OS builds while out and about is ill-advised no matter what. Leads you to the likely situation of getting yourself unbootable, which is bad. Its really not that big of a burden to plug in a wire when doing radical changes like that.
96carboard said:
The reality is that for any device that actually has full working FASTBOOT, there is really no need for these types of recovery systems (i.e. twrp).
Screwing around with different OS builds while out and about is ill-advised no matter what. Leads you to the likely situation of getting yourself unbootable, which is bad. Its really not that big of a burden to plug in a wire when doing radical changes like that.
Click to expand...
Click to collapse
It's not that much of a burden. You got to understand. It's been several years to a decade since I had a android and what I was used to was much different than now. I was used to always having a recovery that backs everything up and could swap roms if I wanted to if I flashed something wrong I could easily get into recovery and reflash the rom or just restore to another one. It's just different but I am grateful for what I have now but was hoping maybe there would be a recovery like twrp or cm recovery etc. Either way still happy for what we have
Pixel devices do not have a recovery partition; recovery lives in /boot with the kernel, as well as whatever patches you've applied. Currently, TWRP and Magisk cannot coincide for whatever reason. You can patch a boot image with TWRP, and it'll work AFAIK....but if you try to patch it with Magisk too, you'll get a boot loop.
Because we have full fastboot access, there's not really any need for TWRP. You can dump and backup partition contents using fastboot, but it's tedious.
jgrimberg1979 said:
It's not that much of a burden. You got to understand. It's been several years to a decade since I had a android and what I was used to was much different than now. I was used to always having a recovery that backs everything up and could swap roms if I wanted to if I flashed something wrong I could easily get into recovery and reflash the rom or just restore to another one. It's just different but I am grateful for what I have now but was hoping maybe there would be a recovery like twrp or cm recovery etc. Either way still happy for what we have.
Click to expand...
Click to collapse
ADP, Nexus, and Pixel devices have NEVER needed a recovery to function fully. This goes right back to the first Android phone in 2008. So nothing really has changed in this respect. Its mostly the "other" brands that need a recovery to work around various restrictions.
Backups can be taken from within the main OS, and restored similarly, and this is actually much preferred since the backup can be stored to a remote location such as a self-hosted Nextcloud server. You can look into seedvault (integrated solution) and neobackup (root solution).
Since Android 11 you cannot have TWRP and Magisk installed at the same time or it will lead to a bootloop. However, you can fastboot boot TWRP (without installing it) and have Magisk installed without getting into a bootloop. At least this is the way it was on Android 11 with the Pixel 2 XL.
Haven't used TWRP in a long time and don't miss it at all, to be honest.