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
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?
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?
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?
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Click to expand...
Click to collapse
WARNING!!! Be careful what you do here. One mistake and the device is soft-bricked. I take no responsibility for bricked devices, lost warranty or even OTAs not working!! Booting and/or flashing files from this post is on your own risk.
Requirements
Unlocked bootloader
Lenovo Tab 4 Plus with and without LTE and both 8 and 10 inch versions (TB-X704L/F, TB-8704X/F) are supported
Known Issues
WARNING! Our device uses dm-verity (verified boot). The system partition should remain read-only. Otherwise a bootloop will occur. You can flash SuperSU to resolve this but OTA's are no longer possible! You have to restore a factory image or clean system backup to receive OTAs
Download
TWRP for TB-8704X/F (8 inch plus): AndroidFileHost
TWRP for TB-8704V (8 inch plus Verizon): AndroidFileHost (provided by @3m1k)
TWRP for TB-X704L/F (10.1 inch plus): AndroidFileHost
TWRP for TB-8504X/F (8 inch): AndroidFileHost (touch input may only work after connecting mouse)
TWRP for TB-X304L/F (10.1 inch): AndroidFileHost
Instructions
Install fastboot and adb on your PC, e.g. from here
Enable developer options and in there select to unlock your bootloader by enabling OEM unlock and enable USB debugging
Connect your PC to your tablet and run
Code:
adb reboot bootloader
using adb on command line. The tablet will reboot into bootloader mode where you will only see the Lenovo logo. Now you use
Code:
fastboot oem unlock-go
to unlock. This will factory reset your device
Setup the tablet again and reboot again to the bootloader
Then run
Code:
fastboot boot twrp-3.2.3-0-<your-filename>.img
to temporarily boot into TWRP. You can also flash if you are sure
Select to keep system read only when TWRP starts to avoid modification which will make OTAs impossible
Backup at least system and boot partitions. Choose "System Image" for the system partition backup. Keep this backup for OTA updates.
Optionally flash SuperSU or Magisk in TWRP which should install system less. Keep OEM unlock enabled if you flash or modify anything
Writable System Partition
Some mods and root apps require write access to the system partition. By default the system partition is read-only to prevent any modification. Please note that if your system partition is modified in any way it needs to be restored to its original state before a system update (OTA) can be applied.
@dywersant has created a Magisk module here to achieve write access
@KreAch3R has updated the Magisk module to the latest version here
System Updates (OTA)
In order to successfully apply Lenovo system updates after root you have to restore the original boot, recovery (if you flashed TWRP) and system partitions from your current installed version (e.g. S000037) for your variant of the tablet. This will NOT delete your apps and data but will unroot. Note that OTAs are block based and always check the contents of most of the partitions. This means that all of these partitions (except your data) have to be original and have to be on the exact same version (e.g. S000037) for the update to succeed.
Credits
@wonderfulme - for testing the 8" version
@Teddy01 - for testing the 10" version
@3m1k - for providing the 8" Verizon version
TeamWin
Source
TWRP Manifest: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-7.1
Device Tree (TB-8704X): https://github.com/Matshias/twrp_android_device_tb_8704x/tree/android-7.1
Device Tree (TB-8704V): https://github.com/3m1k/twrp_android_device_tb_8704v
Device Tree (TB-X704L): https://github.com/Matshias/twrp_android_device_tb_x704l/tree/android-7.1
Device Tree (TB-8504X): https://github.com/Matshias/twrp_android_device_tb_8504x/tree/android-7.1
Device Tree (TB-X304L): https://github.com/Matshias/twrp_android_device_tb_x304l/tree/android-7.1
Changelog
v3:
Update to TWRP 3.2.3-0
v2:
Update to TWRP 3.2.1-0
v1:
Initial Release
TWRP for Tab 4 8/10 without "Plus"
I built TWRP for both devices and need testers. Here are experimental versions:
Tab 4 8 (TB-8504X/F): twrp-3.1.1-0-tb_8504x_testing1.img
Tab 4 10 (TB-x304L/F): no longer needed. Final version in first post
matshias said:
TWRP for Tab 4 8/10 without "Plus"
I built TWRP for both devices and need testers. Here are experimental versions:
Tab 4 8 (TB-8504X/F): twrp-3.1.1-0-tb_8504x_testing1.img
Tab 4 10 (TB-x304L/F): twrp-3.1.1-0-tb_x304l_testing1.img
Click to expand...
Click to collapse
I can test the 8 inch tomorrow. Thanks for building this btw.
---------- Post added at 02:01 PM ---------- Previous post was at 01:58 PM ----------
Wait, these builds are for the Plus variants only? They will not work with ZA2B0009US, correct? :\
w0rdie said:
Wait, these builds are for the Plus variants only? They will not work with ZA2B0009US, correct? :\
Click to expand...
Click to collapse
ZA2B0009US = TB-8504F so you can take the build for Tab 4 8 (TB-8504X/F) and hopefully it will work out of the box.
matshias said:
ZA2B0009US = TB-8504F so you can take the build for Tab 4 8 (TB-8504X/F) and hopefully it will work out of the box.
Click to expand...
Click to collapse
Just landed there myself. I'll give it a go tomorrow morning and update this post.
Thanks again.
I have tested on X304L work perfectly.
Only one thing when i'm on power via usb TWRP still turning off screen in 2min and seems that all operations are put in wait state until screen turned on again.
:good:
boza12 said:
I have tested on X304L work perfectly.
Only one thing when i'm on power via usb TWRP still turning off screen in 2min and seems that all operations are put in wait state until screen turned on again.
:good:
Click to expand...
Click to collapse
Thanks a lot for testing. I moved the TWRP to the first post.
In the TWRP settings you can switch off whether the screen goes off or not. Are you sure TWRP halts processing while the screen is off?
matshias said:
Thanks a lot for testing. I moved the TWRP to the first post.
In the TWRP settings you can switch off whether the screen goes off or not. Are you sure TWRP halts processing while the screen is off?
Click to expand...
Click to collapse
Yes It does - it happened to me last night also.
EggZenBeanz said:
Yes It does - it happened to me last night also.
Click to expand...
Click to collapse
Can you send me the logs (dmesg output and /tmp/recovery.log) after it happens?
Yes sure.
Is anyone able to make available a system image. I deleted my original back up after the update then messed the root up. I now getting setup app crash and can't get passed setup
EggZenBeanz said:
Yes sure.
Is anyone able to make available a system image. I deleted my original back up after the update then messed the root up. I now getting setup app crash and can't get passed setup
Click to expand...
Click to collapse
Download the factory image for your tablet from the Russian Lenovo forum (lenovo-forums.ru) . In there you will find a fragmented system image. You have to puzzle it together with a script according to XML file in the Image directory. If you wanna flash via fastboot you will have to convert it with img2simg to sparse format. You can also use dd command line TWRP with the raw image file. If you tell me your exact model number I can also upload what you need.
matshias said:
Download the factory image for your tablet from the Russian Lenovo forum (lenovo-forums.ru) . In there you will find a fragmented system image. You have to puzzle it together with a script according to XML file in the Image directory. If you wanna flash via fastboot you will have to convert it with img2simg to sparse format. You can also use dd command line TWRP with the raw image file. If you tell me your exact model number I can also upload what you need.
Click to expand...
Click to collapse
Thanks! That would be awesome if you could. I think I may brick it if I do what you suggest! My model is
TB-X704L/F (10.1 inch plus) could you include the boot image too?
EggZenBeanz said:
Thanks! That would be awesome if you could. I think I may brick it if I do what you suggest! My model is
TB-X704L/F (10.1 inch plus) could you include the boot image too?
Click to expand...
Click to collapse
Is it TB-X704L vor F? This is an important difference.
The boot image you can find as can be flashed in the factory image. You can start with this. When I have time I'll prepare the system image. Not sure when that is though.
matshias said:
Is it TB-X704L vor F? This is an important difference.
The boot image you can find as can be flashed in the factory image. You can start with this. When I have time I'll prepare the system image. Not sure when that is though.
Click to expand...
Click to collapse
Thanks!!!! Confirmed TB-X704F
matshias said:
TWRP for Tab 4 8/10 without "Plus"
I built TWRP for both devices and need testers. Here are experimental versions:
Tab 4 8 (TB-8504X/F): twrp-3.1.1-0-tb_8504x_testing1.img
Tab 4 10 (TB-x304L/F): twrp-3.1.1-0-tb_x304l_testing1.img
Click to expand...
Click to collapse
The twrp-3.1.1-0-tb_8504x_testing1.img flashes and boots fine but there is no touch input.
Logs: https://www.dropbox.com/s/vo2dvi4frpsf9hf/logs.zip?dl=0
(I connected a mouse via USB and got SU flashed)
On my Tab4 8 the touch is also not working with this image.
I think the following lines from dmesg.log are showing, that the touch driver ist not loading:
<4>[ 1.323216] [HXTP] Himax common touch panel driver init
<4>[ 1.323221] [HXTP][ERROR] himax_common_init failed, compare_tp_id = 1
w0rdie said:
The twrp-3.1.1-0-tb_8504x_testing1.img flashes and boots fine but there is no touch input.
Logs: https://www.dropbox.com/s/vo2dvi4frpsf9hf/logs.zip?dl=0
(I connected a mouse via USB and got SU flashed)
Click to expand...
Click to collapse
Do you have the TB-8504X or TB-8504F? Very strange that the touch driver won't load. if you have the F variant then maybe it has a slightly different hardware in which case I'll have to compile separate TWRP for this variant. Can you extract me your stock boot or recovery image and send it to me? I'd then build TWRP with the kernel from your tablet and we'll see what happens
EggZenBeanz said:
Thanks!!!! Confirmed TB-X704F
Click to expand...
Click to collapse
Here is the system image in sparse format for fastboot flashing: MEGA
matshias said:
Here is the system image in sparse format for fastboot flashing: MEGA
Click to expand...
Click to collapse
Amazing, thank you so much. All worked and back to normal. I'll root again with the screen off and provide logs
Sorry if this is off topic, but is there a way to convert the Chinese versions of the Tab 4 / Plus to the Global rom? I'm thinking of getting one from China when I'm there but the lack of Google Play support is a major deal breaker.
Can someone tell me Completly How to install Android Q GSI Version On Oneplus5. I tried But i went to stock fastboot mode. can't boot.
things i did
1. install mokee rom
2. wipe data, system, Cache
3.flash the image file
4.mount vendor then format data
5. then reboot system.
its went to fastboot mode. is it correct method??
radirajjj said:
Can someone tell me Completly How to install Android Q GSI Version On Oneplus5. I tried But i went to stock fastboot mode. can't boot.
things i did
1. install mokee rom
2. wipe data, system, Cache
3.flash the image file
4.mount vendor then format data
5. then reboot system.
its went to fastboot mode. is it correct method??
Click to expand...
Click to collapse
Hello Radirajjj,
I'm also trying to install it Right now I can't flash the GSI because apparently my phone doesn't support Project Treble. I'm actually using OB29.
Here what I get when I play :
Code:
adb shell getprop ro.treble.enabled
Code:
false
Did you pass this step ?
Khwaja7 said:
Hello Radirajjj,
I'm also trying to install it Right now I can't flash the GSI because apparently my phone doesn't support Project Treble. I'm actually using OB29.
Here what I get when I play :
Did you pass this step ?
Click to expand...
Click to collapse
I installed treble check app, and it says my device support treble.
And just now run this command and it says "True"
radirajjj said:
I installed treble check app, and it says my device support treble.
And just now run this command and it says "True"
Click to expand...
Click to collapse
Ok. Going to install Mokee and check if my device is compatible with Treble too.
Khwaja7 said:
Ok. Going to install Mokee and check if my device is compatible with Treble too.
Click to expand...
Click to collapse
By updating to the newest oos build, your phone will make a vendor partition and support treble...I haven't tried to flash beta 2 due to reported bugs and secured wifi issues, but wiping all data and internal storage, using stock vendor and boot images, you should be able to boot
Someone please correct me if I'm wrong
Khwaja7 said:
Ok. Going to install Mokee and check if my device is compatible with Treble too.
Click to expand...
Click to collapse
did you install?? Treble supported??
There is now a Semi-GSI Q! Should be easier to install. Did anyone tried? (With or without mokee).
https://forum.xda-developers.com/pr...ment/rom-android-p-developer-preview-t3816659
BakedTator said:
By updating to the newest oos build, your phone will make a vendor partition and support treble...I haven't tried to flash beta 2 due to reported bugs and secured wifi issues, but wiping all data and internal storage, using stock vendor and boot images, you should be able to boot
Someone please correct me if I'm wrong
Click to expand...
Click to collapse
I did install the newest stable OOS build, I can see the Vendor partition AND Treble Check app is saying my phone does support Treble. However, the command to check it through ADB is still saying "false".
radirajjj said:
did you install?? Treble supported??
Click to expand...
Click to collapse
I did install Mokee too, but for me it isn't supporting Treble (command to check Treble still saying "false" as well).
furious.builder said:
There is now a Semi-GSI Q! Should be easier to install. Did anyone tried? (With or without mokee).
https://forum.xda-developers.com/pr...ment/rom-android-p-developer-preview-t3816659
Click to expand...
Click to collapse
Thank you, going to give it a try !
Can't tell what I do wrong, if you have any clue please let me know
@Khwaja7, I think that to have a full A/B support through MoKee you have to fully format /Data but for semi GSI I don't think full A/B is required
furious.builder said:
@Khwaja7, I think that to have a full A/B support through MoKee you have to fully format /Data but for semi GSI I don't think full A/B is required
Click to expand...
Click to collapse
Is all treble roms are have voLTE bug???
furious.builder said:
@Khwaja7, I think that to have a full A/B support through MoKee you have to fully format /Data but for semi GSI I don't think full A/B is required
Click to expand...
Click to collapse
Okay, I did follow the instructions you gave us in your previous post; however, I can't get it working.
Sometimes when booting, it only powers the notification light in blue, and nothing happens. Sometimes, it has a bootloop showing "Android" .
I tried to flash every single img in this Mega repository :
https://mega.nz/#F!CYQxgCDK!Dl4kKANVDRy5kOFkNsuMVw
I think OP5 has A/B partition, but I'm not sure about this so I tried each one.
Can you help me to install this ? I just want to give it a try Did you install it ? @furious.builder
I really think it's A only, but I may be wrong
A friend tried many techniques on his 5T and soft bricked his phone... I think we need an updated Vendor even if it should work on 8.1/9's vendors :/
furious.builder said:
I really think it's A only, but I may be wrong
A friend tried many techniques on his 5T and soft bricked his phone... I think we need an updated Vendor even if it should work on 8.1/9's vendors :/
Click to expand...
Click to collapse
Ok, I see. Thanks for your comment.
So I think we should just wait instead of trying strange techniques :angel:
Did your friend tried this technique, but with a Q semi-GSI ? https://forum.xda-developers.com/oneplus-5/how-to/guide-install-aosp-pie-9-0-via-project-t3833961
radirajjj said:
Is all treble roms are have voLTE bug???
Click to expand...
Click to collapse
VoLTE is always listed as an issue, so I guess yes I can't try, so I can't tell, sorry !
use latest coltos vendor, this work install Q gsi on op5
but need system patch
jahidinbedod said:
use latest coltos vendor, this work install Q gsi on op5
but need system patch
Click to expand...
Click to collapse
Did you try it on op5?
Please explain what do you mean by system patch and also tell us what major bugs you are facing if using on an op5.
Edit: looking at the baseband, thats an op5
Will be thankful if you list the procedure for helping others.
jahidinbedod said:
use latest coltos vendor, this work install Q gsi on op5
but need system patch
Click to expand...
Click to collapse
Thanks ! Going to try it
brajesh.sharma87 said:
Did you try it on op5?
Please explain what do you mean by system patch and also tell us what major bugs you are facing if using on an op5.
Edit: looking at the baseband, thats an op5
Will be thankful if you list the procedure for helping others.
Click to expand...
Click to collapse
System patch is flashing the GSI system img, I think
install this file after install Permissiver_v2 and FixZygote
only decrypted devices
op5 is Aonly
jahidinbedod said:
install this file after install Permissiver_v2 and FixZygote
only decrypted devices
op5 is Aonly
Click to expand...
Click to collapse
And what does this do?
wifi works on android Q GSI ?
Chiku7 said:
wifi works on android Q GSI ?
Click to expand...
Click to collapse
Works on Erfans newest build, atleast with ob28 vendor