Database Develop

[STOCK][C6602&C6603][4.2.2] Update to 10.3.A.0.423 [Rooted & XZDualRecovery][LB/UB]

[STOCK][C6602&C6603][4.2.2] Update to 10.3.A.0.423 [Rooted & XZDualRecovery][LB/UB]
Requirements:
Flashtool by @Androxyde
XZDualRecovery 2.5 BETA
Current FW version: 10.1.A.1.350, 10.1.A.1.434, 10.1.1.A.1.253 or 10.1.1.A.1.307 all can be updated!
Special features:
Superuser integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.5 BETA (CWM 6.0.3.2 & TWRP 2.5.0.0) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
@shem2409 created a nice youtube video guide to assist you in your work, be sure to check this post for it! Thanks m8!
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
C6602: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6602: Download C6602.flashable.423.zip (Bittorrent: 686MB) and C6602_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6602.flashable.423.zip' on (the external) SDcard1;
Put 'C6602_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6602.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6602_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
C6603: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6603: Download C6603.flashable.423.zip (Bittorrent: 719MB) and C6603_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6603.flashable.423.zip' on (the external) SDcard1;
Put 'C6603_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6603.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6603_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone.
After updating your NFC firmware and some update information has been displayed, all is done!
I have done this myself, using my own method and I have not found any problem yet, again! :fingers-crossed:
Enjoy! :victory:
Known XZDualRecovery Issues:
TWRP Usage warning: It seems TWRP 2.5.0.0 has issues with the internal storage, which seem related to the changes made to support encrypted storage volumes... This means the internal storage sometimes shows up almost empty (just folders) and no files. Try to use CWM when that happens.
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a /system ONLY using any means you are familiar with so you can try again.
Root it using [Z][ROOT] DooMLoRD Easy Rooting Toolkit.
Install XZDualRecovery and then try to update again using TWRP. This time you can skip the FTF as it has already done it's job.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /tmp/XZDualRecovery, pack them up and send them to me.
Thank you
Flashable ROM Mutator:
Download AROMA ROM Mutator 0.14
This (former patch package) uses AROMA to create a user friendly menu to choose between updates to be installed.
If you want to switch from SuperSU (default in this ROM) to SuperUser (Be careful, SuperUser is incompatible with 4.2.2!) you can use this to make the change.
If you have the reboot problem when trying to remount /system writable, you can reinstall the superuser app of your preference, it's installation includes the latest patch.
If you are missing /system/bin/chargemon.stock and you want to be able to charge your phone while it's turned off.
Flash using one of the recoveries!
Version 0.13 and upwards is using AROMA 2.70B1 or better, the below warning can be ignored for now. Let me know how it performs!
AROMA Warning: AROMA currently works best in TWRP but even there it has some issues on the Z/ZL. It sometimes does not start up correctly or it has a 'sticky button' issue. It makes it a little less easy to use but this will be fixed in time. It is a combination problem caused by the new hardware and incompatibility with it and the fact the recoveries both have been updated considerably to work on the latest phones, causing issues with some functionality of AROMA.
If it hangs when trying to start, reboot your phone and try again.
If it has the sticky buttons, press the button again to activate.
You can avoid the sticky buttons by pressing them for about half a second (that means not too short and not too long). It will work, it's just showing a bug associated with the latest recoveries.
The Samsung S4, HTC One and One X and the Nexus 4 & 7 show the same issues. For them AROMA sometimes crashes, this is an issue i have not yet observed on the Z/ZL.
Thanks go to @Androxyde for the FTF creation, cheers m8!

nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.

After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.

Ya, I need manual install dual boot to access back to CWM/TWRP then just can install but the preinstall superuser root is not working at all.
Root working back by installing DooMLoRD Easy Rooting Toolkit (v15) - http://forum.xda-developers.com/showthread.php?t=2327472

Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?

Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.

Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.

Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.

zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
I got into the same problem, and cannot get out. Anyone has any advice?

please fix dead links

dopeee said:
nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.
Click to expand...
Click to collapse
I found out with the leak by doomlord that it would be possible to update, no need to wipe, the official update works even better
lysp said:
Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?
Click to expand...
Click to collapse
It's meant as an update process and not wiping anything will make the ROM treat your phone as one that just got updated
Faelz said:
Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.
Click to expand...
Click to collapse
Yes, you need a stock ROM before you can flash this, I would not recommend updating your phone from PAC...
bungknees said:
Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.
Click to expand...
Click to collapse
&
zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
&
chuazy said:
I got into the same problem, and cannot get out. Anyone has any advice?
Click to expand...
Click to collapse
I have modified the guide a bit as i should have done before i posted it...
Restore the kernel to anything other then the 4.2.2 one and then try to flash the update package, after flashing the update, re-flash the kernel.
I made one error in my guide: If someone is not using the correct version of XZDualRecovery (2.5 BETA) then you lose recovery when on the 4.2.2 kernel. The correct steps order to prevent this from happening are now in the OP.

please fix dead links

calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
+1

After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?

calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
buciupetru said:
Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.
Click to expand...
Click to collapse
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now

lethalfriend said:
After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?
Click to expand...
Click to collapse
No need: /data/media IS the 'new' location.

[NUT] said:
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now
Click to expand...
Click to collapse
thanks:good:efficient

[NUT] said:
No need: /data/media IS the 'new' location.
Click to expand...
Click to collapse
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location

lethalfriend said:
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location
Click to expand...
Click to collapse
Ooh... i now see what you mean... you are correct. I'll patch up the flashable package to do it automatically.
For you, use a file explorer to move the contents (skipping the 0 folder) of /data/media to /data/media/0/. Sorry man, i missed that completely on my phone

server stilll unreachable.

Problems installing LP roms on MI 3W

I'm starting to worry. Every Lollipop ROM I've tried has problems... EXCEPT Ivan's.
Resurrection Remix - 20150418-cancrosl (stock partitions, I assume?)
The following processes crash on startup: PHONE APP, android.process.acore
XenonHD - 2015-04-18 release, stock partition version
I get this when installing...
Code:
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/userdata, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such file or directory
unmount of /data failed: no such volume
And when I reboot the phone it's stuck in the XenonHD boot logo forever D;
The message appears anyways, whether I have TrueDualBoot enabled or not.
Euphoria OS - 20150501 -lstock (stock partitions, I assume?)
The very first thing that happens upon boot is the Clock app crashing.
Mokee - 2015-04-29 Release
MoKeeLauncher crashes on startup
BlissPop 2.2 - 20150326-1153
The following processes crash on startup: android.process.media, android.process.acore, com.android.phone, Messaging app...
_____________________________________________________________________________
- For all of them I do the 3 wipes before installing: data, cache, dalvik cache.
- I'm using CWM Recovery, v6.0.5.1(R11)
- All the installs have been made in System1
- As said, the only Lollipop ROM that works fine is Ivan's 5.4.11
Am I doing something wrong? What can I do to fix those troubles?

Huh, quick update.
I installed TWRP (at the cost of losing the ability to switch to System2), used the Repair Filesystem function and tried BlissPop. Now it works without anything crashing.
EDIT: Same with Mokee.... stupid CWM, if it had a Repair Filesystem it would've saved me a lot of time =/

wanny! said:
huh, quick update.
I installed twrp (at the cost of losing the ability to switch to system2), used the repair filesystem function and tried blisspop. Now it works without anything crashing.
Edit: Same with mokee.... Stupid cwm, if it had a repair filesystem it would've saved me a lot of time =/
Click to expand...
Click to collapse
good you solved yourself mate :d

Good for you. Btw, what repair filesystem does? Will it wipe your partition as well?
Sent from my MI 3W using xda Forum

solazz said:
Good for you. Btw, what repair filesystem does? Will it wipe your partition as well?
Sent from my MI 3W using xda Forum
Click to expand...
Click to collapse
Nope. From what I think, it's like doing a chkdsk in Windows. Nothing is wiped.

Wanny! said:
Nope. From what I think, it's like doing a chkdsk in Windows. Nothing is wiped.
Click to expand...
Click to collapse
Ok, thanks! Will try it.
Sent from my MI 3W using xda Forum

Can't install any ROM

Hi, I've a big problem with my S3. I wanted to install 5.1.1 Cyanogenmod but every times I got infinite loading (I wiped/factory resetted after but it din't work). Then I wanted to back to SlimSaber 4.4.4
Currently:
- I can get into TWRP recovery
- I can get into download mode, but it contains "Secure Download: Enabled"
- my phone gets infinite loading with SlimKat logo
- It looks that my sd card and internal storage became read-only. I can't copy any file to it, even 100kb image (separately, sd card is also read-only, even having button at "unlocked")
- When I want to use Kies to emergency recover my phone, it downloads files and then always stucks at 0%
- When I want to use Odin it stucks here (tried with few ROMs downloaded via sammobile): http://i.imgur.com/29sHKnU.png
Could you help me, please!
edit: I can write on sd card now, but I've problem with internal storage.
When I wanted to install RR Rom i got this message:
unmount of /system failed ; no such volume
script succeeded: resutl was [0.200000]
Click to expand...
Click to collapse
It looks that I've problem with mounting system. I tried to use "Mount" at TWRP but it didn't help....

Hi! Please !!!!!!! Exactly I have the same problem. ... If u get solution please contact me or leave me replay. . I get crazy from search. ... if i get any solution i will pm u ...Thanks. ..

Copied from my own post:
1. Flashed 4.4.4 nordic version of stock (I9305XXUFNL1_I9305DNFFOB1_I9305XXUFOA1) in ODIN, and let it complete with its setup-wizards and so forth
2. Flashed clockworkmod for i9305 (v. 6.0.4.5) via ODIN
3. I flashed nameless nightly 09.07.2015 in cwm and booted it (without gapps)
4. Rebooted back to recovery and installed tk-gapps.
5. Well everything works
Sent from my Lenovo S6000L-F using XDA Free mobile app
---------- Post added at 14:00 ---------- Previous post was at 13:59 ----------
You could skip part 1 (maybe). But flash that cwm version.
Sent from my Lenovo S6000L-F using XDA Free mobile app

[RECOVERY][UNOFFICIAL] TWRP 3.1.x

UNOFFICIAL TeamWin Recovery Project
for
Samsung Galaxy Tab 10.1
(p4wifi / GT-P7510)
(p4 / GT-P7500)
(p4tmo / SGH-T859)​
Downloads
Mirror
Changelog:
Code:
3.1.1-20171009_v2
- Fix issue with some updater script functions.
3.1.1-20171009
- Use correct ramconsole address.
3.0.3-20170120
- Compile on android-6.0 base
3.0.3-0 (20161229-p4wifi)
- Update prebuilt kernel
3.0.3-0
- Fix adb sideload
- Enable TRIM
- Reduce GPU carveout size
- Update F2FS
- Compile on Android 7.1.1 base
Donate:
via Paypal​
XDA:DevDB Information
TWRP 3.1.x, Tool/Utility for the Samsung Galaxy Tab 10.1
Contributors
decatf
Source Code: https://github.com/decatf
Version Information
Status: Stable
Created 2016-12-19
Last Updated 2019-05-01

'good,i can t wait。

Update from twrp 3.0.2 and after reboot in the new version only perform a cache cleaning and dalvik-cache, it was done indefinitely and after twenty minutes I had to restart by pressing the power button for a few seconds, Reboot so you might have completed the cleanup. How can I get a log of the bug? Maybe help him to correct it.
Sorry for my bad English...

i tried this last night
it installed fine and boots to recovery fine,
but when i tried to install a new rom it freezes and i have to reboot it by holding the power button
the same thing happens if i try to do a wipe

rexxxlo said:
i tried this last night
it installed fine and boots to recovery fine,
but when i tried to install a new rom it freezes and i have to reboot it by holding the power button
the same thing happens if i try to do a wipe
Click to expand...
Click to collapse
Same here on the p4: formatting partitions or installing images never end (and one cannot see any error/warning either). And it the same behaviour when trying to push files via adb while the formatting process or the install of an image hangs --> simply nothing happens (it hangs,too, like if it is blocked).
Fortunately I had an old 2.8.7.0 version on my p4, so this version 3.0.3.0 definately is not working properly on the p4.
Let me know in case I can do some logging or debugging.
Kind regards, mistersixt.

Build 20170119 is posted. If it still freezes then reboot into recovery again and get the kernel log from /proc/last_kmsg

