Restore original resolution & DPI via sideload .zip OR openrecoveryscript ? - Galaxy Note 4 Q&A, Help & Troubleshooting

Managed to soft brick my Note 4. Set my dpi to 200, and my resolution to 720p. Apparently, it's just too low. Worked great when I set the values, but restarting the phone caused the brick. (It boots, but can't access anything. Unfortunately, I don't have my PC allowed as ADB, so I can't even connect from that state to ADB.)
So.
My idea to prevent full wipe, is to use ADB sideload OR ORS.
- Sideload. Make a "payload" that will replace the build.prop with the stock one.
- ORS. http://wiki.rootzwiki.com/OpenRecoveryScript
How do I actually do this?
Like the RecoveryScript seems to be a great idea, but from TWRP, I could not find a single build.prop file at all. There is a default prop, but it contains no resolution, dpi or whatever.

So I spent another few hours on this. I hate myself. And I hate the app's developer for being so careless.
- Flashed latest Samsung firmware hoping it will kill the software. Nope. It did not.
- Flashed the .zip for build.prop. NO effect.
The system has the correct DPI value so it must not be the issue.
- I think the app auto runs, and sets resolution. So I tried grep, but it cannot find the "1280" string anywher,e and I also removed the app from /data/app and /data/data.
- I cannot get MTP or ADB working in TWRP whatsoever. Huge letdown, but there is just no support. And without seeing what happens on the screen (it must be just my lockscreen there), I can't accept ADB connections either.

Well, so I went YOLO and cleared data. And... behold, NOTHING.
Did this retarded stupid program killed my phone? Holy hell.

Okay, so full entire wipe + reflash + full wipe, and now it works.
This app? Never again. The others are good on the market, so go for it.
App in question: https://play.google.com/store/apps/details?id=com.chornerman.easydpichanger
[ DO NOT USE !!! ]

Instead of wipes at Restore DPI: You can remove only of "com.android.providers.settings" at "/data".

Sorry but I have to resurrect this. I've played with dpi settings and now after reboot I cannot press enter when I type in my password as keyboard is partly off screen. TWRP is not working as it does not support Android 12. Any chance to resolve this beside flash?
Update: Connected keyboard via OTG cable and managed to unlock

Resurrecting this to offer another solution that doesn't involve any wiping/flashing/restoring-to-stock or messing with build.props
I used the same app as OP and feared the worst when I got stuck on recovery after changing DPI
This method allowed me to restore my xiaomi Redmi 9 with android 10
-You need to have a custom recovery installed
-"shell wm" commands don't work in recovery
You need to edit settings_global.xml & settings_secure.xml found in /data/system/users/0
You can do this by pulling&pushing the files to a PC using adb or editing in recovery using nano editor or something similiar.
Search for:
"display_size_forced" in settings_global.xml
"display_density_forced" in settings_secure.xml
Edit those with something close to your default values, then reboot and that's it!
Now that you're no longer stuck in boot you can reset resolution and density with the usual methods like adb or a better app
I hope this helps anyone else stuck in the same problem I was

mrmrva said:
...TWRP is not working as it does not support Android 12. ......
Click to expand...
Click to collapse
Where did you get a A12 version for which Note4?
Owning a N910F=trlte I don't find any higher than A11.

Don't have Samsung but Poco f2 pro and was looking for solution everywhere so posted here.

Related

