NexusHD2 Android Forum

NYLimited wrote:
I don't use ROM Manager so I cannot help you there.

Which install option did you select? If you used DataOnEXT the only recovery that will help you (as far as I know) is TWRP Extended since none of the others would know where your /data partition is located.

You might also want to try ROM Toolbox and like utilities which may help.

Hi NYLimited, thanks for the quick reply. I am on the NAND option. TWRP Extended is the recovery I am using, but I can't fix permissions with it. The script runs and exits normally, but for less than a second, without actually processing any permissions. No error messages. The same happens when I call the fix_permissions script from Terminal, or from Rom Manager.

I didn't try ROM Toolbox but ROM Manager is practically identical to it, and as far as I know they all call the same script.

My question is: Are any of you able to fix permissions on this ROM, and if yes: how do you do it?

Odysseus wrote:I personally have over 2 dozen bad blocks on my NAND, which is why I'm using a data-on-ext install.

Just as an afterthought, DataOnExt was originally looked upon as a solution for EU devices, being able to install more apps or like you noted, for bad blocks.

But, consider that the HD2 NAND operates at roughly Class 4 SD card speed equivalent. With the original Class 2 card supplied with the device NAND installations were, in fact, faster.

However, using a Class 6 (or faster) card and separating the system and data partitions to separate devices, the latter of which includes your cache and Dalvik as well, it actually makes no sense to me to have a NAND only installation these days.

Food for thought...



---
Any clod can have the facts, but having an opinion is an art.

malkovich wrote:
Hi NYLimited, thanks for the quick reply. I am on the NAND option. TWRP Extended is the recovery I am using, but I can't fix permissions with it. The script runs and exits normally, but for less than a second, without actually processing any permissions. No error messages. The same happens when I call the fix_permissions script from Terminal, or from Rom Manager.

I didn't try ROM Toolbox but ROM Manager is practically identical to it, and as far as I know they all call the same script.

My question is: Are any of you able to fix permissions on this ROM, and if yes: how do you do it?

You are right, it should take much longer if it does the job. I remember ROM Toolbox taking quite a while. It can examine each app's manifest to do the job so it need not rely on a script alone.

Unfortunately I can't answer your last question without my old hd2 but hopefully someone's else can.

[ EDIT ] I just realized you said NAND only, sorry. There should not be a difference in that setup from the traditional installations. Perhaps sending the recovery log to kokotas might help shed some light on the problem.


---
Any clod can have the facts, but having an opinion is an art.

NYLimited wrote:
You are right, it should take much longer if it does the job. I remember ROM Toolbox taking quite a while. It can examine each app's manifest to do the job so it need not rely on a script alone.

[ EDIT ] I just realized you said NAND only, sorry. There should not be a difference in that setup from the traditional installations. Perhaps sending the recovery log to kokotas might help shed some light on the problem.

It usually takes about two minutes, and I'm pretty sure they all use the same script. Which has been around for ages, so I don't think it came from kokotas. What recovery log do you mean? There is no error output. The fix_permissions script just starts normally, then a few milliseconds later exits normally.

I thought there would be many people who had tried fixing permissions on this ROM, it's a pretty regular thing for me.

malkovich wrote:
It usually takes about two minutes, and I'm pretty sure they all use the same script. Which has been around for ages, so I don't think it came from kokotas. What recovery log do you mean? There is no error output. The fix_permissions script just starts normally, then a few milliseconds later exits normally.

I thought there would be many people who had tried fixing permissions on this ROM, it's a pretty regular thing for me.

No, it didn't originate from kokotas but the log that twrp writes when you do things and especially while it initializes may help him figure out why the script is not working. Someplace in twrp - I think perhaps advanced, don't recall exactly - you will find an option to copy log to the sd card. Do this just before exiting twrp and once back in android look for the log file in the card's root directory. Post it with your question in the twrp thread here for kokotas to look at and who knows.. Maybe nothing, maybe something. Not a lot to lose.

