For everyone bricking their Nexus 7 by changing the build.prop file like I did. download ROM Toolbox Lite to change the dpi settings safely. Ive changed mine several times through the app with no bricking.
loonie01 said:
For everyone bricking their Nexus 7 by changing the build.prop file like I did. download ROM Toolbox Lite to change the dpi settings safely. Ive changed mine several times through the app with no bricking.
Click to expand...
Click to collapse
Thanks, but you only need to say "warning" once. :silly:
Hmmm bricking from changing DPI, I don't think people understand that word anymore.
Sent from my Galaxy Nexus using Tapatalk 2
miketoasty said:
Hmmm bricking from changing DPI, I don't think people understand that word anymore.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
If they can't get on the internet with it, it is bricked. Yes, that is what it has come to.
Use to mean:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do we really need to explain how a bricked device literally mean its a physical brick and is no longer useable. People need to read the terminology forum they have up on this website.
Sent from my Galaxy Nexus using xda premium
I think I will avoid the dpi changing all together
i'd rather flash a rom with tablet UI baked in. too many bricking their device.
OP made a good suggestion though. I used rom tool previously to modify my Prime build.prop. it seems to be the only app that does it right & safely. plus it makes a backup of your original build.prop. people should be making backups anyway in case something happens and you need to push back the original file.
To be honest, the probably messed it up or something... I've been using build.prop method for the last 48 hours and no issues yet so, not sure if I should really be worried..even if i can't get on the internet I'll just flash back the 4.1 img.
If you get boot loops after changing something in the build.prop, well you messed it up by adding lines that shouldn't be there.
I do things manually because there is no point in downloading some apk to change 3 digits in a .prop file.
My Nexus is on the way. What setting is default and what are yall using? My Incs default is 240 but I run it at 200. I like the higher resolution look. Thanks.
Default = 213
Mine = 160
You should of made the title " Warning, Warning Mr Robinson caution changing the DPI " . Sorry I couldn't resist. Name that movie.
Sent from my Nexus 7 using Tapatalk 2
scooter217 said:
You should of made the title " Warning, Warning Mr Robinson caution changing the DPI " . Sorry I couldn't resist. Name that movie.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Lost in space
I believe he says "warning Will Robinson"
Sent from my Sensation using xda app-developers app
It was "Danger Will Robinson"
Related
USB MOUNT FIXED
I started from scratch, new Install of CM7 RC1.4, Started from scratch with the systemui.apk
Will Be adding an undo zip later. For now do a nandroid backup!
Im reopening this mod under one condition. NO SMART ASS REMARKS!
USB IS FIXED.
TO DO LIST
1)Modify the expanded status bar
2Add carrier label like MIUI.(this is going to be hard)!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Works for CM7 RC1.2,RC 1.3, RC 1.4, Do not blame me if anything goes wrong.
DOWNLOAD HERE
May be beneficial to post the patch for whatever ROM you're running with a disclaimer like "will only work on <insert ROM name here>"
WormDoes said:
May be beneficial to post the patch for whatever ROM you're running with a disclaimer like "will only work on <insert ROM name here>"
Click to expand...
Click to collapse
he stated the rom in the title
yareally said:
he stated the rom in the title
Click to expand...
Click to collapse
Yea, he edited it after my post.
WormDoes said:
Yea, he edited it after my post.
Click to expand...
Click to collapse
oh okay, i thought it was before. mea culpa
BuMp FoR UpDaTe!
jmotyka said:
BuMp FoR UpDaTe!
Click to expand...
Click to collapse
What are the bugs that are still present?
yah this looks very nice..but what are the bugs so I know what to expect lol
Also, what theme are you running as well as icons?
when you get a notification the wording is off to the right, and left status icons overlap just a bit.
the one you sent me does it have the transparent patch? if not how could i achieve this lol.
Is there an un do file-___-
I for got to back up
ill be making an undo patch in am sorry.
jmotyka said:
ill be making an undo patch in am sorry.
Click to expand...
Click to collapse
To undo all u need to do I grab SystemUI.apk from the CM7 rom zip of whatever version you are using, then throw it in a flashable update zip and ur good
Patch does not work for OMFGB for anyone wondering.
Hey man I don't blame you for nothing I really like this but I have my screen density to 190 so when I get a text its everywhere.ITS ALL MY FAULT FOR FORGETING TO BACKING UP.
U should put a reminder on the main post, cos I forget things lol
Anyone else getting stupid slow 4g speeds after this?
Could be me but I'm getting like .12 on speedtest and extremely slow on loading pages.
Edit: never mind back to normal guess Verizon is doing something lol
Sent from my ThunderBolt using XDA App
This is my first contribution to the community so I'm learning what needs to be in the thread and what doesn't. Also this does NOT touch the ril so if u have data issues, consult the cm7 thread.
Bump For update!
Okay when I try to mint the system I get a force close in the status bar. Never happened since I did ur mod.
MONKY_1 said:
Okay when I try to mint the system I get a force close in the status bar. Never happened since I did ur mod.
Click to expand...
Click to collapse
Im aware of the fc while mounting usb. You can either use the mod and use a mount usb widget or not use the mod and wait for me to fix this issue. Im boggled atm cause i didnt even touch the usb mounting part?????
Hello guys,
This phone is giving me headaches. Once I rooted the phone is not allowing me to to flash CWM and nothing at all but continue stock. Im looking like a paranoid for the Pit file and the flash rom for me to go stock 100% but there is nothing in the forum to well organized I guess that I have missed looking for it or getting lucky to find it.
Im on 2.3.3 right now and the more I do factory reset the more the superuser stays installed. Pleas advise how to successfully flash my phone from scratch for me to install one of the custom ported roms we have in the forum.
I came from Samsung Vibrant with an experience of more then 1000 flashes. I think the bad thing about this phone is that we have to navigate over 7 different forums to get the info correctly and is very confusing.
Guys I also dont have Network Signal meaning I cant use the phone.
Thanks guys very much for any help
SVLAN said:
Hello guys,
This phone is giving me headaches. Once I rooted the phone is not allowing me to to flash CWM and nothing at all but continue stock. Im looking like a paranoid for the Pit file and the flash rom for me to go stock 100% but there is nothing in the forum to well organized I guess that I have missed looking for it or getting lucky to find it.
Im on 2.3.3 right now and the more I do factory reset the more the superuser stays installed. Pleas advise how to successfully flash my phone from scratch for me to install one of the custom ported roms we have in the forum.
I came from Samsung Vibrant with an experience of more then 1000 flashes. I think the bad thing about this phone is that we have to navigate over 7 different forums to get the info correctly and is very confusing.
Guys I also dont have Network Signal meaning I cant use the phone.
Thanks guys very much for any help
Click to expand...
Click to collapse
I think you are in the wrong forum this is for the galaxy exhibit 4g aka the exhibit 2. I say this because I think the stock ROM that the exhibit 2 came with was 2.3.5
Sent from my Nexus 7 using xda app-developers app
well the Firmware version of this phone is 2.3.3
with a kernel version 2.6.35.7-T759UVKE8-CL205219
BUILD NUMBER is GINGERBREAD.UVKE8
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The phone I have is that one above
thanks
SVLAN said:
The phone I have is that one above
thanks
Click to expand...
Click to collapse
Sorry man, wrong phone, try googling xda stock t759. Yours is t759 ours is t679. Best of luck
Sent from my Nexus 7 using xda app-developers app
OMG this phone is getting me so frustrate it very soon it will meet my wall.
Do we have a forum for this phone here at XDA?
thanks
SVLAN said:
OMG this phone is getting me so frustrate it very soon it will meet my wall.
Do we have a forum for this phone here at XDA?
thanks
Click to expand...
Click to collapse
No forums, but there are threads. Just Google xda t759 stock and read around. I know that a stock Odin flash able package is available, but I don't remember where. Also post in their forums because although our phones are very similar I don't know the exact steps/files for your phone.
Sent from my Nexus 7 using xda app-developers app
Sorry wrong no forms at all t759 they all were removed!
Sent from my SGH-T759 using xda premium
I have the HTC M8 from sprint. I just finished rooting it and when I went to flash the new nightly (20140527) using TRWP, it showed this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did I do something wrong? If there's some way to add "m8_whl" to the list of devices, please let me know.
pikuseru said:
I have the HTC M8 from sprint. I just finished rooting it and when I went to flash the new nightly (20140527) using TRWP, it showed this:
Did I do something wrong? If there's some way to add "m8_whl" to the list of devices, please let me know.
Click to expand...
Click to collapse
Usually I would get that message in the case of a bad download.
Sent from my One M8 using Tapatalk
I tried redownloading it multiple times to no avail. It just refuses to install because ...
This package is for "m8,m8wl,m8wlv,m8vzw,m8whl,m8spr" devices; this is a "m8_whl"
Click to expand...
Click to collapse
... which makes no sense because I got my m8 from Sprint. Doesn't this mean that the device should be an "m8spr"?
Try using @Captain_Throwback recovery
Sent from my 831C using XDA Premium 4 mobile app
pikuseru said:
I tried redownloading it multiple times to no avail. It just refuses to install because ...
... which makes no sense because I got my m8 from Sprint. Doesn't this mean that the device should be an "m8spr"?
Click to expand...
Click to collapse
Just open the updater-script in the zip file and add m8_whl to the assert line at the top.
Captain_Throwback said:
Just open the updater-script in the zip file and add m8_whl to the assert line at the top.
Click to expand...
Click to collapse
It works!
Will I have to add this line every time there's a new update, or can it be added to the official nightlies?
Edit: I may have spoken too soon. My device was rebooting relentlessly. It would show the "Welcome to CM" screen, then google things would crash, rinse, repeat all in about 10 seconds. Then it went to just showing the boot animation. I managed to turn it off using pwr&vol+, but it somehow encrypted itself. Spooky.
Edit 2 (The return of edit): I forgot to wipe /data. No more crashing now, though my question about the updater-script above still stands.
pikuseru said:
It works!
Will I have to add this line every time there's a new update, or can it be added to the official nightlies?
Edit: I may have spoken too soon. My device was rebooting relentlessly. It would show the "Welcome to CM" screen, then google things would crash, rinse, repeat all in about 10 seconds. Then it went to just showing the boot animation. I managed to turn it off using pwr&vol+, but it somehow encrypted itself. Spooky.
Edit 2 (The return of edit): I forgot to wipe /data. No more crashing now, though my question about the updater-script above still stands.
Click to expand...
Click to collapse
If its not in there, yes. If its in there, no.
Sent from my Sprint M8 Running the latest Viper
EVOuser94 said:
Try using @Captain_Throwback recovery
Sent from my 831C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is the best thing to do OP. Always trust the Cap'n and his code^^ =)
At least, fixed a similar issue I had while using something other than Captain_Throwback's TWRP for the M8....
Hello all
I am using the latest insert coin rom(tried all others too) with the latest elemental x kernel(tried different kernels too) the battery life is always bad. The screenshot shows the regular scenario. If I use screen a lot I get 8-10% per hour. I am using the cpu at 1.5ghz downclocked. Everything is hibernated and appops is preventing anything to keep the phone awake. The last option for me is to format the SD, I can't think of anything else. Or my battery is bad.
Any suggestions appreciated.
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC One using Tapatalk
genseric said:
Hello all
I am using the latest insert coin rom(tried all others too) with the latest elemental x kernel(tried different kernels too) the battery life is always bad. The screenshot shows the regular scenario. If I use screen a lot I get 8-10% per hour. I am using the cpu at 1.5ghz downclocked. Everything is hibernated and appops is preventing anything to keep the phone awake. The last option for me is to format the SD, I can't think of anything else. Or my battery is bad.
Any suggestions appreciated.
Thanks.
View attachment 2797442
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I would RUU back to Stock and see if it helps
other wise you have a hardware problem
clsA said:
I would RUU back to Stock and see if it helps
other wise you have a hardware problem
Click to expand...
Click to collapse
Thanks. I read around about the ruu stuff but what exactly am I supposed to do, I'm not sure. Is it stripping down a rom and install it? Also do you think formatting the internal SD can do any good?
Sent from my HTC One using Tapatalk
Oh my bad. It seems it's a solid ripped rom image. I ll find one and try it. Thanks again.
Sent from my HTC One using Tapatalk
genseric said:
Oh my bad. It seems it's a solid ripped rom image. I ll find one and try it. Thanks again.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
the RUU must match your phone
fastboot getvar all will give you the information you need to find the correct RUU
http://www.androidruu.com/index.php?developer=M7
You have to use RUU not OTA
clsA said:
the RUU must match your phone
fastboot getvar all will give you the information you need to find the correct RUU
http://www.androidruu.com/index.php?developer=M7
You have to use RUU not OTA
Click to expand...
Click to collapse
I did not fool around with s switch the first time I rooted my device. Do I have to toggle it now? Thanks again
Sent from my HTC One using Tapatalk
anyone have any luck doing this?
Tried editing build.prop directly as well as using programs but it never works and reverts back to 240 on restart
I am unlocked, twrp recovery and rooted. (Virgin Mobile)
*EDIT SOLUTION
So this is what I did
Used this kernel - http://forum.xda-developers.com/des...print-virgin-mobile-stock-desire-510-t2958969
But rather than the steps 'fastboot flash boot b.img' I only did fastboot boot b.img'
This temporarily loaded the kernel so that I could have the system editing powers
Deleted the bloat I didn't want among other built in apps I planned on installing anyways so that they were a fresh install rather than upgrade (cleans up a tad bit of space)
Then I used https://play.google.com/store/apps/details?id=com.theSushi.dpichanger&hl=en to change the DPI to 200
After all was said and done, I simply restarted the phone (which you have to do to set DPI anyways) and phone was back on stock kernel since I never flashed it, DPI stayed at 200, and bloatware stayed removed!
Kolma said:
anyone have any luck doing this?
Tried editing build.prop directly as well as using programs but it never works and reverts back to 240 on restart
I am unlocked, twrp recovery and rooted. (Virgin Mobile)
Click to expand...
Click to collapse
I used the DPI Changer app from Google Play Store. It allows you to change your DPI, backup your current DPI on your build.prop, as well as restore it if necessary.
acesavant00 said:
I used the DPI Changer app from Google Play Store. It allows you to change your DPI, backup your current DPI on your build.prop, as well as restore it if necessary.
Click to expand...
Click to collapse
this one? https://play.google.com/store/apps/details?id=com.theSushi.dpichanger&hl=en
Did it work on this phone?
Kolma said:
this one? https://play.google.com/store/apps/details?id=com.theSushi.dpichanger&hl=en
Did it work on this phone?
Click to expand...
Click to collapse
Yeah, that's the app.
acesavant00 said:
Yeah, that's the app.
Click to expand...
Click to collapse
Didn't work
Does this require this custom kernel?
http://forum.xda-developers.com/des...print-virgin-mobile-stock-desire-510-t2958969
Kolma said:
Didn't work
Does this require this custom kernel?
http://forum.xda-developers.com/des...print-virgin-mobile-stock-desire-510-t2958969
Click to expand...
Click to collapse
Yeah, the kernel that removes write protection. You cannot do much of any modifying, even while the phone is rooted, until you either flash that kernel or get S-OFF
SUCCESS!
No more super huge everything. I set the DPI to 200
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*edit
all the sense exclusive live wallpapers are broken now btw
*edit 2
Dialer seems fine, as does the settings menu.
I don't use Blinkfeed nor Sense launcher so don't know if those are broken/don't care
Kolma said:
SUCCESS!
No more super huge everything. I set the DPI to 200
*edit
all the sense exclusive live wallpapers are broken now btw
*edit 2
Dialer seems fine, as does the settings menu.
I don't use Blinkfeed nor Sense launcher so don't know if those are broken/don't care
Click to expand...
Click to collapse
Great! I know the text feels a lot less "in your face" now. I set it to about 213 DPI
Solution added to op
Didn't want to bump an old thread but I think I have to after Googling around and not finding my answer. Can this kernel be used on the Canadian Variant Telus? If not then how would I go about acquiring S-Off for the Desire 510? I have it rooted.
I used app set resolution to 720bye 1280 and 320 dpi.works great.