Hello, guys. Today i'm compiling the latest twrp.img using official omnirom 8.0 & Lineage 14.1 source code.
Seems all works as it should. Enjoy.
Need:
* unlocked bootloader
* latest official firmware .291
How-to:
* download recovery.img
* turn off your phone and flash recovery
Code:
fastboot flash recovery name_of_recovery.img
* press vol-down + power, when phone vibrate, unpress only power button. See logo 'Sony' unpress vol-down button.
Thanks:
* @nailyk for decryption
UPDATE_09.03.2017:
* new version 3.1.0-0
UPDATE_13.05.2017
* new version 3.1.1-0
UPDATE_03.12.2017
* new version 3.2.0-0
UPDATE_09.12.2017
* new version 3.2.1-0
UPDATE_14.12.2017
* added omni's version
Download Lineage 14.1 recovery:
HERE
Download Omni 8.0 recovery
HERE
Well done... Did you test also *.img flash?
I had some issues with 3.0.2.1 for aries. This gave me error messages (sorry cannot remember which in particular)
But 3.0.2.0 works as usual.
EDIT
* press vol-down + power, when phone vibrate, unpress only power button. See logo 'Sony' unpress vol-down button.
For me its just enough to release them both quite quickly after it vibrates...
Is it work only for android n? Or including android M? And is it fota recovery?
fluffi444 said:
Well done... Did you test also *.img flash?
Click to expand...
Click to collapse
What img files are you mean?
Recovery can flash only boot and recovery imgs
dddestiny said:
Is it work only for android n? Or including android M? And is it fota recovery?
Click to expand...
Click to collapse
It's work on Android M and yes, this is fota recovery
russel5 said:
What img files are you mean?
Recovery can flash only boot and recovery imgs
Click to expand...
Click to collapse
boot.img made problems. But I am going to test it for myself. No problem.
fluffi444 said:
boot.img made problems. But I am going to test it for myself. No problem.
Click to expand...
Click to collapse
OK - Looks like that it works!
But still one question left: In Backup CACHE is showing only with (0MB)
I know that backing up cache seams to be useless but sometimes its still usefull. In old TWRP 3.0.2.0 is shows mostly (4MB).
If I backup CACHE with 3.0.3.0 its give me the output 0MB saved.
Has it some thing to do with the arguments of CACHE in recovery.fstab?
Code:
noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,noauto_da_alloc,errors=panic wait,check,formattable
This is the old from 3.0.2.0 (not yet tried to change that in 3.0.3.0)
Code:
nosuid,nodev wait
EDIT
And finally USB-OTG is working! Cool!!!
@fluffi444 bro, twrp not using recovery.fstab, it's using twrp.fstab
and what size of your cache folder when your phone is booting up? my is only 40kb that's all.
russel5 said:
@fluffi444 bro, twrp not using recovery.fstab, it's using twrp.fstab
and what size of your cache folder when your phone is booting up? my is only 40kb that's all.
Click to expand...
Click to collapse
OK - feel a bit dumb now ...
I have 4,08 MB (an 192,53 MB free) - that is what Solid Explorer gives me...
EDIT
I put now an 4,5 MB file to CACHE folder - An now it shows me (5 MB) in recovery
EDIT2
I check again single folders and files in CACHE folder - They have only 22,47 KB in total...(without my manual copied file)
I guess we can close this discussion Thanks again for your work and your help!
I guess they changed the way of correct recognition of the free space.
I installed this recovery in my Z3C running the AOSP 7.1.1 ROM, but, as soon as I turned my phone on afterwards, my SD card was accused to be corrupted. As soon as I went back to TWRP v3.0.2-0, everything went back to normal. It's a 512 GB card, if it matters.
Sent from my Sony D5833 using XDA Labs
casouzaj said:
I installed this recovery
Click to expand...
Click to collapse
Can you post the recovery log to see what happend?
russel5 said:
Can you post the recovery log to see what happend?
Click to expand...
Click to collapse
Nevermind! I flashed it again in order to grab the log, but the issue simply didn't happen. Don't know what caused it the first time I flashed it. I'm keeping it this way. Thanks, anyway!
Sent from my Sony D5833 using XDA Labs
@russel5 Im guessing this is not official, but im a little bit confused? What is that build.prop you have attached in the OP?
EDIT: Btw great work man!
How to flash the recovery on concept 3657? when I flash the recovery, it hints "partition table doesn't exist"
panzerox123 said:
@russel5 Im guessing this is not official, but im a little bit confused? What is that build.prop you have attached in the OP?
EDIT: Btw great work man!
Click to expand...
Click to collapse
What do you mean, not official? Build.prop generated when you compiled something from sources.
Sent from my Sony D5803 using XDA Labs
russel5 said:
What do you mean, not official? Build.prop generated when you compiled something from sources.
Click to expand...
Click to collapse
By not official, I meant it's not on the twrp page yet ...
I was confused because build.prop says omni_aries
panzerox123 said:
By not official, I meant it's not on the twrp page yet ...
I was confused because build.prop says omni_aries
Click to expand...
Click to collapse
It's not on twrp page because i need to write email and send this to omniteam, don't want.
And aries mean z3c, like sirius z2 and other. Omni used aosp names in devices tree, like this https://github.com/sonyxperiadev/device-sony-aries
russel5 said:
It's not on twrp page because i need to write email and send this to omniteam, don't want.
And aries mean z3c, like sirius z2 and other. Omni used aosp names in devices tree, like this https://github.com/sonyxperiadev/device-sony-aries
Click to expand...
Click to collapse
I understand. So is this more stable than 3.0.2-1?
There are so many peoples on my home forum had problems with this version 2-1.
This thread created for you, guys. You can tell me - stable this new version or not
For me all works like it should. Tested on unlocked bootloader and locked.
russel5 said:
There are so many peoples on my home forum had problems with this version 2-1.
This thread created for you, guys. You can tell me - stable this new version or not
For me all works like it should. Tested on unlocked bootloader and locked.
Click to expand...
Click to collapse
Full stable for me. Thanks again for your work.
anyone tried flashing this on carbon rom?
Related
Team Win Recovery Project 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.
CHANGELOGS
Changelogs can be found from TeamWin site TeamWin - TWRP
BUGS:
- No off mode charging, boots straight in to recovery.
INFORMATION:
- Supports the f2fs file system.
2016-05-10
- TWRP version 3.0.2-0
2016-02-06
- TWRP version 3.0.0-1
2015-12-10
- TWRP version 2.8.7.0
2014-10-26
- TWRP version 2.8.1.0
2014-10-15
Today (2014-10-15) I announce a build with F2FS support, today's and upcoming build's will have support for F2FS file system. Read more about F2FS from post #18.
DOWNLOAD:
For u8800pro
Stable:
TWRP_2.8.1.0-20141026-u8800pro.zip
Unstable:
TWRP_3.0.2-0-u8800pro.zip
TWRP_3.0.0-1-u8800pro.zip
TWRP_2.8.7.0-20151210-u8800pro.zip
For u8860
TWRP_2.8.1.0-20141026-u8860.zip
Looking for the u8800 version?
It can be found here: [RECOVERY] TWRP 2.8.1.0 recovery for u8800.
Big thanks to @Dees_Troy, @bigbiff and @Captain_Throwback. Also I want to thank you @desalesouche from his help.
Thanks Lihis and everyone else, I'm glad you are still supporting this device Thumbs up!
CrysisLTU said:
Thanks Lihis and everyone else, I'm glad you are still supporting this device Thumbs up!
Click to expand...
Click to collapse
Thanks and thanks to you and other dev's who was part of this forum, you have made a job which can't be forgotten!
Great. This must be a record. Not so famous device, still getting superb support from devs. Lets see what happens to Android L.
It seems that I must be doing something wrong.
I am using TWRP manager to install the recovery img
choose the downloaded img from the SD card
but when I try to install I get a WARNING that says
1><p> The requested URL /install_command/ was not found on this server. </p>
any idea what I am doing wrong.
obviously rebooting into recovery mode does not work
Greekguy74 said:
It seems that I must be doing something wrong.
I am using TWRP manager to install the recovery img
choose the downloaded img from the SD card
but when I try to install I get a WARNING that says
1><p> The requested URL /install_command/ was not found on this server. </p>
any idea what I am doing wrong.
obviously rebooting into recovery mode does not work
Click to expand...
Click to collapse
I have not never used TWRP manager so I do not have experience with it. I suggest you to use pink screen to replace the recovery.
Lihis said:
I have not never used TWRP manager so I do not have experience with it. I suggest you to use pink screen to replace the recovery.
Click to expand...
Click to collapse
I have access to the pink screen, but it seems it is locked and don't have access to the internal storage.
I suppose I need some custom bootloader for that. Any ideas which is appropriate for the B928 version I am using from Huwaie ?
and once I get access to the internal storage where do I place the new recovery image ?
thanks in advance for all the help.
Greekguy74 said:
I have access to the pink screen, but it seems it is locked and don't have access to the internal storage.
I suppose I need some custom bootloader for that. Any ideas which is appropriate for the B928 version I am using from Huwaie ?
and once I get access to the internal storage where do I place the new recovery image ?
thanks in advance for all the help.
Click to expand...
Click to collapse
Yes, you need unlocked bootloader, take a look in here: Official ICS 4.0.3 V100R001C00B928 with unlock pink screen. When you boot your phone to pink screen the recovery can be found from "image" folder.
Lihis said:
Yes, you need unlocked bootloader, take a look in here: Official ICS 4.0.3 V100R001C00B928 with unlock pink screen. When you boot your phone to pink screen the recovery can be found from "image" folder.
Click to expand...
Click to collapse
I tried those instructions and they don't seem to work.
If I attempt it from the normal recovery screen I get a
Code:
update package;s ext name error
E:ota_pre_update error
Maybe will try to flash everything ie reinstall B928 as well and not just try to unlock the pink screen.
Will keep you posted.
Greekguy74 said:
I tried those instructions and they don't seem to work.
Click to expand...
Click to collapse
What is the error? No, you cannot flash the update.app via recovery.
Lihis said:
What is the error? No, you cannot flash the update.app via recovery.
Click to expand...
Click to collapse
If I try to flash outside the recovery it fails and in dload directory the sd_update.log says
Code:
dload_sd_ram_data_proc->(retry >= DLOAD_RETRY) failed!
I formattted the SD card but that was not the problem.
Interestingly enough if I try to flash with the official Huawei ROMs same thing happens. I am bit at a loss
Greekguy74 said:
If I try to flash outside the recovery it fails and in dload directory the sd_update.log says
Code:
dload_sd_ram_data_proc->(retry >= DLOAD_RETRY) failed!
I formattted the SD card but that was not the problem.
Interestingly enough if I try to flash with the official Huawei ROMs same thing happens. I am bit at a loss
Click to expand...
Click to collapse
In that case unfortunately I can't help you much but you can't flash update.app via recovery, they must be applied via "force update" method which is that dload thing or via stock rom "update" option. You don't have a recovery or a OS now? One thing you can test is to take off the battery and power your phone with USB cable only to apply the update.app, I have heard it helped someone's.
btw, why you didn't unlocked your pink screen in the first place when you upgraded to ICS?
Lihis said:
In that case unfortunately I can't help you much but you can't flash update.app via recovery, they must be applied via "force update" method which is that dload thing or via stock rom "update" option. You don't have a recovery or a OS now? One thing you can test is to take off the battery and power your phone with USB cable only to apply the update.app, I have heard it helped someone's.
btw, why you didn't unlocked your pink screen in the first place when you upgraded to ICS?
Click to expand...
Click to collapse
At the moment my phone works fine with the stock 4.0.3 official android version from Huawei after I managed to replace the bootloader.
I tried without the battery and just the USB cable still no joy.
As for the why I did not unlock it, good question. At the time cyanogenmod was behind ver 4.0.3 for my phone so decided to stick with the official ROM and then to be frank I forgot about it.
I will contact the TWRP manager devs to see if they can fix their app so it applies TWRP without the need for going through the pink screen.
Greekguy74 said:
At the moment my phone works fine with the stock 4.0.3 official android version from Huawei after I managed to replace the bootloader.
I tried without the battery and just the USB cable still no joy.
As for the why I did not unlock it, good question. At the time cyanogenmod was behind ver 4.0.3 for my phone so decided to stick with the official ROM and then to be frank I forgot about it.
I will contact the TWRP manager devs to see if they can fix their app so it applies TWRP without the need for going through the pink screen.
Click to expand...
Click to collapse
Good! Try eg. with RootExplorer to replace the recovery.img. It can be found from /.cust_backup/image
Lihis said:
Good! Try eg. with RootExplorer to replace the recovery.img. It can be found from /.cust_backup/image
Click to expand...
Click to collapse
I did just that and now the phone is in even bigger trouble.
When I boot it it says
Code:
Image signature verify fail!
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one.
You can remove battery for power down.
USB in pink screen mode is not functioning and it seems I cannot flash with any of the official ROMs (which is VERY weird since I did update the phone to 4.0.3 at some point in the past).
:crying:
Greekguy74 said:
I did just that and now the phone is in even bigger trouble.
When I boot it it says
Code:
Image signature verify fail!
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one.
You can remove battery for power down.
USB in pink screen mode is not functioning and it seems I cannot flash with any of the official ROMs (which is VERY weird since I did update the phone to 4.0.3 at some point in the past).
:crying:
Click to expand...
Click to collapse
Ouch.. This is hard situation :/ sometimes I really hate Huawei.. Adb is not accessible in any point? So you can't push files to device?
Lihis said:
Ouch.. This is hard situation :/ sometimes I really hate Huawei.. Adb is not accessible in any point? So you can't push files to device?
Click to expand...
Click to collapse
adb is not accessible but fastboot seems that it is. even though I cannot flash anything since they are locked.
Support for F2FS file system
Added support for F2FS file system.
What is F2FS file system?
F2FS (Flash-Friendly File System) file system is a flash file system initially developed by Samsung Electronics for the Linux operating system kernel (source). Here is some benchmark made with Xperia Z1 [Benchmarks] File System Performance: F2FS vs EXT4.
For now there is no ROM which uses F2FS file system but in future there may be.
Lihis said:
Added support for F2FS file system.
What is F2FS file system?
F2FS (Flash-Friendly File System) file system is a flash file system initially developed by Samsung Electronics for the Linux operating system kernel (source). Here is some benchmark made with Xperia Z1 [Benchmarks] File System Performance: F2FS vs EXT4.
For now there is no ROM which uses F2FS file system but in future there may be.
Click to expand...
Click to collapse
Found one bug with f2fs its fail in restore f2fs system backup data and cache are ok.
If you need you need f2fs backup just backup your current rom
Then rename and replace every "ext4" with f2fs.
mohammad.afaneh said:
Found one bug with f2fs its fail in restore f2fs system backup data and cache are ok.
If you need you need f2fs backup just backup your current rom
Then rename and replace every "ext4" with f2fs.
Click to expand...
Click to collapse
Thanks! Are you working a F2FS enabled rom?
Hi
Here are flashable zip file wich installs latest Sony stock 6.0.1 Marshmallow ROM 23.5.A.1.291_R3D (VMo AU-NZ), SuperSu v2.76 and latest TWRP 3.0.20 with read and write acces to system. Because device is Wi-Fi only region doesn´t matter. Only difference is bloatware. Since Sony hasn´t push update to SGP511 I use SGP512 firmware which is working fine on my device. If you want you can edit build.prop file in /system -folder to correct model number as shown in screenshot.
Here is the link for new 6.0.1 firmware:
https://mega.nz/#!VcxGyRZK!U4NqLOSeg1X_3KNC1_xXm2WnH4_i2OoZ6NwuyaIR6Hw
MD5 is: D3B78445485765AB7BD3A163F2A6C4BD
Make nandroid backup before flashing.
Install it by flashing whole zip file via custom recovery. TWRP recommend. If coming from .570 or .575 firmware dirty flash with art/dalvik cache wipe is okay.
If coming from older firmware factory reset is most likely necessary with cache and dalvik/art cache wipes but anyhow recommend. If you want you can restore your data with TWRP after installation and reboot. This install compatible busybox. If you install incompatible busybox you may loose acces to TWRP.
After flashing .zip file if you are getting bootloop you have atleast two choises.
- With pc and Flashtool use your firmware original ftf -file and flash it by excluding "FOTAKernel", "Partition" and "System". In other words in "exclude section" tick these and don´t wipe anything. (Credits @AlanDS)
- Or download "bootloop fix" from here: https://mega.nz/#!BUxFxSAR!bPVEEDnsPz962JQ1uA2PKJv9tYLKA47N0fhA80ltEvw
(Credits @niaboc79 and @machao44) and flash it with TWRP
Here is the old 23.1.A.1.28 (Customized NCB) FTF -file link:
For SGP511: https://mega.nz/#!sVIn1IJI!Ywqoksuej83vNkc__nNrBy-im6tfLjWr_mbonMd6PPk
MD5 is: aab7e5728dccb59d44d5ebe38c34c8da
This version of firmware should be rootable. For instructions and download go here: http://forum.xda-developers.com/crossdevice-dev/sony/root-how-to-root-5-0-lollipop-t3212108
Credits: @Androxyde @Chainfire @[NUT] @IaguCool @zxz0O0 @Wolfbreak @shoey63 @serajr @championswimmer @russel5
Any news on sgp512? or I can use this one? thanks in advance
Cocolopes said:
Any news on sgp512? or I can use this one? thanks in advance
Click to expand...
Click to collapse
At the moment latest for SGP512 is .726 firmware but you can use this one.
kulvertti said:
At the moment latest for SGP512 is .726 firmware but you can use this one.
Click to expand...
Click to collapse
good...I miss something if I use this? I think the only difference its the internal memory...
Cocolopes said:
good...I miss something if I use this? I think the only difference its the internal memory...
Click to expand...
Click to collapse
Nope. Only difference between devices is memory size and your device regognize correct size even if you use this. Only thing is your device shows as SGP511 but you can chance that in build.prop file if you like.
Er... on my Z2 Tablet with .726 firmware there is no "Ultra Stamina" mode... or am I missing something?
Or is "Ultra Stamina" introduced only with this new firmware version??
Thanks, I just noticed this version was offered as a 21 MB system update on my current ROM (23.1.A.0.690 NCB). But this is much better :good:
hasenbein1966 said:
Er... on my Z2 Tablet with .726 firmware there is no "Ultra Stamina" mode... or am I missing something?
Or is "Ultra Stamina" introduced only with this new firmware version??
Click to expand...
Click to collapse
You are right. Chancelog is copy/pasted from universal source so there is device specific differencies and because this device is wifi only there is no ultra stamina mode.
kulvertti said:
You are right. Chancelog is copy/pasted from universal source so there is device specific differencies and because this device is wifi only there is no ultra stamina mode.
Click to expand...
Click to collapse
hey man...if I flash this I will losse all my internal sd data? or I only need to backup my apps and nothing more? (sorry if I ask to much things)
Cocolopes said:
hey man...if I flash this I will losse all my internal sd data? or I only need to backup my apps and nothing more? (sorry if I ask to much things)
Click to expand...
Click to collapse
For to be safe I recommend to make nandroid backup including kernel, system and data. However if something go wrong system backup with kernel might be enough to bring your device back.
This ain't wipe your internal sd on it's own so it is your choice.
Thanks man, you're always so fast! We should be getting 5.1 next month I read somewhere
Tap to awake isnt working, is ghis a known bug?
BLiapis said:
Tap to awake isnt working, is ghis a known bug?
Click to expand...
Click to collapse
Nope. Double tap to wake work fine here.
Factory reset coming from KK, everything working perfectly, including root/SU and double tap to wake.
In case anyone has similar issues, I couldn't download from Mega directly to device (it kept disconnecting at around 10%), had to download using PC and transfer using SD card.
Thanks Kulvertti for all the work you do for our device, it is much appreciated! :good:
Hello !
I am already on Lollipop & rooted, does updating thanks to the Sony update center will keep my root or does this flashable zip is mandatory to keep root ?
Thanks
Angeal Hewley said:
Hello !
I am already on Lollipop & rooted, does updating thanks to the Sony update center will keep my root or does this flashable zip is mandatory to keep root ?
Thanks
Click to expand...
Click to collapse
This will keep your root. About OTA, maybe with small updates but haven't tested it with latest update.
kulvertti said:
This will keep your root. About OTA, maybe with small updates but haven't tested it with latest update.
Click to expand...
Click to collapse
Thanks for the reply!
I flashed your zip to be 100% sure to keep root
issue
hey man,
I just spent like 2 hours trying to get CWM installed for castor windy. finally ended up using a combo of ADB "fastboot reboot-bootloader" reboot-boot <lightning-bolt-symbol/fastboot mode/select kernal to flash> and put in an extracted boot.img for CWM (nightly build). i then did "fastboot reboot" and rapidly pressed the volume up button. it worked and im now in CWM. I put your zip on my sd card before, and I navigated to that <apply update/choose from sdcard1/flashablesomeupdatedetailsidontwanttocopy.zip> (strangly I noticed that there were 2 identical "choose from sdcard1" options)
cwm paused for a second, then outputted
Install failedFinding update package...
Opening update package...
E:footer is wrong
E:signature verification failed
Installation aborted
sorry about my formatting of what I did, Im new to xda devs
thanks in advance for the help, and thank you for supporting a tablet that very few people seem to use
joeyishar said:
hey man,
I just spent like 2 hours trying to get CWM installed for castor windy. finally ended up using a combo of ADB "fastboot reboot-bootloader" reboot-boot <lightning-bolt-symbol/fastboot mode/select kernal to flash> and put in an extracted boot.img for CWM (nightly build). i then did "fastboot reboot" and rapidly pressed the volume up button. it worked and im now in CWM. I put your zip on my sd card before, and I navigated to that <apply update/choose from sdcard1/flashablesomeupdatedetailsidontwanttocopy.zip> (strangly I noticed that there were 2 identical "choose from sdcard1" options)
cwm paused for a second, then outputted
Install failedFinding update package...
Opening update package...
E:footer is wrong
E:signature verification failed
Installation aborted
sorry about my formatting of what I did, Im new to xda devs
thanks in advance for the help, and thank you for supporting a tablet that very few people seem to use
Click to expand...
Click to collapse
Install Dualrecovery from here: http://forum.xda-developers.com/showthread.php?p=53661356 and use TWRP to flash .zip file.
kulvertti said:
Install Dualrecovery from here: http://forum.xda-developers.com/showthread.php?p=53661356 and use TWRP to flash .zip file.
Click to expand...
Click to collapse
First: Thanks to Kulvertti for all his work.
I am still confused. Do I need to root my device on forehand?
What I have understood so far:
You don't have to have root to flash NUT's [TABZ2][TWRP][PhilZ Touch][CWM] XZDualRecovery (It won't bring you root either).
So you can flash this recovery as long as you are on unrooted but rootable stock firmware (e.g. 17.1.2.A.0.314).
Then can flash this pre-rooted stock Lollipop ROM 23.1.A.1.28 and you will have root.
So only 3 steps to go from unrooted stock Lollipop to to this pre-rooted Lollipop?
1) flash rootable firmware (from PC, using flashtool).
2) flash "NUT's" recovery (from PC, using NUT's installer).
3) flash this pre-rooted stock Lollipop ROM (from sdcard1, using TWRP recovery)
Is this correct??
TWRP isn’t an official build for our device, but we can take it as z1 reference. I have to compile TWRP touch recovery from source. I use cm12.1 source code and with F2FS support.
Download Links:
http://goo.gl/qCiTOA
changeLog:
Updated TWRP to 3.0.2
What’s new in 3.0.2:
Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
Add Greek translation to some builds.
TWRP Install:
PHP:
fastboot flash FOTAKernel Z1C-twrp-3.0.2.img
If you have new bootloader for open devices(with real recovery partition)
PHP:
fastboot flash recovery Z1C-twrp-3.0.2.img
twrp for sony rhine device tree:
https://github.com/charles1018/twrp_android_device_sony_amami
https://github.com/charles1018/twrp_android_device_sony_msm8974-common
https://github.com/charles1018/twrp_android_device_sony_rhine-common
Great. Does it support decrypting?
Sent from my Xperia Z1 Compact using XDA-Developers mobile app
sharonliu said:
TWRP isn’t an official build for our device, but we can take it as z1 reference. I have to compile TWRP touch recovery from source. I use cm12.1 source code and with F2FS support.
Download Links:
http://goo.gl/qCiTOA
TWRP Install:
PHP:
fastboot flash FOTAKernel Z1C-twrp-3.0.1.img
If you have new bootloader for open devices(with real recovery partition)
PHP:
fastboot flash recovery Z1C-twrp-3.0.1.img
twrp for sony rhine device tree:
https://github.com/charles1018/twrp_android_device_sony_amami
https://github.com/charles1018/twrp_android_device_sony_msm8974-common
https://github.com/charles1018/twrp_android_device_sony_rhine-common
Click to expand...
Click to collapse
thank you, works great
frauhottelmann said:
Great. Does it support decrypting?
Sent from my Xperia Z1 Compact using XDA-Developers mobile app
Click to expand...
Click to collapse
It works for me.
I flashed it to real recovery partition and it doesn't even ask for my pattern. Decryption doesn't work for me...
frauhottelmann said:
I flashed it to real recovery partition and it doesn't even ask for my pattern. Decryption doesn't work for me...
Click to expand...
Click to collapse
TWRP 3.0.2-0 Released . This fixes decrypt of full device encryption on devices that support decrypt.
sharonliu said:
TWRP 3.0.2-0 Released . This fixes decrypt of full device encryption on devices that support decrypt.
Click to expand...
Click to collapse
I'll try when i get home...
Sent from my Xperia Z1 Compact using XDA-Developers mobile app
sharonliu said:
TWRP 3.0.2-0 Released . This fixes decrypt of full device encryption on devices that support decrypt.
Click to expand...
Click to collapse
It doesn't work for me... Internal storage is detected as 0MB (it is 16GB) and I can't even tap the checkbox to mount it; the external SD works, although it displays only 4GB instead of 64GB.
Update: The version posted below works for me.
luckyrumo said:
It doesn't work for me... Internal storage is detected as 0MB (it is 16GB) and I can't even tap the checkbox to mount it; the external SD works, although it displays only 4GB instead of 64GB.
Click to expand...
Click to collapse
It works for me.
How enter TWRP?
sharonliu said:
It works for me.
Click to expand...
Click to collapse
Wow, for me is 865mb out of space?
Is it possible to have your wonderful kernel v18 with updated recovery??
Sent from my D5503 using xda premium
Thanks a lot for posting your sources.
Since I recently encrypted my phone, I was in the need of a recovery with working decryption. I spend a bit of time and tried to include it in here thanks to a lot of trial and error. Unfortunately, it not as easy as setting a flag during compilation. Instead, you also need to include necessary blobs, modify fstab, create symlinks to make blobs accessible without mounting the system, build keystore, etc. Finally, it appears to be working. You can download the build here (built within CM12.1 sources):
https://www.androidfilehost.com/?fid=24499762636001730
Here are the links to the repositories that I've changed:
https://github.com/derfelot/twrp_android_device_sony_amami
https://github.com/derfelot/twrp_android_device_sony_rhine-common
Cheers
Cool. It works well on my z1c. Thanks a lot.
hellow people
to with a difficulty here with img TWRP Z1C
3.0.1 can not install on my smartphone .
I need to unlock my phone?
or have full tutorial
chao9002231 said:
hellow people
to with a difficulty here with img TWRP Z1C
3.0.1 can not install on my smartphone .
I need to unlock my phone?
or have full tutorial
Click to expand...
Click to collapse
Start from here:
http://forum.xda-developers.com/showthread.php?t=2631291
derf elot said:
Thanks a lot for posting your sources.
Since I recently encrypted my phone, I was in the need of a recovery with working decryption. I spend a bit of time and tried to include it in here thanks to a lot of trial and error. Unfortunately, it not as easy as setting a flag during compilation. Instead, you also need to include necessary blobs, modify fstab, create symlinks to make blobs accessible without mounting the system, build keystore, etc. Finally, it appears to be working. You can download the build here (built within CM12.1 sources):
https://www.androidfilehost.com/?fid=24499762636001730
Click to expand...
Click to collapse
Thank you so much :good::good::good: for the first time since about a year I am now able to mount my encrypted partition in TWRP :victory::victory::victory:
Can I install this with a locked bootloader?
glennza said:
Can I install this with a locked bootloader?
Click to expand...
Click to collapse
No, you can not. You need to be unlocked.
Sent from my Xperia Z1 Compact using Tapatalk
derf elot said:
Finally, it appears to be working. You can download the build here (built within CM12.1 sources):
https://www.androidfilehost.com/?fid=24499762636001730
Click to expand...
Click to collapse
Works for me THANKS!
derf elot said:
Thanks a lot for posting your sources.
Since I recently encrypted my phone, I was in the need of a recovery with working decryption. I spend a bit of time and tried to include it in here thanks to a lot of trial and error. Unfortunately, it not as easy as setting a flag during compilation. Instead, you also need to include necessary blobs, modify fstab, create symlinks to make blobs accessible without mounting the system, build keystore, etc. Finally, it appears to be working. You can download the build here (built within CM12.1 sources):
https://www.androidfilehost.com/?fid=24499762636001730
Here are the links to the repositories that I've changed:
https://github.com/derfelot/twrp_android_device_sony_amami
https://github.com/derfelot/twrp_android_device_sony_rhine-common
Cheers
Click to expand...
Click to collapse
Doesn't work for me. It's still not able to decrypt my 4x4 pattern encryption
UPDATE:
Moved my TWRP activities into this new thread !
http://forum.xda-developers.com/pixel-c/development/twrp-3-0-2-0v16-t3400503
As I still like to make the "perfect" TWRP for Pixel C .. here are the next versions ...
Update.ZIP_TWRP_dragon_3.0.2-0_v16.zip -> to be installed via TWRP
TWRP_dragon_3.0.2-0_v16.img -> to be installed via fastboot
Changes to previous (v15) version:
- ADB shell was not working in recovery - fixed now !
- chromeos-3.18 kernel -> v160617
Pls find the new version here: http://forum.xda-developers.com/pixel-c/development/twrp-3-0-2-0v16-t3400503
followmsi said:
As it looks like, I do have my prodcutive weekend ..
Today I have released a new TWRP version .. USB-OTG works now.
Update.ZIP_TWRP_dragon_3.0.2-0_v4.zip
Now I have made another version .. Update.ZIP_TWRP_dragon_3.0.2-0_v5.zip
For this version I have ported the Nexus 6 P decryption functionality to Pixel C.
As I don´t have an encrypted /data partition anymore I would like to ask for some testers.
This TWRP version should be able to access your encrypted data partition now - hopefully.
Please install both versions from your current TWRP.
Pls make a "reboot to recovery" once you have installed the .zip file.
Inside the download folder there also .img files for fastboot installation, or you unzip the .zip file.
Download frome here: https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks
Click to expand...
Click to collapse
Good stuff!
I'm decrypted so can't test that, but the USB-OTG is working AOK! :good:
Thanks for report ..
v5 will not make problems if you are already decrypted, like me too.
OTG is working fine in both versions.
I'm now decrypted, but thanks for the efforts for people coming from a clean encrypted state
My usb-c to micro usb is not working for me with my otg cable, so i will have to wait to test that functionaility too.
scoobydu said:
I'm now decrypted, but thanks for the efforts for people coming from a clean encrypted state
My usb-c to micro usb is not working for me with my otg cable, so i will have to wait to test that functionaility too.
Click to expand...
Click to collapse
Thanks for the info ..
I guess I will encrypt my data partition soon and test myself.
Now as I have a quick backup and restore possibility
When you release something you should be able to "fully" test it.
I have a small USB-C adapter which is working in normal system and now in recovery as well.
Luckily it's working .. there are many cables and adapters which are not working.
Cheers
I´m on a decripted device too but I have now a Nandroid on an USB stick! That´s really awesome! Thanks followmsi
My anker adapter doesn't work, but I have ordered another from amazon, due tomorrow, that is supposed to support org, so will hopefully be able to test the otg then.
v4 worked perfectly. It was exactly what i needed. Thank you.
followmsi said:
This TWRP version should be able to access your encrypted data partition now - hopefully.
Click to expand...
Click to collapse
Not sure it's working. From a fresh, locked Pixel C, I unlocked bootloader, flashed TWRP_dragon_3.0.2-0_v5.1.img via fastboot, rebooted into recovery and TWRP still cannot see/mount the data partition. Did I miss a step somewhere or do something wrong?
stevehanler said:
Not sure it's working. From a fresh, locked Pixel C, I unlocked bootloader, flashed TWRP_dragon_3.0.2-0_v5.1.img via fastboot, rebooted into recovery and TWRP still cannot see/mount the data partition. Did I miss a step somewhere or do something wrong?
Click to expand...
Click to collapse
Same for me
RolfFrie said:
Same for me
Click to expand...
Click to collapse
Thanks for the update .. it is not working yet.
It was a test .. I have implemented the "original" TWRP mechanism for decryption .. but Pixel C is using other libraries to decrypt .. "angler" and "bullhead" are using the same way.
But they are not "mixed" ChromeOS devices.
Will remove v5.1 soon from the website .. hopefully we will manage it later on.
Maybe I will add a short technical description .. what I did and maybe someone else is able to get the rest of the puzzle.
Thanks for your help and testing !
Cheers
stevehanler said:
Not sure it's working. From a fresh, locked Pixel C, I unlocked bootloader, flashed TWRP_dragon_3.0.2-0_v5.1.img via fastboot, rebooted into recovery and TWRP still cannot see/mount the data partition. Did I miss a step somewhere or do something wrong?
Click to expand...
Click to collapse
Are you still encrypted ?
Pls have another try .. v5.5 .. the last try
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks
followmsi said:
Are you still encrypted ?
Pls have another try .. v5.5 .. the last try
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks
Click to expand...
Click to collapse
I flashed the N preview 3 like stock but now I'm encrypted... How can uncrypt it ?
En Kee said:
I flashed the N preview 3 like stock but now I'm encrypted... How can uncrypt it ?
Click to expand...
Click to collapse
Encrypted would be good .. but I am not sure if the TWRP works the same on N.
To decrypt you need to format your data .. with encryptable flag, e.g. Install SuperSU 2.72 above.
Cheers
followmsi said:
Are you still encrypted ?
Pls have another try .. v5.5 .. the last try
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks
Click to expand...
Click to collapse
I'm not unfortunately.
I was stuck in a recovery bootloop whatever I do... But... In bootloader it worked with the command : fastboot reboot.... I don't know why but I don't care !
I'm now with the N Preview 3 and rooted
While testing new kernel I had the same issue today.
Recovery bootloop.
"fastboot reboot" sovled the problem ...
Cheers
followmsi said:
While testing new kernel I had the same issue today.
Recovery bootloop.
"fastboot reboot" sovled the problem ...
Cheers
Click to expand...
Click to collapse
any changelog?
worth to update if i'm on your v4.6?
Smaller recovery image due to new lzma compressed kernel .. and the decryption libs are included.
Nothing else has changed.
No real need to upgrade .. but with update.zip the update goes fast anyway.
Cheers
The Recovery bootloop is a little bit tricky sometimes. Because if you do not own a PC (like me for the moment) you couldn't work with the tablet for a while. I had one Loop after making a nandroid. So I fear to turn off the device.
Is it possible to jump back to stock recovery for example before I'm traveling and reflash TWRP back home to minimize the risk of a loop when there is no PC reachable?
Hi. As a result of Androplus stoppage of his kernel support I decided to create this theme. I'm not a developer.
I use LineageOS more than two months, and it's stable. Originally it was built by andralex, he didn't create this threat as he was waiting the permission from other developer whose groundwork he used. But I lost contact with him. Seems he is very busy.
Now the other developer builded the rom, his nickname is kv123.
--------------
To get usb otg working use this in terminal when you inserted usb stick
Code:
su
echo 1 > /sys/module/qpnp_smbcharger_extension/parameters/start_id_polling
------------
After any lineageos update dont forget about play store to give permissions for storage. Otherwise it wont download any apps larger the 20 mb.
Lineage camera is a bit buggy, so it's better to use open camera.
---------
There are the links
[STRIKE]https://www.androidfilehost.com/?fid=745425885120730219[/STRIKE]
https://yadi.sk/d/Zfxi3agx3HkLQL
Some developer links:
https://review.lineageos.org/#/q/project:LineageOS/android_kernel_sony_msm8994
https://github.com/LineageOS/android_kernel_sony_msm8994
If you want I can ask kv123 to build the rom for sgp712 too.
------------
Some screenshots:
Oh. You need also replace wifi calibration file here: /system/etc/firmware/wlan/bcmdhd/bcmdhd.cal and reboot
It's forgotten to be added.
Updated fixed version at yandex disk.
Thanks for this. It is exactly what I am looking for and I hope my tech skills are up to the task.
BTW, this link comes up "404 not found. Can't find it!"
https://www.androidfilehost.com/?fid=745425885120730219
Would you have another we can try?
Thats because kv123 removed version with wifi buggy.
Use my mirror link or this.
https://www.androidfilehost.com/?fid=817550096634767960
alex009988 said:
Hi. As a result of Androplus stoppage of his kernel support I decided to create this theme. I'm not a developer.
I use LineageOS more than two months, and it's stable. Originally it was built by andralex, he didn't create this threat as he was waiting the permission from other developer whose groundwork he used. But I lost contact with him. Seems he is very busy.
Now the other developer builded the rom, his nickname is kv123.
--------------
To get usb otg working use this in terminal when you inserted usb stick
------------
After any lineageos update dont forget about play store to give permissions for storage. Otherwise it wont download any apps larger the 20 mb.
Lineage camera is a bit buggy, so it's better to use open camera.
---------
There are the links
https://www.androidfilehost.com/?fid=745425885120730219
https://yadi.sk/d/Zfxi3agx3HkLQL
Some developer links:
https://review.lineageos.org/#/q/project:LineageOS/android_kernel_sony_msm8994
https://github.com/LineageOS/android_kernel_sony_msm8994
If you want I can ask kv123 to build the rom for sgp712 too.
Click to expand...
Click to collapse
Hi, could you please add some screenshots?
Ok. Added to the top.
need rom for SG712 please...
Thanks for sharing. SGP712 build would be great
Charsher47 said:
Thanks for sharing. SGP712 build would be great
Click to expand...
Click to collapse
Kv123 told me that he's gonna build the rom for 712 too.
I don't have SPG712, so i cannot test it. I was lazy to download firmware for 712, so libs are from 771. Hope they are the same. Who have please leave some feedback.
SGP712_lineageos_14_1
P.S. Nfc may not work. I will need to do some tests.
kv123 said:
I don't have SPG712, so i cannot test it. I was lazy to download firmware for 712, so libs are from 771. Hope they are the same. Who have please leave some feedback.
SGP712_lineageos_14_1
P.S. Nfc may not work. I will need to do some tests.
Click to expand...
Click to collapse
I flashed the rom with Androplus' TWRP-3.0.2-0-20160604, Error 7 because target device is karin_windy but the recovery says the device is karin (actually SGP712, it's karin_windy).
So i deleted the device verification in the updater-script, and it's Error 6 now...
Phil_Libra said:
I flashed the rom with Androplus' TWRP-3.0.2-0-20160604, Error 7 because target device is karin_windy but the recovery says the device is karin (actually SGP712, it's karin_windy).
So i deleted the device verification in the updater-script, and it's Error 6 now...
Click to expand...
Click to collapse
Why do you use androplus recovery? Use normal recovery, take it from yandex disk. And boot by vol- and power till it vibrates.
alex009988 said:
Why do you use androplus recovery? Use normal recovery, take it from yandex disk. And boot by vol- and power till it vibrates.
Click to expand...
Click to collapse
Nothing happens after I flashed the recoveries from yandex disk（both 3.0.3 and 3.1), so I tried androplus recovery...
Is there a modified boot.img for those recoveries?
P.S. I flashed 32.3.A.2.33.ftf first.
---------- Post added at 10:29 AM ---------- Previous post was at 10:22 AM ----------
I flashed 32.3.A.2.33 with flashtool, then flash the recovery in fastboot mode with:
Code:
fastboot flash recovery [I]recovery name[/I]
then pressed vol- and power, nothing happens and the tablet boots to the system.
Maybe it's better: fastboot flash recovery twrp.img ?
This twrp only requires updated bootloader from 7.0 stock.
Also i need to keep these buttons pressed untill it vibrates that is 2-3 seconds.
You can find kv123 at this thread http://4pda.ru/forum/index.php?showtopic=706675
Also you can try to contact with andralex8. He has just 712 tablet. And it worked for him. But I'm not sure if he answers you quickly.
If you keep trouble with the recovery, try twrp from this https://forum.xda-developers.com/z4-tablet/general/guide-nougat-drm-fix-root-twrp-sgp771-t3555265
Phil_Libra said:
Nothing happens after I flashed the recoveries from yandex disk（both 3.0.3 and 3.1), so I tried androplus recovery...
Is there a modified boot.img for those recoveries?
P.S. I flashed 32.3.A.2.33.ftf first.
---------- Post added at 10:29 AM ---------- Previous post was at 10:22 AM ----------
I flashed 32.3.A.2.33 with flashtool, then flash the recovery in fastboot mode with:
Code:
fastboot flash recovery [I]recovery name[/I]
then pressed vol- and power, nothing happens and the tablet boots to the system.
Click to expand...
Click to collapse
Sorry if I have missed something obvious, but are you attempting to flash LineageOS? In which case I am confused as to why you are flashing the Sony Rom 32.A.2.33?
For my part I am gearing up to attempt the LineageOS install but would like to have a backup copy of the Sony firmware in case it goes wrong.
Assuming you installed an English version, which one did you select from here:-
https://xpericheck.com/device/SGP771
Indeed, if you try something especially unchecked, better to have a backup.
But you also need to have last sony rom(any of android 7.0) in order to update bootloader and have last twrp working.
alex009988 said:
Maybe it's better: fastboot flash recovery twrp.img ?
This twrp only requires updated bootloader from 7.0 stock.
Also i need to keep these buttons pressed untill it vibrates that is 2-3 seconds.
You can find kv123 at this thread http://4pda.ru/forum/index.php?showtopic=706675
Also you can try to contact with andralex8. He has just 712 tablet. And it worked for him. But I'm not sure if he answers you quickly.
If you keep trouble with the recovery, try twrp from this https://forum.xda-developers.com/z4-tablet/general/guide-nougat-drm-fix-root-twrp-sgp771-t3555265
Click to expand...
Click to collapse
Androplus‘ recovery need a modified boot.img so I wonder if the same as the recovery in yandex disk?
And recovery from https://forum.xda-developers.com/z4-tablet/general/guide-nougat-drm-fix-root-twrp-sgp771-t3555265 is the same as Androplus’ recovery.
Ok. If you've done everything right I guess 712 dosent work with 771 recovery. I'll tell about it to kv123 and you can say it on your own on 4pda.
Please anybody who has 712 model. Test 3.1 recovery from yandex disk and confirm or contradict if it dosent work for you.
Phil_Libra said:
Nothing happens after I flashed the recoveries from yandex disk（both 3.0.3 and 3.1), so I tried androplus recovery...
Is there a modified boot.img for those recoveries?
P.S. I flashed 32.3.A.2.33.ftf first.
---------- Post added at 10:29 AM ---------- Previous post was at 10:22 AM ----------
I flashed 32.3.A.2.33 with flashtool, then flash the recovery in fastboot mode with:
Code:
fastboot flash recovery [I]recovery name[/I]
then pressed vol- and power, nothing happens and the tablet boots to the system.
Click to expand...
Click to collapse
alex009988 said:
Please anybody who has 712 model. Test 3.1 recovery from yandex disk and confirm or contradict if it dosent work for you.
Click to expand...
Click to collapse
I'm seeing the same results. Tried the same recoveries to no avail.