Noticed something very strange:

When I browse for the backup folder in the settings, I click on the "manual" option, get a folder view and navigate to either the top of the sdcard or the TWRP folder.

Now, when I go into any other folder that has subfolders, I do see the subfolders in the view. When I go to the TWRP folder, however, I do not see any subfolders, although there is the folder named "BACKUPS" in there (and underneath the substructure with the serial number and the individual backups).

I though this could be a permissions problem (so OBackup as a normal user does not see the subfolders, but the online nandroid script running as root as well as nandroid manager sees them). But the permissions are all identical (777) and owned by media_rw:media_rw.

No idea so far what is happening here...

---------- Post added at 02:43 PM ---------- Previous post was at 02:24 PM ----------

Originally Posted by Neuer_User

Now, when I go into any other folder that has subfolders, I do see the subfolders in the view. When I go to the TWRP folder, however, I do not see any subfolders, although there is the folder named "BACKUPS" in there (and underneath the substructure with the serial number and the individual backups).

Now it is getting crazy.

There is a Create option in the folder browser of OBackup. I just made a new folder inside of TWRP called "Test". What happened? Now the folder view shows the "BACKUPS" folder, but not the "Test" folder (although they are both there as verfied by adb).

It seems there is a bug in the folder view. I verified that the folder view always misses one file in the directory. So a directory with two subfolders shows only one subfolder, a directory with one subfolder shows none, and a directory with a file and a directory does show the directory.

But that does not seem to be connected with OBackup not recognizing my existing backups (and its own generated ones).

Originally Posted by Neuer_User

Noticed something very strange:

When I browse for the backup folder in the settings, I click on the "manual" option, get a folder view and navigate to either the top of the sdcard or the TWRP folder.

Now, when I go into any other folder that has subfolders, I do see the subfolders in the view. When I go to the TWRP folder, however, I do not see any subfolders, although there is the folder named "BACKUPS" in there (and underneath the substructure with the serial number and the individual backups).

I though this could be a permissions problem (so OBackup as a normal user does not see the subfolders, but the online nandroid script running as root as well as nandroid manager sees them). But the permissions are all identical (777) and owned by media_rw:media_rw.

No idea so far what is happening here...

---------- Post added at 02:43 PM ---------- Previous post was at 02:24 PM ----------


Now it is getting crazy.

There is a Create option in the folder browser of OBackup. I just made a new folder inside of TWRP called "Test". What happened? Now the folder view shows the "BACKUPS" folder, but not the "Test" folder (although they are both there as verfied by adb).

It seems there is a bug in the folder view. I verified that the folder view always misses one file in the directory. So a directory with two subfolders shows only one subfolder, a directory with one subfolder shows none, and a directory with a file and a directory does show the directory.

But that does not seem to be connected with OBackup not recognizing my existing backups (and its own generated ones).

Hi Neuer_User

Can you post log file created by OBackup here.
http://forum.xda-developers.com/show...postcount=3330

Originally Posted by electricsheepdreamer

Hi Neuer_User

Can you post log file created by OBackup here.
http://forum.xda-developers.com/show...postcount=3330

Well, currently the log is completely empty. I guess you only get log entries if you do a backup?

I can do another backup and post the log. Will, however, take about an hour or so.

---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------

Originally Posted by Neuer_User

Well, currently the log is completely empty. I guess you only get log entries if you do a backup?

I can do another backup and post the log. Will, however, take about an hour or so.

O.K. started the backup. Is running now. Will post the log when it is finished.

The log of the backup was helpful, while still being a bit strange. The backup finished successfully, but the following step to zip the files failed.

The problem is that OBackup cannot read the serial of the device. It says Serial: 0000000000000000000 (not sure about the number of zeros). So, it cannot look into the right folder, but searches for something like "/storage/emulated/0/TWRP/BACKUPS/0000000000000000000000000/".

The online nandroid backup does not have these problems. It finds the right folder and does the backup into it.

So I guess, I need to find out, why OBackup cannot read the serial correctly. Anybody knows how it reads the serial?

O.K. just tried "cat /proc/cpuinfo" and this is the output:

Processor	: ARMv7 Processor rev 0 (v7l)
processor	: 0
BogoMIPS	: 13.52

processor	: 1
BogoMIPS	: 13.52

processor	: 2
BogoMIPS	: 13.52

processor	: 3
BogoMIPS	: 13.52

Features	: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 
CPU implementer	: 0x51
CPU architecture: 7
CPU variant	: 0x1
CPU part	: 0x06f
CPU revision	: 0

Hardware	: UNKNOWN
Revision	: 0003
Serial		: 0000000000000000

This is probably where OBackup gets the serial from.
So, it seems to be kernel related. This is a stock HTC kernel (as there are no fully working custom kernels yet for HTC 4.2.2).

I checked the onandroid script. This uses several approaches to get the serial number. The one that works correctly is:

android_id=`$bb cat /proc/cmdline | $bb tr ' ' '\n' | $bb grep "androidboot.serialno=" | $bb tail -n 1 | $bb cut -d '=' -f 2`

So, it would be nice, if OBackup could introduce a similar serial detection. Otherwise, HTC one users with stock kernel won't be able to use it.