decatf said:
Build 20170119 is posted. If it still freezes then reboot into recovery again and get the kernel log from /proc/last_kmsg
Click to expand...
Click to collapse
Still the same problem with build 20170119, please see last kmesg here (tried to wipe dalvik & cache, it is also waiting forever like when installing zips):
http://144.76.203.117/tmp/last_kmsg_TWRP-3.0.3.0-20170119-P4.txt
Kind regards, mistersixt.

mistersixt said:
Still the same problem with build 20170119, please see last kmesg here (tried to wipe dalvik & cache, it is also waiting forever like when installing zips):
http://144.76.203.117/tmp/last_kmsg_TWRP-3.0.3.0-20170119-P4.txt
Kind regards, mistersixt.
Click to expand...
Click to collapse
Oh, I thought it was locking up. Can you use adb to get the kernel log (dmesg) and and TWRP from /tmp/recovery.log.

decatf said:
Oh, I thought it was locking up. Can you use adb to get the kernel log (dmesg) and and TWRP from /tmp/recovery.log.
Click to expand...
Click to collapse
I am on the move this weekend, will try to help as much as I can on Monday, however, I do remember that accessing the p4 via adb does no longer work once the TWRP is stuck with wiping cache&dalvik or when trying to install a zip file. And it is indeed not locking up completely, this progress bar simply moves forever, with no error message or warning, and one had to do a reset.
Kind regards, mistersixt.

mistersixt said:
I am on the move this weekend, will try to help as much as I can on Monday, however, I do remember that accessing the p4 via adb does no longer work once the TWRP is stuck with wiping cache&dalvik or when trying to install a zip file. And it is indeed not locking up completely, this progress bar simply moves forever, with no error message or warning, and one had to do a reset.
Kind regards, mistersixt.
Click to expand...
Click to collapse
Try the 20170120 build. It is compiled on android 6.0 frameworks instead of 7.1.

decatf said:
Try the 20170120 build. It is compiled on android 6.0 frameworks instead of 7.1.
Click to expand...
Click to collapse
Bingo, this version seems to be running fine again on the p4!
Thanks a lot,
Kind regards, mistersixt.

getting eror 70 flashing gapps

Recovery unsucessful
I am on 3.0.3 20170120 build and when performing a recovery TWRP produces an error in the last part of the recovery when recovering System, data and root.
The process extractTarFork ends with error code 225.

xdatroxx said:
I am on 3.0.3 20170120 build and when performing a recovery TWRP produces an error in the last part of the recovery when recovering System, data and root.
The process extractTarFork ends with error code 225.
Click to expand...
Click to collapse
Go to Advanced.
Tap on Copy Log.
Post the recovery.log that was saved on your device.

decatf said:
Go to Advanced.
Tap on Copy Log.
Post the recovery.log that was saved on your device.
Click to expand...
Click to collapse
I found out the problem occurs when restoring the data partition (tried with different back-up sessions)

xdatroxx said:
I found out the problem occurs when restoring the data partition (tried with different back-up sessions)
Click to expand...
Click to collapse
Did you create a file or folder at /data/app/com.android.vending-1.apk ? Perhaps from one of the methods to prevent Play Services from updating? I can reproduce the same issue by doing this.

Thanks for your support and fast response.
Yes, I did!
If Google Play Store updates then I get Error Messages constantly on the screen which basically makes working with the tablet impossible. That is why I created this file which cannot be updated.
What do you suggest?
I assume the data partition is written correctly during back-up, but cannot be restored because of com.android.vending-1.apk?

xdatroxx said:
Thanks for your support and fast response.
Yes, I did!
If Google Play Store updates then I get Error Messages constantly on the screen which basically makes working with the tablet impossible. That is why I created this file which cannot be updated.
What do you suggest?
I assume the data partition is written correctly during back-up, but cannot be restored because of com.android.vending-1.apk?
Click to expand...
Click to collapse
The permissions are too restrictive such that recovery can't overwrite that file.
Remove that file then restore.
Code:
chattr -i /data/app/com.android.vending-1.apk
rm /data/app/com.android.vending-1.apk
You don't need that hack anymore. Install Play Services 10.5.

