yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] kokotas:
Yes it is. In fact a script (prerecoveryboot.sh) is responsible for getting the file system types for recovery.fstab.

I should also mention that there is room for TWO more scripts that could run at boot (but they are not necessary).

// Check for and run startup script if script exists
TWFunc::check_and_run_script("/sbin/runatboot.sh", "boot");
TWFunc::check_and_run_script("/sbin/postrecoveryboot.sh", "post-boot");

I'm finishing a built-in function to check if the DataOnExt-path is valid and if not try to find a valid one.;)

Regards!
[HD2 Android NAND Development] NYLimited:
Very nice! That may be a nice toy to play with down the line.

In case you don't recognize it that is a portrait of me on the left!

Seriously, I am not trying to make your life more difficult but I can see all the questions being directed to you later by people who never modified anything, so to speak. Of course, you probably have lots of free time for those questions, right? ;)
[HD2 Android NAND Development] Dark_Avenger:
Nice portrait :)
[HD2 Android NAND Development] djinob:
I had cynagenmod 10 on my GSM Galaxy Nexus with CWM. I installed GooManager and flashed TWRP. From within GooManager, I downloaded the latest AOKP Rom (jb 4.2.1 build). I got GooManager to create a backup, wipe data and flash the AOKP Rom.

It rebooted and successfully did all the above in one sweep.

I am having some problems with Titanium backup batch restore freezing. And at this point, I just want to go back to my Cynagenmod setup for now.

So I reboot back into recovery and it loads TWRP. I click the restore button, but nothing is displayed under "SELECT PACKAGE TO RESTORE"

:( :( :( . Where is the nandroid that TWRP created? HELP!!!!!

djino
[HD2 Android NAND Development] NYLimited:
You might want to try

this thread

instead.

The one you are in now is for the HTC HD2 not the Galaxy Nexus. ;)
[HD2 Android NAND Development] sunitknandi:
Now YOU are the one not letting him sleep LOL.

Sent with love from me to you via HTC HD2
[HD2 Android NAND Development] NYLimited:
C'mon, sleep is so overrated! Why? I am glad you asked! Because:

It's really difficult to text while unconscious.

Much easier to hallucinate when sleep-deprived.

It is really difficult to flash a new ROM in your sleep.

If you're going for that hip bedhead look, they have hair gel for that now.

Thomas Edison got fewer than 5 hours per night. Snooki gets 11. So it doesn't even work.

No matter how hard you try to fall asleep thinking "Hugh Jackman Hugh Jackman Hugh Jackman," your dreams usually involve your fifth-grade teacher at a car wash.

The likelihood of cartoon ZZZZZZZZZZs emerging from your mouth is very low.

Why sleep? You're just gonna be up in 20 minutes anyway.

Okay, enough off-topic - sorry.
[HD2 Android NAND Development] kokotas:
OMG, you're naked! And too green! :laugh:

Actually, the posts I read mostly are the trivial/troubling ones...

I just bookmarked your last post and I'm gonna make a T-Shirt out of it. :laugh:

Rev8 of HD2-Extended-TWRP is below.

Changes:

Changed the path where TWRP will save any taken screenshot to "/sdcard/TWRP/screenshots/".

The name of the png file will have this format "TWRPScr-001.png". The increment will be done automatically.

Unfortunately I haven't fixed the quality yet.

Added an option under "Settings" to "Enable path-checking for DataOnExt".

If enabled the path that will be used for the DataOnExt mode will be checked before any errors occur. Hopefully this will help non-experienced users to use DataOnExt function.

Added ability to automatically skip any NativeSD Rom folder from your sd-ext backup.

If you want to backup a NativeSD Rom do it from the NativeSD Manager.

Probably fixed the way TWRP calculates the partition sizes according to our extended settings(skip dalvik-cache - dataonext - skip nativesd roms).

So now the sizes (shown under "Backup" and) used during backup-process should be correct.

Regards!
[HD2 Android NAND Development] Dark_Avenger:
Kokotas, rev8 does not run on my HD2. TeamWin startup splash screen is shown and than after 3-4 seconds just flicker (like TWRP restart) and stays there till another flicker... and looping there.

Download it again, flashed from fastboot - same result. rev8 is a bad build for me. Flashed rev7 - everything is back to normal.
[HD2 Android NAND Development] NYLimited:
Well, yes, but I did use the sign to cover important assets..

What!? You are only allowing 999 images!? :banghead:

---

Sometimes I read because I am too lazy to think... (via Tapatalk)
[HD2 Android NAND Development] shanman-2:
+1.

Just cycles teamwin screen.
[HD2 Android NAND Development] kokotas:
You have to change your theme too. I forgot to mention it.

I have no boot-loops in my case. Could you check the log and if you see anything weird post it here as well.

Too much you think? :D

I've edited the first post with more detailed installation instructions. Could you check the part about MAGLDR..

Regards!
[HD2 Android NAND Development] Dark_Avenger:
I have boot-loops without a theme too. recovery.log is not created (or I can't find it). Maybe it is deleted when TWRP restarts. I've tried to pull the battery out before the restart in order to keep the recovery.log without success. Deleted .twrp file with settings did not help. Have no ideas how to proceed further.
[HD2 Android NAND Development] kokotas:
Me neither.. without a log and without being able to reproduce it, it is difficult..

Did this happen to all of you that flashed rev8?

I can re-upload the file (which btw I just re-flashed, did 2 restores, a backup and a wipe on two different cards with no problems).

Just wait a moment please..

Regards!
[HD2 Android NAND Development] MarkAtHome:
I like that idea. I think it best that TWRP locate the partition, rather than leaving it up to the user.

As for Tytung's mod, I believe that it is intended to enable the sharing of data with NativeSD installs, thereby minimizing redundancy.

____________________

Sent from my HD2 JB-CM10 with XDA Premium
[HD2 Android NAND Development] Dark_Avenger:
I don't use DataOnExt if this matters. I have a normal NAND rom with /sd-ext partition with a2sd script that utilize it.
[HD2 Android NAND Development] pathologo:
Unfortunately yes. Seems like TWRP is restarting all the time aka. bootloop.
[HD2 Android NAND Development] NYLimited:
Actually, it should be too much - who the devil is going to take 999 screen shots while in recovery? I know, famous last words...

Looks fine - I have used both methods in the past. The only thing that I might stress is the name of the img file must match whatever is specified in flash.cfg. That is what people mess up most often - grabbing an img file and using a flash.cfg which has a different name in it.
[HD2 Android NAND Development] kokotas:
Re-uploaded the zip files at the same post.

Waiting any new feedback..
[HD2 Android NAND Development] NYLimited:
Downloading now.. You re-uploaded too fast for me so I have no feedback on the initial rev 8 for you...

[ EDIT ]

Looks like I was not too late after all. Have to agree with the others. Cannot load TWRP. When selecting option 8 from Magldr it starts to load the code, displays the splash screen, sits for about 7-8 seconds (loading some code presumably), and is back to displaying the splash screen again. None of the buttons make a difference. Had to pull battery to stop the loop.​

​

I'd have to agree here.. :)
[HD2 Android NAND Development] Dark_Avenger:
Still boot-loop...
[HD2 Android NAND Development] pathologo:
Just downloaded the re-uploaded file and byte compared it with the first upload.. They are the same.
[HD2 Android NAND Development] NYLimited:
Yes, same on Magldr...
[HD2 Android NAND Development] kokotas:
If all of you with boot-loops are on MAGLDR, maybe that's the problem.

Perhaps I made a change that Magldr doesn't like.

Hmm..I will try reverting something that just came to my mind and will post a revised file.

Sorry guys for the trouble.

Regards!
[HD2 Android NAND Development] Dark_Avenger:
no... I'm on your cLK Black v1.5.1.6.
[HD2 Android NAND Development] shanman-2:
Same here, no luck with re-upload.
[HD2 Android NAND Development] NYLimited:
It seems to get past the mag loader messages and "go go go" stuff without any issues. Looks like it dies several seconds into code load and starts over.

Wanna borrow my green picture? :laugh:
[HD2 Android NAND Development] kokotas:
So, the plot thickens...:o I've made a recovery that runs only on my device:eek:

Attached is rev8b in case you'd like to take another shot.

[EDIT2]Removed it since it is not working too[/EDIT2]

Also attached a log from my device.

Hahaha:D

I hope I won't have to..

Regards!

[EDIT1]I removed the zip files from previous post to avoid confussion[/EDIT1]
[HD2 Android NAND Development] Dark_Avenger:
Sorry... no change... still boot-loop
[HD2 Android NAND Development] pathologo:
Unfortunately rev8b is also bootlooping.

cLK black for me, too, of course.:good:

Please tell me more.:)
[HD2 Android NAND Development] kokotas:
Ok then. You all have to revert to rev7 until I can think of a reason that's causing this behavior.

Thanks for the help guys.

Regards!
[HD2 Android NAND Development] NYLimited:
A long time ago in a galaxy far, far away....

It is a period of civil war.

Rebel spaceships, striking from a hidden base...

This may help narrow the problem to a few less lines of code.

Before the app blew and restarted it had reached the point where the 2 files (.twrps and .version) are updated. Both were written today, late afternoon my time, which coincides with me trying rev 8.

---

Sometimes I read because I am too lazy to think... (via Tapatalk)
[HD2 Android NAND Development] kokotas:
Last attempt for tonight cause my bed is calling me:)

If rev8c works I will upload the SD version too and update the code at github too.

:fingers-crossed::fingers-crossed::fingers-crossed:

Please become one of the News-Writers of XDA.:good: I promise I'll be reading all your articles...;)
[HD2 Android NAND Development] NYLimited:
Me??

News writer???

There must be a word for that..

Oh yeah, I found it! Here ya go:

my·thol·o·gy

/məˈTHäləjē/

Noun

A collection of myths, esp. one belonging to a particular religious or cultural tradition.

A set of stories or beliefs about a particular person, institution, or situation, esp. when exaggerated or fictitious.

​

Go to bed! I was going to get you a screen capture but wasn't sure if working now or not so here's the news:

It is working (loading) fine!!!!!!

:victory::victory::victory::victory::victory:​
[HD2 Android NAND Development] kokotas:
It could be done easily. For example if the Rom makers would place a 0 byte file (ie .dataonext) inside their Rom's /data folder as a mark that DataOnExt method is used by the Rom, then TWRP would just scan the entire /sd-ext for that file and return the path without any user interaction.

find /sd-ext -type f -maxdepth 4 -iname .dataonext | sed -n 's!/.dataonext!!g p'

You just proved my point:p

echo "!HAEY KCUF" | rev

Uploaded the SD version and updated the 1st post. Tomorrow will update the code at github.

Goodnight!
[HD2 Android NAND Development] NYLimited:
You don't really have to do all that work, at least not with Tytung's ROM. Don't forget that he modifies build.prop so the string "[DataOnEXT]" can easily be parsed out of there:

Modify /system/build.prop and append " [DataOnEXT]" to the end of the line of ro.build.display.id

output=`grep -i "^ro\.build\.display\.id.*\[DataOnEXT\]$" /system/build.prop`
if [ -z "$output" ]; then
sed -i '/ro\.build\.display\.id/s/$/ \[DataOnEXT\]/' /system/build.prop
fi

If I was writing such code I would make the match case insensitive since who knows how others will do it, or even if Tytung may some day change it. I also have no idea if others publishing such ROMs do this or not. Xylograph and KovJanos may not do it which would make things more difficult I suppose.

Thanks for tracking this one!

G'night, bro, sleep well!

[ EDIT ] - A quick glance at KovJanos' PA-HD2 ROM shows that he is using Tytung's method (and I suspect script file also) adding "[DataOnEXT]" to the end of the line of "ro.build.display.id" as well.
[HD2 Android NAND Development] DarrenNewsgroup:
I raised the question in http://xdaforums.com/showpost.php?p=36324502&postcount=3

If you look for a 0 byte file for dataonext is this not just one part of the story? What about DalvikOnNand and other permutations? I am just thinking from a user's backup/restore experience that they don't necessarily know where each ROM has installed the stuff that needs backing up.

Darren
[HD2 Android NAND Development] NYLimited:
I tend to agree. This is why - assuming the ROM makers all do it - looking at ro.build.display.id may be more indicative as they tend to identify their ROMs there. Of course, there'll always be the one who does things differently I suppose. :crying:
[HD2 Android NAND Development] shanman-2:
Yes. Working fine now. :). 5*
[HD2 Android NAND Development] NYLimited:
Small stuff, all cosmetic..

DATAONEXT...

Going to SETUP / DATAONEXT shows me the path I have previously entered. The path is correct. Above the path name, in red, the message is telling me to enter a valid path. Hey, it IS valid. The warning remains till I press enter at which time the check is made and I am now told the path (which I didn't touch) is, indeed, valid.

Suggestion: validate the path on entry to that screen and if/when the text is changed.

PARTITION SIZE FOR BACKUPS...

Similar situation. Data is displayed (from previous time perhaps) which will likely be incorrect on entry (although nobody will really know unless they are looking for bugs). Pressing recalculate fixes it, of course.

During the calculations the back arrow is removed from the bottom of the screen - this is about the only hint that something is going on behind the scenes.

---

Everyone has a photographic memory. Some just don't have space left on their sd card ... (via Tapatalk)
[HD2 Android NAND Development] Dark_Avenger:
Rev8c is working for me too, but there is a bug in partitions size calculation. My dalvic-cache is on /sd-ext, but I'm not using DataOnExt. When I check the check box not to include it into the backup both sizes of /sd-ext AND /data partitions are reduced, making /data size 10 M, which is not correct. I think that only the size of the actual partition with dalvic-cache (/sd-ext in my case) should be affected. The size of /data should not be changed. After the backup the size of the compressed data.yaffs2.win file is 57M.

I think an option in Backup page "Don't save NativeSD ROMs folders" ( like "Don't save davlic-cache..." ) will be better. From the main Backup page I'm making a complete backup and I will expect the whole phone storage to be backup - backup complete current state of the phone. If I want to exclude something I will check an option for this. Kokotas, please consider this suggestion. I think that excluding silently something is not a good idea.

Thanks in advance

Updated theme for rev8c is attached.
[HD2 Android NAND Development] NYLimited:
Titanium Backup

Am I the only one with a problem or did I miss something else? :confused:
[HD2 Android NAND Development] Dark_Avenger:
Working fine for me with TB v5.8.0 from today. Probably TB is looking inside data.yaffs2.win, which in case of DataOnExt is missing or without any apps in it.
[HD2 Android NAND Development] Nixda99:
v7 is top, issues in v8c

Thanks kokotas to fix my reported errors so fast, works all beautiful in v7.:good:

Some new issues in Version v8c:

- Fix permissionsis working, but can't make a backup with DataOnExt (tried with both options for "Enable path-checking for DataOnExt", DataOnext subfolder "sd-ext/NexusHD2-ICS/data" is configured)- he said can't find DataOnExt:

... I:Fixing /data/data/com.google.android.location/files/DATA_Preferences, uid: 10018, gid: 10018
Done fixing permissions.
I:Unmounting main partitions...
Done.

I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'advanced'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'backup'
I:Set page: 'backup_run'
Updating partition details...
I:NativeSD Roms detected.
I:Size of sd-ext will be adjusted.
I:NativeSD Roms detected.
I:Excluding 'TWRP' from sd-ext backup.
I:Excluding '4extRecovery' from sd-ext backup.
I:Excluding 'Touch' from sd-ext backup.
I:Excluding 'NexusHD2-JellyBean' from sd-ext backup.
I:Excluding 'Backup' from sd-ext backup.
I:Excluding 'NexusHD2-ICS' from sd-ext backup.
I:Backup Name is: '2013-01-07--10-59-36'
I:Full_Backup_Path is: '/sdcard/TWRP/BACKUPS/htcleo/2013-01-07--10-59-36/'

[BACKUP STARTED]
* Backup Folder:2013-01-07--10-59-36
@ /sdcard/TWRP/BACKUPS/htcleo
I:Calculating backup details...
[B][I]E:Unable to locate dataOnext.[/I][/B]
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'backup'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'

Tested it already with no check permissions before backup, the same result.

- would made a screenshot of unsuccessful backup, after pressing logo he changed the red text "Backup error" in blue "Backup successful":D

- Backup page: size in brackets after data: size is showing correctly after update from v7, after changing path in dataOnExt or not working backup he shows "data (-149)"

- Screenshots had all a size of 0 bytes

Back to v7 and Backup are working with unchanged DataOnExt path, that's why the path is correct.

Started the recovery via Magldr - boot from SD (nativeSD subfolder).
[HD2 Android NAND Development] kokotas:
Hi guys,

So what you're suggesting is:

Mount /system

Check /system/build.prop for "[DataOnEXT]" string

Unmount /system

If "[DataOnEXT]" string is found mount /sd-ext.

...then what? What is the correct path?

(If you meant to also use the Rom's name for the path, then what will happen if the Rom uses the original DataOnExt method?)

Ok, make it 1 byte and write something useful inside like:

1 => All data are on ext partition (so there is nothing on 'userdata')
0 => Not all data are on ext partition (so 'userdata' is not empty)

Anyways, I referred to the .dataonext file as an example.

Just check the checkbox found under "Settings/DataOnExt".

But it is not important/required to save the dalvik-cache too. It will be created on boot. And you will have saved some space on your card by reducing the size of the backup file.

People, please stop using difficult words:silly:

Simple. For the NAND Roms that use various [....]2sd scripts just make sure you have /sd-ext checked before backing up.

They don't necessarily know, but eventually they will learn.

And they will learn by making mistakes, just like many of us.

Absolutely right! But it is not that hard to adopt something that is useful for the most users (an example from the past is the CWM patch for off-mode charging).

I will look into it.

I have already added that, but I haven't enabled it because it is slowing down the UI. And the event you describe below would happen

each time

you enter the "Backup" page

even if you didn't change any settings

.

So I think it is better to

manually "Refresh sizes" after a change in settings

.

I'll see if I can make something else to notify the user that a process is running in background.

You mean the shown size of /data is 10M or reduced by 10M?

If you select to skip dalvik-cache during backup, then "dalvik-cahe" folder will be excluded from everywhere. Won't matter if it is on /cache or /data or /sd-ext.

Honestly I don't like it, but I will add another option.

How is this silently? I clearly said it in the post you quoted:p

Thank you for sharing it:good:

Can't help you. Never used Titanium.

I can't test the SD version, but I would never put it inside the NativeSD folder.

I'd place it directly to the root of card (/sdcard/twrp2.3.3.0.ex).

Don't know if this is just a typo but the path entered should be

[B]/[/B]sd-ext/NexusHD2-ICS/data

not

sd-ext/NexusHD2-ICS/data

.

FYI this part of the log shows how the NativeSD Roms are excluded from the backup.

I am simply using the "/sdcard/NativeSD" folder to make a list of the sub-directories.

And from what I see, you have the SD recoveries in there too. Better if you move them to the root of your card, but it's up to you.:D

The text changed to "successful" because of the screenshot process. But screenshot taking is still not working as it should be.

Regards!
[HD2 Android NAND Development] Dark_Avenger:
Size is shown as 10M. If you take a look at the next report.. it's even shown as negative in his case :)

There is definitely something wrong with the /data partition size calculation.

My dalvik-cache is on /sd-ext.... not in /data. /data partition size is wrongly subtracted by the size of dalvik-cache.

Same size of 176MB (probably the size of dalvic-cache) is subtracted from BOTH /sd-ext and /data. Should be subtracted ONLY from /sd-ext.

Thank you very very much.
[HD2 Android NAND Development] Nixda99:
Yes was only a typo, my path has the backslash at the beginning. Fix permissions is working with this configured path.

The advantage is that I never had to change the SD path in Magldr, because it's always "NativeSD". With the Native SD Manager app I set the recovery or NatvieSD rom and the manager copy the zImage and initrd from /sdcard/NativeSD/TWRP to /sdcard/NativeSD and Magldr start the recovery from the NativeSD folder. That's why it is the same if i place it in /sdcard/twrp2.3.3.0.ex. And TWRP v7 made a backup without problems with this path, only v8c bring the DataOnExt error message.
[HD2 Android NAND Development] kokotas:
Please try the attached recovery and upload a log file.

[EDIT]Got the log! Removing the attachment...[/EDIT]
[HD2 Android NAND Development] shanman-2:
Getting error, Unable to locate dataOnext, when trying to backup data.

Path is set correctly.
[HD2 Android NAND Development] NYLimited:
Sure, get the name from the build.prop also. If you find "[DataOnEXT]" in build.prop that means the ROM went to the trouble of following the Tytung method (not sure what else to call it) and the entire path should be buildable from there.

If the ROM uses the "original" method (are there ROMs which use this? I don't know) youwill not find "[DataOnEXT]" in build.prop and you may have to rely on either a second function to find the location or on the user to enter it.

Since I am not aware of any "rule" on how this is setup by various chefs this will never be a perfect, 100% safe solution.

I suppose this is true...

Don't put a lot of effort into this - it is only a cosmetic feature and, like you said above, we will learn. :)

Hmm.. Are you using compression when creating the backups? Maybe TB is having a difficulty handling the compression which I turned on.
[HD2 Android NAND Development] Dark_Avenger:
Yes... I'm using compression.
[HD2 Android NAND Development] NYLimited:
Oh well, there goes that theory... :(
[HD2 Android NAND Development] Dark_Avenger:
For me, TB does not recognize applications stored in the modified tytung Dataonext data path.
[HD2 Android NAND Development] NYLimited:
I have not looked recently but I am fairly sure TB works with it - when the system is running it should look at /data which is present, no different from the original dataonext setup.

[ EDIT ] - I just checked my TB backups and apps updated yesterday were correctly backed up. It does not seem to be bothered by /data being on the card.
[HD2 Android NAND Development] sunitknandi:
Is it because the folder is getting excluded?

Sent with love from me to you via HTC HD2
[HD2 Android NAND Development] MarkAtHome:
TWRP with WiFi ability?

I know that NTFS support is on your todo list, which is great, and I am anxiously looking forward to it.

How about enabling TWRP with WiFi ability, and thereby provide the means to connect to your LAN?

It opens many possibilities, including saving backups directly to a LAN drive/folder, ftp'ing and more, right from recovery...

Having Team-Win's ear, it might be beneficial to have them include this capability in their source, following your lead, of course. ;)