Hello,
I have just compiled TWRP for my phone, but I got a lots of error, when I booted into the recovery.
I can't see sd card or internal storage when I want to flash something..
There are lots of errors like
"E: invalid block device on '/dev/block/bootdevice/by-name/system........"
" ', 'ext4', 59
E : invalid block device.."
How to fix that?
When I try to use the SDFix tool in Apps2SD I get this error message: "/storage/external_SD/Android/data/in.co.pricealert.apps2sd/files/platform.xml: open failed: ENOENT (No such file or directory)"
How can I fix this? Any help would be appreciated. Thanks.
NOTE: Decrypting data is not currently supported. MTP also does not work, but you can use adb to push and pull files.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.2.1-0:
-minui fixes (cryptomilk)
-Better android-8.0 compatibility in ROM trees (Dees_Troy)
-Fix missing library in android-8.0 (nkk71)
-Fix inconsistent SDCard naming (DevUt)
-Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
-Allow restoring adb backups in the TWRP GUI (bigbiff)
-Fix gzip backup error in adb backups (bigbiff)
-Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
-Better support for installing Android 8.0 based zips due to legacy props (nkk71)
-Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
-Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
-Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
-v2 fstab support (Dees_Troy)
-Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
-Various other minor bugfixes and tweaks
CHANGELOG for 3.1.1-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
NOTE: fastboot flash to recovery_ramdisk and not to recovery as this device does not have a regular recovery partition.
Device Page, Download Links, Mirrors:
https://twrp.me/huawei/huaweihonorview10.html
Download:
https://dl.twrp.me/berkeley
If you wanna backup your old recovery, if in-case anything goes wrong, just follow these steps.
1)Root your device with Magisk
2)In a local terminal app or in adb shell, type su and get a root shell.
3)Do
Code:
dd if=/dev/block/bootdevice/by-name/recovery_ramdisk of=/sdcard/recovery_ramdisk_bak.img
4)Now you can just use
Code:
adb pull /sdcard/recovery_ramdisk_bak.img
to copy the backup image file to your desktop.
5)If in-case anything goes wrong, just do
Code:
fastboot flash recovery_ramdisk recovery_ramdisk_bak.img
Thanks for the TWRP mate
EDIT - As soon as you flash the image, remove the USB cable from the device and press and hold VOL+ and Power button to get into recovery.
Many thanks to TWRP team, to bring us the TWRP Recovery.
@Dees_Troy I can't see a link for download, not listed yet at official site. I suppose we have to wait for a while
Thanks.... But can't see the link to download.
https://eu.dl.twrp.me/berkeley/
That's to the download page
Finally twrp is here
Thanks
Thanks for this. Nice work
Finally TWRP [emoji8][emoji8][emoji8][emoji8]
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 02:27 PM ---------- Previous post was at 01:35 PM ----------
Finally flashed TwRp now working fine [emoji7][emoji7]
Sent from my [device_name] using XDA-Developers Legacy app
Thanks to TWRP Team.
Now is there anybody installed xposed successfully using TWRP?
I tried to install it without TWRP and got bootloop. I'm too scared to do it again even using twrp. :crying:
.
netxking said:
Thanks to TWRP Team.
Now is there anybody installed xposed successfully using TWRP?
I tried to install it without TWRP and got bootloop. I'm too scared to do it again even using twrp. :crying:
.
Click to expand...
Click to collapse
Xposed is incompatible for now. Wait until rovo pushes a update and see if it's fixed then
Read more https://github.com/rovo89/Xposed/issues/310
He states also that it is same issues for mate 9 as well as honor view 10. Something in art of Huawei seems to cause issues
Sent from my DUK-L09 using Tapatalk
Is this working for Honor 9 Lite?
Hey, I managed to "not to take backup" of my stock recovery ...where can I download it?
Rj_Param said:
Hey, I managed to "not to take backup" of my stock recovery ...where can I download it?
Click to expand...
Click to collapse
You can't. Your stock recovery is gone if you didn't back it up to your device/cloud.
Sent from my Honor View 10 using XDA Labs
have flashed the recovery but cant see any zip files and i have nothing on my sdcard somehow. pls let me know how to fix this
i have a question, if i flash twrp, huawei erecovery could be disappear？
cstar patrick said:
i have a question, if i flash twrp, huawei erecovery could be disappear？
Click to expand...
Click to collapse
Yes
Enviado desde mi ONE A2003 mediante Tapatalk
---------- Post added at 07:58 AM ---------- Previous post was at 07:56 AM ----------
iTAZUETA said:
have flashed the recovery but cant see any zip files and i have nothing on my sdcard somehow. pls let me know how to fix this
Click to expand...
Click to collapse
Yes, data partition is not accessible because decryption issue
Enviado desde mi ONE A2003 mediante Tapatalk
cstar patrick said:
i have a question, if i flash twrp, huawei erecovery could be disappear？
Click to expand...
Click to collapse
Nope it won't. eRecovery is in a seperate partition, so even if you flash ramdisk, it won't get replaced. But the ordinary recovery would.
---------- Post added at 09:47 AM ---------- Previous post was at 09:30 AM ----------
Rj_Param said:
Hey, I managed to "not to take backup" of my stock recovery ...where can I download it?
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-view-10/development/stock-recovery-getting-to-stock-t3754797
when i used this recovery, it seems my phone couldn't mount the partitions.
When i flash the zip , it said
unable to mount partitions
-unmounting partitions
updater process ended with ERROR:1
ERROR installing zip file...
updating partitions details...
failed to mount /cache' (invalid argument)
failed to mount /cust' (invalid argument)
failed to mount /data' (invalid argument)
failed to mount /modem_secure' (invalid argument)
failed to mount /product' (invalid argument)
failed to mount /splash2' (invalid argument)
failed to mount /system' (invalid argument)
failed to mount /vendor' (invalid argument)
failed to mount /version' (invalid argument)...done
My phone is Huawei p10p, system is rr.
This twrp is only for Honor view 10.
Take a look into P10plus forum.
Hi,
i'm trying to install Magisk on my I9100, but i fails with error like (this was during the try to patch lineage boot.img within 14.1 with magiskmanager and lineage-su)
Code:
- Device platform: arm
- Extracting files
- Patch boot/ramdisk image: /dev/block/mmcblk0p5
- Unpacking boot image
MagiskBoot v16.3(1630) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
! Unable to unpack boot image
Failed!
! Installation failed
When flashing it the regular way from TWRP (3.1.0-0) i get a similar sounding error (Error 1).
I also tried the latest unofficial 3.2.1-0., but got the same error.
The PIT is changed to 1,5gb System and 6 GB Data.
Hi!
While adb sideload PixelExperienceAndroid10.zip on the end of flashing this error appears: kNewRootfsVerificationError
What can I do?
But... after reboot system Pixel Experience works fine.