LCD density - Desire HD General

Trying to change the density but upon restarting its set back to 240. Any ideas? or do we need perma root?

perma root is needed cause the file is on a protected partition

Ahhh right I thought as much thanks for the confirmation.
Sent from my Desire HD using XDA App

Works for me with Visionary, maybe it was updated or something? Try it again.

Related

[Q] How do I know if I am perm root or temp rooted

I stalled visionary from akaskriller.com since it wasnt on the market. I installed rom manger, titanium back up. Uinstalled some bloatware etc... But how do I know if im temp or perm rooted?????
Uncheck "run on boot" option in Visionary, pull your battery, restart the phone and try running su in terminal emulator. If you get permission denied - you're temp rooted.
Ok km going to try it now
Sent from my HTC Glacier using XDA App
Hey, is your root ok? Can you help me root mine.
Sent from my HTC Glacier using XDA App
I guess im still temp rooted I diff what u said and when I booted up it went straight to visionary and rooted it again so I guess I'll start over
Sent from my HTC Glacier using XDA App
The only thing I can do Is get it to temp root so I don't think I would be much help lol sorry
Sent from my HTC Glacier using XDA App
cal3thousand said:
Manual method is soooooo easy I don't understand the desire to use VISIONary+ for permroot. Its not even real permanent root.
S-OFF is NEEDED for custom ROMs... so if you don't want to use custom ROMS, stick with temproot with VISIONary+
If you DO want custom ROMS and true R/W access, do the manual method. I see 0 point in using the one click permroot.
Click to expand...
Click to collapse
Jmayes1786 said:
The only thing I can do Is get it to temp root so I don't think I would be much help lol sorry
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
it does not turn s-off you will have to do that youre self through terminal or adb
http://forum.xda-developers.com/showthread.php?t=834225
So if it reads "s-off" on the boot screen after reboot it's perm root?
deezndc said:
So if it reads "s-off" on the boot screen after reboot it's perm root?
Click to expand...
Click to collapse
Not really, you have have s=off and not be rooted. all s=off means is the security protocol will not check to see if the phone has been tampered with. IF you have s=off and you go to visionary and click "temp toot" then "perm root" your phone will be rooted until you unroot it. Since the security protocol will not remove the SU access.

[q] visionary black screen

i need help, tried to root and visionary is stuck in the black screen (not responding). is there anything i can do to fix this. usb debugging and fast boot are off, and unknown sources is on.
It should go black for a little bit. What version of visionary are you using.
14 was the only one that worked for me.
Sent from my HTC Glacier using XDA App
same version, just had to reboot phone. but now i tried to root 5+ time already and still cant get permroot, stumped
edit: just attempted using this method http://forum.xda-developers.com/showthread.php?t=858021 still nothing
fnasians said:
same version, just had to reboot phone. but now i tried to root 5+ time already and still cant get permroot, stumped
edit: just attempted using this method http://forum.xda-developers.com/showthread.php?t=858021 still nothing
Click to expand...
Click to collapse
Did you try using visionary r11? I didn't bother with r14 just use r11
Sent from my HTC Glaciee using XDA Premium App
tired it still doesnt work, keep on getting s-on. should i do a factory reset and try again?

recover build.prop

Hi,
I got many times the message, in google play, that app xx is not for my device.
After googeling about this issue, I have found that there is the possibility to change this when I change some values in the build.prop.
I have change this values and after a reboot I stick to the yellow triangle boot menu.
I can change to recovery mode and I have CWM 5.5.0.4 there
Is there a possibility to change the values in the build.prop or must I flash over PC Odin to get the device back to normal working?
Many thanks for your help.
BR Al
i dont get what you mean ?
Do you want to edit the build.prop but are wondering how to get the original one back if it fails ?
Or have you already changed it ?
I have already changed it and rebooted.
Now I get stucked.
Oh I see, re flash the ROM that should suffice
Sent from my GT-N7000 using xda app-developers app
is this the only way?
try this
http://forum.xda-developers.com/attachment.php?attachmentid=1099822&d=1338587068
Download it, remove the build.prop, copy the build.prop from your current ROM and place it into the zip.
Then flash it in CWM
well I flashed now the lq2 lp6 lpt stock :crying:, of course there is no root NOW, I will look into the other threads to get root back.
Thanks for your help.
btw. maybe anyone can help me to remove the google play restriction for the apps?
Thanks
alxdadev said:
btw. maybe anyone can help me to remove the google play restriction for the apps?
Thanks
Click to expand...
Click to collapse
What apps are you getting restrictions on? There are various different levels, including tablet and tegra.
Sent from my GT-N7000 using xda premium
sounds like you might have changed the lcd density to a non standard one

