Related
PREAMBLE
Team Win Recovery Project 2.x, or twrp2 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.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* 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 image
* [B]before[/B] 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.
*/
I'll keep this thread short and simple. Want a changelog or a list of features? Then visit teamw.in.
Want to see screenshots? They can be found here.
DOWNLOAD
You can always get the latest build from here.
INSTRUCTIONs
The builds can be flashed using an existing recovery. However, should you be unable to flash that ZIP (it seems like CM recovery can't flash it) then do the following:
Download the latest TWRP nightly build and extract the recovery image (recovery.img)
Put the file on the root of your internal storage (e.g. by doing "adb push recovery.img /sdcard")
Use a Terminal Emulator on your phone or connect your device to your PC (type "adb shell" in that case) and run the following commands:
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
It doesn't work... Plox halp, dev?
There's absolutely nothing I can do without logs. Do the following:
Code:
adb pull boot.txt
adb pull tmp/recovery.log
Pull the these two files and post them here (also mention what ROM you currently use!) - otherwise your post will be ignored.
XDA:DevDB Information
TWRP for Sony Xperia Z, Tool/Utility for the Sony Xperia Z
Contributors
Olivier
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2014-12-24
Last Updated 2015-04-11
HALP?
In some cases, TWRP won't work because the buffer for uncompressed ramdisks is too small (in the extract_elf_ramdisk binary) - is this my fault? NO! - Ask your ROM dev to cherry-pick these patches: gerrit.omnirom.org/#/q/topic:fusion3-twrp
Example:
Code:
RECOVERY BOOT
ANDROID! format...
Offset: 6137856
Size: 4961834
gunzip error -- Err:inflate -5
Failed to gunzip
cpio: logo.rle not created: newer or same age file exists
cpio: sbin/busybox not created: newer or same age file exists
8735 blocks
The problem is with the boot.img - I have already fixed that in OmniROM, Slim and my HodorKernel. Plus everyone who has flashed MultiROM isn't affected either.
Should your ROM dev be too lazy or just not willing to fix it in his ROM, flash this hack. It will serve you well for now.
Hi, I cant get this to work with CM 12 by infected. Official twrp 2.8.0.1 works, if I flash this one CM recovery shows up.
This is my boot.txt
Wed Dec 24 12:02:04 GMT 2014
ANDROID BOOT
cpio: logo.rle not created: newer or same age file exists
2354 blocks
__bionic_open_tzdata_path: ANDROID_DATA not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
__bionic_open_tzdata_path: ANDROID_DATA not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
__bionic_open_tzdata_path: ANDROID_DATA not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
Wed Dec 24 12:02:07 GMT 2014
I cant find tmp/recovery.log
Is it located somewhere else?
infected_ said:
check your PM box... log is there.
and you really want to go down that road again?
Click to expand...
Click to collapse
Yes, you sent me the log after I had literally begged you to do so. Just wanted to let you know that what you did was wrong.
infected_ said:
check your PM box... log is there.
and you really want to go down that road again?
Click to expand...
Click to collapse
Oliver has got a point. Your messages were rude whilst he was trying to help. Not hard to apologise...
Sent from my Xperia Z using XDA Free mobile app
infected_ said:
Its not working for me on the FOTAKernel, here you have the log: boot.txt, and its better to mention on OP that dd command needs to be run as root ("adb root" before "adb shell" or "su" after "adb shell")
regards..
edit:
trying now;
https://github.com/omnirom/android_...mmit/2c51477bc064e52e4095ecae6df1dbe0dfcb5849
i'll let you know it a bit if it worked.
edit2:
awesome. its working, in the link below is latest infected yuga cm12 boot.img, compatible with TWRP 2.8.3.0 ..
https://www.mediafire.com/?9vnr7t9dmoysqau
thanks to @Olivier for figure it what was wrong.
Click to expand...
Click to collapse
Hi, thank you guys for figuring that out. Where is the difference between oliviers twrp build and the official one? Does the offical twrp build boot with this fix too?
@infected_ taking no prisoners :')
Beans
infected_ said:
you didnt liked that i stated that you toke screenshots of the recovery flashed on "boot" and not FOTAKernel, and saying to everybody that is working?! yes, i did call you a cheater, because exactly what you did
Click to expand...
Click to collapse
Well, look at the date the commit was made - 26 September. This means I had figured this out a good while before I tried building TWRP 2.8.3.0, because that patch was intially needed for MultiROM TWRP. Hence, your argument is invalid, I didn't even need to "cheat" - why would I want to do that? I just didn't know TWRP had become this big as well and because my ROMs and kernels always include that commit, I hadn't noticed, whereas your build lacked it - you therefore assumed my build was broken and started attacking me. Does it make sense now?
hutilicious said:
Hi, thank you guys for figuring that out. Where is the difference between oliviers twrp build and the official one? Does the offical twrp build boot with this fix too?
Click to expand...
Click to collapse
The difference is that my build works. And no, IIRC the official build has another problem.
The recovery worked on his device because all of the kernels he builds have had that commit included since September. When you provided your logs it pointed to the fact that your kernel also needed it. Is there a language barrier here or something?
Also, Olivier can hardly be blamed because of something Team Win are responsible for.
You're obviously an intelligent person, but this is dragging on too far. Take a breath, realise you made a mistake and move on.
Sent from my C6603
I'll explain it as best I can:
Your first mistake was accusing him of cheating everyone by flashing the recovery.img on boot to get screenshots.
The recovery worked properly on his own device, therefore he obviously didn't need to do that.
You then later tried flashing it with commands that don't work on this device and to a location that doesn't even exist and blamed Olivier when it didn't work.
From this post:
Code:
[email protected]:/ # dd if=/sdcard/twrp-2.8.3.0-yuga.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
21680+0 records in
21680+0 records out
11100160 bytes transferred in 0.690 secs (16087188 bytes/sec)
This device doesn't have a recovery partition. Flashing to that location will have no effect.
Proof:
Code:
[email protected] ~/Desktop $ sudo fastboot flash recovery twrp-2.8.3.0-yuga.img
[sudo] password for infected_:
sending 'recovery' (10840 KB)...
OKAY [ 0.354s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.356s
[email protected] ~/Desktop $ sudo fastboot flash FOTAKernel twrp-2.8.3.0-yuga.img
sending 'FOTAKernel' (10840 KB)...
OKAY [ 0.343s]
writing 'FOTAKernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.345s
[email protected] ~/Desktop $
Those fastboot commands aren't allowed on the yuga.
Edited as I read this back today and it was a bit abrupt. Apologies if it seemed so as that wasn't the intent.
Sent from my C6603
See edits to my post above.
Bye.
Sent from my C6603
Please stop all this useless drama...to get back on this thread's use :angel:
Unfortunetly im still on non booting twrp, i indeed applied that twrp-ify and this one too and using latest bootable recovery from omni repos.
yeah i should have brought logs, but i have to leave again; so will bring some overnight or tomorro. Just wanted to know if i forgot something...i don't fell like to revert all commits to 2.0.8.x versions wich back then was working ok if im not mistaken.
thx =)
Looks like I'm a little late to the party
Nothing to see here it seems.....
(if there's any posts you both want deleted, PM me)
MD
Okay some news: As stated above, it's possible to compress the recovery ramdisk using LZMA to make it fit without using my extract_elf_ramdisk hack. As a result, the ramdisk-recovery.cpio file is now 3.6 MB big (TWRP 2.8.3.0).
I have pushed some commits to the OmniROM gerrit - before merging them, I'd like some of our devs to test and confirm it works.
Link: gerrit.omnirom.org/#/q/topic:fusion3-twrp
Thanks man...will give a go overnight or tomorro...and please, "some of our devs" ? lolz only 5 pple work on fusion3 so far x) hahaha
Will report asap.
ok while using latest bootable recovery repo from omni and your latest changes... (this patch is still applied idk if i must take it off)
facing this issue
Code:
----- Making recovery image ------
----- Made recovery image -------- /data1/sources/validus5/out/target/product/yuga/recovery.img
Install: /data1/sources/validus5/out/target/product/yuga/system/priv-app/Telecom/Telecom.apk
Construct recovery from boot
mkdir -p /data1/sources/validus5/out/target/product/yuga/obj/PACKAGING/recovery_patch_intermediates/
PATH=/data1/sources/validus5/out/host/linux-x86/bin:$PATH /data1/sources/validus5/out/host/linux-x86/bin/imgdiff /data1/sources/validus5/out/target/product/yuga/boot.img /data1/sources/validus5/out/target/product/yuga/recovery.img /data1/sources/validus5/out/target/product/yuga/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p
Copying: /data1/sources/validus5/out/target/common/obj/JAVA_LIBRARIES/services_intermediates/classes-jarjar.jar
Copying: /data1/sources/validus5/out/target/common/obj/JAVA_LIBRARIES/services_intermediates/emma_out/lib/classes-jarjar.jar
Copying: /data1/sources/validus5/out/target/common/obj/JAVA_LIBRARIES/services_intermediates/classes.jar
source and target don't have same number of chunks!
source chunks:
chunk 0: type 0 start 0 len 18069
chunk 1: type 2 start 18069 len 16081028
chunk 2: type 0 start 6145090 len 968
chunk 3: type 2 start 6146058 len 9553152
chunk 4: type 0 start 11520489 len 1559
target chunks:
chunk 0: type 0 start 0 len 18069
chunk 1: type 2 start 18069 len 16081028
chunk 2: type 0 start 6145090 len 2825150
make: *** [/data1/sources/validus5/out/target/product/yuga/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p] Error 1
make: *** Waiting for unfinished jobs....
target Java: ethernet-service (/data1/sources/validus5/out/target/common/obj/JAVA_LIBRARIES/ethernet-service_intermediates/classes)
DroidDoc took 22 sec. to write docs to /data1/sources/validus5/out/target/common/docs/api-stubs
/data1/sources/validus5/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld.gold: warning: hidden symbol '__system_property_get' in /data1/sources/validus5/out/target/product/yuga/obj/STATIC_LIBRARIES/base_base_gyp_intermediates/base_base_gyp.a(sys_info_android.o) is referenced by DSO /data1/sources/validus5/out/target/product/yuga/obj/lib/libcutils.so
/data1/sources/validus5/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld.gold: warning: hidden symbol 'SkBitmap::lockPixels() const' in /data1/sources/validus5/out/target/product/yuga/obj/STATIC_LIBRARIES/skia_skia_library_gyp_intermediates/skia_skia_library_gyp.a(SkBitmap.o) is referenced by DSO /data1/sources/validus5/out/target/product/yuga/obj/lib/libjnigraphics.so
/data1/sources/validus5/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld.gold: warning: hidden symbol 'SkBitmap::unlockPixels() const' in /data1/sources/validus5/out/target/product/yuga/obj/STATIC_LIBRARIES/skia_skia_library_gyp_intermediates/skia_skia_library_gyp.a(SkBitmap.o) is referenced by DSO /data1/sources/validus5/out/target/product/yuga/obj/lib/libjnigraphics.so
/data1/sources/validus5/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld.gold: warning: hidden symbol 'SkBitmap::notifyPixelsChanged() const' in /data1/sources/validus5/out/target/product/yuga/obj/STATIC_LIBRARIES/skia_skia_library_gyp_intermediates/skia_skia_library_gyp.a(SkBitmap.o) is referenced by DSO /data1/sources/validus5/out/target/product/yuga/obj/lib/libjnigraphics.so
#### make failed to build some targets ####
im using arm-linux-androideabi-4.8 from google with refs/tags/android-5.0.1_r1 and with cm cwm...its going ok
Alx31TLse said:
facing this issue
Click to expand...
Click to collapse
That error (wherever it is, I can't find it) doesn't seem to be related to my commit - TWRP 2.8.3.0 builds for me in CM11, Omin 4.4 and Omni 5.0.
Code:
----- Making recovery image ------
----- Made recovery image -------- /data1/sources/validus5/out/target/product/yuga/recovery.img
Means that it worked (possibly another commit causing the build error).
Olivier said:
That error (wherever it is, I can't find it) doesn't seem to be related to my commit - TWRP 2.8.3.0 builds for me in CM11, Omin 4.4 and Omni 5.0.
Code:
----- Making recovery image ------
----- Made recovery image -------- /data1/sources/validus5/out/target/product/yuga/recovery.img
Means that it worked (possibly another commit causing the build error).
Click to expand...
Click to collapse
Omni 5.0? Did you build it? If it is working mind sharing on XDA please?
Sent from my Xperia Z using XDA Free mobile app
Works fine! Just wondering why that the recovery provided by the official site doesn't work =/
Alx31TLse said:
facing this issue
Click to expand...
Click to collapse
Just got the same error while building SlimLP. It seems like it tries to generate a recovery_from_boot.p file when it shouldn't (TARGET_NO_SEPARATE_RECOVERY is set to true in device/sony/common). This commit should fix it: https://github.com/CyanogenMod/android_build/commit/651987c5f2f78207edebdd821d1700a0464fdfb5
EDIT: This commit doesn't fix it either. Strangely, the build only fails with "bacon" as a target, but not with "bootimage".
Gesendet von meinem Xperia Z mit Tapatalk
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
This is a continuation of the work by Shakalaca. Currently not much will be different. It does have however the latest security Patches. I will be splitting my time between CM 14.1 and Lineage 15. If you have questions please ask. The Z017 should work with both versions, I am running the Z012(KE552KL) and it seems okay.
Prerequisites:
TWRP
Unlock Bootloader
What Works?
- No Major Issues
What's broken ?
You tell me
Download Links
ROM:
https://drive.google.com/drive/folders/0B9R9sRY5L3uiM055Z3ZYeF9MXzA?usp=sharing
TWRP:
https://drive.google.com/drive/folders/0B9R9sRY5L3uidzNmTmpzSWthMTQ
GAPPS:
http://opengapps.org/
Special Thanks @anhenrique @shakalaca
Source Code:
https://github.com/LineageOS-Zenfone3
XDA:DevDB Information
LineageOS 14.1 for ZE552KL and ZE520KL, ROM for the Asus ZenFone 3
Contributors
basenode, basenode
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: Beta
Created 2017-08-31
Last Updated 2017-08-30
Changelog:
Aug 30 2017:
- Build Using Latest CM14.1 Sources (Android 7.1.2)
- Includes August Security Updates
I'll try it out sir. Considering I sat across from you for two days while you were dinkin around with it
Nice man Hope you can fix 60fps record bug
Is it 7.1.2?
sontranngoc said:
Is it 7.1.2?
Click to expand...
Click to collapse
Yes it is.
[email protected]
basenode said:
Yes it is.
Click to expand...
Click to collapse
Thank you. I'm installing. But why I cannot install a zip file from internal memory, it has no choice (I can do that with Xperia Z). I have to install by adb sideload instead.
sontranngoc said:
[email protected]
Thank you. I'm installing. But why I cannot install a zip file from internal memory, it has no choice (I can do that with Xperia Z). I have to install by adb sideload instead.
Click to expand...
Click to collapse
What Recovery are you using? I have TWRP and when I select install and navigate to /sdcard/ I am able to flash from internal
Can you insert ViperOS / ResurrectionRemix functions? How to lock the power menu and block fast access, both with the screen locked? This helps a lot when the cell phone is lost or stolen.
kiq1702 said:
Can you insert ViperOS / ResurrectionRemix functions? How to lock the power menu and block fast access, both with the screen locked? This helps a lot when the cell phone is lost or stolen.
Click to expand...
Click to collapse
I would like to keep this rom as stick as possible. I am open to Updating the existing ViperOS Rom for this device. I am one person so it might be difficult for me to support too many roms especially considering my personal desire to see oreo on this device. I will take a look @ Viper and see what I can do.
basenode said:
What Recovery are you using? I have TWRP and when I select install and navigate to /sdcard/ I am able to flash from internal
Click to expand...
Click to collapse
I cannot boot to TWRP:
fastboot flash recovery twrp-3.1.0-0-Z012-20170408-N.img
target reported max download size of 536870912 bytes
sending 'recovery' (21080 KB)...
OKAY [ 0.697s]
writing 'recovery'...
OKAY [ 0.135s]
finished. total time: 0.838s
...
..
fastboot reboot
rebooting...
finished. total time: 0.016s
After this command, the phone start normally, not into TWRP
---------- Post added at 01:54 PM ---------- Previous post was at 01:42 PM ----------
basenode said:
What Recovery are you using? I have TWRP and when I select install and navigate to /sdcard/ I am able to flash from internal
Click to expand...
Click to collapse
I can boot into TWRP, but after wipe cache, system, dalvik, i install the zip file, it shows the error:
Can't install this package on top of incompatible data
Updater process ended with ERROR: 7
Error installing file 'zip ......'
sontranngoc said:
I cannot boot to TWRP:
fastboot flash recovery twrp-3.1.0-0-Z012-20170408-N.img
target reported max download size of 536870912 bytes
sending 'recovery' (21080 KB)...
OKAY [ 0.697s]
writing 'recovery'...
OKAY [ 0.135s]
finished. total time: 0.838s
...
..
fastboot reboot
rebooting...
finished. total time: 0.016s
After this command, the phone start normally, not into TWRP
---------- Post added at 01:54 PM ---------- Previous post was at 01:42 PM ----------
I can boot into TWRP, but after wipe cache, system, dalvik, i install the zip file, it shows the error:
Can't install this package on top of incompatible data
Updater process ended with ERROR: 7
Error installing file 'zip ......'
Click to expand...
Click to collapse
Hi!
This will solve your problem.:
1- Open the ROM with Winrar;
2- Go to: META-INF -> com -> google -> android;
3- Run the "updater-script" file with Notepad ++;
4- Delete the first 1 line, save and update the file in ROM;
Update your TWRP from main Zenfone 3 folder: https://mega.nz/#F!kl8lmKRL!ZbLvz1b4YgLMr_n09vRrTA (twrp-3.1.1-0-Z017-20170826.img)
ToDream said:
Hi!
This will solve your problem.:
1- Open the ROM with Winrar;
2- Go to: META-INF -> com -> google -> android;
3- Run the "updater-script" file with Notepad ++;
4- Delete the first 1 line, save and update the file in ROM;
Update your TWRP from main Zenfone 3 folder: https://mega.nz/#F!kl8lmKRL!ZbLvz1b4YgLMr_n09vRrTA (twrp-3.1.1-0-Z017-20170826.img)
Click to expand...
Click to collapse
Thanks. I have installed successfully.
We have to remove 2 BELOW RED LINE, NOT FIRST 1 LINE:
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "/data", "");
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
The first line will check for products, I saw that line already included Z017 and Z012, it's not a problem.
sontranngoc said:
Thanks. I have installed successfully.
We have to remove 2 BELOW RED LINE, NOT FIRST 1 LINE:
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "/data", "");
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
The first line will check for products, I saw that line already included Z017 and Z012, it's not a problem.
Click to expand...
Click to collapse
Actually it depends on the program that you will use to edit, using Notepad ++ you delete only this line of verification.
Follows attached
RobinRo said:
Nice man Hope you can fix 60fps record bug
Click to expand...
Click to collapse
@kyle_l88 and I are working on it but I can't make and promises
Battery Issues
Hi, I am having a lot of battery drain from LineageOS. "LineageOS System" is taking 27% and "Android OS" is taking up 24%. I have battery optimization on for everything possible, and I have battery saving kick in at 25%. My location services are on battery saving, and Bluetooth and WiFi are off. I probably have a screen on time for 1 to 2 hours, so I should end the day with a lot more than I have. Also, double tap to wake isn't working for me as well.
So far everything seems pretty great. Had a couple force close issues. The camera certainly doesn't support 60FPS recording on 1080p yet. But i am working on that part of the code. Otherwise there seems to be few, if any, issues. High five! :good:
jyao6429 said:
Hi, I am having a lot of battery drain from LineageOS. "LineageOS System" is taking 27% and "Android OS" is taking up 24%. I have battery optimization on for everything possible, and I have battery saving kick in at 25%. My location services are on battery saving, and Bluetooth and WiFi are off. I probably have a screen on time for 1 to 2 hours, so I should end the day with a lot more than I have. Also, double tap to wake isn't working for me as well.
Click to expand...
Click to collapse
I am running it on a test device and and looking at the battery life. I'll leave it on tonight also to see how it does. I don't think this version has doubletap to wake. I know there is double tap on statusbar for sleep.
I added an issue here for tracking: https://github.com/LineageOS-Zenfone3/android_device_asus_Z017/issues/2
jyao6429 said:
Hi, I am having a lot of battery drain from LineageOS. "LineageOS System" is taking 27% and "Android OS" is taking up 24%. I have battery optimization on for everything possible, and I have battery saving kick in at 25%. My location services are on battery saving, and Bluetooth and WiFi are off. I probably have a screen on time for 1 to 2 hours, so I should end the day with a lot more than I have. Also, double tap to wake isn't working for me as well.
Click to expand...
Click to collapse
Did you wipe everything before installing or dirty flash over the shakalaca ROM?
basenode said:
Did you wipe everything before installing or dirty flash over the shakalaca ROM?
Click to expand...
Click to collapse
No, I did not wipe it. This problem was also present in the most recent ROM from shakalaca if that helps.
DisclaimerThis software comes with no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are not supported,only stock EMUI 8.x .
Download and Installation
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [name of the file].img --> ex: fastboot flash recovery_ramdisk twrp_clt_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features
Internal storage decryption = working (if it pin/password, pattern fails then try by removing them (password, pin, pattern, fingerprint) from Android before booting to TWRP.
MTP and OTG connection = working
Backup&Restore = working
Note: This was tested only by few P20 Pro owners,so if you test it,please report back!There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9 forum.
Credits
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
Download links
twrp_clt_0.1.img - Decryption support (you can use the same password/pin/pattern to decrypt in TWRP), /recovery_ramdisk not available for backup./vendor not available for backup (use /vendor_image instead)
Glad to see this. Any chance of sources or a pull request on my device tree to get decryption working?
hum.. it seem that decryption working great.
See :
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Yes. I was just asking for sources or a pull request on my Github repository. IMHO the decryption method used would be useful for anybody interested in ROM/Recovery development - and also required to comply with XDA licensing / GPL requirements.
a1Pha said:
Yes. I was just asking for sources or a pull request on my Github repository. IMHO the decryption method used would be useful for anybody interested in ROM/Recovery development - and also required to comply with XDA licensing / GPL requirements.
Click to expand...
Click to collapse
This is not based 100% from sources, i have another version with working decryption, which is based on open source tree, bur it's not ready yet, just private testing.
This is not breaking any GPL/XDA rule, because it's using just a dummy kernel, not compiled or modified by me! ?
Pretoriano80 said:
This is not based 100% from sources, i have another version with working decryption, which is based on open source tree, bur it's not ready yet, just private testing.
This is not breaking any GPL/XDA rule, because it's using just a dummy kernel, not compiled or modified by me! ?
Click to expand...
Click to collapse
Thanks for clarification. Would you mind sharing some details via PM with me? I'd be glad to improve my repo
a1Pha said:
Thanks for clarification. Would you mind sharing some details via PM with me? I'd be glad to improve my repo
Click to expand...
Click to collapse
Yes, no problem! Also have a look at my Github (pretoriano80). My goal is also to make a fully open source version. ?
Quote: Note: This was tested only by few P20 Pro owners,so if you test it,please report back!
Hi Pretoriano80, Hi All,
Great job ! Just installed... I confirm that it works on my CLT-L29 8.1.0.106(C432)
Internal storage decryption, MTP and usb OTG connection, Backup& Restore (incl /vendor_image) : All working !
Many thanks & Cheers
CLT-L09 (C782) all is working as it should, successful backup and mount of my 1tb hard drive.
Absolutely fantastic work
Thanks :good:
Well this is very positive.
Less than 2 calendar weeks from release to TWRP release.
I think we can possibly have pretty high expectations for development on the P20 Pro.
Hey im getting this when I attempt to run the fastboot flash recovery command:
C:\Users\andre\Desktop\twrp>fastboot flash recovery_ramdisk twrp_clt_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.151s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.171s
Can anyone advise please?
andrewglass3 said:
Hey im getting this when I attempt to run the fastboot flash recovery command:
C:\Users\andre\Desktop\twrp>fastboot flash recovery_ramdisk twrp_clt_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.151s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.171s
Can anyone advise please?
Click to expand...
Click to collapse
You have to unlock bootloader first!
Pretoriano80 said:
You have to unlock bootloader first!
Click to expand...
Click to collapse
Yep - I forgot that step - had the code but missed it out lol - Im an idiot lol
whats difference between your version and a1pha?
also does this trigger safety net? (i installed magisk via patched ramdisk.img and google pay wont work) will it work with TWRP (no root)
virtyx said:
whats difference between your version and a1pha?
also does this trigger safety net? (i installed magisk via patched ramdisk.img and google pay wont work) will it work with TWRP (no root)
Click to expand...
Click to collapse
Have you made sure that the Google Pay app is selected in the Magisk Hide list in the app? It doesn't tick automatically like it used to with Android Pay. You should pass safetynet with Magisk installed. Also, after flashing TWRP still passes safetynet too.
virtyx said:
whats difference between your version and a1pha?
also does this trigger safety net? (i installed magisk via patched ramdisk.img and google pay wont work) will it work with TWRP (no root)
Click to expand...
Click to collapse
TWRP has nothing to do with SafetyNet! Maybe you installed a firmware which didn't passed Google check yet.
Is this what I actually need to do to root my P20 Pro?
I unlock the bootloader, flash the twrp recovery, then install supersu.zip via twrp recovery and I'm done, right?
Or is there something else I left out?
Thank you very much so far!
m00h said:
Is this what I actually need to do to root my P20 Pro?
I unlock the bootloader, flash the twrp recovery, then install supersu.zip via twrp recovery and I'm done, right?
Or is there something else I left out?
Thank you very much so far!
Click to expand...
Click to collapse
Try Magisk instead of SuperSU. It has better support for Oreo than the latter.
BTW anyone here tried flashing Magisk to root the device?
DJBhardwaj said:
Try Magisk instead of SuperSU. It has better support for Oreo than the latter.
BTW anyone here tried flashing Magisk to root the device?
Click to expand...
Click to collapse
I did on the other TWRP thread, worked fine.
The page for getting an unlock code seems to 404 for me. Is this happening for anyone else too?
Hello all,
I am pretty sure my problem has nothing to do with Carbon ROM, but one of the symptom I have is the unability to perform OTA update from CR-6.1, I ask for help here instead of on the ROM thread in case someone experienced the same :
- I used TWRP to flash CR-6.1 on a Z3C with TWRP. I unlocked the bootloader and flashed the recovery using fastboot (fastboot flash recovery xxx.img).
- CR-6.1 was properly flashed, boots without issues, but then if I try to reboot on recovery from here (using the power menu), the phone just reboots, and won't go to TWRP. Then it seems logical that when it tries to reboot on recovery to perform the OTA update it fails, since it just reboots to CR.
- My only was to access recovery is to press the down volume button while powering it up : It boots to TWRP successfully
- But then, if I try to manually flash the .zip file downloaded by the OTA, I get an error message (error 7): The devicename does not match, TWRP (official release 3.0.2-1) detects the phone as "". Note that with unofficial release 3.2.3-0 found here I get no error 7 message : The manual flash is successful.
I checked other posts here on XDA, one solution would be to just modify the device name in the .zip, then it works but I wonder if all these are not a symptom of an incorrect TWRP flash as recovery. I tried to reflash it from TWRP, unfortunately, it only proposes me to flash to boot. Flash to recovery is not available.
Thanks for your help!
Lionel
I'm dealing with this exact problem on my wife's phone. I've made progress though. First up, boot into bootloader, "adb reboot booloader", then boot into recovery, making sure you have a suitable twrp image on your desktop, "fastboot boot twrp-3.2.3.img". Now you're in TWRP, which is where I now am. I'm going to wipe the recovery partition, boot back into the bootloader and flash recovery. Let's see how that goes.
---------- Post added at 11:29 AM ---------- Previous post was at 10:59 AM ----------
Ignore the above, got it working. It seems that the version of CarbonRom is playing funny for some reason. Here's the recipe to fix things:
- On the phone, check and download the latest CarbonRom. Don't flash it.
- Run "adb reboot bootloader"
- Run "fastboot boot twrp-3.2.3.img"
- In TWRP, install the latest CarbonROM from sdcard/CarbonDelta
- Reboot
- Reboot back into bootloader, "adb reboot bootloader"
- Flash recovery, "fastboot flash recovery twrp-3.2.3.img"
- Run "fastboot reboot"
Everything is back the way it should be.
Good Morning,
I am the dev of the LineageOS 16 builds for this device and i have been working on a new TWRP tree. Therefore i have found some things according to you problem.
First of all we should make the basics clear: On our Z3 Compact we have got a bootloader update which can boot a recovery from powered off state by pressing volume down and the power button. Because we haven't ever had this updated bootloader and not all sony devices received the update, there have been some intelligent people who brought a special init binary which can handle recovery boots during a normal boot. This means when using advanced reboot from the ROM or pressing a volume key while the sony logo appears at boot. https://github.com/LineageOS/android_device_sony_common/commits/lineage-16.0
To make this work there is this binary to extract the ramdisk: https://github.com/LineageOS/androi...eage-16.0/extract_ramdisk/extract_ramdisk.cpp which uses zlib to decompress it. So far so good, zlib can decompress the default compression for recovery ramdisk which is gzip. However LZMA is more effective to reduce the size so we took it's advantage: https://github.com/omnirom/android_...mmit/885b01223a460d3f2500155ea415bdc8573679bc in order to fit recoverys compiled from recent environments (android-9.0 in my case) into our small FOTAKernel partition.
According to this change the init_sony can't handle the recovery boot anymore because it can't decompress the recovery's ramdisk so nailyk and Diewi (as far as i know) added support to decompress LZMA compressed ramdisk's with this chain: https://github.com/sonyxperiadev/device-sony-common-init/pull/20/commits
However these commits have never been merged into the LineageOS/android_device_sony_common nor the sonyxperiadev/device-sony-common-init. Since your ROM, CarbonROM, is using a fork of LineageOS/android_device_sony_common is missing these commits the recovery boot fails with a kernel panic, like this: https://del.dog/egawososux.htm
So you can either use a recovery which doesn't compress the ramdisk with LZMA (for example the one from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192 or ask your ROM developer to pick the according commits into the sony_common tree/use my fork of LineageOS's one https://github.com/z3c-pie/android_...mits/fa85dfcc07f42d73f9a1abf1f4c82d8bf0486a93 which would enable you to use recent TWRP builds with a LZMA compressed ramdisk.
I hope i presented it clearly and in the right way,
Have a nice day!
EDIT: Minimized patch for LZMA is available here: https://review.lineageos.org/c/LineageOS/android_device_sony_common/+/252923
NeoArian said:
Good Morning,
I am the dev of the LineageOS 16 builds for this device and i have been working on a new TWRP tree. Therefore i have found some things according to you problem.
First of all we should make the basics clear: On our Z3 Compact we have got a bootloader update which can boot a recovery from powered off state by pressing volume down and the power button. Because we haven't ever had this updated bootloader and not all sony devices received the update, there have been some intelligent people who brought a special init binary which can handle recovery boots during a normal boot. This means when using advanced reboot from the ROM or pressing a volume key while the sony logo appears at boot. https://github.com/LineageOS/android_device_sony_common/commits/lineage-16.0
To make this work there is this binary to extract the ramdisk: https://github.com/LineageOS/androi...eage-16.0/extract_ramdisk/extract_ramdisk.cpp which uses zlib to decompress it. So far so good, zlib can decompress the default compression for recovery ramdisk which is gzip. However LZMA is more effective to reduce the size so we took it's advantage: https://github.com/omnirom/android_...mmit/885b01223a460d3f2500155ea415bdc8573679bc in order to fit recoverys compiled from recent environments (android-9.0 in my case) into our small FOTAKernel partition.
According to this change the init_sony can't handle the recovery boot anymore because it can't decompress the recovery's ramdisk so nailyk and Diewi (as far as i know) added support to decompress LZMA compressed ramdisk's with this chain: https://github.com/sonyxperiadev/device-sony-common-init/pull/20/commits
However these commits have never been merged into the LineageOS/android_device_sony_common nor the sonyxperiadev/device-sony-common-init. Since your ROM, CarbonROM, is using a fork of LineageOS/android_device_sony_common is missing these commits the recovery boot fails with a kernel panic, like this: https://del.dog/egawososux.htm
So you can either use a recovery which doesn't compress the ramdisk with LZMA (for example the one from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192 or ask your ROM developer to pick the according commits into the sony_common tree/use my fork of LineageOS's one https://github.com/z3c-pie/android_...mits/fa85dfcc07f42d73f9a1abf1f4c82d8bf0486a93 which would enable you to use recent TWRP builds with a LZMA compressed ramdisk.
I hope i presented it clearly and in the right way,
Have a nice day!
EDIT: Minimized patch for LZMA is available here: https://review.lineageos.org/c/LineageOS/android_device_sony_common/+/252923
Click to expand...
Click to collapse
Hi NeoArian,
I've been away for a while and have just gotten back to playing with the z3c. I still have problems but that may just be my misunderstanding of things.
When the phone is in the bootloader, I update FOTAKernel thus:
Code:
fastboot flash FOTAKernel twrp-3.3.1-0.3-z3c.img
target didn't report max-download-size
Sending 'FOTAKernel' (13264 KB)...
OKAY [ 0.419s]
Writing 'FOTAKernel'...
OKAY [ 0.885s]
Finished. Total time: 1.322s
And update recovery too:
Code:
fastboot flash recovery twrp-3.3.1-0.3-z3c.img
target didn't report max-download-size
Sending 'recovery' (13264 KB)...
OKAY [ 0.421s]
Writing 'recovery'...
OKAY [ 0.878s]
Finished. Total time: 1.318s
Yet I'm unable to boot into recovery.
From the bootloader, I this is what I see if I try boot directly into recovery:
Code:
fastboot boot twrp-3.3.1-0.3-z3c.img
Downloading 'boot.img'
OKAY [ 0.419s]
booting
FAILED (remote: dtb not found)
Finished. Total time: 0.499s
I've read through quite a bit of the forum notes but still am no wiser. I do however much admire your work and that of others and the time you spend helping others.
Fudgemond said:
Hi NeoArian,
I've been away for a while and have just gotten back to playing with the z3c. I still have problems but that may just be my misunderstanding of things.
When the phone is in the bootloader, I update FOTAKernel thus:
Code:
fastboot flash FOTAKernel twrp-3.3.1-0.3-z3c.img
target didn't report max-download-size
Sending 'FOTAKernel' (13264 KB)...
OKAY [ 0.419s]
Writing 'FOTAKernel'...
OKAY [ 0.885s]
Finished. Total time: 1.322s
Click to expand...
Click to collapse
I now think this isn't correct. Work I've done on another phone (Xperia Z) suggests that unpacking CarbonROM and extracting the boot.img is what I should flash to FOTAboot. Something to try.
Did you manage to get twrp to work again? I want to move away from CR6.1 to LOS16 or 17 (just to give it a try), but I'm stuck now.
I am trying to flash an Android 12 GSI onto my Samsung Galaxy Tab Active3. Goal is to install the GSI without root / voiding the warranty. My company produces an app which is primarily used on Android on Galaxy Tab Active devices. It's expected Galaxy Tab Active3 will get Android 12 update in the next few months and we wanted to do some regression testing in advance of that. Hence the need to get Android 12 GSI onto the Tab Active3.
Device is an arm64 so I downloaded the arm64+gms version of Android 12 GSI (from Google's website). I have successfully unlocked the bootloader, and enabled DSU support. The device supports Project Treble and the VNDK isolated namespace, so in theory should support GSIs.
Everything I tried so far has failed. Any ideas to get it working?
Manual DSU
I have tried to install the GSI by manually starting the DSU via activity manager ("am start-activity -n com.android.dynsystem/com.android.dynsystem.VerificationActivity..." etc). Every time it just says "Installation failed" after reaching about 50% progress. I have tried setting different sizes for the USERDATA: 8GB (Google's recommended size), 2GB and 1GB. I get the same error every time. The device has around 40GB free space and the GSI image size is around 2GB (1GB gzipped), so it shouldn't be anything to do with the space requirements.
Logcat reports an error:
11-11 13:10:09.620 1103 3695 I DynamicSystemService: Failed to install system
11-11 13:10:09.621 16445 23403 E InstallationAsyncTask: java.io.IOException: Failed to start installation with requested size: 1257738436
This doesn't help unfortunately; it is thrown from the following file and this is just thrown if there is any error in the underlying dynamic installation:
packages/DynamicSystemInstallationService/src/com/android/dynsystem/InstallationAsyncTask.java - platform/frameworks/base - Git at Google
PS: Unfortunately the device does not support DSU Loader even though it's running Android 11 (searching for "dsu" in the settings returns no relevant results). Apparently none of the Samsung devices are supporting DSU Loader.
Fastboot / FastbootD
The device can be rebooted into fastboot mode ("adb reboot bootloader") but every command just hangs forever (except for "fastboot devices", which does detect the device). I tried "fastboot reboot fastboot", but it just reboots into the standard mode of the device and does not enter a fastboot userspace mode (fastbootd mode) as some have suggested it should.
Heimdall
At least one person has said they can patch GSIs using Heimdall: https://forum.xda-developers.com/t/can-i-flash-gsi-roms-with-odin.4029921/
That person was able to flash their GSI to the SYSTEM partition, but my device doesn't have a SYSTEM partition. The partitions are like SUPER, PRISM, etc.
I'm not able to get Heimdall working properly on Windows 10. I have tried with WinUSB, libusb0 and libusbK, but the same is true for all of them. After rebooting the device into ODIN mode, the device can be detected with "heimdall detect", but I can't do anything more including "heimdall print-pit", as I get a "Failed to access device. libusb error: -12" error.
I managed to set up Heimdall on an Ubuntu instance of WSL and map the USB using USBIPD. Inside WSL, "heimdall print-pit" does work but I can't get further to flashing anything (I tried to flash the GSI to SUPER, not sure if this was a good idea but anyway it failed) as I get a "Protocol initialisation failed!" error.
Odin
I am not sure if Odin itself even supports GSIs and I can't find anyone saying it supports them. I have tried flashing the GSI as an AP in Odin 3.12, 3.13, 3.14 and the patched 3.14 which removes signature checks. But every time it just fails.
Custom recovery
Just to also note, it seems none of the custom recoveries (TWRP, SHRP, Orangefox etc) support the Tab Active3, or I could have tried to flash those using Heimdall/Odin and then use them to flash the GSI. But I feel it's likely I would have had the same issues, at least with Heimdall.
you need custom recovery with dynamic partition support
aIecxs said:
you need custom recovery with dynamic partition support
Click to expand...
Click to collapse
as I mentioned, I couldn't find any custom recovery which supports my device...
Also, if I did have say TWRP or LOS recovery for my device, it seems I could run fastboot through the custom recovery (fastbootd). Then I assume I could just flash GSI using instructions like these: https://forum.xda-developers.com/t/...devices-with-dynamic-super-partition.4256667/
But it's a moot point because no such custom recovery exists for my device. There are custom recoveries for Tab Active 1 and 2, but not 3. So I'm trying to see what I can do with Heimdall
Also, quote from the above-linked thread in response to someone who asked about flashing using TWRP:
kusti420 said:
you can only do it in twrp if you rebuild the whole super partition with the gsi of your choice and flash that
Click to expand...
Click to collapse
if someone could tell me how to "rebuild the whole super partition with the gsi of your choice", that may help. because if I could convert gsi to super partition and if I could get Heimdall working (e.g. using native Linux version off a live USB or whatever), then I could use Heimdall to flash SUPER (in theory)
On that note, I found a couple of possible leads:
(1) https://forum.xda-developers.com/t/...r-img-and-flashing-our-modifications.4196625/ - shows how to unpack and re-pack super image using lpunpack and lpmake. I am wondering if I could use this to replace the system.img in my existing super partition with the one from GSI. But how to get the vendor.img and product.img? I don't think Heimdall has any command to backup existing partitions from a device
(2) https://source.android.com/devices/tech/ota/dynamic_partitions/implement#factory-images - it suggests that you can use "make dist" to build super.img, but I'm not sure if this requires me to completely rebuild AOSP from source or I can do it from existing system.img (i.e. GSI)
super_image_dumper
regarding build TWRP from source there are helpful users here
I ran Heimdall on native Linux rather than on WSL or the Windows version. This worked better and fixed the issues I was having before with Heimdall.
I then tried to flash VBMETA (the one bundled with the GSI) using Heimdall which worked, however my device was then soft-bricked, could only boot into Download Mode, and gave the following error:
ODIN MODE (AVB fail)
vbmeta: Public key used to sign data rejected. (5)
vbmeta: VERIFICATION_DISABLED bit is set.
CUSTOM VBMETA
VBMETA : No sign info
VBMETA ,
I also tried a VBMETA from avbtool, which gave a very similar error on boot:
ODIN MODE (AVB fail)
vbmeta: Error verifying vbmeta image: OK_NOT_SIGNED (3)
vbmeta: VERIFICATION_DISABLED bit is set.
CUSTOM VBMETA
VBMETA : No sign info
VBMETA ,
I managed to restore my stock vbmeta by extracting it from the stock ROM and installing using Heimdall, so my device can boot again, but it's back to vbmeta with verification enabled. How can I resolve this?
I tried to run lpmake, but I don't know my super partition size ("--device super:...") I thought it might be the partition block count from the PIT. but that is 1740800 for SUPER, whereas my system.img has size 2752909312, so surely it doesn't fit inside?
Got it fixed eventually (i.e. I am now able to run the GSI on Samsung Galaxy Tab Active3). I had made a really stupid error when running the DSU command. For KEY_SYSTEM_SIZE I was passing the gzipped system size, not original system image size. This is why the installation always failed after 50%, because it was only installing 50% of the system image. Also another really important thing to note is that after running DSU, you have to restart the system from the DSU notification and not from the normal power menu of the device.
In addition, I did flash "vbmeta_samsung.img" but I'm not sure if this was strictly necessary or not (I happened to notice that vbmeta_samsung.img has the same file size as the vbmeta disable images - 4KB vs 10KB for stock vbmeta). I'm going to be trying to help one of my colleagues to follow the same process, probably in the next few days, so will hopefully be able to report back on whether this flash is strictly necessary.
Also, I found that both Heimdall on native Linux and Heimdall on WSL actually suffer from the same problem. You can only post one command to the device, then subsequent commands fail with "protocol initialisation failed". On WSL I was doing things like "heimdall print-pit --no-reboot" and that's why I was facing issues when flashing. Basically, if you get protocol initialisation failed, just reboot the device and it should work.
ajbcc said:
I tried to run lpmake, but I don't know my super partition size ("--device super:...") I thought it might be the partition block count from the PIT. but that is 1740800 for SUPER, whereas my system.img has size 2752909312, so surely it doesn't fit inside?
Click to expand...
Click to collapse
stumbled across this post
https://forum.xda-developers.com/showpost.php?p=82241115&postcount=70
edit: bytes = block count × block size
aIecxs said:
stumbled across this post
https://forum.xda-developers.com/showpost.php?p=82241115&postcount=70
edit: bytes = block count × block size
Click to expand...
Click to collapse
Thanks for pointing this out, but this doesn't help me unfortunately. The number I'm trying to calculate here is the number 4294967296 in that post, which is the one number the guide doesn't explain how to calculate. Also, the PIT doesn't give my block size, only the "block size/offset". This seems to be just a plain offset, as it increases for every partition, even the small ones. So I have no idea what my block size is.
Just ran through the install steps with one of my colleagues (also with Samsung Galaxy Tab Active3) and there was no need to disable AVB as part of the process. We managed to get through with just the vanilla steps from Google. So all that stuff about "vbmeta_samsung.img" was just a red herring.