DPI Changer has broken my Nexus 7, after boot I just see the Google logo and then a black screen.
Using recovery I was able to take the backup DPI Changer created (\sdcard\build.prop.bak) and overwrite \system\build.prop, but that has done no good. Can someone share a unedited and working build.prop or any suggestion on how to correct. Thanks!
jleecong said:
DPI Changer has broken my Nexus 7, after boot I just see the Google logo and then a black screen.
Using recovery I was able to take the backup DPI Changer created (\sdcard\build.prop.bak) and overwrite \system\build.prop, but that has done no good. Can someone share a unedited and working build.prop or any suggestion on how to correct. Thanks!
Click to expand...
Click to collapse
i have the same problem...this is so stupid can someone help, why would replacing the build.prop break the device.....
Certain dpis won't work.
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
Certain dpis won't work.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
yes but i used recovery to restore the original build.prop and still brick
this is crazy, it was always easy to change and play around the build.prop why the brick?
is there a fix without reflashing image?
same problem here.......anyone?
Okay I did this once and I have found only one solution that no one will like... you have to reinstall the ROM. Dun Dun Dunnnn.....
Lol but seriously that's how I fixed it. But I did it through fastboot because I like the thoroughness of it
Sent from my Nexus 7 using Tapatalk 2
I'm not sure bow you restored you buildprop but I just messed up mine on my china tablet. I could still use adb tho so this is what I did.... I put my build.prop file in android-sdk/platform-tools and then in adb I typped
adb remount
adb push build.prop /system
adb reboot
Sent from my Galaxy Nexus using Tapatalk 2
Related
i tried to instal a modified build.prop using root explorer but if i start me phone it just flashes black white black white....
Tried to connec the phone to odin and it doenst work
pleaseeeeeeeeeeee heeeeeelp ;(
Logcat please
Sent from my HTC Desire Z using XDA App
did you try booting in recovery?
RafayelG said:
did you try booting in recovery?
Click to expand...
Click to collapse
yep i get a messange that says: forced upload by key pressing
then it freeze
mintaeroboy said:
Logcat please
Sent from my HTC Desire Z using XDA App
Click to expand...
Click to collapse
how i do a logcat i can start me phone...
clarkkov said:
Your phone is fine, you just effed up your os. Boot to download mode and flash a clean firmware.
Sent from cramped soft keyboard!
Click to expand...
Click to collapse
Download yes -> connecting the phone nothing happens i flashed roms before so i know how to flash them
help plz
Edite: Hmm i started clicking crazy in download mode and my phone found it is now downloading the rom i hope it works....
Edite2: phone is now on boot logo i hope it works...
Edite3: Yihaaaaaaa he works again
Do i need to do a factory reset now?
Lol! They totally owned you. Correct solution is to pull the build.prop using adb when your phone is flashing black and white, remove the edits you made to it, then push it back. Reboot and its fine. And yes, you can use adb when its flashing black and white
Sent from my GT-I5800 using XDA Premium App
tanyh said:
Lol! They totally owned you. Correct solution is to pull the build.prop using adb when your phone is flashing black and white, remove the edits you made to it, then push it back. Reboot and its fine. And yes, you can use adb when its flashing black and white
Click to expand...
Click to collapse
Well that s a clever solution.
tanyh said:
Lol! They totally owned you. Correct solution is to pull the build.prop using adb when your phone is flashing black and white, remove the edits you made to it, then push it back. Reboot and its fine. And yes, you can use adb when its flashing black and white
Sent from my GT-I5800 using XDA Premium App
Click to expand...
Click to collapse
dude you are to slow
But with reflashing me phone it is faster
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
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
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
I have done some searching to see if anyone has done this already and not found anything. Has anyone ported the stock Nexus 4 boot animation to Nexus 5 resolution? I preferred that Nexus boot animation to the one that came with the N5, and would love to have it scaled up to fit the resolution of this phone.
I'll port it tomorrow when I have time (I have finals to study for).
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thanks a lot! That would be awesome.
thor6577 said:
I'll port it tomorrow when I have time (I have finals to study for).
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Here, this should work. (Removed since it didn't work) Happy theming!
Thanks bud, unfortunately it didn't work. I replaced my stock one with this in Root Explorer, and it stayed on the boot up "Google" image all the way until loading the lock screen. It never played the boot animation.
thor6577 said:
Here, this should work. http://d-h.st/nNa Happy theming!
Click to expand...
Click to collapse
tebower said:
Thanks bud, unfortunately it didn't work. I replaced my stock one with this in Root Explorer, and it stayed on the boot up "Google" image all the way until loading the lock screen. It never played the boot animation.
Click to expand...
Click to collapse
Sorry for that. I'll fix it when I get home.
Sorry for the bug. I redid it so check if it works now : http://d-h.st/L0n Remember to put it in the system/media without renaming it. Backup your old bootanimation in case. Happy theming.
thor6577 said:
Sorry for the bug. I redid it so check if it works now : http://d-h.st/L0n Remember to put it in the system/media without renaming it. Backup your old bootanimation in case. Happy theming.
Click to expand...
Click to collapse
would love to try this.. do u just flash in recovery?? how would i go about backing up my current.. just make a back up in twrp>?
Using root explorer or other root file app, you rename the old bootanimation.zip to bootanimation.bak
The you copy and paste the new file you downloaded into the system/media folder
QUOTE=P.Mobile;48651546]would love to try this.. do u just flash in recovery?? how would i go about backing up my current.. just make a back up in twrp>?[/QUOTE]
Sorry to make another note on this, the image is super stretched out, so something may have gone wrong with the resolution.
thor6577 said:
Sorry for the bug. I redid it so check if it works now : http://d-h.st/L0n Remember to put it in the system/media without renaming it. Backup your old bootanimation in case. Happy theming.
Click to expand...
Click to collapse
tebower said:
Sorry to make another note on this, the image is super stretched out, so something may have gone wrong with the resolution.
Click to expand...
Click to collapse
They say 3rd times the charm! http://d-h.st/IEJ I tested it myself this time and made sure it worked. Happy theming!