Oops! I changed LCD Density and now will not boot up.

Hey Everyone,
So I was being impatient and wanted to change the Density of my LCD on my Nexus 7. I changed it from the stock DPI to 170 using LCD Density Modder on the Market. Ever since reboot I have not been able to get past the google screen when you first turn on device. I can get into bootloader as well. My bootloader is unlocked and device is rooted if that helps.
Is there any easy way to recover the device besides a adb, or fastboot method? If not, what are the adb, fastboot commands to flash the OTA image to device from my PC?
Thanks
Download the nexus root toolkit, it can turn everything stock.
Sent from my LG-P999 using xda app-developers app
I have the nexus root toolkit, but don't you need the device powered on to put in usb debugging mode, etc? All I can do is hit google splash screen and get into bootloader, recovery.
There's buttons that say revert to stock, I believe those work in recovery.
Sent from my LG-P999 using xda app-developers app
redmonke255 said:
Download the nexus root toolkit, it can turn everything stock.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
+1 just unlock and reflash
Sent from my i777 using xda app-developers app
Whenever I try to flash stock + unroot I get error message, "Windows cannot find 'C:\\data\gnexwug_DLnX.exe'. Make sure you typed the name correctly, and then try again."
Im not trying to type in anything, all I am doing is trying to restore to stock.
did you make a nandroid backup?" i am goign through the same thing right now. I am goign to restore from backup.
To change the desinty, it must be manually done in build.prod i assume. LCD Density modder might not be compatible, yet.
edit: Crap, i cant boot to recovery for some reason :/
edit2: it seems the only way to boot into recovery now is from a ROM manager application. Ijust finished restoring using the Nexus Toolkit.
I finally figured how to get SDK going and restored via nexus root toolkit. Thanks guys!
Sent from my Nexus 7 using xda app-developers app
mheller91 said:
I finally figured how to get SDK going and restored via nexus root toolkit. Thanks guys!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi,
I stupidly did the same thing and am now in the same situation. :crying:
Can you tell me how you finally got it sorted?
Cheers
damienleetobin1976 said:
Hi,
I stupidly did the same thing and am now in the same situation. :crying:
Can you tell me how you finally got it sorted?
Cheers
Click to expand...
Click to collapse
Personally,
i booted into fastboot (all buttons if i remember correctly), then hit up the Tool Kit, go to advanced > temporary recovery, From there, i just restored my nandroid backup, or if you have any roms on there, just flash that.
You could do that, or once in fastboot and connected, you could just unlock, which will wipe everything.
tremblingwater said:
Personally,
i booted into fastboot (all buttons if i remember correctly), then hit up the Tool Kit, go to advanced > temporary recovery, From there, i just restored my nandroid backup, or if you have any roms on there, just flash that.
You could do that, or once in fastboot and connected, you could just unlock, which will wipe everything.
Click to expand...
Click to collapse
Hi,
I tried this and went for the Unlock route but after a restart it now just seems to be stuck at the google splash screen.
Is it usual to take this long?
Cheers
So what program is everyone using to change the DPI without getting a black screen?
Sent from my Nexus 7 using xda premium
theusername said:
So what program is everyone using to change the DPI without getting a black screen?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Just using a file explorer (specifically, solid explorer but root explorer should also work), navigating to /system/build.prop, and changing the number ro.sf.lcd_density.
changing that particular number's easy, and the last app I tried somehow managed to make a second build.prop inside the same file. So yeah.
Don't forget to backup your build.prop (preferably externally as well, in case you need to flash it) before trying this. And/or make a nandroid.
damienleetobin1976 said:
Hi,
I tried this and went for the Unlock route but after a restart it now just seems to be stuck at the google splash screen.
Is it usual to take this long?
Cheers
Click to expand...
Click to collapse
Im not sure, i dont want to advise something that is wrong, but, no, it doesn't take extraordinarily long. How long has it been?
I would boot into fastboot again and try the other route (provided you have a rom on the device or hopefully, better yet, a nandroid)
If you're using the cwm recovery from the toolkit you must be plugged in to usb to access cwm from the bootloader menu. From there you can reflash whatever you want to fix it.
jamesbra said:
If you're using the cwm recovery from the toolkit you must be plugged in to usb to access cwm from the bootloader menu. From there you can reflash whatever you want to fix it.
Click to expand...
Click to collapse
Yep, this is how it got it back and running last night.
I then used root explorer to edit build.prop and it worked like a charm.
Thanks all

