On the original n7 lowering DPI made the status bar move to the bottom, and made it a tablet mode. How do you do this on this one. What's the DPI you need to set It to. It's 320 out of the box
Sent from my Nexus 7 using Tapatalk 2
imablackhat said:
On the original n7 lowering DPI made the status bar move to the bottom, and made it a tablet mode. How do you do this on this one. What's the DPI you need to set It to. It's 320 out of the box
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Not sure what dpi you need to modify to but you would do this in the build.prop found under /system
you will just want to look for the following line
ro.sf.lcd_density
modify the value as needed then push back to /system and set permissions to 644 or -rw-r--r--
imablackhat said:
On the original n7 lowering DPI made the status bar move to the bottom, and made it a tablet mode. How do you do this on this one. What's the DPI you need to set It to. It's 320 out of the box
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Merely setting your DPI lower will not engage the tablet mode as far as I know. I know Paranoid Android will let you do tablet mode very easily, so go check that out in the original development forums.
oh no.. i changed the dpi value as you said and now my screen just stays black after i rebootet the device.
so if someone is reading this: DON'T CHANGE THIS VALUE IN THE BUILD.PROP!!
Edit:
Well so i made a backup of the build.prop... is there any possibility to push that backup file back into the /system folder without starting android? I tried to do that by booting into the tw recovery but i don't seem to be able to perform that task by using the filemanager..
has anybody an idea how to do this? otherwise i would have to wipe everything and install the factory image and i will lose my data:/
unfortunately i did not make a nandroid backup
Upload your build.prop and I´ll create you a flashable package
Jemus said:
oh no.. i changed the dpi value as you said and now my screen just stays black after i rebootet the device.
so if someone is reading this: DON'T CHANGE THIS VALUE IN THE BUILD.PROP!!
Edit:
Well so i made a backup of the build.prop... is there any possibility to push that backup file back into the /system folder without starting android? I tried to do that by booting into the tw recovery but i don't seem to be able to perform that task by using the filemanager..
has anybody an idea how to do this? otherwise i would have to wipe everything and install the factory image and i will lose my data:/
unfortunately i did not make a nandroid backup
Click to expand...
Click to collapse
Gorgtech said:
Upload your build.prop and I´ll create you a flashable package
Click to expand...
Click to collapse
Thank you for your help but i guess it may be a problem that the backup of my build.prop is only on my nexus and not on my pc or laptop
If the Nexus 7 would have a micro sd card slot it would be manageable but without one.. i don't know.
Would the build.prop file of another nexus 7 20013 user also be okay?
I can give you my generic build.prop ( suitable for a STOCK deodexed or odexed JB 4.3 Firmware ) If you´re not on CM or another similar ROM, it may work out well for you
Jemus said:
Thank you for your help but i guess it may be a problem that the backup of my build.prop is only on my nexus and not on my pc or laptop
If the Nexus 7 would have a micro sd card slot it would be manageable but without one.. i don't know.
Would the build.prop file of another nexus 7 20013 user also be okay?
Click to expand...
Click to collapse
Gorgtech said:
I can give you my generic build.prop ( suitable for a STOCK deodexed or odexed JB 4.3 Firmware ) If you´re not on CM or another similar ROM, it may work out well for you
Click to expand...
Click to collapse
Yeah I'm on stock to! Thank you so much! That should work for me
Flash this one with your recovery
https://www.dropbox.com/sh/s2mubg7zvee3dmb/ckFFHdOF3L
Jemus said:
Yeah I'm on stock to! Thank you so much! That should work for me
Click to expand...
Click to collapse
Gorgtech said:
Flash this one with your recovery
https://www.dropbox.com/sh/s2mubg7zvee3dmb/ckFFHdOF3L
Click to expand...
Click to collapse
Once again thanks a lot!
I'll give it a try right now but i will do it via nexus root toolkit v1.7.2 because i don't know how to get the file you provided me with on my nexus without being able to boot into android
mmhm I flashed the file but it didn't work out for me. after the reboot there was the same black screen as before. but i did really not do annything else but change this ohne line in the build.prop
You can also try to wipe the Dalvik Cache & Cache Partition
Jemus said:
Once again thanks a lot!
I'll give it a try right now but i will do it via nexus root toolkit v1.7.2 because i don't know how to get the file you provided me with on my nexus without being able to boot into android
mmhm I flashed the file but it didn't work out for me. after the reboot there was the same black screen as before. but i did really not do annything else but change this ohne line in the build.prop
Click to expand...
Click to collapse
Gorgtech said:
You can also try to wipe the Dalvik Cache & Cache Partition
Click to expand...
Click to collapse
I'll give it a try! But if it doesn't work afterwards, could you use my own build.prop to create a flashable zip for me? I managed to pull the file from my Nexus via the toolkit
https://www.dropbox.com/s/7e51i7a589d6uvl/build.prop
Here you go https://www.dropbox.com/s/u2x1g4nzv26eo60/build-prop-restore-2.zip
Jemus said:
I'll give it a try! But if it doesn't work afterwards, could you use my own build.prop to create a flashable zip for me? I managed to pull the file from my Nexus via the toolkit
https://www.dropbox.com/s/7e51i7a589d6uvl/build.prop
Click to expand...
Click to collapse
Gorgtech said:
Here you go https://www.dropbox.com/s/u2x1g4nzv26eo60/build-prop-restore-2.zip
Click to expand...
Click to collapse
So now i used the zip you made from my very own build.prop backup and also wiped the cache and davlik as suggested but once again the screen stays black. Do you have any idea what i could do to restore my system or is it the only way out to flash back to stock and wipe everything?
Hopefully you didn´t brick any hardware components, there is a way to restore your system:
https://dl.google.com/dl/android/aosp/razor-jss15q-factory-4f77b811.tgz
You´ll have to first lock your bootloader again and flash this factory image after.
I'm curious as to what happened here.... Changing LCD density shouldn't cause these problems...
So now my device i running as before my try to change the dpi. i flashed back the factory image and it booting up
yeah maybe the change of dpi shouldn't end up so badly but i was sso dumb and had so less knowledge that i set the dpi value from 320 to 32. i just did that because i used this MOD earlier and so i thought, that 32dpi should be okay.
Well now i will first do a nandroid backup and afterwarsd try a different dpi but this time by using an app i think thanks for the help!
I've never gone lower than 160 or higher than 280.
The tablet combined bar was remove in android 4.2. Without a custom ROM there is no way to do this at the moment.
Sent from my Nexus 7 2013 using xda premium
---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------
Gorgtech said:
Hopefully you didn´t brick any hardware components, there is a way to restore your system:
https://dl.google.com/dl/android/aosp/razor-jss15q-factory-4f77b811.tgz
You´ll have to first lock your bootloader again and flash this factory image after.
Click to expand...
Click to collapse
You do not need to lock the bootloader to flash factory images.
Sent from my Nexus 7 2013 using xda premium
Related
Click HERE
Working on trying to get some deodex love going...
Just got Xoom WiFi tonight, let me know what I can do to help out the xoom wifi community.
I am curious. How were you able to extract the stock system dump image for the wifi version? Could you put down instructions since I am trying to learn these things.
Just a quick heads up. Moto was handing out DMCA notices on sysdumps. You may wanna save it for those who make it to #xoom on freenode.
bigrushdog said:
Just a quick heads up. Moto was handing out DMCA notices on sysdumps. You may wanna save it for those who make it to #xoom on freenode.
Click to expand...
Click to collapse
Moto can suck an egg...will post link on my site :-D
Feel free to post the link on irc...
teamdefuse.com
Angdroid said:
Click HERE
Working on trying to get some deodex love going...
Just got Xoom WiFi tonight, let me know what I can do to help out the xoom wifi community.
Click to expand...
Click to collapse
1. one click root and unroot
2. safe way to over clock
3. a way to relock the xoom and bring to factory default
4. overclocikng
5. voodoo color fix
6. voodoo sound fix
lets start with that
thanks
ericdabbs said:
I am curious. How were you able to extract the stock system dump image for the wifi version? Could you put down instructions since I am trying to learn these things.
Click to expand...
Click to collapse
Install latest moto drivers
Install Android SDK
Enable USB Debug in Xoom settings
Open command prompt
Create new directory
CD to new directory
At command prompt type: adb pull /
files will be dumped to current path of command prompt
I Got the one (well, couple a clicks) root and unroot covered. You can check that one off the list. Thread open over yonder if you want to give it a spin... I am just uploading the newest version that one click updates to HRI66.
jwtyler said:
I Got the one (well, couple a clicks) root and unroot covered. You can check that one off the list. Thread open over yonder if you want to give it a spin... I am just uploading the newest version that one click updates to HRI66.
Click to expand...
Click to collapse
good, will be looking for it. NOW, an easy way to overclock to 1.5 would be wonderfull...
ericizzy1 said:
1. one click root and unroot
2. safe way to over clock
3. a way to relock the xoom and bring to factory default
4. overclocikng
5. voodoo color fix
6. voodoo sound fix
lets start with that
thanks
Click to expand...
Click to collapse
1 is being worked on...NVM...Check out jwtyler one click root thread.
2 & 4 Going to try the same method that was used for Droid2 and DroidX. Create module for OC. I have not had time yet to look at kernel but I see someone is already creating kernels so should be able to do it from kernel with multiple settings; not sure if kernel behaves same way as it does in Droid.
3 Not sure if bootstrap (clockwork recovery) is available yet for Xoom WiFi but if it is just make a backup before you mod anything.
Not sure what you are talking about with 5 and 6 ... I am a Xoom noob, only been out of box for a couple of hours
ericizzy1 said:
good, will be looking for it. NOW, an easy way to overclock to 1.5 would be wonderfull...
Click to expand...
Click to collapse
Sweet
Drop me a line if you want to try to bang out some stuff together...
Thanks Angdroid for the system dump. I downloaded a copy of the system dump for kicks. I will keep it on my hard drive in case anyone loses it and needs a backup copy.
Hopefully we can create a stock boot.img soon for us wifi owners in case something goes wrong or need to return it to factory state. It looks like from the system dump we have access to the stock bcm4329.ko wifi driver.
ericdabbs said:
Thanks Angdroid for the system dump. I downloaded a copy of the system dump for kicks. I will keep it on my hard drive in case anyone loses it and needs a backup copy.
Hopefully we can create a stock boot.img soon for us wifi owners in case something goes wrong or need to return it to factory state. It looks like from the system dump we have access to the stock bcm4329.ko wifi driver.
Click to expand...
Click to collapse
Any word on the stock boot.img?
fabian29906 said:
Any word on the stock boot.img?
Click to expand...
Click to collapse
I am not a developer. I just meant a community as a whole come up with the files for the stock boot.img.
Still no word from Motorola of providing the stock boot.img for the wifi Xoom.
Do you think it's possible to extract languages in Wifi firmware to flash 3g xoom?
Or flash with entire wifi firmware?
I don't think the adb pull way is the best way at it.
Creating an actual image using dd will retain symlinks and mod perms (not owners).. but it also won't dump a bunch of tiny >1kb files on your computer (whose cluster size may be over 4kb).. plus you can mount it as a loop device..
adb shell
# busybox dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/mnt/sdcard/system.img
and then if you want
adb pull /mnt/sdcard/system.img
but I wouldn't.. just using the mtp interface is faster..
sausalito said:
Do you think it's possible to extract languages in Wifi firmware to flash 3g xoom?
Or flash with entire wifi firmware?
Click to expand...
Click to collapse
What do you mean? are you talking about the ./system/vendor/firmware/fw_bcm4329.bin
I just compared the two system images for both devices
fw_bcm4329_mfg.bin is the only file with a matching checksum..
I gotta run.. otherwise i'd check the version with a hex editor..
I doubt you're talking about the wifi firmware anyways..
ericizzy1 said:
1. one click root and unroot
2. safe way to over clock
3. a way to relock the xoom and bring to factory default
4. overclocikng
5. voodoo color fix
6. voodoo sound fix
lets start with that
thanks
Click to expand...
Click to collapse
Ya! A color calibration app would be awesome!
Azrael X 4.0
100mbit:
http://gititbit.ch/xRx3 - Xoom_Wifi_3.0.1.zip
That's what I did for this image. http://www.mediafire.com/file/2fknnmy6nw6i19n/StockWiFiSystem.zip
Note, you need to be able to mount a YAFS2 filesystem to read the contents.
Blades said:
I don't think the adb pull way is the best way at it.
Creating an actual image using dd will retain symlinks and mod perms (not owners).. but it also won't dump a bunch of tiny >1kb files on your computer (whose cluster size may be over 4kb).. plus you can mount it as a loop device..
adb shell
# busybox dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/mnt/sdcard/system.img
and then if you want
adb pull /mnt/sdcard/system.img
but I wouldn't.. just using the mtp interface is faster..
Click to expand...
Click to collapse
Sent from my Xoom using Tapatalk
can someone post the 3.1 wifi-model USA system
(i need build.prop)
Not sure if this is of interest to anyone but I managed to get Sky go working by side loading the apk and making one change to the build.prop.
change the following in build.prop
ro.product.model=SGP312
to
ro.product.model=C6603
You will also need to temporarily unroot device while using Sky go (You can remove and restore root without restarting tablet).
I used hide my root to hide the su binary and then uninstalled superuser.
jonathanp said:
Not sure if this is of interest to anyone but I managed to get Sky go working by side loading the apk and making one change to the build.prop.
change the following in build.prop
ro.product.model=SGP312
to
ro.product.model=C6603
You will also need to temporarily unroot device while using Sky go (You can remove and restore root without restarting tablet).
I used hide my root to hide the su binary and then uninstalled superuser.
Click to expand...
Click to collapse
Any chance of uploading an APK for those of us not so good at tweaking buildprops?
No idea how to make an apk I'm afraid but I could upload an update zip if you're running a recovery?
jonathanp said:
No idea how to make an apk I'm afraid but I could upload an update zip if you're running a recovery?
Click to expand...
Click to collapse
Yes please !
GretaLewd said:
Yes please !
Click to expand...
Click to collapse
Here are the update zips, sorry it took so long
Great, now all we need are some usernames and passwords for non sky customers!
Sent from my Nexus 7 using xda app-developers app
Cheers dude! Going to try tomorrow. Only issue is the damned account being locked to 2 devices now. I miss when it was 4 for free!
Wait a sec...what are the 2 zips for?
The sky go zip replaces the build.prop with a sky friendly version, the other zip puts the original build.prop back in place. You'll need a recovery to use the zips.
Btw the build.props the zips are based on are from a SGP312
Sent from my SGP312 using XDA Premium HD app
Thanks!!
Thank you!!!:good:
Grrr I going to cry
Ok guys so i change the font using an app and after reboot the device get stuck at bootanimation.
The problem is that i can't have acces to system partition so i'm afraid my mojo is softbrick....
i try to update the device using fastboot command (c:/sdk/fastboot update c:/mojo.zip) but i got the "waiting for device" even when it is pluged
Do you have any idea of what i can do to revert the android ttf to stock ??
[Edit] Ok i have to thanks again Paul OBrien for his root method because i simply edit is own boot.img by adding in the superboot folder the stock font and addind line to the script to put it in the right folder and set correct permissions. I go into fastboot, flash reboot and it's finaly repair
AH AH AH AH AH AH AH AH AH
[Edit] i think if someone could make a system.img with just the stock font in it or the stock system.img i should probably able to flash it
Dead-neM said:
[Edit] i think if someone could make a system.img with just the stock font in it or the stock system.img i should probably able to flash it
Click to expand...
Click to collapse
Idk. Maybe try rooting it and see if you can get it to boot. It's very easy to root if you haven't done so already.
mherma said:
Idk. Maybe try rooting it and see if you can get it to boot. It's very easy to root if you haven't done so already.
Click to expand...
Click to collapse
it's already rooted. I don't know want you wanna do at boot
Dead-neM said:
Grrr I going to cry
Ok guys so i change the font using an app and after reboot the device get stuck at bootanimation.
The problem is that i can't have acces to system partition so i'm afraid my mojo is softbrick....
i try to update the device using fastboot command (c:/sdk/fastboot update c:/mojo.zip) but i got the "waiting for device" even when it is pluged
Do you have any idea of what i can do to revert the android ttf to stock ??
Click to expand...
Click to collapse
I know reading in one of the other threads in the mojo general forum that someone took theirs apart and there is 3 buttons inside. You might see if you can locate that thread on how to disassemble it and try holding down on a button while plugging it in. There is no known documentation on what they do but if your bricked what could it hurt.
willdj79 said:
I know reading in one of the other threads in the mojo general forum that someone took theirs apart and there is 3 buttons inside. You might see if you can locate that thread on how to disassemble it and try holding down on a button while plugging it in. There is no known documentation on what they do but if your bricked what could it hurt.
Click to expand...
Click to collapse
Yes i see that in forum but i don't want to open it because it's avoid the warranty
i repair the mojo by an other method i'll update the thread soon thanks
Dead-neM said:
Yes i see that in forum but i don't want to open it because it's avoid the warranty
i repair the mojo by an other method i'll update the thread soon thanks
Click to expand...
Click to collapse
I think rooting it voids the warranty?? which is why I don't get how MC can advertise instructions on their website.
You should raise a support request with them on their site.
Hopefully kitkat is around soon.
Good luck!
We've decided to take an open stance on rooting - it's your box to do with as you wish. Of course the obvious caveats apply that you run the risk of causing boot issues, as Dead-neM has found!
Dead-neM in the interests of sharing, could you detail exactly what changes you made to the script and exactly what you did so it's explicitly spelled out for anyone else who runs into the same issue?
Yeah, how do you mount the superboot.img and modify the contents?
Ok this what i have do exactly hope it can be helpfull so:
1/ Have cygwin + Android kitchen tool on your pc ( This software is use to decompile the boot.img and it can be find into xda forum ) So open it decompile the boot.img of Paul Obrien MmM3 ( Kitchen can't decompile boot if it have not system.img too so i decompile first the 110ww official zip rom and replace the boot img by the Paul Obrien's )
2/Go onto the folder of the decompile Boot.img : So open /boot.img-ramdisk/superboot/ there is a superboot.sh script open it
You can see all command. What you have to do is to put yours before the 3 last line ( mount -o ro, remount -t ext4 ........)
I type { cat /superboot/Clockopia.ttf>/system/fonts/Clockopia.ttf
cat /superboot/Roboto-Regular.ttf>/system/fonts/Roboto-Regular.ttf
chmod 777 /system/fonts/clockopia.ttf
chmod 777 /system/fonts/Roboto-Regular }
cat is used to move file and chmod to set permission
3/ Now i said to the boot img to replace file and set permission to it i need to put the file into the boot.img folder so i just copy the Clockopia and Roboto font into superboot folder
4/Now you can recompile the boot img using kitchen then flash it using Paul Obrien script
Enjoy i think you can put gapps with this method so if there is a courageous one here your welcome !!
Dead-neM said:
Grrr I going to cry
Ok guys so i change the font using an app and after reboot the device get stuck at bootanimation.
The problem is that i can't have acces to system partition so i'm afraid my mojo is softbrick....
i try to update the device using fastboot command (c:/sdk/fastboot update c:/mojo.zip) but i got the "waiting for device" even when it is pluged
Do you have any idea of what i can do to revert the android ttf to stock ??
[Edit] Ok i have to thanks again Paul OBrien for his root method because i simply edit is own boot.img by adding in the superboot folder the stock font and addind line to the script to put it in the right folder and set correct permissions. I go into fastboot, flash reboot and it's finaly repair
AH AH AH AH AH AH AH AH AH
Click to expand...
Click to collapse
i have a black screen problem.
can you tell how you solved your problem?
thanks
angus1225 said:
i have a black screen problem.
can you tell how you solved your problem?
thanks
Click to expand...
Click to collapse
Did you get it solved?
Sent from my LGMS395 using Tapatalk
Unjustified Dev said:
Did you get it solved?
Sent from my LGMS395 using Tapatalk
Click to expand...
Click to collapse
After reading a lot...yes!
I managed to conect mojo to a tv and a laptop to the mojo. Then i turn on mojo in flastboot and using the commsnds that a copy from the superboot.bat. i boot the mojo in twrp recovery and from there i flash the mojo rom.
And i recover the mojo just as i left it before the problem
I wish this helps someone.
[emoji106]
This solution works for anyone that doesn't want to root their device.
however required a unlocked boot loader.
you can use TWRP file manager to replace below files. (hence not needing root).
(or someone can kindly create a flashable)
I have recomplied the power.shamu.so (replacing the missing codes from https://android.googlesource.com/device/moto/shamu/+/2084f7d0cf50baf394759d175bc28ad80cf7cace^!/ )
What this does is also re-enable the double-tap to wake.
to use,
backup a copy of
/system/lib/hw/power.shamu.so
then copy the attached power.shamu.so to /system/lib/hw/
change the permission of power.shamu.so to 0644
then boot your device. volia... you now have double tap to wake again.
Note. this has been tested with my own nexus 6.
Thanks. I think this would be better in themes n apps section though.
Thank you Sir! I'm going to remove the app and try this on Elix-R!
EDIT: Works great! Thank you again.
Which permissions are 0644?
smalltownbird said:
Which permissions are 0644?
Click to expand...
Click to collapse
User: R,W
Group: R
Other: R
Thanks that's what I thought I just wanted to make sure
Can I just flash the zip file that's in the beginning of the thread? Also would I need to re-install after wiping and flashing different roms or will it stay?
Figured it out.
No Worky on Slim
mr_clean5953 said:
No Worky on Slim
Click to expand...
Click to collapse
Working fine here. You probably never set permissions
suzook said:
Working fine here. You probably never set permissions
Click to expand...
Click to collapse
I did. And triple checked it
mr_clean5953 said:
I did. And triple checked it
Click to expand...
Click to collapse
Strange working here on beta 8
suzook said:
Strange working here on beta 8
Click to expand...
Click to collapse
I redownloaded and reloaded the file and its working fine now
Awesome
.....working like charm....
Sent from my Nexus 6 using XDA Free mobile app
Working great here!!! Thank you.
Stock ROM...
Sent from my Nexus 6 using Tapatalk
nice, although no root required makes no sense considering you have to copy and paste this to /system that requires root... or am i missing something?
BeansTown106 said:
nice, although no root required makes no sense considering you have to copy and paste this to /system that requires root... or am i missing something?
Click to expand...
Click to collapse
You can do it from recovery which has system access even if the ROM doesnt have root privileges.
What I am wondering though is if you can use fastboot to simply boot recovery without flashing it, and would you be able to do that command without unlocking the bootloader? Or does booting a custom system file require it to be unlocked?
BeansTown106 said:
nice, although no root required makes no sense considering you have to copy and paste this to /system that requires root... or am i missing something?
Click to expand...
Click to collapse
Idea is just like rooting.
You need to some how replace the power.shamu.so once, and thats it.
Some people dont like phones to be rooted, as some software are really particular with root such as 'good for ent' or banking app. Idea is so that these people can still have doible tap to wake.
Hence you require a unlocked boot loader.
Eg, i guess i can also repack the file to a flashable zip, then user can just flash from recovery.
Note, i found that your tap needs to be quite consistant (can't be too fast or slow. There is a specific window)
what about pocket detection? (proximity sensor)
antiochasylum said:
what about pocket detection? (proximity sensor)
Click to expand...
Click to collapse
Don't think there is such feature. One you Mentioned is ambient display which I choose to switch off. As I believe it might detect lots of false pick up.
Awesome! Works great!
Stock rom
Sent from my Nexus 6 using Tapatalk
Hey guys was just wondering if anyone can post a video with a changed DPI? I'm not routes and I heard it can be done without root but wanted to see what it looks like first would really appreciate it
syphern said:
Hey guys was just wondering if anyone can post a video with a changed DPI? I'm not routes and I heard it can be done without root but wanted to see what it looks like first would really appreciate it
Click to expand...
Click to collapse
Not sure where you heard it can be done without root. Because it simply can't. Without root you cannot modify system files.
Sent from my Nexus 6P using Tapatalk
It can be done without root but needs to be done using ADB on a PC.
On your PC while the phone is connected:
ADB shell
WM density 480 (or whatever you want for your device)
Restart your device to complete.
Just try it. U can easily go back to default. But i promise, u dont want :b
I am rooted on my Nexus 6P, although I cannot get it to change the dpi settings.
I tried using texdroider_dpi, tried the adb method and even went to /system/build.prop and changed it via ES File Explorer.
When I set the DPI to anything but 560 my SwiftKey Keyboard breaks but the overall screen density doesn't change.
The value I entered is still displayed in the build.prop though ..
I had it changed already, but when I updated to the latest security patch 2016 I had to reinstall my phone since I flamingod something I guess.
Went ahead with Heisenbergs guide and followed Step 11 (http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928) to get my phone back to work. Only thing not working now is the dpi change ..
Any help?
Are you mounting system as R/W and saving the build.prop after you change the value?
dastinger said:
Are you mounting system as R/W and saving the build.prop after you change the value?
Click to expand...
Click to collapse
I didn't specifially mount the system as R/W - but when I restart the device afterwards the change is still persistent.
Try using another File Explorer (Fx with the root add-on for example) and make the change with that one mounting as R/W before doing anything else.
dastinger said:
Try using another File Explorer (Fx with the root add-on for example) and make the change with that one mounting as R/W before doing anything else.
Click to expand...
Click to collapse
I love you. #nohomo
Thank you very much.
[emoji4]
No problem, mate.
clubtech said:
It can be done without root but needs to be done using ADB on a PC.
On your PC while the phone is connected:
ADB shell
WM density 480 (or whatever you want for your device)
Restart your device to complete.
Click to expand...
Click to collapse
I do this but my Swiftkey is broken and some image elements are huge.
Does anyone know why something like texdroider used to work perfectly scaling everything and now it does not?
Before this update, after flashing the SuperSU 2.66 my twrp would give me the warning my phone was not rooted. Now, I do not receive this warning.
Sent from my Nexus 6P using Tapatalk