[Q] Nexus 4 not bootin afer modifying build.prop :(

Hey guys,
I hope you can gibe me a hint how to get my Nexus 4 alive again.
Short intro:
- Phone fell of the desk => display broken
- Sent it to a repair company and received it working again, except the proximity sensor
=> this seems to be a common issue after screen replacements as I found out
- Unfortunately I left my brain at home today and I tried to disable the proximity sensor manually (read in this thread: http://forum.xda-developers.com/showthread.php?t=1626611). Didn't see this was for a Desire S ...
- After adding the line "gsm.proximity.enable=false" to the /system/build.prop file the phone won't boot anymore .... the CM11 boot animation isn't appearing
So, the phone is rooted. I am running CM11 M8 and CWM 6.0.2 (no touch).
So the plan was to alter the file via adb again, but I'm not able to access the phone in any ways.
The Nexus 4 Toolkit however recognizes the phone (with serial Number) and if the phone is in fastboot or ADB Mode. But when ein try to pull files from the device the toolkit says, that I don't have a unsecure boot image ... the adb functions doesn't seem to work either ...
But maybe I'm just not clever enough ...
Have you guys an idea how to get my phone back to life again? I assume wipen the phone will not fix the problem, since there seems to be an important system file corrupted (despite loosing all my data :crying
Hoping for helping words. Thanks in advance.
Gerd
1828
Don't use Nexus Toolkit ... use the native Google Android SDK and everything works fine ....
AntiFanBoy said:
Hey guys,
I hope you can gibe me a hint how to get my Nexus 4 alive again.
Short intro:
- Phone fell of the desk => display broken
- Sent it to a repair company and received it working again, except the proximity sensor
=> this seems to be a common issue after screen replacements as I found out
- Unfortunately I left my brain at home today and I tried to disable the proximity sensor manually (read in this thread: http://forum.xda-developers.com/showthread.php?t=1626611). Didn't see this was for a Desire S ...
- After adding the line "gsm.proximity.enable=false" to the /system/build.prop file the phone won't boot anymore .... the CM11 boot animation isn't appearing
So, the phone is rooted. I am running CM11 M8 and CWM 6.0.2 (no touch).
So the plan was to alter the file via adb again, but I'm not able to access the phone in any ways.
The Nexus 4 Toolkit however recognizes the phone (with serial Number) and if the phone is in fastboot or ADB Mode. But when ein try to pull files from the device the toolkit says, that I don't have a unsecure boot image ... the adb functions doesn't seem to work either ...
But maybe I'm just not clever enough ...
Have you guys an idea how to get my phone back to life again? I assume wipen the phone will not fix the problem, since there seems to be an important system file corrupted (despite loosing all my data :crying
Hoping for helping words. Thanks in advance.
Gerd
Click to expand...
Click to collapse
I don't suppose you made a nandroid and can just restore that.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I don't suppose you made a nandroid and can just restore that.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
due to the lack of free space, I haven't. But as you can read above, the problem was solved.
AntiFanBoy said:
Hi,
due to the lack of free space, I haven't. But as you can read above, the problem was solved.
Click to expand...
Click to collapse
whenever that happens again, just re set the file permission, when you change a file, sometimes it can change it´s permission.
if didnt get to bootanimation after modifying build.prop, the permissions of it are wrong, just set them back to 644 or rw-r-r
Hi,
thanks for you comment. :good:
actually I changed the rights by myself to 666, so I can modify it, but didn't change the permissions back.
So you thinks the permission was the problem and not the content of the file?
I added this line:
gsm.proximity.enable=false
AntiFanBoy said:
Hi,
thanks for you comment. :good:
actually I changed the rights by myself to 666, so I can modify it, but didn't change the permissions back.
So you thinks the permission was the problem and not the content of the file?
I added this line:
gsm.proximity.enable=false
Click to expand...
Click to collapse
Yes, this is a common problem as far as I know
If you use TWRP as your recovery (not sure if it's possible with cwm, too) you can use the built-in file explorer to navigate to the build.prop and set the permissions. Just reboot and it should work fine again
If you can enter recovery do a factory reset
Mashed_Potatoes said:
If you can enter recovery do a factory reset
Click to expand...
Click to collapse
Well, I'd say this would be the last option as he'd lose all his data. Maybe there's another way to fix the problem
no need for factory reset, in case like this refleshing the rom will do the job. there is no need for wipe or anything just flesh the same rom again and everythink will be ok
Hey guys,
looks like I didn't express myself clearly enough
Don't use Nexus Toolkit ... use the native Google Android SDK and everything works fine ....
Click to expand...
Click to collapse
Besides the problemative build.prop file, the nexus 4 toolkit was the problem. After using the standard Android SDK I was able to push a CM Image onto the phone via adb and simply updated the os and everything was fine again. Don't know why the toolkit spun around, always worked fine, but this now thought me a lesson => back to the roots
Resetting the phone to factory defaults/wiping everything wouldn't have solved the problem I assume.
Thanks guys.
Please read:http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909

[Q] Messed up my phone

Hello!
I have messed up my Note 3 a lot. When booting it up, it gives me error "Unfortunately, com.sec.android.sviewcover has stopped." This comes up instantly again after pressing the "OK" button (I have 0.5 seconds to do something between these errors). After entering the PIN code and unlocking the lock screen I get the error "Unfortunately, TouchWiz Home has stopped (and just shows a black background)." I can still access the settings by pulling down the Action Bar.
I'll start with some background facts:
- Rooted my phone about 3 months ago. It has worked great this far.
- Today I managed to enter a too high value in the "Textdroider DPI" app, and after restarting the problems began.
Now I've factory reset the phone as that was the only thing I could do but that didn't change anything.
I'm so screwed. Can anyone help me?
EDIT: It's a Note 3 SM-N9005 N9005XXUGNG1
I had the same thing happen on my Note 10.1 the other day while messing around with DPI settings. Touchwiz doesn't play nicely with different screen densities and it crashes. There is a file in the /system folder called build.prop. Inside this file there will be a line that looks like this:
Code:
ro.sf.lcd_density=###
.
On a completely stock N9005 (I have the exact same model) this value should be 480. All you need to do is edit this line and reboot.
teh_geek said:
I had the same thing happen on my Note 10.1 the other day while messing around with DPI settings. Touchwiz doesn't play nicely with different screen densities and it crashes. There is a file in the /system folder called build.prop. Inside this file there will be a line that looks like this:
Code:
ro.sf.lcd_density=###
.
On a completely stock N9005 (I have the exact same model) this value should be 480. All you need to do is edit this line and reboot.
Click to expand...
Click to collapse
Firstly, thanks for your reply!
Is there any way I can access the /system folder from my computer?
Skrube said:
Firstly, thanks for your reply!
Is there any way I can access the /system folder from my computer?
Click to expand...
Click to collapse
Yes there is. It's a bit technical however and it depends on what recovery you're running. I've managed to solve this problem on my tablet running TWRP.
I also found something else you can try to do to hopefully get rid of the force close messages temporarily. Boot up your phone, connect it to your PC and (assuming USB debugging is enabled) run the following command from a terminal:
Code:
adb shell wm density 480
You mentioned in your previous post that you have rooted your phone, so I'm going to assume you're somehow familiar with commands and ADB
If all goes well, your screen density should change on the fly. Reboot your phone at this stage and if this gets rid of the force close messages and allows you to interact with your device, it should be quite easy to edit the build.prop file. Just go to the Play Store, install a root file manager (or better yet the application you used in the first place - Textdroider DPI) and edit the file. Make sure you set the density to 480.
teh_geek said:
Yes there is. It's a bit technical however and it depends on what recovery you're running. I've managed to solve this problem on my tablet running TWRP.
I also found something else you can try to do to hopefully get rid of the force close messages temporarily. Boot up your phone, connect it to your PC and (assuming USB debugging is enabled) run the following command from a terminal:
Code:
adb shell wm density 480
You mentioned in your previous post that you have rooted your phone, so I'm going to assume you're somehow familiar with commands and ADB
If all goes well, your screen density should change on the fly. Reboot your phone at this stage and if this gets rid of the force close messages and allows you to interact with your device, it should be quite easy to edit the build.prop file. Just go to the Play Store, install a root file manager (or better yet the application you used in the first place - Textdroider DPI) and edit the file. Make sure you set the density to 480.
Click to expand...
Click to collapse
Yes! I got it working now. (had some issues with adb and permissions but got it sorted)
Thanks a lot for your help!
No problem. Glad I could help Just remember to be careful when messing around with screen densities and to always keep a build.prop backup in case something goes wrong

[Q] Backup from TWRP with USB

I've managed to softbrick my nexus 10 by trying to disable extra services (was getting about 1.5 hours battery life with media services running the processor 100% all the time). It worked wonderfully (no negative side effects, went back to 10+ hours with the screen on, or days on standby) until I reboot it and now it won't load past the moving colors (Android 4.4.3, unlocked and all that).
I have TWRP, I was hoping to backup everything possible via usb, but it seems it's incapable of doing so. ADB backup can't be done using TWRP since there's no unlock function (reaaal useful there, recovery mode that doesn't support backups) and adb pull fails if I try to pull everything since there are files and folders with invalid file names (who puts ":" in folder names? they should be shot), and I don't know specifically what to pull, I was just going to get everything put back what I found was missing that I needed. There's no room to do a backup onto the device, and since the N10 has to sd/microsd, well... Useless options are useless.
Is there anyway to just do a proper backup with TWRP over USB? Or is the "recovery" mode as useless as I think it is when it comes to backups? (I'm aware I can get the tablet back to working order if I disregard the data on it, this is a question about backing things up before doing so)
Edit: Also, I have a pro version of SkipSoft ToolKit, but unless you can actually load into the OS the toolkit can't do anything at all.
Just really frustrated with the lack of doing something as basic as copying files from one place to another. Been messing with this all morning.
Diet6 said:
I've managed to softbrick my nexus 10 by trying to disable extra services (was getting about 1.5 hours battery life with media services running the processor 100% all the time). It worked wonderfully (no negative side effects, went back to 10+ hours with the screen on, or days on standby) until I reboot it and now it won't load past the moving colors (Android 4.4.3, unlocked and all that).
I have TWRP, I was hoping to backup everything possible via usb, but it seems it's incapable of doing so. ADB backup can't be done using TWRP since there's no unlock function (reaaal useful there, recovery mode that doesn't support backups) and adb pull fails if I try to pull everything since there are files and folders with invalid file names (who puts ":" in folder names? they should be shot), and I don't know specifically what to pull, I was just going to get everything put back what I found was missing that I needed. There's no room to do a backup onto the device, and since the N10 has to sd/microsd, well... Useless options are useless.
Is there anyway to just do a proper backup with TWRP over USB? Or is the "recovery" mode as useless as I think it is when it comes to backups? (I'm aware I can get the tablet back to working order if I disregard the data on it, this is a question about backing things up before doing so)
Edit: Also, I have a pro version of SkipSoft ToolKit, but unless you can actually load into the OS the toolkit can't do anything at all.
Just really frustrated with the lack of doing something as basic as copying files from one place to another. Been messing with this all morning.
Click to expand...
Click to collapse
Do you still need help? What about mtp mounting? You can pull * for a whole folder
Why not adb sideload a new rom?
I don't think I can MTP mount a Nexus 10, at least not in recovery mode. What I ended up doing was buying a OTG usb drive and making a backup to that. Problem was it split the tar over 4 files, which corrupted them (or at least made them not work with 7zip or tartool) fortunately I was able to get them to work with cygwin enough to get the files I wanted. I didn't want to sideload a new rom until I had backed up certain application data just in case it removed it.
All in all, had to buy a OTG usb drive (I would have just bought a cable but all the stores around here had was this "Dane 16gb OTG drive". So 20 bucks later I had the files I needed. Still annoyed that you can't do a ADB backup from fastboot or recovery mode, it seems like those would be the best places because no system files are in use, but who knows maybe the developers know something I don't.
In summary:
TWRP recovery cannot confirm a ADB backup over USB. ADB backups can only be done from the operating system.
TWRP recovery mode can only backup to OTG (if your device supports it, Nexus 10 does), but if the backup is larger than 2gb it will split the file and you will need some form of linux to extract it.
ADB cannot copy every file in recovery mode over USB due to certain file names being invalid for NTFS (this is probably not a problem on other file system types), this is problematic since the "pull" command has no skip option, it just fails when it hits one of these files.
Well you can easily flash latest rwrp that does well on my Linux mount internal storage but another solution is just flashing a rom with abd sideload and the'the back up from pc the content
---------- Post added at 04:24 AM ---------- Previous post was at 04:23 AM ----------
Or that will just un brick your tablet
Diet6 said:
Still annoyed that you can't do a ADB backup from fastboot or recovery mode
Click to expand...
Click to collapse
adb doesn't work in fastboot mode, only recovery or Android itself.
Diet6 said:
In summary:
TWRP recovery cannot confirm a ADB backup over USB. ADB backups can only be done from the operating system.
Click to expand...
Click to collapse
Maybe because /data (not talking about /data/media) wasn't mounted?
Diet6 said:
TWRP recovery mode can only backup to OTG
Click to expand...
Click to collapse
Huh?
Diet6 said:
ADB cannot copy every file in recovery mode over USB due to certain file names being invalid for NTFS (this is probably not a problem on other file system types), this is problematic since the "pull" command has no skip option, it just fails when it hits one of these files.
Click to expand...
Click to collapse
That's NTFS' problem, not TWRP's.
beekay201 said:
1. adb doesn't work in fastboot mode, only recovery or Android itself.
2. Maybe because /data (not talking about /data/media) wasn't mounted?
3. Huh?
4. That's NTFS' problem, not TWRP's.
Click to expand...
Click to collapse
1. I was just covering that you can't actually do a ADB backup unless you have access to android OS, in case anyone else came across this. (I didn't know when I started, and it took awhile to find it said concretely anywhere)
2. I made sure everything was mounted, the issue is when you send a backup command over ADB it says the "Now unlock your device and confirm the backup operation" message in terminal which you can't do from recovery mode on the device, thus you cannot do a ADB backup command over TWRP (or other recovery modes I'd imagine).
3. I should have been more specific. TWRP can do a backup to the device itself (built in storage), SD card (if your device has one and you mount it), or a OTG (on the go) device via usb directly to media like a flash drive. It cannot issue a backup over USB to a computer.
4. Completely agree it's a NTFS issue, but it could be mostly avoided by allowing files that error to be skipped or renamed rather than terminating the process. (I understand that's on the android devs since pull is made by them, and I doubt they would care to improve the command for a file system I doubt they use). Again I mostly included that so if anyone else is trying to figure it out they can stop looking for "a way" and just accept it can't be done.
Ultimately Khaon is right in that sideloading a rom would have unbricked it and I could have done the ADB backup then, I just wasn't sure how that might affect the app data storage so I was looking for a way to back it up before doing that.
Diet6 said:
1. I was just covering that you can't actually do a ADB backup unless you have access to android OS, in case anyone else came across this. (I didn't know when I started, and it took awhile to find it said concretely anywhere)
2. I made sure everything was mounted, the issue is when you send a backup command over ADB it says the "Now unlock your device and confirm the backup operation" message in terminal which you can't do from recovery mode on the device, thus you cannot do a ADB backup command over TWRP (or other recovery modes I'd imagine).
3. I should have been more specific. TWRP can do a backup to the device itself (built in storage), SD card (if your device has one and you mount it), or a OTG (on the go) device via usb directly to media like a flash drive. It cannot issue a backup over USB to a computer.
4. Completely agree it's a NTFS issue, but it could be mostly avoided by allowing files that error to be skipped or renamed rather than terminating the process. (I understand that's on the android devs since pull is made by them, and I doubt they would care to improve the command for a file system I doubt they use). Again I mostly included that so if anyone else is trying to figure it out they can stop looking for "a way" and just accept it can't be done.
Ultimately Khaon is right in that sideloading a rom would have unbricked it and I could have done the ADB backup then, I just wasn't sure how that might affect the app data storage so I was looking for a way to back it up before doing that.
Click to expand...
Click to collapse
I'd just 'tar' what I wanted on the device and then pull that with adb.
Yeah, I just had no idea what I wanted. I'm not 100% familiar with how the system stores application data, I figured if I copy everything than anything I "miss" after I formated it I'll be able to just research where it was and dig in the backup and pull it out.
Yeah adb sideload a rom will only affect system partition thus your data would not have been modified in any way. So you are done with your issue?
Sent from my Xiaomi MI2s
Khaon said:
Yeah adb sideload a rom will only affect system partition thus your data would not have been modified in any way. So you are done with your issue?
Sent from my Xiaomi MI2s
Click to expand...
Click to collapse
Yes, sorry for the slow reply. I've completed my update, just wanted to follow up on everything I did incase the information is useful for anyone else new to this like I am.

DPI conflicts in LMY47E

Today I found something really strange about builds LMY47E and LMY47D. I had been running 47D since last week with a DPI of 520, which was adjusted using Root Explorer in the build.prop. After trying to do the same in 47E, rebooting my device would display the "Android is upgrading... Optimizing app 1 of XXX" screen, and make it bootloop after optimizing the last app, displaying the same screen and optimizing my apps again and again.
After many hours trying to isolate the culprit, I found that to properly change DPI In 47E, one has to edit the build.prop lcd density AND use "adb shell wm density XXX". That's the only way I've made sure my device reboots properly.
I think this is really weird, since 47D and 47E are supposed to be identical. Does anybody have any clue about this?
redsmith said:
Today I found something really strange about builds LMY47E and LMY47D. I had been running 47D since last week with a DPI of 520, which was adjusted using Root Explorer in the build.prop. After trying to do the same in 47E, rebooting my device would display the "Android is upgrading... Optimizing app 1 of XXX" screen, and make it bootloop after optimizing the last app, displaying the same screen and optimizing my apps again and again.
After many hours trying to isolate the culprit, I found that to properly change DPI In 47E, one has to edit the build.prop lcd density AND use "adb shell wm density XXX". That's the only way I've made sure my device reboots properly.
I think this is really weird, since 47D and 47E are supposed to be identical. Does anybody have any clue about this?
Click to expand...
Click to collapse
I just changed it with root explorer. I didn't have any issues.
Then again I stayed within the default density's from my past devices.
Nexus 6 is 560, I went to 480.
antiochasylum said:
I just changed it with root explorer. I didn't have any issues.
Then again I stayed within the default density's from my past devices.
Nexus 6 is 560, I went to 480.
Click to expand...
Click to collapse
That's weird. Mine would survive a couple of reboots but after that, bootloop fest.
I'll keep an eye on this issue anyway.
I just went through this on 47E. It was bad but it turns out that you only need to do "adb shell wm density XXX" and not edit the build prop. Editing the build prop sent me through the bootloop
krazekid007 said:
I just went through this on 47E. It was bad but it turns out that you only need to do "adb shell wm density XXX" and not edit the build prop. Editing the build prop sent me through the bootloop
Click to expand...
Click to collapse
The thing is, if you only do "adb shell wm..." you will get weird graphical glitches, especially in the keyboard. So far, I've managed to avoid them by editing build.prop too.
redsmith said:
The thing is, if you only do "adb shell wm..." you will get weird graphical glitches, especially in the keyboard. So far, I've managed to avoid them by editing build.prop too.
Click to expand...
Click to collapse
Still get glitches even after rebooting?
Lol, I'm so glad someone brought this up. Thought I or my phone was going nuts!
All I've ever done is change the build.prop, no adb stuff, never had issues...for all builds
Sent from my Nexus 6 using XDA Free mobile app
A2CKilla said:
All I've ever done is change the build.prop, no adb stuff, never had issues...for all builds
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
It lasts for a few days sometimes.... Usually after a reboot or 2 its gameover.. It'll usually let me reboot 2x before looping .. If I don't reboot it'll just randomly turn off and then..well.. Loop
Not the only ones with this issue... here's what I have found even with "D" & "E" working with the group trying to port the Blinkfeed Launcher from Sense 7 which requires a DPI change to work correctly on the Nexus 6.
532DPI use to work with 5.0.1 & 5.0.2... No longer the case for any 5.1 build (haven't tried "M" build yet) which is the perfect setting for Blinkfeed Sense 7 Launcher....
I am using 520 right now... other experience issues with the bootloop at 520... I have found a way to test:
1. TWRP backup current good DPI setting... Backup up everything cache, efs, system, data, etc.
2. After TWRP backup, boot up and apply the new settings you wish to test. Apply then completely power off.
3. Power on and boot up. If no optimizing apps issues, you have passed step one.
4. Now TWRP backup your new settings, backup everything, reboot system. If no bootloop, then you should be golden
I think it is something in the code to streamline how it handles graphics... however it seems that what is acceptable varies from phone to phone. Most see good results staying with factors of 40 & 80 while others can do even factors of 20....
Don't think anyone has figured out root cause entirely..... I really like to know why I could 532 before and can't now???
Yea 532 was my buttah
redsmith said:
The thing is, if you only do "adb shell wm..." you will get weird graphical glitches, especially in the keyboard. So far, I've managed to avoid them by editing build.prop too.
Click to expand...
Click to collapse
So were you able to successfully change your DPI by editing the build.prop?
I had to do adb shell trick too, otherwise, bootloops.
Build.prop edit LCD_density
redsmith said:
. . . . . I think this is really weird, since 47D and 47E are supposed to be identical. Does anybody have any clue about this?
Click to expand...
Click to collapse
Started with rooting 5.0.1. Then edited build.prop with 'build.prop.editor and changed the LCD-density to 493.
Because the native resolution is of the N6 screen is 493.
After upgrading to LMY47D the DPI value was 520 (0r 560?) again. I edited this value 'ro.sf.lcd_density' and set the value to 384.
With that value the N6 is in tablet mode.
After rebooting the value of 'ro.sf.lcd_density was 384, but the display was not different.
In the Build.Prop editor there is a menu item called Build.Prop Tweaks. In the Tweaks-list the entry 'LCD Density' was missing.
I did not have a backup of the build.prop file so a full restore in recovery was needed to correct this.
The Build.Prop editor has an option to create a backup. Use this option first before editing.
Now for about a week with 47D and DPI 384 and font size to huge, the N6 works fine. (Stock, rooted, encrypted).
Remark.
Because the N6 has a amoled display it's a bit strange that the name 'ro.sf.lcd_density' is used.
NLBeev said:
Started with rooting 5.0.1. Then edited build.prop with 'build.prop.editor and changed the LCD-density to 493.
Because the native resolution is of the N6 screen is 493.
After upgrading to LMY47D the DPI value was 520 (0r 560?) again. I edited this value 'ro.sf.lcd_density' and set the value to 384.
With that value the N6 is in tablet mode.
After rebooting the value of 'ro.sf.lcd_density was 384, but the display was not different.
In the Build.Prop editor there is a menu item called Build.Prop Tweaks. In the Tweaks-list the entry 'LCD Density' was missing.
I did not have a backup of the build.prop file so a full restore in recovery was needed to correct this.
The Build.Prop editor has an option to create a backup. Use this option first before editing.
Now for about a week with 47D and DPI 384 and font size to huge, the N6 works fine. (Stock, rooted, encrypted).
Remark.
Because the N6 has a amoled display it's a bit strange that the name 'ro.sf.lcd_density' is used.
Click to expand...
Click to collapse
whojabacod said:
Yea 532 was my buttah
Click to expand...
Click to collapse
krazekid007 said:
So were you able to successfully change your DPI by editing the build.prop?
Click to expand...
Click to collapse
redsmith said:
I had to do adb shell trick too, otherwise, bootloops.
Click to expand...
Click to collapse
I don't believe there is any rhyme or reason to it bootlooping... something is definitely different in the programming in 5.1... tried everything last night to get 532DPI to stick.... build.prop.... adb command... tried them all... would reboot 1 time ok, second time "op apps" bootloop. this was not the case with 5.0.1 or 5.0.2... I remember tweaking the dpi by 2 up and down to find a perfect dpi for a Blinkfeed launcher port on 5.0.2 and never had this issue. It is either something Google did on purpose for this build or on accident. Either way, we are kind of screwed until someone smarter than I can put a finger on as to what is causing this... I just think 5.1 was rushed to get VoLTE out there for the Verizon release...
When your N6 is bootlooping in 5.1. And you can't find the cause and/or a solution then you could decide to go back to the factory settings including unroot. This can be done easily with the toolkit of Wugfresh.
I did that and I am using now 5.1 (47D) and edited buil.prop. DPI set to 384.
NLBeev said:
When your N6 is bootlooping in 5.1. And you can't find the cause and/or a solution then you could decide to go back to the factory settings including unroot. This can be done easily with the toolkit of Wugfresh.
I did that and I am using now 5.1 (47D) and edited buil.prop. DPI set to 384.
Click to expand...
Click to collapse
Or you can just fastboot flash system.img and save time and your data. It's what I did on a DPI bootloop.
SilkyJohnson said:
Or you can just fastboot flash system.img and save time and your data. It's what I did on a DPI bootloop.
Click to expand...
Click to collapse
Let's hope for him.
NLBeev said:
Let's hope for him.
Click to expand...
Click to collapse
No need to hope - it works. I did it.

[GUIDE] Android 11 GSI With GApps and Root (magisk)

DON'T DO THIS ON A RAZER PHONE 1 OR IT WILL BE OMEGA BRICKED! ONLY DO THIS ON A RAZER PHONE 2!
This was just an experiment to see if i could cobble together some GSI install guides (that on their own are kinda confusing) to make something moderately more cohesive and understandable. Here's my moderately usable guide!
-----------------------------------------------------------------
VIDEO!
-----------------------------------------------------------------
-----------------------------------------------------------------
Things that work and don't work:
-----------------------------------------------------------------
This section will update periodically as issues arise or fixes arise for said issues.
Note: Things that work: Bluetooth*, all sensors, audio, LTE/SIM/phone stuff, 120hz (you need to go into the settings > Phh treble settings > Misc features > Force FPS > [email protected])
Things that probably work: N/A
Things that don't work for some reason: SafteyNet with Magisk. All modules that I've used work tho...??! Verizon.
Remember, you can always flash back to stock if something doesn't work properly.
-----------------------------------------------------------------
FIXES!!!
-----------------------------------------------------------------
AUDIO FIX!!! GO TO Phh Treble Settings > Qualcomm features > Use alternate audio policy.
Bluetooth audio stops working with this enabled. Disable it for Bluetooth audio. The audio fix doesn't apply to Bluetooth audio ether way.
BLUETOOTH FIX!!! Download a root file browser from the google play store and allow it to have root access. Delete BluetoothCommonRes.apk which is found in the overlay folder which is found in the vendor folder. After you delete BluetoothCommonRes.apk, rename the RazerAuraBluetoothRes.apk to BluetoothCommonRes.apk.
-----------------------------------------------------------------
Important notes
-----------------------------------------------------------------
THIS IS ASSUMING YOU HAVE ALREADY UNLOCKED THE BOOTLOADER OF YOUR DEVICE AND HAVE GOTTEN A SERIAL NUMBER OUTPUT FROM CMD AFTER TYPING IN "fastboot devices" AND MAKE SURE YOU HAVE TYPED IN "fastboot flashing unlock" AND "fastboot flashing unlock-critical".
***NOTE: I AM NOT RESPONSIBLE FOR ANY HARD BRICKED DEVICES OR ANGRY PARENTS. PLEASE DO NOT COME BACK AT ME SAYING I AM STUPID AND BRICKED YOUR PHONE. YOU DECIDED TO DO THIS. PLEASE PROCEED WITH CAUTION AND DON'T SKIM***
ANOTHER IMPORTANT NOTE: The stock firmware is actually really good for unbricking devices. Razer made it easy to fix your bricked device. So basically, if you can get in to fastboot mode, (which you basically always can do) you can unbrick your device super easily.
AGAIN JUST PLEASE, MAKE SURE TO FOLLOW ALL THESE INSTRUCTIONS CAREFULLY AND DONT SKIM OR ELSE YOU MIGHT BREAK SOMETHING!!!
-----------------------------------------------------------------
Introduction
-----------------------------------------------------------------
This is a quick and easy guide for how to install Android 11 on the Razer Phone 2. I'm kind of a noob here myself but I did this and it worked flawlessly. (also if you do run into any issues PLEASE don't count on me for troubleshooting tips (I'm not that great at that))
-----------------------------------------------------------------
Pre-requisites/Downloads
-----------------------------------------------------------------
Get the factory firmware for your phone. It's a good failsafe in case of a bootloop or a bad case of the phone not booting up. Download it here: P-SMR6-RC001-RZR-201022 (latest build at the time of writing)
Extract this with 7zip or WinRar (or windows. You will need 7zip or WinRar for the rest of this)
First you need the actual GSI. Get the latest version. (Make sure its not a pre-release). system-roar-arm64-ab-vndklite-gapps.img.xz is the version that you should get. The vndklite release will allow you to modify the system partition making it possible to get magisk. Note: If you want magisk, MAKE SURE TO COMPLETELY follow the magisk section of this guide aswell or else magisk will NOT install correctly and will NOT work.
This version also has GApps. It will give you Gmail, the google play store, google play services, etc.
Use 7zip or WinRar to extract this.
Your also gonna need the Trinity Kernel (v2). This gives you TWRP and I'm pretty sure you also need this to have the ability to boot up the phone (I may be wrong but it's required.)
use 7zip or WinRar to extract this.
You will also need this zip file made by arter97 I don't really know what it does but you need it. here is the download: Download.
Don't extract this.
Put all these in a known folder that you can access later.
Alright. Now that we're done with the downloads, time to test to make sure your ready to put this on your phone.
-----------------------------------------------------------------
Making sure your computer is ready
-----------------------------------------------------------------
First things first. Go open your platform tools folder, shift-right click and open a PowerShell, or command prompt window there. Shut down your Razer phone 2 and turn it back on with the power and volume down buttons.
Plug it into your PC and type in
Code:
fastboot devices
you should end up with the serial number of the device. if you don't, follow Razer's instructions on how to install USB drivers and then come back here. Link to PDF.
If you get a serial number, close that and flash stock firmware by going into the aura-p-release-etc. folder, then opening flash_all.bat.
When it finishes and the screen goes black, hold the power and volume down buttons again to get back in to fastboot mode.
open back up the CMD/PowerShell platform tools window thing again.
-----------------------------------------------------------------
Installing/Flashing
-----------------------------------------------------------------
In your CMD or PowerShell window, (while in fastboot mode on the phone) type
Code:
fastboot flash system <file name>
in the <file name> area, just drag and drop the system-roar-arm64-etc.img file into your command line. your command will look a little something like this:
Code:
fastboot flash system C:\Users\user\Desktop\system-roar-arm64-ab-gapps.img
Wait until it says complete or something similar like done or something and has no errors.
Then, time to flash the kernel. it should just be called boot.img.
We will be typing in:
Code:
fastboot flash boot <file name>
Do the same thing that you did for the last command which is drag and drop the boot.img file for the file name.
Again, wait until it says done or complete and has no errors.
After that is done, use the volume buttons to select reboot bootloader with your power button on your phone.
Go to recovery mode and swipe where it says to swipe.
Go to the wipe menu and then tap on format data. Type yes and then press enter/ok.
Go back to your computer and open file explorer.
Put the last zip file that I was talking about earlier (the f2fs thing) on the razer phone 2's internal storage. Head back to your phone, and press install.
Scroll down until you find the zip file and press it and install it. (ignore the errors that may or may not be there) After that, go back to the TWRP home screen (with the 8 options)
Go to the reboot menu, then reboot into recovery
Tap on format data and type in "yes" and tap ok. click on "don't install" because you don't need the TWRP app on your phone.
The phone will shut down. Turn it on normally and everything will work!
----------------------------------------------------------------------------------------------------------------------------------
GET THESE THINGS IF YOU WANT 120Hz, GCam, and a SNAZZY RAZER LOGO.
----------------------------------------------------------------------------------------------------------------------------------
To get 120Hz, you need to go into the settings > Phh treble settings > Misc features > Force FPS > [email protected].
If you want your Razer logo to light up again, use Logo+. here is a download: Logo+ APK
The default camera app sucks. Make sure to get GCam 7.4 from Cyanogen Mods (v8.0 is broken). you can get it here.
Download a root file browser from the google play store and allow it to have root access. Delete BluetoothCommonRes.apk which is found in the overlay folder which is found in the vendor folder. After you delete BluetoothCommonRes.apk, rename the RazerAuraBluetoothRes.apk to BluetoothCommonRes.apk.
-----------------------------------------------------------------
Magisk
-----------------------------------------------------------------
So this part was pretty long-awaited. It half-passes SafteyNet and modules work! (at least all the modules that I've used.)
Make sure you have the vndklite variant. That is the only way that this will work.
1. Open up an adb/fastboot powershell/cmd/windows terminal window.
2. Type adb root and hit enter.
3. Type adb shell and hit enter.
4. Type mount -o remount,rw / and hit enter.
5. Type mv /bin/resetprop_phh /bin/phh-resetprop and hit enter.
6. Type phh-securize.sh and hit enter.
The phone should reboot after you approve the request (if there is one) and you are now able to install magisk!
MAKE SURE THAT THE SUPERUSER APP IS NOT THERE AFTER RUNNING phh-securize.sh.
Get specifically this version of Magisk. Download the zip file.
Boot into TWRP and tap on mount, and select everything (usb storage doesn't matter in this case. it never mounts either way.)
Transfer over your zip file via file explorer, and go back to your phone.
Tap install, then scroll down until you find the zip file and tap it. Swipe to flash and wait. After it is done, you can reboot!
You should see Magisk manager in your app drawer. Open that. It might ask you to install it, if so, install it. Allow apps from this source then install. Open it up. You should see that Magisk is installed. Update it and turn on Magisk hide.
If it passes SafteyNet, it's a miracle.
-----------------------------------------------------------------
In case of failure
-----------------------------------------------------------------
If it starts bootlooping or is perpetually stuck at the razer logo, powered by android screen, go back into fastboot mode and run the flash_all.bat stock firmware thing. it will unbrick your phone automatically. Really make sure you don't skim if you try it again. If it did work (which it probably did), then have a good time with android 11!
There is one bug that has stopped me from going GSI. On every one I've tried, there is a game music bug that is common in many of the games I own. If the volume is set to below 50%, the music will cut in and out constantly. It resolves itself if you keep media volume above 50%. It may not be a deal breaker for everyone, but it was for me, as I use my RP2 heavily for games. Other than that, GSIs work beautifully. Thanks for the comprehensive guide!
Reznor7 said:
There is one bug that has stopped me from going GSI. On every one I've tried, there is a game music bug that is common in many of the games I own. If the volume is set to below 50%, the music will cut in and out constantly. It resolves itself if you keep media volume above 50%. It may not be a deal breaker for everyone, but it was for me, as I use my RP2 heavily for games. Other than that, GSIs work beautifully. Thanks for the comprehensive guide!
Click to expand...
Click to collapse
Just curious, what games have that issue?
Marcos8760 said:
Just curious, what games have that issue?
Click to expand...
Click to collapse
All of The Room games, Battle Chasers: Night War, and most premium games that I've bought. For some reason, Monster Hunter Stories doesn't. It seems like mostly games that have more complex audio/music.
Reznor7 said:
All of The Room games, Battle Chasers: Night War, and most premium games that I've bought. For some reason, Monster Hunter Stories doesn't. It seems like mostly games that have more complex audio/music.
Click to expand...
Click to collapse
Thanks for the info. I added that to the top of the thread.
EDIT: Fix at the top of the thread
Ultimately at the end of the day I could not get Dolby Atmos and the RGB lighting on the back of the phone to work on GSI 10. Hopefully someone will come up with a work around for those 2 items in GSI 11.
RJR
rrusek said:
Ultimately at the end of the day I could not get Dolby Atmos and the RGB lighting on the back of the phone to work on GSI 10. Hopefully someone will come up with a work around for those 2 items in GSI 11.
RJR
Click to expand...
Click to collapse
I got the Razer logo working flawlessly with logo+. I didn't really see the appeal for Dolby Atmos as all it did was made it louder and made the audio clip more.
I did have success getting Atmos to work with this module: https://github.com/reiryuki/Dolby-Atmos-Razer-Phone-2-Magisk-Module
Reznor7 said:
I did have success getting Atmos to work with this module: https://github.com/reiryuki/Dolby-Atmos-Razer-Phone-2-Magisk-Module
Click to expand...
Click to collapse
How can I get magisk on the phone though? it has Superuser pre-installed but it doesn't have support for modules and stuff (as far as I can tell). I really would like some info on how to install magisk if possible.
Marcos8760 said:
How can I get magisk on the phone though? it has Superuser pre-installed but it doesn't have support for modules and stuff (as far as I can tell). I really would like some info on how to install magisk if possible.
Click to expand...
Click to collapse
Actually, I may be misremembering. That may have been on a 10 GSI. I don't think I ever did get Magisk to work on an 11.
Reznor7 said:
Actually, I may be misremembering. That may have been on a 10 GSI. I don't think I ever did get Magisk to work on an 11.
Click to expand...
Click to collapse
Alright good to know. like the other info I've gathered, ill put that at the top of the thread until further notice.
The unofficial LOS GSI just got updated with supposed Magisk support. I'm going to give it a try in a few.
Reznor7 said:
The unofficial LOS GSI just got updated with supposed Magisk support. I'm going to give it a try in a few.
Click to expand...
Click to collapse
Nope, Magisk doesn't work.
Thank you. I got it all set up and mostly working well. I was wondering if you could try Minecraft and let me know if it will let you get to the actual login screen.
I cannot get flashing the Android 11 GSI to work.
I downloaded the latest factory image (MR6) and proceeded to install it. To do that, I had to copy the "fastboot.exe" from the SDK platform tools download to the "aura-p-release..." folder with the factory image.
I open a CMD line and type in "fastboot devices" which get me a string of numbers. Then I type in "fastboot flash system system-roar-arm64-ab-gapps.img.xz" which tries to install it but concludes with an error message, being 'Error: Last flash failed : Bad Buffer Size'.
I tried using different computers and cables, but I end up with the same thing. I'm able to flash the factory image just fine, but can't flash Android 11.
AgentXGhost said:
I cannot get flashing the Android 11 GSI to work.
I downloaded the latest factory image (MR6) and proceeded to install it. To do that, I had to copy the "fastboot.exe" from the SDK platform tools download to the "aura-p-release..." folder with the factory image.
I open a CMD line and type in "fastboot devices" which get me a string of numbers. Then I type in "fastboot flash system system-roar-arm64-ab-gapps.img.xz" which tries to install it but concludes with an error message, being 'Error: Last flash failed : Bad Buffer Size'.
I tried using different computers and cables, but I end up with the same thing. I'm able to flash the factory image just fine, but can't flash Android 11.
Click to expand...
Click to collapse
You forgot to extract it with winrar or 7zip. make sure it is a .img file and not a .xz file.
Wow. I spent close to 7 hours trying and trying again. But that's what I get when I don't read all the instructions. -____-
Thanks very much. It works perfectly.
AgentXGhost said:
Wow. I spent close to 7 hours trying and trying again. But that's what I get when I don't read all the instructions. -____-
Click to expand...
Click to collapse
oh noes!
When in TWRP, the system is not mounted, and I cannot see it on my PC nor in TWRP itself. Any ideas what I did wrong?
Gurcharan5 said:
When in TWRP, the system is not mounted, and I cannot see it on my PC nor in TWRP itself. Any ideas what I did wrong?
Click to expand...
Click to collapse
Try going to wipe, then format data. That might fix the problem. If not, try everything again.

Categories

Resources