screen resolution change bricked my nexus 7

so i installed this app to (LCD Density Modder) change resolution to 240 , next thing i know after it restarted is a black screen with only the ability to boot the device , after searching around i found out that the app chages the build.prop file permission to 777 instead of 644 and the resolution is changed to 240 instead of 213 standred , so i used the nexus root toolkit to pull that file chaged the resolution back to 213 but the device is the same cause of the permission thing i don't know how to change , so please any help appreciated , i just want to know if the diagnosis is right and how to change the permission of a file in the bricked device , thanks people i know u will help
my nexus 7 was on 4.2
If it boots can you boot to fast boot and reflash ?
Sent from my Nexus 7 using xda premium
---------- Post added at 10:43 PM ---------- Previous post was at 10:42 PM ----------
When you start ch modding you can mess up a lot of stuff, I would just start over
Sent from my Nexus 7 using xda premium
danie1_ said:
so i installed this app to (LCD Density Modder) change resolution to 240 , next thing i know after it restarted is a black screen with only the ability to boot the device , after searching around i found out that the app chages the build.prop file permission to 777 instead of 644 and the resolution is changed to 240 instead of 213 standred , so i used the nexus root toolkit to pull that file chaged the resolution back to 213 but the device is the same cause of the permission thing i don't know how to change , so please any help appreciated , i just want to know if the diagnosis is right and how to change the permission of a file in the bricked device , thanks people i know u will help
my nexus 7 was on 4.2
Click to expand...
Click to collapse
reflash your rom, itll fix it. dont wipe anything.
change permission
eventually i was going to do this , but i was thinking of a more simple solution to keep my apps and settings
, cause i saw some comments on the app where people said that changing the permission would solve the problem , i just don't know how to change permissions in the brick tab ,
danie1_ said:
eventually i was going to do this , but i was thinking of a more simple solution to keep my apps and settings
, cause i saw some comments on the app where people said that changing the permission would solve the problem , i just don't know how to change permissions in the brick tab ,
Click to expand...
Click to collapse
If you just reflash your ROM without wipe it will keep your apps and settings.
danie1_ said:
eventually i was going to do this , but i was thinking of a more simple solution to keep my apps and settings
, cause i saw some comments on the app where people said that changing the permission would solve the problem , i just don't know how to change permissions in the brick tab ,
Click to expand...
Click to collapse
reflashing your rom wont mess up your settings, you dont have to wipe anything. reflash your rom and boot up, itll be like nothing ever happened. if you made a nandroid backup, you could restore that also.
thansk
thanks dud i will give it a try , thanks for the quick reply (just to make sure, flashing the stock rom is done just by the nexus root toolkit and i just click flash stock +unroot ,right) thanks
If it boots it's not a brick...
Sent from my Nexus 7 using xda app-developers app

Categories

Resources