NexusHD2 Android Forum

Odysseus wrote:If you choose to go this route I highly recommend SuperSu as It's still being actively developed where as superuser isn't anymore

tytung wrote:As Odysseus said, maybe to flash SuperSu is quicker for you since you cannot see Settings -> Superuser option.

coohdeh wrote:flashing supersu to nativesd rom is more difficult no?
maybe put in zip file and install rom again?

I have never done NativeSD installation but my guess would be that the traditional supersu.zip file might not necessarily know where the Nativesd installtion is.. As I said, this is only a guess since I have never looked at it.

tytung wrote:Maybe the permission of /system/xbin/su is incorrect.

Code: Select all

adb shell chmod 6755 /system/xbin/su
adb shell ls -l /system/xbin/su


If not, then I'm out of idea since I didn't see any logcat.

As Odysseus said, maybe to flash SuperSu is quicker for you since you cannot see Settings -> Superuser option.

First, many thanks to you three to take time to help me.
I will try to execute these adb commands.
I don't know how to flash SuperSU with NativeSD install and 4ExtRecovery : each time I try such an operation install runs fine but no change in the rom.
What I've already done :
- Installing SuperSU from the store : install Ok, I can lauch SuperSU but the binary update (normal mode) fails.
- Inserting SuperSU.apk in the zip of the rom before installing : SuperSU cames as a system app, I can lauch SuperSU but the binary update (normal mode) fails.
- Installing SuperSU in the 4.2 JB rom : install OK, lauch OK, update binary OK !

Odysseus wrote:Are you trying to use the superuser that's built in to the ROM or SuperSu or Superuser .apk? If you're trying to use a version other than what's included already in cyanogenmod then you need to flash it from recovery or else you won't be able to overwrite the default binary already in /system/xbin. You can manage the included su from system settings, but there won't be any applet unless you install one of the other versions from the market and overwrite by flashing as previously mentioned. If you choose to go this route I highly recommend SuperSu as It's still being actively developed where as superuser isn't anymore.

I hope this helps.

Ciao

Yes, I'm trying to replace the included superuser by SuperSU, as I've noticed some difficulties with granting access, and as Titanium Backup tells me (from the last version) that the included superuser app may not work correctly, and as it seems that only SuperSU has workarounds for JB 4.3.
I don't know how to flash SuperSU (nor any zip file) with a NativeSD install. I use 4ExtRecovery, that let me install any zip file but without result nor change in the rom. If you know how to do, it will be great for me !

coohdeh wrote:
flashing supersu to nativesd rom is more difficult no?
maybe put in zip file and install rom again?

I've tried that as tytung advise me, SuperSU becames a system app but I still can't update binary.

benlm72 wrote:I've tried that as tytung advise me, SuperSU becames a system app but I still can't update binary.

You cannot update the su binary after flashing or installing SuperSU because you don't have the root permission (i.e., the file permission of /system/xbin/su is not 6755).
Please check it first.