NYLimited wrote:
Just as an afterthought, DataOnExt was originally looked upon as a solution for EU devices, being able to install more apps or like you noted, for bad blocks.

But, consider that the HD2 NAND operates at roughly Class 4 SD card speed equivalent. With the original Class 2 card supplied with the device NAND installations were, in fact, faster.

However, using a Class 6 (or faster) card and separating the system and data partitions to separate devices, the latter of which includes your cache and Dalvik as well, it actually makes no sense to me to have a NAND only installation these days.

Food for thought...



---
Any clod can have the facts, but having an opinion is an art.

I've read so much on the other board about the pros and cons of a straight SD install. My thing is my phone is real finicky about fast SD cards. I've already posted about my 8GB Sandisk Ultra issue. My current 16GB PNY is a slower rated slower card (still a cl10), but works better. I've got it setup with almost 13GB storage and 2GB ext. I like the space I have now and the flexibility that much storage gives me. With a larger card perhaps I'd think about it.

Odysseus wrote:
I've read so much on the other board about the pros and cons of a straight SD install. My thing is my phone is real finicky about fast SD cards. I've already posted about my 8GB Sandisk Ultra issue. My current 16GB PNY is a slower rated slower card (still a cl10), but works better. I've got it setup with almost 13GB storage and 2GB ext. I like the space I have now and the flexibility that much storage gives me. With a larger card perhaps I'd think about it.

I was never very big on NativeSD myself. Call me old fashioned but I always liked the concept of "multiple spindles". Now, before someone jumps all over this one I *do* know this is solid state and there are no spindles. But there is a card bus in addition to NAND and my 32GB Class 6 Samsung gave me a lot of flexibility, space and improved performance for $20. I also had 400mb for system, just in case, with room to spare.


---
Any clod can have the facts, but having an opinion is an art.

NYLimited wrote:
If the download is corrupt you should really be able to tell by the published md5.

There are simple ways to check for bad blocks which I and others have documented numerous times. Even easier is to try a larger system partition as already suggested.

It seems to me that you are a tad bit too busy to use search and find your answers. Fortunately for me my device is already fine so I will stop this nonsense. Perhaps we shall continue when you have more time and you don't wish me to do your research for you.


---
Any clod can have the facts, but having an opinion is an art.

Heh!
Sorry but the day was getting long in the tooth and I was merely replying to your helpful post before attempting anything myself, I will let you know when I do.
Of course I should check the download with md5 checksum and sure I'll try the larger system partition, but it might be a while because for now, the phone is now working. But I like speed, and bleeding edge...
I must admit I like the Xperia launcher feature of the ROM I'm using, it should let me be able to play Runescape from the phone which might get me back into the game. Maybe I should get some practice and try working on implementing the Xperia Launcher into Tytung's ROM...

i have a problem,

i have 2.08.HSPL, Leo_RADIO_2.15.50.14, MAGLDR v1.13, ClockworkMod Recovery 5.0.2.6 and 2gb sd card

i instal thru aroma instaler, and istal on nand, everything is sucesful, and device restar, but stuck on boot screen where is a circle cyanongeMod. It can take a hour but nothing change.

Is problem with system partition i have 400m, or what i doing wrong.

every rom that i instal on nand stuck on boot screen, if i istal rom on sd card than work perfect, but where to fin a rom like this for instal on sd card

domix wrote:i have a problem,

i have 2.08.HSPL, Leo_RADIO_2.15.50.14, MAGLDR v1.13, ClockworkMod Recovery 5.0.2.6 and 2gb sd card

i instal thru aroma instaler, and istal on nand, everything is sucesful, and device restar, but stuck on boot screen where is a circle cyanongeMod. It can take a hour but nothing change.

Is problem with system partition i have 400m, or what i doing wrong.

every rom that i instal on nand stuck on boot screen, if i istal rom on sd card than work perfect, but where to fin a rom like this for instal on sd card

Does your HD2 have 512 MB (Europe version) or 1024 MB (T-Mobile USA version) ROM?
If 512MB, your remaining data partition will be too low.