Related
Hello, iam trying to get teamwin recovery on the gio
Current status:
-Compiles good, no errors and a recovery.img of 7.9MB, phiexz device profile used
-But doesnt work actually, if it boots the screen turns blue , and adb doesn't work
Can some more experienced dev help me?
What i did
Downloaded CM7 source
Insterted phiexz device profile in it
Insterted TWRP stuff in it
Adjusted boardconfig.mk:
Commented out custom graphics libary(graphics.c)
Added TWRP required flags in the boardconfig
Did a make -j5 recoveryimage
Can somebody point out what iam doing wrong?
!!! NOTE: THIS IS FOR INTERNATIONAL TEGRA 3 HTC ONE X VERSION ONLY !!!
Ave, folks
Touch Recovery versions won't be available here, as touch recovery source is closed and owned by Koush; it's his baby, so thank him pls for his work he put in it
Credits:
Koushik Dutta for his Clockworkmod Recovery and giving us the source to play with! And for the kernel which is used in this recovery
Steve Kondik for his CyanogenMod repos (from where I cloned the recovery source tree)
WHAT'S WORKING?
ADB
USB Mass Storage
ADB Sideload
Charging while phone is off or in recovery
and everything else which is expected to work
works faster than standard CWM
FEATURES:
YES/NO Adv-Wipe JB422
using 3.1.10 JellyBean kernel from now on reverted to 2.6x kernel for better compatibility
UMS unmounting working now
bigger font
only one yes & no in confirmation menus, yes on first place (you can do this with standard version too, just create a file named ".one_confirm" in /sdcard/clockworkmod folder)
additional menu entry "advanced - reboot bootloader"
additional menu entry "advanced - wipe everything except sd" wipes system, userdata, sd-ext, android-secure and cache partition
now using erase_volume for wipe'em all instead of a simple format
edited menu entry "advanced - wipe dalvik and cache" wipes not only dalvik cache but cache partition, too
removed "partition sdcard" menu entry
removed "key test" menu entry
added "POWER OFF" menu entry
governor changed to interactive, therefore...
[email protected] only when needed => much more battery friendly and faster
single core (original CWM from recoverybuilder runs with 4cores active)
noop scheduler
As always: I'm not responsible for anything that may happen to your device when you're flashing this. You're doing this on your own risk. But: it's working
How do I flash this?
The usual way (presuming a working adb / fastboot environment):
- reboot to hboot
- open a cmd / terminal, cd to the location to which you downloaded the recovery-image and type
- fastboot flash recovery <name_of_recovery_image>.img
- done
Have fun!
Downloads:
JellyBean "CWM-based AdvWipe JB422 Recovery" v1.2:
- Clockworkmod Recovery 6.0.3.2 NonTouch
- Mirror
.
.
.
OLD VERSIONS (no more supported)
New JellyBean "CWM-based AdvWipe JB422 Recovery" v1.1:
- Clockworkmod Recovery 6.0.3.0 NonTouch
- Mirror
New JellyBean "CWM-based AdvWipe JB422 Recovery" v1.0:
- Clockworkmod Recovery 6.0.3.0 NonTouch
- Mirror
Version 2.1:
- Clockworkmod Recovery 6.0.2.7 NonTouch, Yes/No Adv-Wipe version, Mirror
Version 2.0:
- Clockworkmod Recovery 6.0.1.9 NonTouch, Yes/No Adv-Wipe version, Mirror
- Clockworkmod Recovery 6.0.1.9 NonTouch, Standard version, Mirror
Version 1.3:
- Clockworkmod Recovery 6.0.1.5 NonTouch, Yes/No Adv-Wipe version
Version 1.2a:
- Clockworkmod Recovery 6.0.1.5 NonTouch, Yes/No Adv-Wipe version
Version 1.2:
- Clockworkmod Recovery 6.0.1.5 NonTouch, Standard version
- Clockworkmod Recovery 6.0.1.5 NonTouch, Yes/No Adv-Wipe version
Version 1.1:
- Clockworkmod Recovery 6.0.1.5 NonTouch, Standard version
- Clockworkmod Recovery 6.0.1.5 NonTouch, Yes/No Adv-Wipe version
Source:
Github
BUGS:
Touch keys aren't working
Same bug as in other recoveries: device starts itself after a while when charging in switched off state. But it looks like this is only happening with Sense ROMs and not with AOSP / AOKP / CM
How to check if it's really charging...?
Code:
adb shell cat /sys/devices/platform/htc_battery/power_supply/battery/batt_vol
adb shell cat /sys/devices/platform/htc_battery/power_supply/battery/status
Changelog:
6 May 2013:
CWM 6.0.3.2, Adv-Wipe JB422 v1.2
- updated to newest sources
- reverted back to 2.6.x kernel, should solve UMS / ADB problems for some
.
.
.
11 April 2013:
CWM 6.0.3.0, Adv-Wipe JB422 v1.1
- used 3.19 firmware base kernel: PLS REPORT BACK IF CHARGING / ADB (install newest adb drivers first!) / USB Mass Storage etc IS WORKING!!
i'm on 3.14 firmware base, so can't test it
- added two known lun file pathes, backwards compatibility should be given
11 April 2013:
CWM 6.0.3.0, Adv-Wipe JB422 v1.0
- updated to latest sources
- left in "install zip from sideload": it has a cancel option now and: it's working
- removed "partition sdcard" menu entry
- switched from format to erase_volume for wipe'em all function
- used freshly compiled cm stock 3.1.10 kernel
07.01.2013
CWM 6.0.2.7, Adv-Wipe v2.1
- updated to latest sources
22.11.2012
CWM 6.0.1.9, Adv-Wipe v2.0
- updated to latest sources (incl. git)
- rewrote edits (source changed a little bit)
- edited some displayed texts
- added poweroff menu entry
23.10.2012
CWM 6.0.1.5, Adv-Wipe v1.3
- removed "install zip from sideload" functionality and menu entry
02.11.2012
CWM 6.0.1.5, Adv-Wipe v1.2a
- reverted key remapping: vol up = scroll up, vol down = scroll down, power button = select/enter
18.10.2012
CWM 6.0.1.5, Adv-Wipe v1.2
- Added key repeating (scroll on holding button)
- Remapped keys (see above)
- Bigger font for standard version, too
- Description in header for standard version, too
- Unmounting usb mass storage now does its job
17.10.2012:
CWM 6.0.1.5, Adv-Wipe v1.1
initial release
How to compile this?
- Prerequisite: device tree for your device and correctly configured recovery configuration in BoardConfig.mk of your device tree
- Get the Cyanogenmod 10 source: it's already described in many threads how to do this
- Create a file named "local_manifest.xml" in your (cm10-source-root-dir)/.repo folder and put the following in:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project name="CyanogenMod/android_bootable_recovery" path="bootable/recovery" />
<project name="seader/android_bootable_recovery" path="bootable/recovery" />
</manifest>
- Sync again with "repo sync"
- Build the recovery with following command (replace endeavoru with your device you want to build for):
Code:
. build/envsetup.sh; lunch cm_endeavoru-userdebug; mka recoveryimage
Hi,
i see no advantages over the version 5.8.4.0.
5.8.4.0 works completely.
cheers
starbase64
...current Clockworkmod Recovery Touch versions...
Click to expand...
Click to collapse
...but 6.x versions don't
starbase64 said:
Hi,
i see no advantages over the version 5.8.4.0.
5.8.4.0 works completely.
cheers
starbase64
Click to expand...
Click to collapse
Well ICS works just fine too doesn't it? So why does Google or HTC even bother putting out Jellybean or anything else. Because people want updated software with new features. So if you want to use the older then do so, no need to comment letting us know you don't want it. I highly doubt even one single person reading this thread is going to think to themself before downloading, "hmm, I wonder if starbase64 is using this, cause if he's not I'm not."
@OP, thanks for your work and releasing this for us to try.
xD he only stated his opinion np @all, and he's right, too: beside the fact, that new version brings new stuff like dedupe backup format etc.
seadersn said:
!!! NOTE: THIS IS FOR INTERNATIONAL TEGRA 3 HTC ONE X VERSION ONLY !!!
Ave, folks
As current Clockworkmod Recovery Touch versions doesn't offer USB Mass Storage and for some versions no charging mode too (while off or in recovery), I decided to offer a fully functional NON TOUCH version with everything working. Better have a fully working non touch recovery than a touch version with some essential stuff missing; beside that, touch is for the lazy ones
Touch Recovery versions won't be available here, as touch recovery source is closed and owned by Koush; it's his baby, so thank him pls for his work he put in it
Credits:
Koushik Dutta for his Clockworkmod Recovery and giving us the source to play with! And for the kernel which is used in this recovery
Steve Kondik for his CyanogenMod repos (from where I cloned the recovery source tree)
What's working, for both standard and edited versions?
ADB
Usb Mass Storage (unmounting fixed)
Charging while phone is off or in recovery
and everything else which is expected to work
What versions are available?
Standard version with no edits
YES/NO Adv-Wipe version with additional stuff:
- only one yes & no in confirmation menus, yes on first place (you can do this with standard version too, just create a file named ".one_confirm" in /sdcard/clockworkmod folder)
- bigger font
- only one yes and no in confirm menus, yes on first place
- additional menu entry "advanced - reboot bootloader"
- additional menu entry "advanced - wipe everything except sd" wipes system, userdata, sd-ext, android-secure and cache partition
- edited menu entry "advanced - wipe dalvik and cache" wipes not only dalvik cache but cache partition, too
- removed "key test" menu entry
As always: I'm not responsible for anything that may happen to your device when you're flashing this. You're doing this on your own risk. But: it's working
Have fun!
Downloads:
Clockworkmod Recovery 6.0.1.5 NonTouch, Standard version
Clockworkmod Recovery 6.0.1.5 NonTouch, Yes/No Adv-Wipe version
Source:
Github
Note: you should be able to use this source for compiling a working recovery for other devices, too. If you don't know how to do this... Well, let it be
Click to expand...
Click to collapse
Thanks! Now a touch version would be great... waiting..
won't come, at least not from me => necessary files are on koush's hard disk only
great,thanks!
there's a button for thanking merci!
@seadersn
will it boot if the phone is put in charge while its turned off(one of the issues in the current cwm)?
nope, it will stay off only thing which will turn on is the led
btw: what are the other issues of jenkins recovery builder clockworkmod versions?
Long time no see my friend :highfive:
salve, maestro you're a hox owner too? greets
seadersn said:
salve, maestro you're a hox owner too? greets
Click to expand...
Click to collapse
Is it possible to build touch version based on this ? http://forum.xda-developers.com/showthread.php?p=32930355#post32930355
should work; but i think usb mass storage and charging won't work
updated 1st post, forgot a little bit
added:
Both versions contain following additional edits:
- governor changed from userspace to interactive
- therefore [email protected] only when needed
- single core (original CWM from recoverybuilder runs with 4cores active, clocked @1500MHz)
- noop scheduler
:cyclops:
@ OP can you provide some screenshot, please..
this isn't 4ext, screenshots aren't possible and here's no cam available for taking photos. when there's the possibility to take some pics i'll use it, ok?
How can I go out of the adb sideload option one chosen? Had to reboot the device. Also if tried this option will work?
Also one another thing, can it be that the recovery is faster? Because I would say its faster, pretty much so. Even though you write is single core and UC. Or is it a placebo effect as its soon in the morning?
Thanks
I got my hands on a Xperia S and just started looking into the android development stuff...
If I would compiled a JB kernel for the device as well as AOSP 4.1.2, and lets say the recoveryimage from CM. I am wondering how / if everything works together.
The recovery partition seems to be non writable and it seems that people are advised to flash the CWM recovery to the boot partition. I thought this partition is the one for the actual kernel? Even if so, how does the combination of my kernel.elf and CWM recovery work?
If I get this done this brings up the next question, is the same kernel used to bootup the whole system later on? What I would like to see is something like a flow chart where I see how control is passed around and to what address, and which initrd does what... maybe someone can correct or expand the following:
first stage bootloader (recovery partition?)
apparently I can boot into different modes (fastboot, flash, ...)
on normal boot the kernel from the boot partition gets loaded into ram (execution starts at 0x40208000 ?)
kernel (boot partition)
... does initializaiton stuff ...
in the end init from initrd fires up either the CWM recovery (?) or userspace (?)
I assume in userspace the usr init fires up the dalvik vm and android boots as usual (this is the system partition I get from AOSP ?)
How exactly does it work for CWM and where is it located in the ROM and RAM?
I am sorry if the information is already posted somewhere in these forums but I wasn't able to acquire it so far.
cheers
Welcome to the forum. Thread moved, please post your questions here in Q&A in future.
Thanks
AvRS
Hi,
Let me try to clarify a bit, at least on how I see it:
Bootloader is indeed capable of handling multiple modes:
- flash mode
- fastboot
- normal kernel boot
- recovery / fota kernel boot (disabled with unlocked bootloader)
When unlocking bootloader, the only kernel we can boot is normal kernel. You can write to fota kernel partition, but it will not boot anything unsigned there and will boot normal kernel instead.
So in our custom roms, Android and recovery are using the same kernel, we add recovery files in the Android initramfs, and the switch is handled by init.*.rc with a script that detects keypress and is launching recovery if volume key is pressed.
Finally there is a TWRP capable of decrypting /data on android versions > nougat.
Big thanks @NeoArian
I haven't tested everything in detail as I mostly focused on decryption. If you experience issues or can confirm something working that's not green in the table down below, please share.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Status
List template by TWRP
Code:
[B]Blocking checks[/B]
- [COLOR="green"]Correct screen/recovery size[/COLOR]
- [COLOR="green"]Working Touch, screen[/COLOR]
- [COLOR="green"]Backup to internal/microSD[/COLOR]
- Restore from internal/microSD
- [COLOR="green"]reboot to system[/COLOR]
- [COLOR="green"]ADB[/COLOR]
[B]Medium checks[/B]
- update.zip sideload
- [COLOR="green"]UI colors (red/blue inversions)[/COLOR]
- [COLOR="green"]Screen goes off (and on :))[/COLOR]
- F2FS/EXT4 Support, exFAT/NTFS where supported
- [COLOR="green"]all important partitions listed in mount/backup lists[/COLOR]
- backup/restore to/from external (USB-OTG) storage
- backup/restore to/from adb
- [COLOR="green"]decrypt /data[/COLOR]
- Correct date
[B]Minor checks[/B]
- MTP export
- [COLOR="green"]reboot to bootloader[/COLOR]
- [COLOR="green"]reboot to recovery[/COLOR]
- [COLOR="green"]poweroff[/COLOR]
- [COLOR="green"]battery level[/COLOR]
- [COLOR="green"]temperature[/COLOR]
- encrypted backups
- [COLOR="green"]input devices via USB (USB-OTG) - keyboard, mouse[/COLOR]
- USB mass storage export
- [COLOR="green"]set brightness[/COLOR]
- [COLOR="green"]vibrate[/COLOR]
- [COLOR="green"]screenshot[/COLOR]
Limitations
Following limitations are known:
none
Click to expand...
Click to collapse
prerequisites
For reboot to recovery from your android system (and OTA updates) your ROM needs the following patches 1, 2 and 3. Following ROM's currently support this:
AICP 14
AICP 15
LineageOS 15
LineageOS 16
LineageOS 17
Click to expand...
Click to collapse
For correct time inside TWRP your ROM needs the following patch. Following ROM's currently support this:
AICP 15
LineageOS 16
LineageOS 17
Click to expand...
Click to collapse
Download
SourceForge
AndroidFileHost
Click to expand...
Click to collapse
How to build
https://github.com/115ek/manifest#build-twrp
Click to expand...
Click to collapse
XDA:DevDB Information
[RECOVERY][Unofficial][amami] TWRP 3.4.0, Tool/Utility for the Sony Xperia Z1 Compact
Contributors
115ek, NeoArian
Source Code: https://github.com/115ek/twrp_device_sony_amami
Version Information
Status: Beta
Created 2019-08-25
Last Updated 2020-08-22
Changelog
15.09.2020 3.4.0-1
again: fix non working OTA update in rare cases (rebooting to recovery and stucking there unable to install update automatically)
22.08.2020 3.4.0-0
latest TWRP changes
29.02.2020 3.3.1-0.4
display sony bootlogo at boot
show version number
remove TWRP app
19.09.2019 3.3.1-0.3
fix non working OTA update (rebooting to recovery and stucking there unable to install update automatically)
05.09.2019 3.3.1-0.2
enable reboot to bootloader (fastboot mode) (you have to connect the phone via usb BEFORE rebooting)
25.08.2019 3.3.1-0.1
decrease size
allow decryption in any case of patchlevel value
25.08.2019 3.3.1-0
initial release
Reserved
Backup to microSD seems to be working fine (haven't restored anything yet):good:
I uploaded a new build 3.3.1-0.1 with decreased size and a "more clean" way to allow /data decryption.
Furthermore I thought about getting this official.
BTW: You won't see the increased version number in TWRP. It's still 3.1.1-0
115ek said:
I uploaded a new build 3.3.1-0.1 with decreased size and a "more clean" way to allow /data decryption.
Furthermore I thought about getting this official.
BTW: You won't see the increased version number in TWRP. It's still 3.1.1-0
Click to expand...
Click to collapse
Hi, thank you for this build. I was waiting to try Pie on my z1 compact and I'm glad I did because the version of TWRP was blocking my use of encryption.
Sadly I didn't have luck installing the latest builds (the ones from 3 days ago and one week ago) on my Z1 Compact. I got this error:
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
When trying to flash to recovery partition. The same command worked to flash back to 3.2.3 (not sure if necessary, done just in case). If there's any way you could look into these builds I'd appreciate it!
bananabytes said:
Hi, thank you for this build. I was waiting to try Pie on my z1 compact and I'm glad I did because the version of TWRP was blocking my use of encryption.
Sadly I didn't have luck installing the latest builds (the ones from 3 days ago and one week ago) on my Z1 Compact. I got this error:
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
When trying to flash to recovery partition. The same command worked to flash back to 3.2.3 (not sure if necessary, done just in case). If there's any way you could look into these builds I'd appreciate it!
Click to expand...
Click to collapse
What command did you use?
Code:
fastboot flash recovery
or
Code:
fastboot flash FOTAKernel
Do you have the newest bootloader installed? So can you boot directly into recovery with VOL down and power pressed (with 3.2.3 version where flashing was successful)?
Or do you use the method with pressing VOL down when the LED lights up?
EDIT:
By looking at your error code I get the feeling it has something to do with fastboot directly. libsparse is a build dependency of the fastboot binary.
What version of fastboot are you using?
I'm using fastboot installed from the packetmanager with
Code:
apt install fastboot
.
Code:
fastboot --version
gives fastboot version 1:8.1.0+r23-5~18.04.
This would mean 27.0.0 or 27.0.1 according to this scheme. I don't know why they are using different naming schema
However, I'd guess you're using an outdated version (or a very current one - but I don't think so).
115ek said:
What command did you use?.
Click to expand...
Click to collapse
I used fastboot flash recovery, with the newest bootloader. This time I got into recovery by selecting it in my older TWRP because I always get the up/down method mixed up, I have done it before it's just easier that way.
115ek said:
By looking at your error code I get the feeling it has something to do with fastboot directly. libsparse is a build dependency of the fastboot binary.
...
However, I'd guess you're using an outdated version (or a very current one - but I don't think so).
Click to expand...
Click to collapse
I am actually indeed using a very current version, 29.0.2 (so your second less likely guess was correct!) I'm on Manjaro/Arch so we get the bleeding edge updates unlike if you are on a Debian/Ubuntu system that's tied to a lot of different libraries and held back. This is exactly why I stopped using those distros but this is the first time I've had the problem in reverse. I don't know if this is a bug that was introduced into fastboot or what. I do see that the more recent versions have things to do with partitioning. This may be a bug to open with fastboot or to look into further with them? But if it's not a bug with them it would be good to have the build working on the latest fastboot.
bananabytes said:
I used fastboot flash recovery, with the newest bootloader. This time I got into recovery by selecting it in my older TWRP because I always get the up/down method mixed up, I have done it before it's just easier that way.
I am actually indeed using a very current version, 29.0.2 (so your second less likely guess was correct!) I'm on Manjaro/Arch so we get the bleeding edge updates unlike if you are on a Debian/Ubuntu system that's tied to a lot of different libraries and held back. This is exactly why I stopped using those distros but this is the first time I've had the problem in reverse. I don't know if this is a bug that was introduced into fastboot or what. I do see that the more recent versions have things to do with partitioning. This may be a bug to open with fastboot or to look into further with them? But if it's not a bug with them it would be good to have the build working on the latest fastboot.
Click to expand...
Click to collapse
Can you please verify that you also fail with the fastboot binary from here
It's also 29.0.2 and it works fine for me.
I have tried this version with LOS 16 and it worked well. Some things to improve
boot to fastboot is not possible
backup and restore of boot is not possible
good catch with encryption, I have give it up :good:
Micha_Btz said:
boot to fastboot is not possible
Click to expand...
Click to collapse
Well, I actually didn't know this was possible in earlier versions. However it should work now --> see the changelog
You have to connect usb cable before rebooting to bootloader, otherwise it won't work and just reboot the system.
Micha_Btz said:
backup and restore of boot is not possible
Click to expand...
Click to collapse
I can't confirm that. What exactly was the problem for you? Backing up or restoring? Did you got any errors?
Have had a look yesterday, Backup and restore of boot is possible (don't now what happends)
@115ek,
I have a mysterious problem with 3.3.1-0.0.and 3.3.1-0.1:
I used all twrp versions before without problems and now your twrp did not show the correct date (1970-xx-xx) and time (7-8 hours back).
I tried the following several times:
1. reflash your twrp, clear recovery and flash again,
2. flash older versions: date and time was wrong even after reboot
The only way to get the correct date/time back in twrp was (at least for me) flash stock ROM with EMMA and after flashing twrp 3.2.3 my backup.
I do not want to repeat this as this is a lot of work incl. copying back the internal storage.
tramp20 said:
@115ek,
I have a mysterious problem with 3.3.1-0.0.and 3.3.1-0.1:
I used all twrp versions before without problems and now your twrp did not show the correct date (1970-xx-xx) and time (7-8 hours back).
I tried the following several times:
1. reflash your twrp, clear recovery and flash again,
2. flash older versions: date and time was wrong even after reboot
The only way to get the correct date/time back in twrp was (at least for me) flash stock ROM with EMMA and after flashing twrp 3.2.3 my backup.
I do not want to repeat this as this is a lot of work incl. copying back the internal storage.
Click to expand...
Click to collapse
Can you try the latest version?
At first you have to set the right timezone in TWRP settings.
The time is stored in a real time clock (RTC) which runs even if the device is powered off. Setting and reading it's value is done by a kernel driver. If you set the right time in android system it gets stored in the RTC. Then, if you boot into TWRP, the time is read again. And for me this works fine. However it takes some seconds (there's a wrong time at the beginning).
115ek said:
Can you try the latest version?
At first you have to set the right timezone in TWRP settings.
The time is stored in a real time clock (RTC) which runs even if the device is powered off. Setting and reading it's value is done by a kernel driver. If you set the right time in android system it gets stored in the RTC. Then, if you boot into TWRP, the time is read again.
Click to expand...
Click to collapse
Thank you. I know this all, I tried reset to default in TWRP and set TZ etc. but these two mentioned TWRP versions do not read the RTC time (AICP ROM).
All TWRP versions before were ok. I tried this several times.
I noticed this "bug" on my Z1c after a backup with your TWRP (Date from 1970 and a complete false time even after setting the TZ).
Even after flashing one of the older TWRP date/time are wrong (only in TWRP), after booting to Android date/time is correct until I boot to TWRP again.
As I wrote the way back to a correct date/time in TWRP was for me flashing stock ROM with EMMA.
Where is this "kernel driver"? In your TWRP version or in a hidden partition? Sorry I do not know much of these internals.
I assume you did not change in the newest version something regarding this problem.
I have not the time to try the last version for now
Generic question re: encrypting this device
Installed this twrp version and (unlike others) I don't see anything strange. Only thing I haven't tried so far is restoring a nandroid backup I created with this twrp release.
A few days back after I had installed this the first time Itried to encrypt my phone; after a while I received the message that encryption was completed.
Then upon reboot of the device I had to unlock it even before boot sequence had started. Aftter unlocking booting resumed and from then on everything appeared to be as before.
This surprised me a bit because on my other phone (OnePlus6 running stock OOS Pie) I have to unlock after boot sequence has completed. But OK, this may be the LOS 16 way.
Then I devided to unencrypt the phone (this is my secondary device and I only use it for playing around a bit, until I decide to sell it, maybe). Again, from my OP6 I'm used to the fact that if I remove any device locking pattern encryption is gone. But obviously not on my Z1c: after I had removed the security pattern (= set security to nothing) everything appeared to be normal. But after the next reboot all data were gone.
Question: is there a supported way to unencrypt this phone without losing any data?
If there isn't such a way: what happens to my Nandroid backups I took while the phone was encrypted? Are they still usable e.g. after I install a ROM update?
tramp20 said:
Thank you. I know this all, I tried reset to default in TWRP and set TZ etc. but these two mentioned TWRP versions do not read the RTC time (AICP ROM).
All TWRP versions before were ok. I tried this several times.
I noticed this "bug" on my Z1c after a backup with your TWRP (Date from 1970 and a complete false time even after setting the TZ).
Even after flashing one of the older TWRP date/time are wrong (only in TWRP), after booting to Android date/time is correct until I boot to TWRP again.
As I wrote the way back to a correct date/time in TWRP was for me flashing stock ROM with EMMA.
Where is this "kernel driver"? In your TWRP version or in a hidden partition? Sorry I do not know much of these internals.
I assume you did not change in the newest version something regarding this problem.
I have not the time to try the last version for now
Click to expand...
Click to collapse
Flashing stock ROM isn't necessary - I'm 99% sure. Maybe you can get a log with
Code:
adb pull /tmp/recovery.log
while your in TWRP and connected to a PC...
The kernel driver is - as the name says - located in the kernel, which is part of the recovery.img
So everyone flashing this image should have the same functionality (in theory). As it works for me (and some others) I'm just wondering.
lm089 said:
Installed this twrp version and (unlike others) I don't see anything strange. Only thing I haven't tried so far is restoring a nandroid backup I created with this twrp release.
A few days back after I had installed this the first time Itried to encrypt my phone; after a while I received the message that encryption was completed.
Then upon reboot of the device I had to unlock it even before boot sequence had started. Aftter unlocking booting resumed and from then on everything appeared to be as before.
This surprised me a bit because on my other phone (OnePlus6 running stock OOS Pie) I have to unlock after boot sequence has completed. But OK, this may be the LOS 16 way.
Then I devided to unencrypt the phone (this is my secondary device and I only use it for playing around a bit, until I decide to sell it, maybe). Again, from my OP6 I'm used to the fact that if I remove any device locking pattern encryption is gone. But obviously not on my Z1c: after I had removed the security pattern (= set security to nothing) everything appeared to be normal. But after the next reboot all data were gone.
Question: is there a supported way to unencrypt this phone without losing any data?
If there isn't such a way: what happens to my Nandroid backups I took while the phone was encrypted? Are they still usable e.g. after I install a ROM update?
Click to expand...
Click to collapse
The behaviour is totally expected as amami uses the deprecated full disk encryption (FDE). Most likely your oneplus 6 is using file based encryption (FBE). That's the reason it can boot to your lockscreen because some files necessary for booting aren't encrypted (or not encrypted using your password...). To boot a device with fully encrypted /data you have to decrypt it first. If you're interested in details have a look here.
The other thing sounds a bit strange. However I don't know if it's possible to remove the FDE completely. Maybe the device just sets a default password then?
Concerning your question:
What definitely should work is taking a backup in TWRP (of course need to decrypt /data before), then format /data and restore the backup. Anyhow - I didn't test such a case so far.
115ek said:
Flashing stock ROM isn't necessary - I'm 99% sure. Maybe you can get a log with
Code:
adb pull /tmp/recovery.log
while your in TWRP and connected to a PC...
The kernel driver is - as the name says - located in the kernel, which is part of the recovery.img
Click to expand...
Click to collapse
Flashing stock ROM was the only way that all older TWRP could read the correct date again after trying your twrp version.
I will try to get a log if I have enough time.
So the recovery.img = twrp.img or at least a part of it?
Thank you.
New update:
As I had problems with installing OTA updates (especially with /data encrypted, but not limited to) on LineageOS 16.0 I came up with a fix.
Download Currently only on sourceforge - android filehost is buggy at the moment...
19.09.2019 3.3.1-0.3
fix non working OTA update (rebooting to recovery and stucking there unable to install update automatically)
Edit:
As reminder for me / interested guys: This commit breaks the OTA updating in some cases (when mmap isn't sufficient). The buildflag
Code:
-D_FILE_OFFSET_BITS=64
doesn't work as intended on my setup. Maybe I missed something.
tramp20 said:
@115ek,
I used all twrp versions before without problems and now your twrp did not show the correct date (1970-xx-xx) and time (7-8 hours back).
Click to expand...
Click to collapse
Have the same time/date problem with twrp-3.3.1-0.3-amami.img
recovery.log >> https://pastebin.com/rBdHAmz2
Also does not reboot into the recovery from system (AICP 14), just shutdown and then power+volume down works.
Hello everyone
I have a rooted (with Magisk) Samsung Galaxy S20 Ultra 5G (G988B) device with TWRP installed in recovery partition.
Stock kernel version: 4.19.187-20291612
Build number: G988BXXU5CTKG
My purpose is to have a custom kernel which is identical to stock kernel except for configs for ftrace and kgdb (can be changed in defconfig before compilation)
Steps I've performed to flash a custom kernel for the given device:
1) Downloaded Linux Kernel for the given device from https://opensource.samsung.com/ SM-G988B_RR_Opensource.zip according to the above mentioned build number
2) Used https://github.com/kdrag0n/proton-clang toolchain to build the kernel
3) Used Android Image Kitchen to generate a new boot.img in the following way:
* Extracted boot.img from the device via dd utility (100% correct, I've reflashed the extracted image for the sake of validation and had no problems)
* ./unpacking.sh original_boot.img
* Replaced original_boot.img-kernel file in /split_img directory with custom_kernel_root_dir/arch/arm64/boot/Image
* ./repacking.sh
* Got image-new.img which must contain a bootable custom kernel
4) Rebooted into TWRP and flashed the image-new.img in Boot and then rebooted into System
After that, the device is stuck (NOT bootloop!) in warning screen (device logo + name and warning about an unlocked bootloader warranty void) forever. Luckily, I am able to reboot to TWRP and reflash the previous boot.img in order unbrick the device and be able to boot into the rooted device again.
During unpacking and repacking it seems that the original and the custom boot.img files have the same values for kernel base, offset and other values.
So what's the problem? Can toolchain be problematic/unsuitable even though I was able to compile the kernel with it?