benlm72 wrote:Hi tytung,
Help ! I've disabled superuser, but now (as I always don't manage to install SuperSU) superuser has disappeared from settings so I can't reactivate it by this way. I've reinstalled your rom, but superuser is always not visible (and I've lost root rights). How can I get superuser back ?
Thank's

Here's something that I think will work for you, but I haven't tried it myself, as I'm perfectly happy with the SU capability that comes with Tytung's ROM.

First, reinstall Tytung's ROM using the Native SD method. Boot the ROM and let it settle. This is done to ensure a good starting point that has root.

Then go back to recovery and install SuperSU using this file: https://dl.dropboxusercontent.com/u/22856583/UPDATE-SuperSU-v1.65-NexusHD2-JB-NativeSD.zip. The file is the recovery install of SuperSU with the script file modified to mount the NativeSD /system and /data partitions instead of the NAND partitions. If you look at the update-binary file in the "UPDATE-SuperSU-v1.65-NexusHD2-JB-NativeSD\META-INF\com\google\android" folder, you'll see that there are a lot of extra manipulations that happen during the install besides just copying the APK file to your device. I'm guessing that the lack of these extra manipulations are probably what caused your previous install attempts to fail.

Good luck, and please report back if you decide to try this.

@benlm72, Just out of curiosity why are you using 4EXT Recovery with your HD2? Don't get me wrong, I think it's a great recovery as I use it now with my Amaze 4G, but I don't believe it's the best choice for the HD2. With my Amaze it works well because even though I have my bootloader officially unlocked via the HTC Dev unlock tool, it remains S-off. So the only way to flash a kernel or a ROM with an included kernel is using 4EXT with "smart flash" enabled. However this isn't a problem with the HD2. Once you've used HSPL you've already obtained "S-off" which is how we're able to flash different radios and ROMs that have no relation to the mobile carrier the phone was built for.

I don't mean to discredit 4EXT in any way, I like it so much with my Amaze that I paid for it, but I'm not at all familiar with how well it works on the HD2. Out of the popular recoveries for the HD2, Extended-TWRP has the most HD2 features specific for this device, such as recognizing the modified Data-on-EXT or NativeSD installs that don't exist with most other phones. The other logical choice would be the custom CMR for the HD2 or the newer touch version.

Take a look at the recovery threads here or on the HD2 forums @xda and you'll see what I'm talking about.

I hope this helps

Ciao

tytung wrote:
1. Wakelock Detector 1.5.5
Android Media process will scan your SD card at boot. I guess you may have a lot of files in the SD card. Just wait for the process to finish its job. Or try another empty SD card to identify the issue first.
akmd is the process to control your g-sensor. G-sensor is for tilting, rotating, etc. Did you install any app related to G-sensor?

2. T9 Dialer is a new feature on stock Android 4.3. I'm not sure if the CM team will change it later on CM 10.2 or not. Nothing I will do.

3. Quit the camera app and run it again. Or install another app from Google Play.

4. If you turn on the flashlight too long, you will get high battery drain (that explains the hot battery) and the led may be damaged.

Thanks Tytung for your reply,
first of all, I've Installed 3.2,
1- till now, there are no problems like the previous setup.

2- is there a way to return back to an older dialer?, DW contacts is great, but it becomes heavy by time.

3- no problem, in 3.2 I didn't face any problems yet with the camera.

4- No, I didn't turn it on for too long, maybe only 30 seconds, anyway it did not happen in 3.2 either.

5- I'm not facing any battery drains in 3.2, so definitly there were some serious problems with my previous setup of 3.1, maybe the problem wasn't in 3.1, rather something went wrong somewhere

thanks again for your help, it's much appreciated!

Hi, does anyone know how to change screen resolution on this rom? I have looked through the FAQ and searched this forum but found nothing. Thanks.

Thanks for your GREAT work !!!

I have noticed that in past few ROMs VPN over 3G/Mobile data does not work, when I want to connect it says that phone does not have any connection...

How could I fix it or could you tell me how may I help you fixing it?

Thank you

Simon

mmcml wrote:Hi, does anyone know how to change screen resolution on this rom? I have looked through the FAQ and searched this forum but found nothing. Thanks.

A relatively quick and easy way would be to edit the build.prop file located in the /system directory. You can use a root enabled text editor or something like ROM Toolbox to edit the file. The line you need to find and change is

Code: Select all

ro.sf.lcd_density=240

where the value could be between 160 (small) and 240 as I recall. Note that this may alter the availability of apps on Google Play although 160 and 240 are generally considered safe.

Odysseus wrote:@benlm72, Just out of curiosity why are you using 4EXT Recovery with your HD2? Don't get me wrong, I think it's a great recovery as I use it now with my Amaze 4G, but I don't believe it's the best choice for the HD2. With my Amaze it works well because even though I have my bootloader officially unlocked via the HTC Dev unlock tool, it remains S-off. So the only way to flash a kernel or a ROM with an included kernel is using 4EXT with "smart flash" enabled. However this isn't a problem with the HD2. Once you've used HSPL you've already obtained "S-off" which is how we're able to flash different radios and ROMs that have no relation to the mobile carrier the phone was built for.

I don't mean to discredit 4EXT in any way, I like it so much with my Amaze that I paid for it, but I'm not at all familiar with how well it works on the HD2. Out of the popular recoveries for the HD2, Extended-TWRP has the most HD2 features specific for this device, such as recognizing the modified Data-on-EXT or NativeSD installs that don't exist with most other phones. The other logical choice would be the custom CMR for the HD2 or the newer touch version.

Take a look at the recovery threads here or on the HD2 forums @xda and you'll see what I'm talking about.

I hope this helps

Ciao

Hi,
I will have a look to the CMR, as you advice me. I use 4Ext till NativeSD appeared for our HD2, I didn't know another way to install zip roms, backup roms with tytung's tool,...
@tytung, what do you think as the best way to install your roms ?