Thank you very much!!!
Recovery was successful. :good:

Sorry, but I got another error message when trying to flash Viper4Athmos (https://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137).
Installation of ZIP file aborts with error code 4. Log is attached.
Thanks for taking a look!

[TWRP][E5823] Latest TWRP 3.2.1 for Z5 Compact

Updated TWRP for the Z5 Compact
REQUIRES:
- Unlocked bootloader
- Have Fastboot drivers installed on the PC you use for flashing
FEATURES:
- MTP support
- ADB root
- Reboot to Bootloader
- SD Card access
Not working (for now):
- Decryption <- working on it when I have time
Changelog:
23.02.2018
- Backup/Restore fix for USB OTG
- small fstab tuning (thanks @GreyLeshy)
- DL link updated - Now you will have access to all builds inside GDrive folder
22.02.2018 - 2
- Fix SD Card (again) on latest build
22.02.2018
- USB OTG fixed
15.02.2018
- Possibly fixed decryption, need feedback
13.02.2018
- Fixed SD card
7.02.2018
- First build
DOWNLOAD LINK
Google Drive
Instructions:
- Connect phone to PC in Fastboot mode
- Open Command Prompt and type
Code:
fastboot flash recovery recovery-name.img
- Take off the cable and boot into recovery by holding Power + Vol Down until you feel a vibration
Disclaimer: I am merely distributing the ready image. I will do my best to keep this thread up-to-date with the latest TWRP releases and provide fixed images in case there is a bug, I can help you to solve some problems but do not expect any timeframe.
I am not responsible for any bricked phones, missed alarms or thunderstorms. What you do with your phone is your own choice. Happy flashing!
Credits:
@TwrpBuilder for making this, all credits go to them
and all other maintainers and contributors to the code

trax7 said:
Needs testing:
- Decryption
Click to expand...
Click to collapse
Decryption is not working
Good job anyway, we have an updated TWRP at least!!

Don't need decryption and everything else works fine!! Strange how md5 checksum is now Digest!! Must be an Oreo thing
Sent from my Sony Xperia Z5 Compact using XDA Labs

@trax7
I own a Zuk Z2, on it the decryption problem was caused by unaligned/updated vendor blobs. I hope this can give you an hint on how to fix decryption.

Doe.it said:
Decryption is not working
Good job anyway, we have an updated TWRP at least!!
Click to expand...
Click to collapse
You tried with a password? Try with factory reset (not wipe data) and it should work... Note that you will lose data so be sure to copy it somewhere first.

trax7 said:
You tried with a password? Try with factory reset (not wipe data) and it should work... Note that you will lose data so be sure to copy it somewhere first.
Click to expand...
Click to collapse
I am encrypted everyday on my phone (I have set a password), I am using latest official stock firmware, decryption doesn't work returning a "failed decryption" message.

Thank you!

Hello trax7,
first of all ... many, many, many thanks for the provision of a current TWRP !!!!!
I searched for it so long !!!
Not working (for now):
- Decryption
- You tell me
Click to expand...
Click to collapse
For the moment I found three things for need of improvement:
1. When going into Recovery, the purple lamp (at the top of the case) does not light up.
2. Double touch the screen, doesn't wake up / switch on the screen again.
3. When starting a backup, I get five error messages:
unable to locate /persistent partition for backup calculations,
unable to locate /misc partition for backup calculation,
unable to locate /firmware partition for backup calculation,
unable to locate /persist partition for backup calculation,
unable to locate /ta partition for backup calculation,​... but the backup of the five partitions "boot, cache, data, recovery and system" runs through error-free.
However - I'm glad that we have became a current TWRP for our device!
And if one day the decryption works, I will be happy!

rm43115 said:
Hello trax7,
first of all ... many, many, many thanks for the provision of a current TWRP !!!!!
I searched for it so long !!!
For the moment I found three things for need of improvement:
1. When going into Recovery, the purple lamp (at the top of the case) does not light up.
2. Double touch the screen, doesn't wake up / switch on the screen again.
3. When starting a backup, I get five error messages:
unable to locate /persistent partition for backup calculations,
unable to locate /misc partition for backup calculation,
unable to locate /firmware partition for backup calculation,
unable to locate /persist partition for backup calculation,
unable to locate /ta partition for backup calculation,​... but the backup of the five partitions "boot, cache, data, recovery and system" runs through error-free.
However - I'm glad that we have became a current TWRP for our device!
And if one day the decryption works, I will be happy!
Click to expand...
Click to collapse
That's weird... I haven't experienced any of those bugs Maaybe just the purple lamp but I haven't even paid attention to that lol
Edit: Yes, purple LED does not light up. However the recovery did not complain at all during backups and locking and unlocking the screen is just fine. Are you using E5823 or E5803?

What about encrypted data partition. Is it possible to fix decrypting?

jw96 said:
What about encrypted data partition. Is it possible to fix decrypting?
Click to expand...
Click to collapse
At the moment no, but you can try and test whether it picks it up after a factory reset... Backup ur data tho.

trax7 said:
That's weird... I haven't experienced any of those bugs Maaybe just the purple lamp but I haven't even paid attention to that lol
Edit: Yes, purple LED does not light up. However the recovery did not complain at all during backups and locking and unlocking the screen is just fine. Are you using E5823 or E5803?
Click to expand...
Click to collapse
Ha, last night I found the problem for the strange error messages during the backup (it's not a problem of your TWRP-version):
In the .TWRPS file these partitions (persist, persistent, misc, firmware, ta) are still registered for backup from the old TWRP-version I used before.
I just had deleted the .TWRPS file and have created it again ... AND ... ERROR GONE!
I use E5823, but I would not call the problems with the violet lamp and the double-touch-unlock-screen an error ... rather a nice-to-have feature.
I mean, do not waste time with these banalities, if you do not know the solution.

USB OTG storage support
Hello trax7,
at the coming weekend I want to test the decryption of the TWRP - during preparation I realize that "USB OTG storage support" is missing.
Is it possible to implement "USB OTG storage support"?

rm43115 said:
Is it possible to implement "USB OTG storage support"?
Click to expand...
Click to collapse
@Trax , add to fstab
Code:
/usb-otg auto /dev/block/sda1 /dev/block/sda

Doe.it said:
Decryption is not working
Good job anyway, we have an updated TWRP at least!!
Click to expand...
Click to collapse
Doe.it said:
I am encrypted everyday on my phone (I have set a password), I am using latest official stock firmware, decryption doesn't work returning a "failed decryption" message.
Click to expand...
Click to collapse
jw96 said:
What about encrypted data partition. Is it possible to fix decrypting?
Click to expand...
Click to collapse
Decryption can't be achieved by only password. It requires a factory reset (not wipe data!). This is a security measure and each Android device creates their own password for encrypted data partition. So any other passwords such as lock screen security pin won't work. All ways go to performing a factory reset. In addition, in order not to have encrypted data partition again, fstab inside boot image must be modified.
rm43115 said:
Hello trax7,
at the coming weekend I want to test the decryption of the TWRP - during preparation I realize that "USB OTG storage support" is missing.
Is it possible to implement "USB OTG storage support"?
Click to expand...
Click to collapse
Yes, it is possible. Your device support OTG on it's stock fstab. After we get our works done, we will look onto this too!
Stay tuned!
berkanktz​

GreyLeshy said:
@Trax , add to fstab
Code:
/usb-otg auto /dev/block/sda1 /dev/block/sda
Click to expand...
Click to collapse
@GreyLeshy: Can I add it manually?

rm43115 said:
Can I add it manually?
Click to expand...
Click to collapse
Yes, You can with Android Image Kitchen

New build posted, USB OTG fixed as per @GreyLeshy 's suggestion.

trax7 said:
New build posted, USB OTG fixed as per @GreyLeshy 's suggestion.
Click to expand...
Click to collapse
THANK YOU!!!!
Now I can test the decryption this weekend ... if my children let me.
trax7 said:
Changelog:
22.02.2017
-USB OTG fixed
15.02.2017
-Possibly fixed decryption, need feedback
13.02.2017
- Fixed SD card
7.02.2017
- First build
Click to expand...
Click to collapse
You mean 2018 and not 2017.

In the latest two builds SD card access is broken again (or at least I can't access it). Reverting to recovery_suzuran-130218.img SD card access works again.