Related
So, trying to get root on this phone, and was following the steps mentioned here:
http://forum.xda-developers.com/showthread.php?t=2160490
Grabbed the scatter, read things from the phone just fine - although it failed to extract the yaffs2 partitions when asked - but when it came time to flash the recovery SP Flashtool complained that 'pmt is ready and layout has been changed'... and advised doing a full firmware upgrade. Well, since I had all the files - and I have two of these phones - I decided to give it a try.
The good news is that it successfully installed CWM recovery. The bad news is that, after writing 10mb or so, it died with 'the length of read back operation is not page aligned' (why it's trying to read back, I don't know...). And it dies like this every time, regardless of whether I use the original recovery or the new recovery. From booting into recovery I can see that there's nothing left of my system/data/cache partitions, and the phone (unless booted into recovery) gives a blank screen.
So, my next crazy plan is to use nandwrite (or something else?) from adb shell to plonk those partitions back on the appropriate /dev/mtd things. Does this sound sane? Any advice?
Well, that just doesn't work
Wrote the partition, said it was writing it, but when I mounted it in recovery there was nothing at all there...
This is basically a copy of my Z380M TWRP thread adopted for the ZenPad 10. I decided to start a new one since the OP of justshaun's original recovery/rooting thread has gone stale, even as I had posted several new releases of TWRP over the months. Its instructions are also a little outdated. I've also compiled a version for the new Z301M(F) models and needed a place to post it. This is where I will be posting TWRP updates from now on.
In addition to this thread, referring to the Z380M TWRP thread and the original Z300M thread (links above) may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the others.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows or Linux PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)
MediaTek VCOM drivers (available through Windows Update)
ZenPad 10 scatter file for SPFT, attached (choose the one for your tablet)
Recovery image, attached (choose the one for your tablet)
ZenPad Z300M, Z301M or Z301MF tablet upgraded to Android N
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 10.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image for your device (twrp-3.2.1-0-z30*m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z30*m.img
Once inside TWRP, flash twrp-3.2.1-0-z30*m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". On the Z301M/Z301MF, that option is labeled Factory Reset. Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
WARNING 2: Make sure you use the correct scatter file for your device (i.e. don't mix up the Z300 and Z301 files). For the initial flash, there is no check for scatter file correctness. If you use the wrong one, SP Flash Tool will alter and lock your GPT to that scatter file layout, possibly bricking your device. It will not be easy to restore it. Flashing with the correct scatter file later on will not work because Flash Tool will not allow you to use a different file than the one you used initially.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
SP Flash Tool v5.1532
Z300M Scatter file for all storage sizes (right click, Save link as...) -- do not use for other models
Z300M TWRP 3.2.1-0 image -- updated March 15, 2018
Z301M(F) series Scatter file for all storage sizes (right click, Save link as...) -- do not use for Z300M or other devices
Z301M TWRP 3.2.1-0 image -- updated March 13, 2018
Z301MF TWRP 3.2.3-0 image -- updated August 29, 2018
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Heya, thanks for the new thread..
Stupid question(coming from Samsung flashing)
Ive got Zenpad S3 10 P027, is this TRWP not ideal for this?
Currently, have some su (root) issues. Recovery shows Android icon chest with ! and says "No Command"
When running su in Terminal ADB via PC, says command not recognized.
Looks like I need to reflash recovery. When in TRWP (launched via fastboot boot twrp on PC) I flashed stock recovery but had system mounted read only. Could that be the problem?
Bro, I think you need to do some more homework on root, su, dm-verity, mods, etc. and read the instructions more carefully before applying these hacks. You are making a lot of simple mistakes and ending up shooting yourself in the foot for it. I don't think there's anything wrong with the Z500 TWRP. It can handle installing the stock firmware just fine. The problem is elsewhere. The unlock tool also works fine in TWRP as well in my testing.
The No Command screen is normal. That's been answered many times... you need to hold power+vol. up (or down) to get to the menu. There is no way the stock recovery image can be broken and still boot up.
The su thing, IDK what the problem is, but I'm sure if you install Magisk Manager and make your own patched image from your currently installed firmware, and fastboot-boot with it, you will have su functionality. Just like what it says in the unlock tool instructions.
Lastly and most important, never mount system in read-write mode, as I've repeated several times and exactly as it says in the directions:
7. At the TWRP welcome screen, do not select to modify the system partition and touch Keep System Read-only instead. Doing otherwise will render your tablet unbootable.
8. Mount system in TWRP (in read-only mode)
Click to expand...
Click to collapse
The only time you can mount it in read-write mode is when you are absolutely sure you have disabled dm-verity in your boot image.
I've successfully installed TWRP on Z301M using the instructions from the first post, but then I somehow managed to lose the system. Yes, I should have backed up like the OP suggests.
I thought I should be able to reinstall the original firmware downloaded from Asus (e.g. UL-ASUS_P028_1-WW-3.3.12.0-user.zip) but both the 'adb sideload' method and the TWRP failed to install that firmware zip. My device looks bricked. The only thing I can do is to boot into TWRP (I actually need to select Factory Reset on the bootloader screen to get into TWRP). The folder 'system' is empty.
Can anyone suggest what I am doing wrong when trying to restore the Asus firmware?
When I try to sideload the zip, setting TWRP in the sideload mode, the computer begins uploading but after a few seconds gives the message "Total xfer: 0.01x" and stops, while Android errors with "set boot part fail. can not open misc-sd".
When I install the firmware zip from TWRP it also starts installing fine but shortly gives the same error "set boot part fail. can not open misc-sd".
Thanks
@ahacker, first of all, thank you for the feedback on the Z301M platform. You are literally the first person to have said anything about that version of TWRP.
To see the files on system, you first have to mount the system partition. Did you do that? If not, I suggest mounting it read-only. If there was any corruption on it, then reinstalling the firmware should have fixed it. The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
At which point did it stop booting? Also, did you use the scatter file from first post? And can you tell me if the touch screen works fine in TWRP on your tablet?
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
diplomatic, thanks for replying!
diplomatic said:
[MENTION=4776997]
To see the files on system, you first have to mount the system partition. Did you do that?
Click to expand...
Click to collapse
I do mount the system partition. It appears empty. When I reboot into system TWRP says that the OS is not installed.
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
I would indeed try to mount the system read only. This is not the first Android system I rooted (maybe fifth), and I was always able to restore the system either from sideload or recovery. But here it seems Asus is making us jump extra hoops to do that.
diplomatic said:
[MENTION=4776997]
Reinstalling the firmware should have fixed it.
Click to expand...
Click to collapse
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
diplomatic said:
[MENTION=4776997]
The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
Click to expand...
Click to collapse
Thank you for the information.
diplomatic said:
[MENTION=4776997]
Also, did you use the scatter file from first post? Does the touch screen work fine in TWRP on that tablet?
Click to expand...
Click to collapse
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
diplomatic said:
[MENTION=4776997]
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
Click to expand...
Click to collapse
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
---------- Post added at 01:19 AM ---------- Previous post was at 12:57 AM ----------
Now system refuses to mount
ahacker said:
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
Click to expand...
Click to collapse
Er, the password should have been for decrypting your userdata. If you didn't have one set up, there might be something wrong there.... Or possibly just unformatted.
ahacker said:
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
Click to expand...
Click to collapse
Yeah, that has to be the right one. The installation script has to match the model name reported by the recovery. Otherwise it would simply abort.
ahacker said:
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
Click to expand...
Click to collapse
Great! Guess my kernel patch was on the dot and the partition layout has not changed from the Z300.
ahacker said:
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
Click to expand...
Click to collapse
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
diplomatic said:
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
Click to expand...
Click to collapse
I've tried both ways, with and without system mounted, a few times. The installation would fail after something like 5 seconds.
diplomatic said:
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
Click to expand...
Click to collapse
I think I am giving up on this cheap tablet. I cannot even format it in the Flash Tool: it says "To format code area is forbidden on this phone". Asus is forbidding too much for me to ever buy it again. Attached the logs.
Thanks, diplomatic
OK, found the problem. Check your PMs, ahacker.
diplomatic said:
OK, found the problem. Check your PMs, ahacker.
Click to expand...
Click to collapse
I have replied (twice), but the reply does not appear in my Sent Items. I hope it has reached you. If not, I'll paste the reply here, if you don't mind.
i not understand... i have Asus ZenPad 10 LTE Z301MFL.. a root method has been released ???
@diplomatic
Would this be compatible with Z0310M ? can't find anything for this damn model...
Hi, NeBouse,
Are you sure you have the correct information? It looks like just a misspelling of Z301M, aka P028....
I have z301m.
One thing that was a surprise for me is that the TWRP recovery flashed with the method described in the original post does not stick. You have to flash it each time you use it. If you are like me this information is important, because the original recovery plainly wipes your data without asking or warning.
After you have flashed TWRP on the device, to go to the recovery mode you have to chose "Factory Reset" in the bootloader. Then it will complain about wrong OS, which is the sign that flashing TWRP worked; choose 'yes'. The first thing you should do in TWRP is a ful nandroid backup. (Not listening the OP's advice about backing up when Installing TWRP with a wrong scatter file almost cost me the device. Thankfully diplomatic managed to remotely fix my problem, probably spending a lot of his personal time. The scatter file in the original post is a correct one now.)
Creating a nandroid backup in TWRP takes unusually long time, I even once decided that it hanged. Taking long time, like 10-30 minutes, for a full backup is normal.
Asus Z300M , Magisk 16.3 (beta) and FW 5.3.19 WW now works!
z301m, WW-3.3.12.0 firmware
For rooting I've installed in TWRP Magisk v15.3 (diplomatic warned against 16.x, someone else against 15.4) - link.
Installed in TWRP xPosed framework 88.2 - link, and xPosed Installer apk from within Android - link.
So far, so good.
What I've found is that TWRP seems to have problems with external sd cards (lots of fs corruption). I found it safer to unmount by hand by unticking the sd card checkbox in "Mount". Not very conclusive about this though.
Thanks, ahacker. Good feedback. Although to be fair, I didn't say to avoid Magisk 16.x. I said 16.0. I'm pretty sure whatever bug it had is already fixed in the latest version.
Now that you've installed root, TWRP will stick around on the emmc. The stock recovery only gets installed if you have the original unpatched boot image on it. I mean, this is not unique to these devices. That's been standard Android functionality since some 4.x or 5.x version. And this is essentially what's in the warning on the OP.
The backup I'm talking about in the installation method is done with the SP Flash Tool readback function. That will pull the partition tables and your device's "metadata" that's unique to your unit. I don't think nandroid covers that...
Oh, and what is this SD corruption you're talking about? What file system is it formatted in? Have you checked your card for errors in Windows?
Asus releases so many difference Z301M model, so I am curious if this also works on Z301MF model?
Notice Z300MF has the MTK8163BA (or MTK8163A?) CPU model while Z301M uses : 8163B
Anyone tested that already? Thanks.
my zenpad 10 has frp lock. it this a solution to remove the frp lock?
Pls help how i flash original software via fastboot ?????
[RECOVERY] TWRP 3.6.0_11-0 - 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 loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of official builds.
Device Config: https://github.com/bigbiff/android_device_google_crosshatch
Hello, this is a test build for crosshatch users.
If others thing don't work, please report the issue and let me know.
I am opening this thread to replace @Dees_Troy's thread with his blessing.
http://twrp.me
I tried to boot to this image on my bootloader-unlocked Pixel 3, but the operation failed.
With the device connected and the bootloader active, I ran the following command:
Code:
$ fastboot boot twrp-3.6.0_11-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 1.797s]
Booting FAILED (remote: 'Error verifying the received boot.img: Buffer Too Small')
fastboot: error: Command failed
I had just performed a factory reset (from
blueline-qq3a.200805.001). Flashing a blank vbmeta.img to disable verification did not resolve the error.
Thanks @bigbiff I've now got this installed on my Pixel 3 running Lineage 18 (A11). So nice to have TWRP back!! I've got one question about backing up. I'm seeing the following backup options:
Data (excluding storage)
Boot
Persist
Super (system system_ext vendor product)
I've not seen this "Persist" before. If I want to backup/restore the device, using TWRP, should all four of these options be selected?
Thanks again!
brainchild said:
I tried to boot to this image on my bootloader-unlocked Pixel 3, but the operation failed.
With the device connected and the bootloader active, I ran the following command:
Code:
$ fastboot boot twrp-3.6.0_11-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 1.797s]
Booting FAILED (remote: 'Error verifying the received boot.img: Buffer Too Small')
fastboot: error: Command failed
I had just performed a factory reset (from
blueline-qq3a.200805.001). Flashing a blank vbmeta.img to disable verification did not resolve the error.
Click to expand...
Click to collapse
See this post, and the subsequent posts.
TWRP 3.2.3-2 for Pixel 3
MTP does not work in TWRP on the Pixel 3 and will not work until we have time to update the TWRP MTP implementation. You may still use adb to push and pull files. Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot...
forum.xda-developers.com
OTG not working -_-
Thank you for the earlier reply. I am still learning about the relation between original firmware, Android version, recovery version, and partition layout. Whereas previously each had been largely independent of the others, recent changes have brought them into a very close dependence, which is often not clarified in the distribution of the various components.
I applied Android 11 firmware to the device, and was able to boot from the image.
I am now having problems installing custom Android 11 images, due to limited space on the system partition. In some cases, I can install the image but not Gapps, not even the pico size.
The general recommendation for this problem is to use the Advanced Wipe feature to resize the partition, but I have found no partition labeled System in the list.
The partitions listed under Advanced Wipe are only the following:
Dalvik / ART Cache
metadata
Data
Internal Storage
USB-OTG
I was able to install LineageOS entirely successfully using the project's own recovery, and then, once the main system was ready, install the TWRP 3.6 recovery image. While this procedure has appeared as a viable workaround, I look forward to any clarification about completing the installation entirely through TWRP. I also look forward to clarification about whether these observations indeed represent a current limitation in the TWRP images available for the device, and whether any other limitations are known.
Wow - TWRP for the Pixel 3 - finally!! What a great job, and thank you very, very much! Successfully completed my very first backup of my Blueline tonight; for the first time since buying this great phone over 18 months ago.
Issues I have found:
USB-OTG doesn't seem to work; I was hoping I could perform the backup to a USB flash drive.
Also, could not seem to get ADB from my computer to work.
Thank you so much @bigbiff for your hard work on this. It is very much appreciated! Well done!!
I do have one question, if I may: is it safe to flash this to recovery, or should we only use it via "fastboot boot twrp..."?
shaunoleary said:
Wow - TWRP for the Pixel 3 - finally!! What a great job, and thank you very, very much! Successfully completed my very first backup of my Blueline tonight; for the first time since buying this great phone over 18 months ago.
Issues I have found:
USB-OTG doesn't seem to work; I was hoping I could perform the backup to a USB flash drive.
Also, could not seem to get ADB from my computer to work.
Thank you so much @bigbiff for your hard work on this. It is very much appreciated! Well done!!
Click to expand...
Click to collapse
Thank you so much too, @bigbiff . Although USB-otg cannot be used, I can back up data on ArrowOS 12.0 without issues. Till now, I haven't tested restoration of my backup data yet.
Can this version of TWRP handle encrypted phones? (ones with lock screen passwords) I've been poking around the internet finding conflicting information.
Fnord12 said:
Can this version of TWRP handle encrypted phones? (ones with lock screen passwords) I've been poking around the internet finding conflicting information.
Click to expand...
Click to collapse
It can handle Android 11 encryption. I don't believe Android 12 encryption works yet.
dcarvil said:
It can handle Android 11 encryption. I don't believe Android 12 encryption works yet.
Click to expand...
Click to collapse
Fun, looks like i'll be waiting for a bit then as I was eyeballing one of the Android 12 ROMs to put on my Pixel 3 and i'll need encryption for NFC payment stuff.
Fnord12 said:
Fun, looks like i'll be waiting for a bit then as I was eyeballing one of the Android 12 ROMs to put on my Pixel 3 and i'll need encryption for NFC payment stuff.
Click to expand...
Click to collapse
You can still use it on Android 12 - you just need to remove the PIN first, then restore it afterwards.
dcarvil said:
You can still use it on Android 12 - you just need to remove the PIN first, then restore it afterwards.
Click to expand...
Click to collapse
You need to remove PIN on Android 12 before invoking backup process of your encrypted data on TWRP as @bigbiff said another thread. Probably, you can restore the backup data after removing PIN on Android 12. Then, you can set PIN on Android 12 again after the restoration.
Another observation... After a OTA update, LineageOS replaced the recovery with its own. From booting the TWRP image from a fastboot connection, the resulting session of TWRP shows option in the advanced menu for installing TWRP to the device. I'm not sure that I would be able to reinstall TWRP without this option, since attempts to flash through fastboot had failed previously. I'm confused about why this menu item no longer appears.
brainchild said:
Another observation... After a OTA update, LineageOS replaced the recovery with its own. From booting the TWRP image from a fastboot connection, the resulting session of TWRP shows option in the advanced menu for installing TWRP to the device. I'm not sure that I would be able to reinstall TWRP without this option, since attempts to flash through fastboot had failed previously. I'm confused about why this menu item no longer appears.
Click to expand...
Click to collapse
You can use Flash Current TWRP to have TWRP reinjected in the ramdisk, it's not showing up for you?
bigbiff said:
You can use Flash Current TWRP to have TWRP reinjected in the ramdisk, it's not showing up for you?
Click to expand...
Click to collapse
No. I believe what has happened is that the OTA update switched the active slot from A to B, with TWRP still residing on the now inactive slot A. Perhaps TWRP only looks in slot A, and if it finds itself installed, it hides this menu entry.
I am not sure what the general use pattern is, as I am still learning the newer paradigm of seamless updates, and A/B and dynamic partitions. Is TWRP compatible with OTA updates? What is the general usage pattern? The updated slot seems to have retained Magisk.
brainchild said:
No. I believe what has happened is that the OTA update switched the active slot from A to B, with TWRP still residing on the now inactive slot A. Perhaps TWRP only looks in slot A, and if it finds itself installed, it hides this menu entry.
I am not sure what the general use pattern is, as I am still learning the newer paradigm of seamless updates, and A/B and dynamic partitions. Is TWRP compatible with OTA updates? What is the general usage pattern? The updated slot seems to have retained Magisk.
Click to expand...
Click to collapse
Usually you have to reinstall twrp to the boot partition, which is typically not A/B
bigbiff said:
Usually you have to reinstall twrp to the boot partition, which is typically not A/B
Click to expand...
Click to collapse
The boot partition is shared by both slots, or each has a separate boot partition? It seems two recoveries are resident on the device.
brainchild said:
The boot partition is shared by both slots, or each has a separate boot partition? It seems two recoveries are resident on the device.
Click to expand...
Click to collapse
There are two boot partitions, boot_a and boot_b.
dcarvil said:
There are two boot partitions, boot_a and boot_b.
Click to expand...
Click to collapse
Right. It seems that when I originally loaded the firmware and installed TWRP, it installed to slot A. Later, LineageOS installed its OTA update on slot B, and activated it. Now the active recovery is the LOS recovery, in slot B. I can boot TWRP from fastboot, but the resulting session may be hiding the menu entry for installation on the the device because it detects itself already installed on slot A.
I suppose the questions are whether installation to multiple slots is supported by TWRP, and whether TWRP and LOS support integration for OTA updates.
More generally, the overall question is what is the overall recommended usage pattern for updating LOS when TWRP is also installed.
Hey Guys,
Since it doesnt seem like anybody else is-- im trying to port TWRP to the Duo.
Problem im running into is after extracting all the partitions i dont get a "Recovery.img" partition but i get a Boot_A and Boot_B partitions.
After extracting the Boot_A partition to check for recovery.img (or something relative) theres a recovery.fstab in there.
Does anyone know how I can get the recovery.img partition? or what I might be able to do with Boot_A/B?
none24 said:
Hey Guys,
Since it doesnt seem like anybody else is-- im trying to port TWRP to the Duo.
Problem im running into is after extracting all the partitions i dont get a "Recovery.img" partition but i get a Boot_A and Boot_B partitions.
After extracting the Boot_A partition to check for recovery.img (or something relative) theres a recovery.fstab in there.
Does anyone know how I can get the recovery.img partition? or what I might be able to do with Boot_A/B?
Click to expand...
Click to collapse
Pretty sure that modern A/B devices usually don’t come with a separate recovery partition. In my experience it’s a part of the boot image.
filfat said:
Pretty sure that modern A/B devices usually don’t come with a separate recovery partition. In my experience it’s a part of the boot image.
Click to expand...
Click to collapse
Correct.
Would u know what I could do as next steps given that I only have the a/b partition? I'm not sure where to transfer the files to. Or if there's a twrp porting guide that details A/B partitions
none24 said:
Correct.
Would u know what I could do as next steps given that I only have the a/b partition? I'm not sure where to transfer the files to. Or if there's a twrp porting guide that details A/B partitions
Click to expand...
Click to collapse
Im not 100% about this, but i think TWRP is dead as of the newer hardware specification in android, as it stands. You would have to package a boot image with the recovery programming, making it difficult to match up with existing setups. You would have to package for every kernel available, and hope your users dont pick the wrong one when they go to install, or else they will be stuck in a bootloop, with no way to force into recovery, because there is no recovery. I have been working on TWRP for the Unihertz Titan and have increasingly found information that TWRP if still active, is in its final days. I just bought a Duo, so there is a lot i dont know yet, but on the unihertz devices, there are tools to force your phone into preloader mode that all mediatek devices have, to flash your roms back to stock state. Even in a 100% not bootable state, you can save your device. Super slick. But if you nuke both your boot partitions by accident, there is effectively no way to recover to my knowledge, on the Duo. These tools are Very handy for developers. I am unaware of any tool that exists for the Duo that will do the same, not to say one can't or hasn't been written yet. But without someone with deep (im talking super deep) android experience, a Duo to spare, and the time and effort needed for the project, it might be safe to assume that most custom software will not arrive on the Duo, even with its ease of rooting and unlocking. I will be taking a close look at the kernel and everything else i can find to determine what will be possible for the Duo in the coming months.
Upon further research, there is a bootloader mode that does not seem to be based on boot/recovery partition. In powered off state, hold volume down and plug in to a computer. This will allow you to get into fastboot and flash anything you'd like.
** UNOFFICIAL A-TEAM RELEASE**
*******Testing ONLY*******
**testing has only been done on GN2200 July patch device but should atleast boot into twrp on other sec patch on GN2200 devices***
***Let us know if not***
*****HEED THE WARNING OF IMPENDING APOCALYPSE, DOOM, BOOTLOOPS , BRIMSTONE AND FIRE, AND ALSO TWRP ******
***NOBODY IS RESPONSIBLE FOR WHAT YOU DO WITH THIS EXCEPT YOU***
***DO NOT BUILD AND FLASH THIS UNLESS YOU KNOW EXACTLY WHAT YOUR DOING***
****DONT DO ANYTHING I SAY, I CANT BE HELD RESPONSIBLE FOR WHAT I SAY OR DO*****
**THIS IS AN ** UNOFICIAL RELEASE ** SO DONT GO CRYING TO ANYONE THAT YOU MADE YOURSELF AN EXPENSIVE PAPERWEIGHT IF YOU USE ANYTHING IN THIS POST***
********* THE RESPNSIBILITY LIES SOLELY UPON YOU***
***FLASHING IN CURRENT STATE DOES NOT BOOT INTO SYSTEM****
****READ EVERYTHING BEFORE YOU DO ANYTHING******
******ONLY POSTING THIS FOR DEV PURPOSES*******
******Huge THANKS to PizzaG for this!!!******
***Thanks to Eduardo as well for his contributions, he may still be working on his own release***
Am posting this with a copy/paste i posted in telegram group..
We need people with the knowledge/skills and experience to help get this TWRP finished AND/OR work out the bugs.
GitHub - PizzaG/recovery_device_oneplus_OP515AL1
Contribute to PizzaG/recovery_device_oneplus_OP515AL1 development by creating an account on GitHub.
github.com
*this is not ready for release but the source is here for anyone who can build upon it*
touch is not working
you cant fastboot boot on this device so DO NOT flash this to your device without a backup of your stock/current boot image
issues we are having is no touch, can't mount /data, and so far cant boot into system with the recovery installed so if you want to use it youll need to flash this to boot, use it for whatever and then flash stock boot back, if your magisk patched youll need to flash the backup of that patched boot image you made before flashing this in order to get back into your system....... i have sort of found a slight work around for having to keep flashing the boot partitions until someone can get this to boot by placing my current boot image on an sdcard along with the twrp, flash the twrp to the active boot partition, boot into twrp, install image and install your backed up boot image to the current slot, then go back to advanced and install twrp to ramdisk and select and install the twrp image to the ramdisk, if your magisk patched you need to flash magisk zip right now, you can adb shell into twrp to pull a copy of this boot image if you want and i have flashed my "twrp-ramdisk installed boot image" on the Slot that my system is on and stock/backup boot image to inactive slot because its the only way to boot back to system for now without reflashing the stock(backed up) boot image back to the slot. and reboot into bootloader, change active and reboot and your back into your system.... when you need twrp you can set active to the other slot, it will bootloop once into bootloader and choose recovery to get back to twrp... when done reboot to bootloader and set active back to the other slot and reboot into system.............otg mouse works, adb works, mtp works, some work has been done on the touch but thats still not working yet, everything seems to be mounting except data............. big shout out to PizzaG for this
***this is a very round-about way to get a currently buggy twrp on the device but if you have a usb-c adapter and mouse you can navigate twrp....***
PizzaG doesnt have the device and has spent more time than anyone could possibly ask someone to spend on this for free... I dont have the skills required yet to really work on this. I have tested as much as possible and here it is for those who can build and work on it. i dont recommend releasing in its current form because im sure alot of people will be complaining and bricking their devices. if you can build it im sure you can work on it and should have the skills to atleast recover and have the sense to make backups first.......
Thanks again to everyone who has already donated the valuable time working on this for us and to everyone who will follow and build upon this!
You can find the telegram group for our device here:
You can find the A-Team in telegram
Also FYI in case you missed the post about our kernel source, it can be found here:
GitHub - OnePlusOSS/android_kernel_msm-5.4_oneplus_sm6375 at oneplus/sm6375_r_12.0.1_oneplus_nord_n20_5g
Contribute to OnePlusOSS/android_kernel_msm-5.4_oneplus_sm6375 development by creating an account on GitHub.
github.com
If anyone with experience building twrp and especially for OnePlus devices needs a tester or any files from the device hit me up on telegram @PsYk0n4uT2 and I will do my best to provide whatever you need and test builds along with providing logs.
heres a compiled boot image from the above tree as of 10/02/2022.
**remeber it DOES NOT boot to system, this is twrp only, not installed into recovery ramdisk yet. so BACKUP YOUR STOCK(current) boot image FIRST**** you will have to flash your stock(current) boot image back to boot back into your system. you can sort of get around this by above mentioned method BUT here it is for the GN2200 anyways. working on my July patched device and my May patched device so it should work for other GN2200 sec patches too...
***BACKUP BACKUP BACKUP*****
also cant change active slot from twrp, must reboot to bootloader to change active slot
Heres TWRP installed to ramdisk on a july patched boot image. does not boot to system but since it doesnt you should still be able to use this on any patch for testing purposes.....
You can backup your boot image and flash your current boot image to inactive slot and flash this to active slot by selecting recovery from bootloader after it loops once.... use twrp then go back to bootloader and change active and reboot to get back into your system.
**BACKUP YOUR CURRENT BOOT IMAGE****
***DOES NOT BOOT TO SYSTEM**
***YOU WILL NEED YOUR CURRENT BOOT IMAGE TO BOOT YOUR SYSTEM< YOU SHOULD ALREADY HAVE A BACKUP OF YOUR STOCK IMAGE IN THE CASE THAT YOU ARE MAGISK PATCHED ALREADY< KEEP A COPY OF BOTH IN CASE YOU DECIDE TO WIPE DATA< YOU WILL NOT BOOT BACK INTO YOUR SYSTEM WITH A MAGISK PATCHED BOOT IMAGE IF YOU WIPE DATA*******
if someone can get their system to boot after installing the TWRP from post 4 or their own build after personal edits please post here how you were able to achieve the install and maintain booting into system..
currently twrp indicates that path to /mnt could not be found and cant mount /data .. i think if someone could fix this maybe some progress could be made
ScarletWizard said:
I wonder if TWRP will work for devices with a serial number defeicy
Click to expand...
Click to collapse
halfway working on mine, just isnt finished yet, we need someone who knows alot more about this than i do. another dev is working on twrp but needs a device. the serial wont affect anything else other than the oneplus care app and getting the unlock token..... other than that u have full functionality.... the one posted above needs ALOT of work to finish. no touch yet but it could work for SOME things....
I know C/C++ at a decent level, however; I don't have much experience with low level stuff (especially dealing with bootloaders and other specific proprietary android kernel stuff). If there is anything that needs testing, I am down for it since this is just a secondary phone for me and I won't be too upset if it explodes.
I'm going to attempt this
[ SOLUTION ] [ MTK ] to Fix Touch not Working on TWRP / Philz Due to Kernel Disabled Touch.
In this tutorial, i'm going to show how i managed to patch kernel to enable touch in recovery TWRP / Philz. WARNING : This worked fo...
factopea.blogspot.com
It's written for mtk device but might have similar enough instructions to port for qcom kernel,
But I believe this is what is needed to get the TWRP touch going
Is the trwp.fstab using the right version? Both have different
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,resize,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,checkpoint=fs
Try this instead in twrp.fstab
Code:
/data f2fs /dev/block/bootdevice/by-name/userdata flags=fileencryption=ice:aes-256-cts;wrappedkey;keydirectory=/metadata/vold/metadata_encryption
Techted89 said:
Is the trwp.fstab using the right version? Both have different
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,resize,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,checkpoint=fs
Try this instead in twrp.fstab
Code:
/data f2fs /dev/block/bootdevice/by-name/userdata flags=fileencryption=ice:aes-256-cts;wrappedkey;keydirectory=/metadata/vold/metadata_encryption
Click to expand...
Click to collapse
i just unpacked the twrp image with AIK and made the suggested edits and repacked, reflashed, same...... another person is working on twrp and has gotten much of the fstab corrected in their build but their keeping their source closed til they get it ready for release and is still very far from being finished with it and doesnt have much time to work on it right now so we are just kinda stuck waiting on someone that knows what their doing to help get this going. the other person has touch working on theirs so i know its possible i just dont know how long it will be before we see a beta even
Techted89 said:
Is the trwp.fstab using the right version? Both have different
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,resize,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,checkpoint=fs
Try this instead in twrp.fstab
Code:
/data f2fs /dev/block/bootdevice/by-name/userdata flags=fileencryption=ice:aes-256-cts;wrappedkey;keydirectory=/metadata/vold/metadata_encryption
Click to expand...
Click to collapse
also i see a recovery.fstab instead of twrp.fstab in /system/etc. is this what your referring to?
You need both from what iv read ,. TWRP.flags is a module that rewrites the stab at a certain point which may be the reason it's not compiling but I will post. Recovery.fstab is supposed to be a copy paste from the boot.img and gives the general mount partitions locations,. TWRP.fstab is mounted using the same partitions but different format/flag structure to be available to TWRP .
Techted89 said:
You need both from what iv read ,. TWRP.flags is a module that rewrites the stab at a certain point which may be the reason it's not compiling but I will post. Recovery.fstab is supposed to be a copy paste from the boot.img and gives the general mount partitions locations,. TWRP.fstab is mounted using the same partitions but different format/flag structure to be available to TWRP .
Click to expand...
Click to collapse
Interesting article above. Were you able to get that to work? I know it says MTK but seems like mechanism should be the same, or atleast I would assume anyways that the function would be very similar in the case of a flag. Was told you needed to use original kernel but then I couldn't get that to boot period. I'm out of my area of knowledge at this point but always willing to learn.
Also I tried messing around a little with the f stab and TWRP flags I was told that TWRP flags is pretty much the same as the twrp.fstab... also this build needs to have something added to the drivers I do believe that this is somehow related to USB touch it is a goodix gt9886 touch panel using the Samsung 9886 drivers. Maybe the init's need some help here as well.
I have the programming knowwledge that TWRP would require, but have not as of yet created one as my devices were typically readily complete before-hand. Once my device is back up, and running I am going to boot into Ubuntu and give it a go.
I need some excuse to have learned assembly x86, c, c++, Java, Python, and rust and have been eyeing learning scripting so it could be a fun side project assuming it is still incomplete as of the moment?
Is it normal for manufacturers to use components from other's in their builds? The kernel posted seemed to indicate at least a couple Samsung files included.
Well C is a guarantee possibly some C++ as well and definitely some sh scripting if you know rust and know how to attach it to C well enough that could add more possibilities I would imagine. The recovery is from my understanding in the boot image Android Image Kitchen would help you see it unmodified if that is the case.
I found a unofficial TWRP that flashes to the boot partition, and works pretty damn well, id have to say! I am not an experienced developer, I just like to flash around on my phone in my spare time.. Anyways here y'all go:
I am down while I got partitions backed up to the cloud.