yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
Some (most nand) roms dont have the haret files, just saying that they are in the /sdcard/recovery folder anyway since most, if not all wm6.5 users will be using your sdrecovery. if you make a nand recovery version, those users won't have wm6.5 in nand. The path in startup.txt would still need to be changed though, sed twrp2 NativeSD.

trying UnivBeta1 DirectSD PixelDroid_LIQUID_4.4.4

It says "please flash testy using recovery" it means tempy;)

recovery exits install almost immediately after showing credits.

have attached recovery log.

Edit; updater-script seems unchanged, have attached
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
have attached startup.txt from portadroid 4

Edit; have attached screen
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
it was in /sdcard/tempy/test.zip

Edit; unexpected "else" line 469 (expecting "}")

i can't see an if in that function
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Forget that - I changed it after you posted it
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
i uncommented line 467:o

and get the screen below
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
that second / is the issue there

can you run

pwd

I was getting /tmp are you getting /tmp/ by any chance

can you ls the /tmp/tmp folder and cat the log file if it's there (if it isn't on the sdcard - I haven't added the copy to sdcard if it exits due to command error (exit 1) ).

Also try running the script from root (/)
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
running from root seems to work up to a point, see screens

Edit; can't find a log file on sdcard
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
i get the screens below, tried installing the new zip but it finishes almost immediately.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
What do you want a diff of? i can post a couple of initrd.gzs, nand and sd build.

i can also post a superRAM initrd.gz and one that i think puts the first 100mb of /system into RAM and the rest into system.ext4.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
have attached ramdisks

beta1d seems to install ok, but the new rom.zip install still finishes early, the updater script shows credits so i think is unedited. the *run.log is in /tmp and on sdcard, but only shows one line "/tmp/mountfs-DirectSD"

Edit; deleted previous new rom.zip and run.log from sdcard, tried again and get same result.

Edit2; tried porta, get screen below.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
tried beta1e porta, get "line 621: romsize: parameter not set"

SuperRAM:fingers-crossed::fingers-crossed::D

Edit; tried DirectSD, get same thing with updater-script not modified, it didn't say which zip to flash but the zip was on /sdcard. can post screens and whatever

Edit2; have attached directsd run.log
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
beta1f porta, see screen, no run.log created

Edit; tried beta1f DirectSD, see screen, no log