I'm attempting to successfully complete a backup of my system, data, recovery and boot in TWRP format using OBackup and then upload to Google drive, but it's failing as you can see in this log. Can anyone tell me what the problem might be? I just rooted my Droid DNA using the moonshine method and have not flashed any custom ROMs, just have TWRP recovery.


22:12:48 Using busybox from: /data/data/com.pommedeterresautee.twoborange3/files/busybox
22:12:48 Checking for root permissions...
22:12:48 Root permissions acquired!
22:12:48 Analysing battery level...
22:12:48 Sufficient battery available!
22:12:48 Checking version of BusyBox installed...
22:12:48 BusyBox version 1.20 or above installed!
22:12:48 Searching for SD card...
22:12:48 Alternate storage media provided!
22:12:49 This is an EMMC based device!
22:12:49 This device has a patch file installed!
22:12:49 TWRP backup mode selected at run time!
22:12:49 Advanced backup mode selected at run time!
22:12:49 Checking for required tools...
22:12:49 All required tools available!
22:12:49 Checking disk space...
22:12:50 SD Card Free Space: 4353 MB
22:12:50 Required Space: 3012 MB
22:12:50 Necessary disk space available!
22:12:50 Detecting mountpoints to exclude...
22:12:50 Backing up to /storage/sdcard0/TWRP/BACKUPS/FA2C7S501737/2013-06-15.22.12.46_-_Stock_DNA_-_JRO03C
22:12:50 Backing up /boot...
22:12:52 Backing up /recovery...
22:12:55 Backing up /system...
22:14:42 Backing up /data...
22:18:38 Generating md5sum for boot.emmc.win...
22:18:44 Generating md5sum for data.ext4.win...
22:19:47 Generating md5sum for recovery.emmc.win...
22:19:53 Generating md5sum for system.ext4.win...
22:20:37 Online Nandroid Backup Completed in 7 minutes 49 seconds!
chmod: /storage/sdcard0/TWRP/BACKUPS/0000000000000000/2013-06-15.22.12.46_-_Stock_DNA_-_JRO03C: No such file or directory
exit code [0]

Sent from my Droid DNA

Originally Posted by blackstallion

I'm attempting to successfully complete a backup of my system, data, recovery and boot in TWRP format using OBackup and then upload to Google drive, but it's failing as you can see in this log. Can anyone tell me what the problem might be? I just rooted my Droid DNA using the moonshine method and have not flashed any custom ROMs, just have TWRP recovery.


22:12:48 Using busybox from: /data/data/com.pommedeterresautee.twoborange3/files/busybox
22:12:48 Checking for root permissions...
22:12:48 Root permissions acquired!
22:12:48 Analysing battery level...
22:12:48 Sufficient battery available!
22:12:48 Checking version of BusyBox installed...
22:12:48 BusyBox version 1.20 or above installed!
22:12:48 Searching for SD card...
22:12:48 Alternate storage media provided!
22:12:49 This is an EMMC based device!
22:12:49 This device has a patch file installed!
22:12:49 TWRP backup mode selected at run time!
22:12:49 Advanced backup mode selected at run time!
22:12:49 Checking for required tools...
22:12:49 All required tools available!
22:12:49 Checking disk space...
22:12:50 SD Card Free Space: 4353 MB
22:12:50 Required Space: 3012 MB
22:12:50 Necessary disk space available!
22:12:50 Detecting mountpoints to exclude...
22:12:50 Backing up to /storage/sdcard0/TWRP/BACKUPS/FA2C7S501737/2013-06-15.22.12.46_-_Stock_DNA_-_JRO03C
22:12:50 Backing up /boot...
22:12:52 Backing up /recovery...
22:12:55 Backing up /system...
22:14:42 Backing up /data...
22:18:38 Generating md5sum for boot.emmc.win...
22:18:44 Generating md5sum for data.ext4.win...
22:19:47 Generating md5sum for recovery.emmc.win...
22:19:53 Generating md5sum for system.ext4.win...
22:20:37 Online Nandroid Backup Completed in 7 minutes 49 seconds!
chmod: /storage/sdcard0/TWRP/BACKUPS/0000000000000000/2013-06-15.22.12.46_-_Stock_DNA_-_JRO03C: No such file or directory
exit code [0]

Sent from my Droid DNA

Hi there,
It seems to be the same issue as the one above Neuer_User has.

Your device id number is not recognized properly (and thus TWRP backup folder) when trying to reach a successfully made backup in order to upload it.

We need to wait for snoopy, he's a bit busy with life ATM but he'll be here soon.

Originally Posted by electricsheepdreamer

Hi there,
It seems to be the same issue as the one above Neue_User has.

Your device id number is not recognized properly (and thus TWRP backup folder) when trying to reach a successfully made backup in order to upload it.

We need to wait for snoopy, he's a bit busy with life ATM but he'll be here soon.

Yeah, absolutely. You are also using a stock htc kernel (DNA, if I see that correctly).

Btw, you will see that the backup has been done correctly. Just the upload is not working, as OBackup does not look into the right directory. You can upload the backup manually.

Let's wait for the developer to fix the serial detection.