Develop Bugs

[Q] Flash by apx

Hey guys,
Is it possible to flash full image by?
Really important I get stuck with no bootloader when trying to flash..
What cab I do?
Thank you

APX is a hardware defect, no solution for that at the moment....yes there is one ! Replace the mainboard

THe thing is I switched the tegra IC and now its stuck on APX but I can Use APX only need the files.
Nothing like the known problem...

Ow oke......good luck then

Thanks
Any one knows a way to full flash by apx ?"

Maybe you can look by posts from nitrous2 or TripnRaver......they know more about APX. At least in general so it might be helpful

Some one any ideas ?

Trip has released drivers for apx mode however you will need the sbk for the one x in order to flash anything which is something that nobody except HTC have
Sent from my HTC One X using xda app-developers app

deadwolf666 said:
Hey guys,
Is it possible to flash full image by?
Really important I get stuck with no bootloader when trying to flash..
What cab I do?
Thank you
Click to expand...
Click to collapse
Did you manage to get the files to flash with APX ?
I have the device stuck in APX mode and I got the drivers, but that's as far as I could get without the files.
Thanks in advance!

Bugz! said:
Did you manage to get the files to flash with APX ?
I have the device stuck in APX mode and I got the drivers, but that's as far as I could get without the files.
Thanks in advance!
Click to expand...
Click to collapse
Sorry but I didnt manage to fix it then but here are some possible solution I found today on google:
http://forum.xda-developers.com/showthread.php?t=2118259
http://forum.gsmhosting.com/vbb/f485/htc-onex-pj46100-dead-solution-1653973/index2.html
http://www.gsmforum.ru/threads/161505-HTC-One-X-s720e-PJ46100-%D0%BD%D0%B5-%D0%B2%D0%BA%D0%BB%D1%8E%D1%87%D0%B0%D0%B5%D1%82%D1%81%D1%8F
https://www.youtube.com/watch?v=nmzk92rV6k4
apparently you need to be s-off to have any chance
Ive also attached the files needed (from the above links)
Hope it helps, also please update.

Thanks for the reply !
I have been able to communicate with the device from the second link you provided, but it gives errors when trying to repartition it.
I will post the errors first thing in the morning as I don't have the device with me now to regenerate it
I've read on so many forums that the mainboard may be fried as in it needs to be replaced, but then again I've proven forums wrong before when it comes to unknown errors and situations, so I'm hoping they're wrong again.
I'm curious, how far did you go with your device? where did you stop and give up on it?

deadwolf666 said:
Sorry but I didnt manage to fix it then but here are some possible solution I found today on google:
http://forum.xda-developers.com/showthread.php?t=2118259
http://forum.gsmhosting.com/vbb/f485/htc-onex-pj46100-dead-solution-1653973/index2.html
http://www.gsmforum.ru/threads/161505-HTC-One-X-s720e-PJ46100-%D0%BD%D0%B5-%D0%B2%D0%BA%D0%BB%D1%8E%D1%87%D0%B0%D0%B5%D1%82%D1%81%D1%8F
https://www.youtube.com/watch?v=nmzk92rV6k4
apparently you need to be s-off to have any chance
Ive also attached the files needed (from the above links)
Hope it helps, also please update.
Click to expand...
Click to collapse
Ok here's my log:
Code:
C:\Documents and Settings\Bugz\Desktop\RD_release(with_sbk)without sis>nvflash -
-blob blob.bin --bct flash_enc.bct --setbct --odmdata 0x40080105 --configfile fl
ash_32g.cfg --create --bl hboot_enc.img --go
Nvflash v1.2.57794 started
Using blob v1.1.57813
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x81
chip uid: 0x015d256462581c11
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: flash_enc.bct
- 6128/6128 bytes sent
flash_enc.bct sent successfully
odm data: 0x40080105
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: hboot_enc.img
- 2097168/2097168 bytes sent
hboot_enc.img sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: DIA
creating partition: BIF
creating partition: GP1
creating partition: WLN
creating partition: WDM
creating partition: RCA
creating partition: LNX
creating partition: SOS
creating partition: PG1
creating partition: PG2
creating partition: PG3
creating partition: SIF
creating partition: SP1
creating partition: RV1
creating partition: APP
creating partition: CAC
creating partition: ISD
creating partition: UDA
creating partition: DUM
creating partition: MSC
creating partition: RFS
creating partition: DLG
creating partition: PDT
creating partition: GPT
failed executing command 13 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x9) flags: 0
C:\Documents and Settings\Bugz\Desktop\RD_release(with_sbk)without sis>pause
Press any key to continue . . .
Did you get this far? I don't know what this error means as I don't have any experience with nvflash
I'll be looking into the error code, just wanted to share this in case someone is following the footsteps

[TOOL][I9505-I9505G/I9515-I9515L] Full IMEI backup/restore tool [EOL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Full IMEI backup/restore tool for Samsung Galaxy S4 GT-I9505/GT-I9515
Brought to you by AntaresOne​
NOTE: This is only for Galaxy S4 with Qualcomm Snapdragon 600, Galaxy S4 Active version is here, Exynos 5410 (GT-I9500) version is here.
To devs: modifications & redistribution are not allowed. Contact me before including my work or any part of it in your stuff.
Explanation
What is IMEI?
Wikipedia
Why should I backup it?
When you start to mod your phone, sometimes may happen that you lose it (a bad flash, a wrong mod...) and without your phone is like this. Shortly, you lose mobile network forever.
The Qualcomm variant of Galaxy S4 doesn't have IMEI stored in EFS as most people think, it's stored in another place. Partitions to backup/restore are 8, each is required by the system to have IMEI. These are: EFS (there is IMEI's country code), modemst1, modemst2, m9kefs1, m9kefs2, m9kefs3, backup and fsg. It doesn't do miracles, so if you lose IMEI and don't have a backup, you're lost.
Features
Complete IMEI backup
Autozipping of saved partitions
Installation
Download tool from the link below
Put the zip file in your sdcard
Reboot in recovery
Install zip from sdcard
Choose downloaded zip file
Reboot system
Usage
When installed, the "imeibkp" executable goes in /system/bin. Obviously root is a must. This is not an app, so to run it you must use Terminal Emulator. It's very user-friendly and n00b-approved (joking :laugh, normally you shouldn't run into issues while using it.
Open Terminal Emulator
Write su and press enter (this is to obtain root access)
Invoke this tool by writing imeibkp and pressing enter
To restore just invoke again imeibkp
In case you want to export your backup, it is in /sdcard/IMEIBackup and called IMEIBackup.zip (Internal Memory on PC through USB connection)
If you change ROM you'll lose this tool (you'll not lose a backup already made), in this case just follow again Installation steps
Download
IMEI Backup tool is hosted on my AndroidFileHost
XDA:DevDB Information
IMEI backup/restore tool for Galaxy S4 GT-I9505-I9505G/GT-I9515/GT-I9515L, Tool/Utility for the Samsung Galaxy S4
Contributors
AntaresOne
Version Information
Status: No Longer Updated
Stable Release Date: 2014-12-16
Created 2014-12-16
Last Updated 2017-05-19

Changelog
25/5/2015
Added support for the following variants:
GT-I9508
GT-I9515L
SGH-M919N
SGH-M919V
SGH-I337C
SCH-R970
SCH-R970C
SCH-R970X
4/3/2015
Added support for Bell SGH-I337M (same thread as AT&T variant)
9/2/2015
Added Galaxy S4 AT&T support (its own thread is here)
Fixed Galaxy S4 Active issue
31/1/2015
Added Galaxy S4 T-Mobile support (its own thread is here)
Little code update
26/1/2015
Added full zip binary in flash package (this should fix stpcpy error)
Little code update
9/1/2015
Added zip binary in flash package (not all the ROMs have it included, fixes zipping process)
Little code update
8/1/2015
Added auto zipping of saved files during backup process
Added auto unzipping of IMEIBackup archive when restoring
Better backup identification for restore process
Various code updates
4/1/2015
Added support for GT-I9505G (S4 Google Play Edition)
21/12/2014
Fixed busybox path (some ROMs have it in different location)
16/12/2014
Initial public release
Other S4 variants
If you want this tool for any other Galaxy S4 variant device write me a PM or mail me to [email protected] including a full cmdline copy & partition table.
Through Terminal Emulator or ADB, do this:
For cmdline
Code:
su [b](to acquire root access)[/b]
cat /proc/cmdline > /sdcard/cmdline.txt
For partition table
Code:
su [b](same reason as above)[/b]
ls -la /dev/block/platform/msm_sdcc.1/by-name > /sdcard/partitions.txt
You will find two files named cmdline.txt and partitions.txt in your internal storage (/sdcard)
Other Samsung devices
PM or mail me at [email protected] for details.

Sei il migliore

This is suit for SGH-i337M , right?

I feel nice and safe now, I always thought I was OK having efs backed up but apparently that's not enough right.
So now I have my imei nice and safe on my external SD - just in case, better safe than sorry
Thank you AntaresONE

Thanks for this, looks good.
I understand this can't generate an IMEI from the phone itself, but I have a dead S4 which has a null IMEI which I know (it's on the box it came in). Is there a method for me to insert this into another S4 IMEI backup (I have another working S4 as my main phone so could use it's backup)?

Hi great tool AntaresOne. Thanks for sharing.
Quick note: if some those like me busybox is installed under /system/xbin/; you can have trouble to launch the imeibkp like a noob
Backing up EFS ....
/system/bin/imeibkp[171]: /system/bin/busybox: not found
...
Click to expand...
Click to collapse
I have created a symlink from the source file like this (done via adb, but can be directly done via a terminal console):
C:\Baud\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # ln -s /system/xbin/busybox /system/bin/busybox
ln -s /system/xbin/busybox /system/bin/busybox
[email protected]:/ # imeibkp
imeibkp
***********************************
* AntaresOne's IMEI backup tool *
***********************************
Checking device...
GT-I9505 found!
Checking backup...
Backup not found. Do you want to make it now?
1 - Yes
2 - No
Type 1 or 2 and press enter:
1
Backing up EFS...
27904+0 records in
27904+0 records out
14286848 bytes (13.6MB) copied, 2.645813 seconds, 5.1MB/s
Backing up modemst1...
6144+0 records in
6144+0 records out
3145728 bytes (3.0MB) copied, 0.563782 seconds, 5.3MB/s
Backing up modemst2...
6144+0 records in
6144+0 records out
3145728 bytes (3.0MB) copied, 0.568542 seconds, 5.3MB/s
Backing up m9kefs1...
1560+0 records in
1560+0 records out
798720 bytes (780.0KB) copied, 0.143830 seconds, 5.3MB/s
Backing up m9kefs2...
1560+0 records in
1560+0 records out
798720 bytes (780.0KB) copied, 0.142853 seconds, 5.3MB/s
Backing up m9kefs3...
1560+0 records in
1560+0 records out
798720 bytes (780.0KB) copied, 0.149078 seconds, 5.1MB/s
Backing up backup...
12288+0 records in
12288+0 records out
6291456 bytes (6.0MB) copied, 2.140778 seconds, 2.8MB/s
Backing up fsg...
6144+0 records in
6144+0 records out
3145728 bytes (3.0MB) copied, 0.574982 seconds, 5.2MB/s
Writing log...
Operation successfully completed!
Thanks for using this tool!
Remember to leave a feedback on XDA thread
[email protected]
[email protected]:/ #
Click to expand...
Click to collapse
Hope it helps

Disrespective said:
Thanks for this, looks good.
I understand this can't generate an IMEI from the phone itself, but I have a dead S4 which has a null IMEI which I know (it's on the box it came in). Is there a method for me to insert this into another S4 IMEI backup (I have another working S4 as my main phone so could use it's backup)?
Click to expand...
Click to collapse
I can confirm this works. I bought an s4 off eBay which was blacklisted. I've had it now for about 6months now and never been able to sort it. UNTIL NOW!!. Backed up my IMEI number off my phone and restored it to blacklisted phone. Now all is good!!

OK, OK, so I am definitely a noob, and this wasn't hard to run, however, I can only see the files when I look at the phone with a file browser. How can I retrieve them from the phone? I can't see them from a PC when I move them to a different location (extSD).

They are saved in the internal memory mate. You can just drag the folder IMEI BACKUP to a pc

Yeah, you'd think that, wouldn't you? I've used a number of different file browsers and they all see the folders but when trying to view the folders with a PC (or OSX) they just don't exist.
I just compressed them and emailed them to myself with ES.

this works on cm12?

Jackyqxl said:
This is suit for SGH-i337M , right?
Click to expand...
Click to collapse
Yes it is
baudbox said:
Hi great tool AntaresOne. Thanks for sharing.
Quick note: if some those like me busybox is installed under /system/xbin/; you can have trouble to launch the imeibkp like a noob
I have created a symlink from the source file like this (done via adb, but can be directly done via a terminal console):
Hope it helps
Click to expand...
Click to collapse
If busybox is installed in xbin, always has a symlink in /system/bin (automatically created at the moment of ROM installation/busybox installation)
If you open xbin and bin with a root browser or adb shell, you'll see that all the binaries in xbin are symlinked to bin, then there's no need to manually create a symlink
Chibbo said:
this works on cm12?
Click to expand...
Click to collapse
Yes, works on any ROM that has root and busybox installed. Works in Aroma filemanager's terminal and TWRP console too

doesn't work on cm12
its looking for busybox in bin folder but its in xbin. anyways it's easy to fix but just sayin it isn't working "out of the box"

If i make a backup, what i have to do to restore it?
--
Believes in Christ and you and your family will be safe of the Great day of Jehovah's wrath
I9505 Powered with Phoenix Rom v9.4 - Tamirda
GoogyMax Kernel v1.1.5 - Googy_anas
Philz touch Recovery - Philz
S5's S-view Cover service - Karkasss
Jehovah's Thunder Bootanimation - Pas2001
Bootanimation sound - Me
A lot of mods and stuff - Xda community
Thanks to all of you...

Conito11 said:
If i make a backup, what i have to do to restore it?
--
Believes in Christ and you and your family will be safe of the Great day of Jehovah's wrath
I9505 Powered with Phoenix Rom v9.4 - Tamirda
GoogyMax Kernel v1.1.5 - Googy_anas
Philz touch Recovery - Philz
S5's S-view Cover service - Karkasss
Jehovah's Thunder Bootanimation - Pas2001
Bootanimation sound - Me
A lot of mods and stuff - Xda community
Thanks to all of you...
Click to expand...
Click to collapse
Same process only when you have backup it gives you option to restore

I tried it but this is what I got:
Quote
imeibkp
***********************************
* AntaresOne's IMEI backup tool *
***********************************
Checking device...
GT-I9505 found!
Checking backup...
Backup not found. Do you want to make it now?
1 - Yes
2 - No
Type 1 or 2 and press enter:
1
1
1
1
2
2
Yes
No
Unquote
There is no response after I typed 1 and enter! Typed again and again and other options but nothing! Can someone help please ?
p.s I used 3C Toolbox Terminal. There is an (su) append to each entry.

KenHua said:
I tried it but this is what I got:
Quote
imeibkp
***********************************
* AntaresOne's IMEI backup tool *
***********************************
Checking device...
GT-I9505 found!
Checking backup...
Backup not found. Do you want to make it now?
1 - Yes
2 - No
Type 1 or 2 and press enter:
1
1
1
1
2
2
Yes
No
Unquote
There is no response after I typed 1 and enter! Typed again and again and other options but nothing! Can someone help please ?
p.s I used 3C Toolbox Terminal. There is an (su) append to each entry.
Click to expand...
Click to collapse
Use this terminal
Tool updated, fixed busybox path & various updates to the code
Download: https://www.androidfilehost.com/?fid=95864024717067320

AntaresOne said:
Use this terminal
Tool updated, fixed busybox path & various updates to the code
Download: https://www.androidfilehost.com/?fid=95864024717067320
Click to expand...
Click to collapse
Thumbs Up :good: for your quick response. Now I get :
[email protected]:/ $ su
[email protected]:/ # imeibkp
***********************************
* AntaresOne's IMEI backup tool *
***********************************
Checking device...
GT-I9505 found!
Checking backup...
/system/bin/imeibkp[39]: busybox: not found
/system/bin/imeibkp[39]: busybox: not found
Backup not found. Do you want to make it now?
1 - Yes
2 - No
Type 1 or 2 and press enter:
1
Backing up EFS...
/system/bin/imeibkp[180]: busybox: not found
Backing up modemst1...
/system/bin/imeibkp[180]: busybox: not found
Backing up modemst2...
/system/bin/imeibkp[180]: busybox: not found
Backing up m9kefs1...
/system/bin/imeibkp[180]: busybox: not found
Backing up m9kefs2...
/system/bin/imeibkp[180]: busybox: not found
Backing up m9kefs3...
/system/bin/imeibkp[180]: busybox: not found
Backing up backup...
/system/bin/imeibkp[180]: busybox: not found
Backing up fsg...
/system/bin/imeibkp[180]: busybox: not found
Writing log...
/system/bin/imeibkp[180]: busybox: not found
Backup path: /sdcard/IMEIBackup
Operation successfully completed!
Remember to leave a feedback on XDA thread
[email protected]
[email protected]:/ #
My Busybox is:
BusyBox
Stephen (Stericson)
- 22 November 2014
I think the commands are Installed in Xbin by default.

Same here, come back to previous version and it works.

[Recovery][crackling] Team Win Recovery Project for the Wileyfox Swift

Team Win Recovery Project 3.0.2
Notice: This is a test build as a start to becoming an official build, I am looking for feedback right now - do not consider this stable!
I am currently looking for users to test all the features and report back with what works.
Quote the 2nd post and put a pass or fail in each of the [ ] boxes!
Please, if you can, post your recovery.log after doing the tests that fail, as well as dmesg.log
Code:
adb shell cat /tmp/recovery.log > recovery.log
adb shell dmesg > dmesg.log
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
https://idlekernel.com/twrp/crackling/ (temporary! THESE ARE TEST BUILDS!)
Find instructions on how to unlock and root your device with fastboot here:
https://twrp.idlekernel.com/devices/wileyfoxswift.html (temporary device page - do not download from here!)
CHANGES
v3.0.2-0 - See here for the changes.
FEATURES
MTP support
USB Mass Storage support
Micro SDcard support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Brightness node not set (unknown location, join #twrp to help!)
Battery status possibly unknown
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
Device tree: https://github.com/jcadduono/android_device_wileyfox_crackling
Kernel sources: https://github.com/jcadduono/android_kernel_cyanogen_msm8916/tree/twrp-6.0
TWRP: https://github.com/omnirom/android_bootable_recovery
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Wileyfox Swift, Tool/Utility for the Wileyfox Swift
Contributors
jcadduono, The Team Win Recovery Project team
Source Code: https://github.com/jcadduono/android_device_wileyfox_crackling
Version Information
Status: Testing
Current Beta Version: 3.0.2-0
Beta Release Date: 2016-04-27
Created 2016-04-28
Last Updated 2016-04-29

TWRP functional checklist
Code:
Blocking checks
[ ] - Correct screen/recovery size
[ ] - Working touchscreen
[ ] - Backup to internal/microSD
[ ] - Restore from internal/microSD
[ ] - Reboot to system
[ ] - ADB & ADB shell
[ ] - Flash zips in Install page
[ ] - Flash boot.img/recovery.img using Flash Image in Install page
Medium checks
[ ] - Flash zip with ADB sideload
[ ] - UI colors (red/blue inversions)
[ ] - Screen goes off (and back on :))
[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[ ] - System, Data, Internal Storage, microSD card, and Firmware partitions listed in mount/backup choices
[ ] - Decrypt encrypted /data
[ ] - Correct date
[ ] - MTP read/write
[ ] - USB Mass Storage read/write
[ ] - Set brightness level
Minor checks
[ ] - Reboot to bootloader
[ ] - Reboot to recovery
[ ] - Power Off
[ ] - Battery level
[ ] - Temperature
[ ] - Encrypted backups
[ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition

Blocking checks
[pass] - Correct screen/recovery size
[pass] - Working touchscreen
[pass] - Backup to internal/microSD
[pass] - Restore from internal/microSD
[pass] - Reboot to system
[fail] - ADB & ADB shell
[pass] - Flash zips in Install page
[pass] - Flash boot.img/recovery.img using Flash Image in Install page
Medium checks
[ ] - Flash zip with ADB sideload
[pass] - UI colors (red/blue inversions)
[pass] - Screen goes off (and back on )
[pass] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[pass] - System, Data, Internal Storage, microSD card, and Firmware partitions listed in mount/backup choices
[fail] - Decrypt encrypted /data
[pass] - MTP read/write
[pass] - USB Mass Storage read/write
[pass] - Set brightness level
Minor checks
[pass] - Reboot to bootloader
[pass] - Reboot to recovery
[pass] - Power Off
[pass] - Battery level
[pass] - Temperature
[fail] - Encrypted backups
[pass] - Vibration
[pass] - Screenshot

Epmak said:
Blocking checks
[fail] - ADB & ADB shell
[fail] - Decrypt encrypted /data
[fail] - Encrypted backups
Click to expand...
Click to collapse
Thanks! You're sure adb isn't working? I can't find any reason it wouldn't. :S
I will try CM 13.0 decryption libs instead of CyanogenOS, maybe that will help with encryption.
For the third item, encrypted backups - you were unable to backup say...system, and use the encryption option in the options page?
(if that is so, can you get me a log trying to make an encrypted backup?)

jcadduono said:
You're sure adb isn't working? I can't find any reason it wouldn't. :S
Click to expand...
Click to collapse
Yes, i plug phone usb cable.
adb shell
see
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
adb working in another UNOFFICIAL TWRP beroid
jcadduono said:
For the third item, encrypted backups - you were unable to backup say...system, and use the encryption option in the options page?
(if that is so, can you get me a log trying to make an encrypted backup?)
Click to expand...
Click to collapse
I use the encryption option, backup can't encrypt.
See log files.

Epmak said:
Yes, i plug phone usb cable.
adb shell
see
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
adb working in another UNOFFICIAL TWRP beroid
I use the encryption option, backup can't encrypt.
See log files.
Click to expand...
Click to collapse
i don't see any error in the log for encrypted backup? it saved fine?
uploaded test3 if youre up for trying again!

I'm planning on giving this a run through later (possibly later in the week), but I needed to clarify something in the mean time:
jcadduono said:
Code:
[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
Click to expand...
Click to collapse
Do the above requirements apply to the SDcard, or just the phone internal storage?
(My phone is currently encrypted, so I'm currently stuck with an older CM13 build, so have to flash anew. I haven't tested restoring from backup, and I'm hesitant to potentially lose access to a certain app right now.)
The list of mountable partitions includes a partition named "persist", unsure if this is of any relevance?
Additionally, comparing the Swift's fstab in TWRP to others, it would appear that it might be lacking in the encryption related flags on some mounts?
Also, thanks!

ryzened said:
I'm planning on giving this a run through later (possibly later in the week), but I needed to clarify something in the mean time:
Do the above requirements apply to the SDcard, or just the phone internal storage?
(My phone is currently encrypted, so I'm currently stuck with an older CM13 build, so have to flash anew. I haven't tested restoring from backup, and I'm hesitant to potentially lose access to a certain app right now.)
The list of mountable partitions includes a partition named "persist", unsure if this is of any relevance?
Additionally, comparing the Swift's fstab in TWRP to others, it would appear that it might be lacking in the encryption related flags on some mounts?
Also, thanks!
Click to expand...
Click to collapse
I suppose you can ignore NTFS as the Swift doesn't support OTG storage anyways.
exFAT/vfat/f2fs would apply microSD cards.
ext4/f2fs would also apply to data, however you would need a rom with a kernel/fstab capable of taking advantage of that.
I can remove persist from the fstab, it probably shouldn't be there anyways.
Explain what you think is missing related to encryption? I believe I have everything.
When backing up data, it will be unencrypted unless you select the encrypt backup option (even if the partition is already encrypted), and when restoring a data backup, it will be whatever the partition currently is (if the filesystem is encrypted, then restoring unencrypted data backup will still keep your data partition encrypted), unless you use the [Format Data] button on the Wipe page to remove encryption from the data partition.

locking checks
[pass ] - Correct screen/recovery size
[ pass] - Working touchscreen
[ pass] - Backup to internal/microSD
[ ] - Restore from internal/microSD
[pass ] - Reboot to system
[fail ] - ADB & ADB shell
error: insufficient permissions for device
[ ] - Flash zips in Install page
[ ] - Flash boot.img/recovery.img using Flash Image in Install page
Medium checks
[ ] - Flash zip with ADB sideload
[ ] - UI colors (red/blue inversions)
[ ] - Screen goes off (and back on )
[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[ ] - System, Data, Internal Storage, microSD card, and Firmware partitions listed in mount/backup choices
[ fail] - Decrypt encrypted /data
[ ] - Correct date
[ ] - MTP read/write
[ ] - USB Mass Storage read/write
[ ] - Set brightness level
Minor checks
[pass ] - Reboot to bootloader
[ pass] - Reboot to recovery
[ ] - Power Off
[ ] - Battery level
[ ] - Temperature
[ ] - Encrypted backups
[ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition
Sorry couldn't test everything, cause can't mount local Storage.

piratoes said:
locking checks
[pass ] - Correct screen/recovery size
[ pass] - Working touchscreen
[ pass] - Backup to internal/microSD
[ ] - Restore from internal/microSD
[pass ] - Reboot to system
[fail ] - ADB & ADB shell
error: insufficient permissions for device
[ ] - Flash zips in Install page
[ ] - Flash boot.img/recovery.img using Flash Image in Install page
Medium checks
[ ] - Flash zip with ADB sideload
[ ] - UI colors (red/blue inversions)
[ ] - Screen goes off (and back on )
[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[ ] - System, Data, Internal Storage, microSD card, and Firmware partitions listed in mount/backup choices
[ fail] - Decrypt encrypted /data
[ ] - Correct date
[ ] - MTP read/write
[ ] - USB Mass Storage read/write
[ ] - Set brightness level
Minor checks
[pass ] - Reboot to bootloader
[ pass] - Reboot to recovery
[ ] - Power Off
[ ] - Battery level
[ ] - Temperature
[ ] - Encrypted backups
[ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition
Sorry couldn't test everything, cause can't mount local Storage.
Click to expand...
Click to collapse
error: insufficient permissions for device
I was on linux when I saw this, the problem turned out to be the wheel group in the sudo file was hashed out ran visudo as root and un hashed it
No change, rebooted and the message disapered
Note adb still worked in windows

Thanks for your work! I am looking forward to the Swift becoming officially supported by TWRP.
I tried the test3 build and also couldn't decrypt the data
But please note that I am also not able to decrypt my data partition using the cyanogenmod recovery. Using latest CM13 nightly.

I'm finding that adb and adb shell work fine until you click "cancel" when TWRP can't decrypt the data. So therefore you have to push all your files prior to touching the phone. It also has the effect of not permitting adb sideload from working.
I expect once the encryption issue is solved the adb and adb shell won't be an issue for people either.

can we root Android N with this version?

Will this be stabile soon?

thebrainkafka said:
Will this be stabile soon?
Click to expand...
Click to collapse
Stable is here: http://forum.xda-developers.com/showthread.php?t=3350351

TWRP Wont Complete Backup!! Error 255

i have a fully rooted and unlocked nexus 5x,
To Start of i rooted my phone and installed twrp custom recovery after this i proceded to try and install cm13 and gapps when my install came to a conclusion (of it bieng BROKE as Hell) i decided to boot back into recovery and restore a backup i did before installing cm13 (a full backup Boot, System, System Image, Data, EFS, Cache Ect).This worked fine
Then a new Rom came out that i like the look of and decided to see if my phone would accept it, haveing previously deleted the backup i had before i tryed to make a new one, i got this from the recovery log
I:Backup Name is: '2016-10-13--20-39-38_NRD90R'
I:Full_Backup_Path is: '/data/media/0/TWRP/BACKUPS/006b8a96ed69b064/2016-10-13--20-39-38_NRD90R/'
I:Calculating backup details...
* Total number of partitions to back up: 10
* Total size of all data: 10899MB
* Available space: 16400MB
[BACKUP STARTED]
* Backup Folder: /data/media/0/TWRP/BACKUPS/006b8a96ed69b064/2016-10-13--20-39-38_NRD90R/
Backing up Boot...
I:Reading '/dev/block/mmcblk0p37', writing '/data/media/0/TWRP/BACKUPS/006b8a96ed69b064/2016-10-13--20-39-38_NRD90R/boot.emmc.win'
Iartition Backup time: 0
* Generating md5...
I:MD5 for /data/media/0/TWRP/BACKUPS/006b8a96ed69b064/2016-10-13--20-39-38_NRD90R/boot.emmc.win: 11d56bb372a47552eb72ca57de7ac225 boot.emmc.win
* MD5 Created.
Backing up System...
Error opening: '/system/app/BasicDreams' (Not a directory)
I:Error in Generate_TarList!
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/006b8a96ed69b064/2016-10-13--20-39-38_NRD90R/system.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/006b8a96ed69b064/recovery.log
I:Set page: 'action_complete'
I: operation_end - status=1
I:Set page: 'clear_vars'
I:Set page: 'backup'
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
Click to expand...
Click to collapse
After this i researched the BasicDreams file and the error 225, as for the basicdreams file i tryed to delete it (in root browser) but instantly came back again, and i could only find post on error 225 when restoring a backup not making one.
Please if anyone as any idea what is happening help me out.
Ben

[HELP] TWRP Nandroid Backup ERROR: 255.

Device: OnePlus 5T (dumpling)
OS: crDroid v6.5
Firmware: firmware_H056_oneplus5T
TWRP Version: 3.3.1-20190908-0-codeworkx-signed-forcedecrypt
Add-ons: Magisk-v20.4 and MinMicroG-NoGoolag-2.7-beta2.
Hello XDA Fourm,
Every time I go to do a backup; I get an error upon backing up the "Data" partition. Here is a snippet of the "recovery.log" TWRP produced:
Code:
I:addFile '/data/per_boot' including root: 0
==> set selinux context: u:object_r:system_data_file:s0
failed to lookup tar policy for '/data/per_boot' - '3ceb982b622fe097'
I:Error adding file '/data/per_boot' to '/data/media/0/TWRP/BACKUPS/[REDACTED]/2020-04-22--23-01-37_QQ2A200405005_release-keys/data.ext4.win'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/[REDACTED]/2020-04-22--23-01-37_QQ2A200405005_release-keys/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/[REDACTED]/2020-04-22--23-01-37_QQ2A200405005_release-keys/recovery.log
Things I have tried:
Backing up everything except the "Data" partition. Back up completes successfully.
Reflashing TWRP.
Any help is appreciated.

Hi,
I'm facing the same issue.
Did you find any solution for this issue?
THX

Use TWRP file manager and go to "/data/per_boot" and delete the folder "per_boot" and try backup again it will work
Thank me later