Edit2; the updater-script in /meta-inf... looks ok though
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
beta1g directsd, see screen, no /sdcard/*run.log

seemed to take ages "cleaning"

will clean sdcard card tomorrow and re-test

Edit; reformatted p1 fat, p2&3 ext4

tried pixel4.4.4 directSD with your edited post above (beta1h), see new screens, updater script doesn't seem to be edited after flashing new zip (credits show)

no log, stuck a bit on "cleaning":)

Edit2; tried porta, get screen 4
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
i tried beta1i see screen.

since a few tests ago, i have been running the .sh from root. i looked at /tmp after running and only see recovery.log, i can't see 7za in root either.

Edit; here is testing screen too, busybox blkid is same as blkid
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
tried beta1j, i get slightly different results depending on whether there is just the rom.zip present or an earlier test i think.

I have to chmod 0777 the .sh file before it runs.

Edit; tried porta see two added screens
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
after reboot recovery shows /dev/block/mmcblk0p1 mounted on /sdcard

tried porta-o, see screen for end of output

My brain isn't working too well tonight, need sleep:o

Edit; tried no options, see screen. it seems to be waiting for user input on the "runn to runn" line but can't input anything.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
It was a typo with ROM_NAME last night:o

Tried beta1l installed to /, get the attached .txt from command prompt (so as to show the whole output), using DirectSD PixelDroid KitKat(dataname)

Edit; i just tried sh-ing beta1l.sh from phone without any options, get the second .txt attached
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
I'll start using dropbox to host the script, so any minor fixes will be reflected there.

http://bit.ly/MultiDL

Moved the user input to desktop (Ubuntu) only.

Could use some other case reports: i.e

mount > mount.txt

m NativeSD ROM_NAME

mount >> mount.txt

m DirectSD ROM_NAME2

mount >> mount.txt

and post the mount.txt file.

NAND and DataOnExt I believe may be broken, need to add the NAND mounts for those.

For anyone looking to flash a zip to a Native/DirectSD ROM. If the updater-script doesn't have any mount /system lines then you can flash them by first running this script as:

sh UnivBeta.sh m NativeSD ROMname

if there is a mount line (there probably is) then rename the zip as ROMnameStuff.zip and run

sh UnivBeta.sh NativeSD ROMname

and then flash the zip
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
Had a really busy week:o

tried UnivBeta1.3 DirectSD LIQUID, get .txt below and mount screen
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
I tried flashing the RMNET_to_PPP_update.zip on tytung's latest rom using this, there is a "mount("MTD", "system", "/system");" line in updater-script so renamed the zip to /sdcard/NexusHD2-KitKatStuff.zip and from adb ran the script and flashed the zip. No PPP files were in /system. the *Stuff.zip's updater-script was unchanged. Have added screen and mount.txt. From mount.txt it seems p3 was mounted.
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Yea, you've ran it with m, if the updater-script needs changed you need to run it like a ROM.zip, I have added a check for if the zip is a ROM or not (checks for a vold.fstab file), so that ramdisk/mountfs stuff doesn't run if the zip isn't a ROM. Also moved a few things around new 1.4 upped (forgot to increment number). p3 will always be mounted as /DirectSD if detected (forgot to add it to the unmounts)
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
i just tried 1.2v with tytungs latest, directSD NexusHD2, the resultant zip installs "successfully" immediately. attached test.txt, updater-script and recovlog.

Edit; tried 1.4 DirectSD NexusHD2, attached 1.4.txt
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
typo with 1.4 and missing ,'s in updater-script - fixed with 1.5
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
yeah i added m, but am a bit confused as to what exactly to do.:o:)

Edit; tried 1.5, same; new rom.zip "success"
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
missing ; - fixed 1.6
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
NexusHD2 DirectSD hangs on htc screen, attached test.txt and dmesg, no logcat(shows as offline)

Edit; still not entirely sure about zip flashing

1 renamed RMNET_to_PPP_update.zip to NexusHD2-KitKatStuff.zip and put on /sdcard

2 pushed beta1.6 to /

3 adb shell sh UnivBeta1.6.sh NativeSD NexusHD2-KitKatStuff > test1point6rmnet.txt get attached text.

4 flash the resulting /sdcard/NexusHD2-KitKatStuff_NativeSD.zip attached

5 boot the rom from NativeSD folder as usual but it still has rmnet, no ppp system files.
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Ah, I get you now... when I said ROM_NAMEstuff I mean ROM_NAME*.zip, the ROM_NAME needs to be the same as the ROM you want to install to. i.e. NexusHD2-KitKat , you may have a NexusHD2-KitKatStuff foder on p2 with the ppp stuff there.

A few things I noticed ...

If you have numerous zips called ROM_NAME*.zip for example:

NexusA.zip

NexusB.zip

NexusC.zip

on /sdcard with a ROM_NAME of Nexus, the sh will work with NexusA.zip, however if A, B or C is a ROM.zip (contains vold.fstab), it will start to look for a ramdisk to modify, it will look in NexusA.zip as well as at /sdcard/initrd.gz and/or /sdcard/boot.img, but there is an exit if it doesn't find one... so as long as you don't have a initrd/boot.img at /sdcard it'll be fine.

All that being said there may be a way to use the portadroid method of updating with Native/DirectSD, but I'm not going to touch the ramdisk modifications for the time being
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
1. mountfs-DirectSD.sh is in initrd.gz, attached

2. /system seems ok attached screen

3. /system/bin list attached

Edit; Tried 1.6 on PixelDroid_CARBON DirectSD, hangs on pixel's carbon screen (replacement of HTC screen), attached dmesg

My thoughts are that sleep commands aren't working, i know you tried whiles instead of waits earlier, when we had the same problem.

Edit2; scratch that, i just tried "/sdcard/.../bin/busybox sleep 5" from adb on the busybox from the extracted initrd.gz made by the script from tytung's rom, and it sleeps for 5 seconds. perhaps need to add more?

Edit3; just noticed there is a missing carriage return in the mountfs script below
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Edit2 - it's a while loop i.e. sleep 5 cycles until it's no longer needed.

Edit 3 - yea noticed those, fixed in 1.7 (also added rw into mount options just for good measure)
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
NexusHD2 DirectSD boots :highfive::D
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Good to here, back to being a properly running script.

Next up need to see if the porta stuff will work, then when I've got time need to see if I can merge the two; loops and binds.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
sorry busy again.

tried pixel with porta-o get txt below from adb

it seems to detect an f2fs partition, but p2 & p3 are ext4. I also seem to be running out of sdcard space again, will delete some stuff again and try nexushd2 although i should have 1.6gb on fat32.

Edit; tried nexus, attached adb txt, flashed the new zip, it seemed to install rather quickly but took a few seconds. i took the boot folder out of /sdcard/NativeSD and put it on /sdcard so magldr could boot it (not sure if necessary), it hangs on htc screen. Interestingly, the sdcard contents showed up on windows as a removeable disk whilst stuck on htc screen. have also attached recovery log, updater-script, dmesg and initrd.gz

Edit2; i remembered that i did try the first pixel test before on the same ext4&ext4, but didn't post about it, so there might have been extant files on the sdcard, giving odd results. Also, is it the internal memory we are running short of? I appear to be running short of my internal memory too;):D
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
A few things fixed with 1_8, the storage you're running low on is actually the system.ext4 file (it should have been made to fit the zip but that doesn't seem to be the case from the logs (let me know if the size of system.ext4 is different that that of data and cache.ext4) ). The f2fs thing was due to where I put the checks in (they weren't run). If you can run the verbose(v) script you can see every command run, so should be able to pick up where things are slipping up.

What it should be doing is creating the default size system.ext4 (if one doesn't exist), and then it should be deleted and a new one with the full size made (not an elegant approach but seemed simpliest at the time), there is however a place where you can manually specify the size you want - In a file at /sdcard/porta.txt add:

ext4 128000 25600 25600

Which will make the system.ext4 500MB and the data and cache 100MB

EDIT - system.img size may be fixed with 1_9

The porta stuff should work - albeit not as it did before, however there are some services added to init.rc that I'll start adding to the porta side of things.

I took a look at the user input (no arguments) way of running it again - and it works fine over adb just not on device - and am unsure if there's a way around it...
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
tried 2_3, get txt below. can set verbose if needed
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
1_9 (or 1_8 just change url) would be better - much more likely to run properly, and haven't added the porta fixes to the alphas yet
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
sh can't open 1_9:confused:

tried chmod 0777 but it still can't open it

Edit: my bad, forgot to put v at end of sh filename, it is taking some time to run...

Edit2; hanging on htc screen, booted from NativeSD folder. Still able to access sdcard from pc. attached some stuff.

install folder has cache.ext4 78mb, data.ext4 78mb, system.ext4 370mb
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Sizes look good. Have reupped 1_9 - noticed 1 glaring error (that isn't reported by the dmesg for some reason) - the .exts are in a NexusHD2-KitKat-CM_porta-o folder, right??? (the porta-o is missed by the mountfs.sh).

Try running 1_9 as:

./univ.sh mr porta-o NexusHD2-KitKat-CM

no need to install the whole system again.

we can leave the beta script as is for the time being and test out mountfs scripts by adding them to the /sdcard/bins folder from here on...

I try and trim the original porta scripts to something compatible with this script.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
still hangs on htc screen, i can post dmesg but forgot to echo output of screen to file.

Edit; added screens and dmesg

Edit2; added initrd.gz, good luck with inits, pre-inits, loops and binds:fingers-crossed:
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
dmesg and the initrd.gz would be fine - the mountfs stuff I'm guessing may be too simplistic for porta. I'll get a modified one from portadroid up tomorrow... ( the difference between the original and mine is when the mounting happens, originally it's done before init is run, here it's done a tad later on )

Edit. Yea, mr shouldn't have remode the loops I think the issue was the -f's (I'm sure they worked when I tested it a few weeks back). Have changed it to -e's (still 1_9), you're gonna have to run the full script again to install system

Edit2. There's some residual stuff left over I think - the mountfs wasn't changed at all.

BTW can you confirm where the .ext4 files are being made /sdcard/NativeSD/ROM_NAME_type ??
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
see last edit
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
tried latest 1_9 and get

with no line number. Can't find a ( without a corresponding ) in the script:confused:

yea the install folder is /sdcard/NativeSD/ROM_NAME_type, i think that for porta rom it would be best to be in /sdcard/ROM_NAME_type, and have initrd.gz just look for the *.ext4 files in the same directory as itself. That way people can change the name of the install folder. Does this make sense?

Edit; scratch the above, i had brackets in the .sh name:o

Hangs on htc screen

Have attached stuff

Edit2; i just looked at mountfs-porta-o.sh and the path is "losetup /dev/block/loop1 /sdcard/NexusHD2-KitKat-CM_porta-o/system.ext4", so i put the folder in /sdcard and tried again, hangs on htc screen, dmesg2 below.

Edit3; is it an idea to have porta with system.ext4, cache.ext4 and data.f2fs?
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
That's what I was thinking when I added the /sdcard/porta.txt bit, just thought I'd stick with ext2/4 for the moment

Have upped a 1_91 , can't find much info on the bio too big bit...

Edit try the 1_92v - running mr

Edit2 yeah I see I have mountfs looking in the wrong place - changed in gamma - the reason I'm using the NativeSD folder is that the NativeSD app should work with the porta kernel/ramdisk
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
tried mr 1_92 (still named 1_9v on DL page)

get txt below, ramdisk not made
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
typo - reupped
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
tried mr 1_92, hangs on htc screen.
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
try gamma3 with porta-init.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
gamma3 in notepad++ shows mainly greyed text from lines 431 to 860

if i run it i get "/GAMMA3.sh: line 863: syntax error: unexpected "}" (expecting "fi")"
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Yea missing a fi there - reupped. it's meant to be greyed (took a while to get it that way), the text there is in most part from the original portadroid. Have made it so that porta-init starts the same way the original portadroid did - i.e before init is executed.

Edit. just noticed I need to escape (\) some of the $'s in the grey part, wait for a gamma4

Edit2 . gamma4 done
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
tried gamma4 get txt attached
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
needed to escape the `'s in the grey ... gamma4_1
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
got txt, doesn't seem to mount /data etc.
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
can you delete /sdcard/porta.txt and run it again (I think it's the ext2 that's causing the problem - need to look into it)
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
it now thinks i have f2fs again and not mounting too

the porta.txt did seem to have 41 bytes in it, i should have checked contents before deleting it. it is usually just empty.
[HD2 Android Q&A, Help & Troubleshooting and Genera] macs18max:
[MENTION=4056517]HypoTurtle[/MENTION]

I hope this is not the wrong place to discuss this but need your help with my aroma script.

On test kernel 3.0.xx for magldr using

cat six_mb.gz initrd.gz2 > initrd.gz

where initrd.gz2 is the actuall ramdisk

six_mb.gz is a file with zero of size 6MB

Then I copy it to my sdcard and boot(nativesd).

However now I want to do this in my old aroma script for slimrom 4.2.2, but in an efficient way (without packing 3 different 7MB ramdisk for nand, data2ext, and nativesd in the installer). Can you help me please?

Take a look at the script please..

Thanks
[HD2 Android Q&A, Help & Troubleshooting and Genera] macs18max:
[MENTION=4056517]HypoTurtle[/MENTION] I was just thinking, are commands "dd" and "cat" supported by our recovery. Or do we have to provide some files yo get them working? Sorry I'm total noob when it comes to Linux commands
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
Both dd and cat are supported, at least in the twrp recovery from HypoTurtle's dropbox page

In terminal, typing dd gives

Are you looking at munjeni's posts?:D
[HD2 Android Q&A, Help & Troubleshooting and Genera] macs18max:
Mujeni's post? Which one?

I'm planning to use some codes from hypo script in the installer for future ROM updates

As mention in previous post above, which adds 6mb to initrd. It uses dd and cat.

Apart from this I will be adding boot image flasher for cLK nativesd installations which I used earlier in slim 4.2.2 ROM installer.

;) that's why asked for installer files yesterday.

I have nothing but time here doing nothing, but don't have Linux machine or hd2

Hey Robbie, also could you post slim422 "kernel" folder, without zImage and initrd.gz files.

I need to have a look at .sh files and other related files
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
here you go http://d-h.st/R2I

I was looking at this post of munjeni http://xdaforums.com/showpost.php?p=20294617&postcount=17

which uses dd and then saw your post above:)
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
ooh, i managed to mount an ext4 loop to nand using munjeni's post linked above

Using tytung's kitkat v4.6 NativeSD, nothing android on nand. The fortest partition is 10mb.

system.ext4 on nand?

system.f2fs on nand?:D

Edit; i created a 400mb system partition on nand, and mounted an ext4 loop to it.

tried to cp /system to it but am getting errors, see screens in box below (can't seem to attach screen to post ATM)

I probably need to push the files from rom.zip on pc.

just need to edit updater script and use the patcher to edit init.rc and see if it boots:fingers-crossed:, but i am out of time tonight i think:crying:
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Yea recovery is similar to a rooted rom and for the commands they use a combination of toolbox and/or busybox, dd to make the 6MB and cat to add to it works just fine. Here you can see what options are available, without needing to add any other binaries. There may be some variation depending on the toolbox/busybox compiled with the recovery I suppose, but cat and dd should be fine (as long as you don't let it default).

My approach to the ext4 looping that I added to the script (I know the installation itself wasn't working, but the looping was), was to format to ext2 and then add a journal to it. I wouldn't be 100% sure with f2fs being used with system due to permissions/security etc especially with KK, and given that it;s far from being a 3.10 kernel, perhaps if someone could try and add the f2fs patches to one of the latest kernels that might prove better that the one I compiled.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
yeah, you mentioned security issues before with system on f2fs, would kernel changes (backporting?) to the latest hd2 kernels solve them, or is it inherent to f2fs?

I think system on ext4 loop on nand is a good idea if it can work, we can fill the whole available nand with /system and have sd recovery and boot from magldr adsd. Data on ext4 loop on nand would be too restrictive of space ~420mb Edit; for EU hd2 that is;)
[HD2 Android Q&A, Help & Troubleshooting and Genera] macs18max:
I didn't understand what u meant by "don't let it default"

Anyways I've created a script from your codes. But don't have device to test it.

In aroma updater script that I am working on, these function are already been carried out:

Mount boot partition (also mount boot_dir in nativesd installations)

It detect magldr as boot loader

Extracts initrd to tmp folder

Extract add6mb.sh script to tmp folder

Set permission and run add6mb.sh script to add 6mb zeros to initrd

I have attached the add6mb.sh script, Please have a look and let me know if it will work, or do I need to make any changes