i think yes....bl unlocked warning screen is there on rebooting after failure of fastboot during flashing recovery(twrp or rwrp)
[RECOVERY][X00T] KudProject's Unofficial TWRP 3.4.0-0 [16-06-2020]
- Thread starter krasCGQ
- Start date
Do you try using different usb port? And make sure DON'T use usb3 port
i tried with usb 2.0 and usb 3.0 both..same result in both port......i also changed cables...but no result,,,gimme solution pls
It was new notebook problem. With an old usb-hub worked like a charm.
This just an FYI:
There have been 2 TWRP (unofficial?) releases recently for X00T/X00TD. Found one (v3.4.0-0, released 08-June-2020) on Telegram forum and the other on AndroidFileHost (v3.3.1-0, released 17-May-2020). In both, the native File Manager shows the contents of /system. But, - even after rebooting recovery and mounting /system - Aroma File Manager (run by flashing .zip file) does not. Also, USB OTG does not get mounted in v3.4.0-0. (BTW, both issues are not present in OrangeFox R10.1_6.) If anyone finds workarounds for both the above issues, please post here.
There have been 2 TWRP (unofficial?) releases recently for X00T/X00TD. Found one (v3.4.0-0, released 08-June-2020) on Telegram forum and the other on AndroidFileHost (v3.3.1-0, released 17-May-2020). In both, the native File Manager shows the contents of /system. But, - even after rebooting recovery and mounting /system - Aroma File Manager (run by flashing .zip file) does not. Also, USB OTG does not get mounted in v3.4.0-0. (BTW, both issues are not present in OrangeFox R10.1_6.) If anyone finds workarounds for both the above issues, please post here.
This thread and its contents is long dead. And Who build that 3.4.0 version?
Which is the best recovery currently for the device
check the screenshot.
Attachments
-
IMG-20200612-WA0059.jpg
OrangeFox R10.1_6 is what i use and it gets the job done always.
Are pixel experience ota updates supported on this recovery
And please provide the forum link for the same
check the screenshot.
Attachments
-
IMG-20200612-WA0072.jpg
Orfox
---------- Post added at 09:13 PM ---------- Previous post was at 09:09 PM ----------
Oh he's the one who built it. Thanks again
I am having issues with the MTP whenever I select file transfer the device doesn't show up in the file system but on linux lsusb indicates the device is connected I got a workaround by going into twrp and then enable and disable MTP but after using orfox the workaround doesn't help I can't connect my device to pc as MTP anymore
Digging into orfox logs I found this error
E:|MTP] Failed to start usb driver!l
Can anybody tell me why is this happening is this an issue with the rom or the device itself.
Digging into orfox logs I found this error
E:|MTP] Failed to start usb driver!l
Can anybody tell me why is this happening is this an issue with the rom or the device itself.
R10.1_6-stable
But these MTP issues are happening irrespective of the recovery or rom I think it has something to do with the drivers on the phone
But these MTP issues are happening irrespective of the recovery or rom I think it has something to do with the drivers on the phone
Last edited:
I only support my own builds. That sounds OrangeFox to me.
Sent from my MI 9 SE using XDA Labs
Request to make a new TWRP
OrangeFox-R10.1_7-Stable-X00T.zip does not mount USB OTG (tried many ways mentioned at several places on the Internet) - neither in recovery nor in booted ROM. My post here might be of relevance. Screenshot added for additional reference. Wonder if the device tree is the cause of the issue. Reverting to OrangeFox-R10.1_6-Stable-X00T.zip restores USB OTG functionality.
Posting here only to request @krasCGQ to make a new TWRP with the latest recovery changes / commits, decryption ability etc., while retaining full USB OTG functionality. I believe the latter is important to many people. Many thanks in advance.
OrangeFox-R10.1_7-Stable-X00T.zip does not mount USB OTG (tried many ways mentioned at several places on the Internet) - neither in recovery nor in booted ROM. My post here might be of relevance. Screenshot added for additional reference. Wonder if the device tree is the cause of the issue. Reverting to OrangeFox-R10.1_6-Stable-X00T.zip restores USB OTG functionality.
Pushed one, but I limit it temporarily at Telegram scope for wider testing. Decryption as always only works on latest stock as well as custom ROMs with same security patch as TWRP.
I'll publish here in few days so stay tuned in that case.
Sent from my MI 9 SE using XDA Labs
waiting to try your new twrp. just a couple of questions; hope you'll address them in the new twrp and post in the thread.
(1) does usb otg work - both in recovery and booted rom - with your soon-to-be-released twrp?
(2) how about full nandroid backup and *full* restore - do they both work flawlessly? i always face bootloop while doing *full* restore of nandroid backup. restoring data alone works sometime. is there a proper workaround?
(2)after u restore full backup..dirty flash same rom to resolve boot loop
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
61
[SIZE=+1]This is basically a tl;dr thread.
I don't want to make a thread that everyone will lazy to read.[/SIZE]
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. 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.
[SIZE=+1]Disclaimer[/SIZE]Code:/* * Your warranty is... still valid? * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this RECOVERY * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. */
[SIZE=+1]Requirements[/SIZE]- ASUS ZenFone Max Pro (M1) ZB601/2KL (of course)
- Unlocked bootloader, in either ways (official, unofficial)
- Some knowledge on how to deal with your device... and patience.
[SIZE=+1]Flashing Instructions[/SIZE]I assume you've done (very) basic steps on preparing to flash your device.
- Reboot device to bootloader. If device is powered off, press and hold Power + Volume Up button until ASUS logo with "FASTBOOT MODE" message appears.
- Under same directory as TWRP image and ADB/Fastboot executables (if ever required), type this command:
Where x and y are version of TWRP you're going to flash.Code:fastboot flash recovery twrp-3.x.x-y-KudProject-X00T.img - IMPORTANT: After flashing, immediately press and hold Power + Volume Down for about 10 seconds button to reboot to recovery.
- Swipe the option to allow modifications. This way, you'll trip Android Verified Boot (AVB) and it's required to flash no verity zip in order to be able to boot stock ROM.
[SIZE=+1]Downloads[/SIZE]
Webserver | MEGA
Old releases only: OSDN | AndroidFileHost
[SIZE=+1]Known Issues[/SIZE]- Due to QTI keymaster's behavior, only specific stock firmware as well as custom ROMs with same platform security patch level that can only be decrypted by TWRP. Applicable versions will be indicated explicitly in the changelog.
[SIZE=+1]Special Thanks[/SIZE]- Dees_Troy and everyone behind TWRP
- shakalaca - base device tree used for older releases
- Ankit Gourav - his work on whyred
- Shivam Kumar Jha - person who kickstarted ZenFone Max Pro (M1) development
- Everyone involved in testing numbers of test builds.
[SIZE=+1]Device Sources[/SIZE]
XDA:DevDB Information
Unofficial TWRP 3.x (X00T), Tool/Utility for the Asus ZenFone Max Pro M1
Contributors
krasCGQ
Source Code: https://github.com/KudProject/bootable_recovery-twrp
Version Information
Status: Stable
Current Stable Version: 3.4.0-0-KudProject
Stable Release Date: 2020-06-16
Current Beta Version: 3.3.0-0-20190513
Beta Release Date: 2019-05-13
Created 2019-01-09
Last Updated 2020-06-2824[SIZE=+1]Some stuffs...[/SIZE]Another TWRP thread? Why?
I like to keep discussions about my builds separate. Moreover, the existing TWRP that already available on XDA before doesn't seem to be maintained anymore.
I flashed via fastboot but it always fails.
Check or change your cable, use other USB slot (especially 2.0 one if 3.0+ doesn't work), or if needed try to flash recovery with USB connected to a hub.
[SIZE=+1]Changelogs[/SIZE]twrp-3.4.0-0-KudProject-X00T
- Merged TWRP source changes up to 11 June 2020 (UTC+8)
- Can decrypt 16.2017.2005.082 stock firmware and any custom ROM with 5 May 2020 security patch
- Switched f2fs-tools to latest AOSP master
- Only allow user to backup system and vendor images
- set_version script doesn't longer touch persist partition; script now has hardcoded SKU and version instead in case ASUS props can't be found
- Updated prebuilt kernel based on S082 source drop
- F2FS kernel driver updated to 5.3-rc1 with backports up to 5.7-rc1 from 4.9
- Switched to arter97's fork of exFAT
- Switched from NTFS kernel driver to FUSE ntfs-3g due to incomplete write support
15[SIZE=+1]Notes[/SIZE]- "fastboot boot" command isn't supported by our bootloader. Don't ever try that. (blame ASUS/Huaqin)
I'll try to always keep this recovery updated especially when ASUS releases firmware update that also updates AOSP security patch. Security patch set in TWRP needs to match stock firmware used so TWRP can decrypt data partition.This isn't possible with current state as the bump is useless.
[SIZE=+1]Unmodified Stock Firmware Support[/SIZE]With introduction of unmodified stock firmware support, I need to clear up some confusions you've if any. Notes below are copy-pasta from my post elsewhere:
Code:Starting this build, recovery supports flashing stock firmware without modifying the updater-script. In order for it to be possible, ro.product.device has to be set to ASUS_X00TD. This, however, breaks flashing of custom ROMs that check for either X00TD or X00T. Simply supporting it doesn't mean that you can flash stock firmware directly; you need to be at least on stock when you flash the recovery, so required properties can be exported to /persist which then will be set on every recovery boot up. Still not sure though, as some ROMs check for ro.product.device and then fallback to ro.build.product for matching devices. Flashing incremental OTAs are supported but not recommended, since you'll most likely flash verity disabler at the minimum and get the flashing failed upon patching boot.
In plain text:
- The recovery has ro.product.device set to ASUS_X00TD that may break custom ROM flashing.
You need to be on stock before booting the recovery for the first time,then afterwards you can flash any stock firmware. 21 June 2020 UPDATE: Now not required, as it's now hardcoded in the script itself and since touching persist is never a good idea to begin with.- If you modify your system in any ways and don't have any system backup to restore, don't flash incremental OTAs. This also includes TWRP tampering system to prevent stock recovery from overwriting TWRP.
[SIZE=+1]Verifying released builds[/SIZE]This was originally posted on KudProject's Telegram channel and copy pasted here with minor edits for easier access.
Following TeamWin's stance about unofficial TWRP downloads here, all release builds from KudProject will start to be signed using my GPG key to ensure that you get a copy of legitimate builds directly from me.
You can download both of my currently active public keys here. Importing from PGP keyserver will be made available in the future.
To import on Linux:
Code:gpg --import krascgq.gpg
To verify builds on Linux:
Code:gpg --verify <build-name>.sig <build-name>
Windows users will need to search for compatible tools.8As I've given X00T to my father and due to lack of testing on my further limited-testing builds, I decided to stop all further updates to the recovery.
I'll still keep this thread open for further discussion of my and Alex builds.
Sorry if this sounds disappointing but I've no further choice.
Sent from my MI 9 SE using XDA Labs
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone