Two possible scenarios:
(1) The problem could be that the data on your phone is encrypted. If you set up a pin to unlock your phone when it boots up you enter the same pin into TWRP. Then it can decrypt your data. If you cancel out of the password screen then TWRP doesn't have access to your data which is why you can't find your folder.
(2) In recovery, you might need to format data (not wipe data) - select menu "
wipe" then select "format data" and type YES. Once it's done, select back to main menu then select "reboot" select "recovery"Now, you enable MTP to mount your Internal Storage to Windows. You can transfer your zip files to install in TWRP
NB: This procedure will wipe the files that you have on Internal Storage.
In the OP:
- A12 support is still a WIP, but most things are working, A12 is all new, keep that in mind.
But it also lists A12 as not working. Which is it? Could someone edit the OP to be a bit more clear, because right now it reads as if A12 mostly works, but it's new and isn't fully supported yet. Then it's followed with a definitive A12 not working.
I'm not asking if TWRP with A12 works, but I can see how the wording in the OP would lead people to think at first glance that it mostly works.
- A12 support is still a WIP, but most things are working, A12 is all new, keep that in mind.
But it also lists A12 as not working. Which is it? Could someone edit the OP to be a bit more clear, because right now it reads as if A12 mostly works, but it's new and isn't fully supported yet. Then it's followed with a definitive A12 not working.
I'm not asking if TWRP with A12 works, but I can see how the wording in the OP would lead people to think at first glance that it mostly works.
I don't think you would be able to boot TWRP at all if the bootloader wasn't unlocked and allowed to run unsigned code.
Then I can not solve the problem, you try to format data directly, and then restart to enter TWRP
I'm not the one having the problem. You may want to tag whoever you were originally responding to instead of me. That may help them with the answers they're looking for.
yes, would also like to know what the OP means? is it mostly working? or is it a definitive NOT working?
That's not what's in question. The OP contains vague and conflicting information about A12.
The way I understand the OP is that the list of what's working is for A11 while the work in progress bit is for A12.
I'm in the same camp, but that OP is worded in a way where someone could very easily think that most things in A12 are working, but it's an overall WiP.
I only brought it up a couple days ago because I've seen at least a couple posts asking if A12 was supported. Rewording that bit could seriously cut back on the confusion of newbies.
Genius.
Anyway, isn't there anyone so brave to try and tell us what's working on A12?
well for aosp a12 roms or oos12/cos12(dont know them) roms use losrecovery or pixelrecovery to clean flash for the first time with sideloading. For ex. Evox A12L has a custom recovery which supports adb sideload, wipe and other stuff, havent seen one which can decrypt data on A12.
Last time i tried latest twrp in here, i booted it but like i said above, it didnt decrypt data on oos12 or aosp12/12.1
You can see the flashing steps/guide for each rom. Evox says boot recovery then sideload the rom, PE has it's own recovery too if im right. In summary roms use custom recoveries but those cant decrypt data. only flash/sideload stuff.
just flashed the latest beta 12. but I keep coming back to the recovery when I reboot. How do I reboot back to system? still on Android 11, not 12
somehow my storage is not mounted. and i when i select storage, it shows internal storage (0MB).
Please help! Much thanks
somehow my storage is not mounted. and i when i select storage, it shows internal storage (0MB).
Please help! Much thanks
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
10
1. The A12 kernel source is incomplete (missing various things like touch panel driver and techpack)@infected_ now that the kernel source of 12.1 is out, will there be A12 support finally
?
2. It doesn't work like that. The encryption/decryption algorithm in A12 has yet to be implemented correctly into any 3rd party recovery. And this is for all android devices running 12, not just op8 series.
Update: As of last night, enough of the kernel source has now been released to start the oplusification of 8 series. However this still doesn't change anything regarding the encryption algo in A12 from being implemented in twrp. -
61TWRP for OnePlus 8 and 8 Pro
TWRP is an open source, community project. TWRP development is done by a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers, and zulip-chat.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM".
Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no responsibility for any damage that may occur from installing or using TWRP.
Code:#include /* * * Yea, though I walk through the valleys of c++ and java, of the shadow of death on these forums, * I will fear no evil and i will develop and code restless: for thou art with me and my keyboard; * thy rod and thy staff they comfort me, and my mouse.. * */
A12 support is still a WIP, but most things are working, A12 is all new, keep that in mind.
WORKING:
Decryption
ADB Sideload
Format Data
Flashing zips (kernels and ROM's)
Backup/Restore
MTP is working
adb is working
vibration
stock firmware flashing
OTG
NOT WORKING
wip
A12
Download
:: SourceForge ::
:: AndroidFileHost ::
Instructions
Windows
Install oneplus usb driver, after disabling driver signature enforcement
Download and install platform tools, unzip and add the folder to Windows path,
"Settings > Advanced System Settings > Environment Variables > New"
Example -> http:///imgur.com/a/x8XOofQ
open command prompt, or powershell, and:
fastboot flash recovery_a twrpname.img
fastboot flash recovery_b twrpname.img
Linux
Download and add to path (.bashrc) platform-tools:
export PATH=$HOME"/platform-tools:$PATH"
dont forget udev rules if you're using ubuntu based distro:
https://github.com/M0Rf30/android-udev-rules
open a terminal and:
fastboot flash recovery_a twrpname.img
fastboot flash recovery_b twrpname.img
that's all.
Source Code:
https://github.com/infectedmushi/android_device_oneplus_instantnoodle-dev
https://github.com/infectedmushi/android_bootable_recovery
https://github.com/bigbiff/android_device_oneplus_instantnoodle
https://github.com/TeamWin/android_bootable_recovery
https://github.com/systemad/android_device_oneplus_instantnoodle
Credits:
@bigbiff
@Lossyx
@Captain_Throwback for original tree
@mauronofrio for original tree
TWRP team23uploaded beta 6.
changelog:
* Add custom kernel for recovery
* crypto: only set crypto state and type if not already set
* crypto: only show FBE error if device is encrypted
* digest: fix checking of digest on restore
* fs_mgr: allow deleting merged snapshots
* merges: allow user to perform snapshot merges in advanced menu
* mtp: don't create storage device after format data
* recovery: Allow kernel to read and write unlabeled files
* repacker: add root overwrite warning
regards.23uploaded beta 3. it's possible now to backup persist partition also.
twrp-op8-3.6.0_11-infected-b3.img
twrp-op8-3.6.0_11-infected-b3.zip
* 0c94cd7 - fstab: it's now possible to backup persist partition.
* b99d112 - module load: Try loading prior modules first
* 5ab53dc - libresetprop: use the latest header
* 60927bc - kernel_module_loader: Set a prop after completing
* 3a95d18 - fscrypt v1: support legacy ioctl
* 540c802 - build: add option to create recovery installer zip
* 7284ace - vndk: remove exclusion in recovery
* aa2f760 - update_engine: handle payload that contain xbl_lp5 partitions
* f1db62e - libresetprop: update to magisk HEAD
* b65b045 - soong: Add TARGET_LEGACY_HW_DISK_ENCRYPTION conditional
regards.22uploaded beta 8.
* sdcard: only bind mount sdcard after successful preparation of data
* Add TW_QCOM_ATS_OFFSET flag to manually set time/date offset
* System_Property_Get: Allow specifying multiple prop file paths
* update RECOVERY_INSTALLER_PATH to proper path
* fastbootd: Check for and run startup script if script exists
* Adding TARGET_OTA_ASSERT_DEVICE flag for custom device asserts
* theme: move TW_THEME_VERSION to variables.h
* theme: clean up TW_THEME_VERSION shell command
* prebuilt: update magiskboot to v24.1 stable
regards.
