Database Users

So what to do when I'm temp-rooted?

After having the phone for 3 weeks, today i finally temp-rooted.
Only because I needed to edit the root folder so that I can use ad-hoc internet, which stock android phones can't find. Well now it works and it feels pretty cool!
what else can I do now while I am temp rooted?

thunder9111 said:
After having the phone for 3 weeks, today i finally temp-rooted.
Only because I needed to edit the root folder so that I can use ad-hoc internet, which stock android phones can't find. Well now it works and it feels pretty cool!
what else can I do now while I am temp rooted?
Click to expand...
Click to collapse
Get rid of the annoying stock apps that come with the phone

i was trying to do that just now, but when i was in the application manager the uninstall button was still darkened out..
am I supposed to go to the superuser app and give it access first?
will uninstalling those stock apps have any effects? i still plan on continuing to use the stock htc sense rom as i see nth wrong with it.

No point because you're temp rooted, after a reboot.. they come back.
Sent from my T-Mobile G2 using Tapatalk

true. found that out the hard way.
sucks, even the wpa_supplicant that i editted will go back to the original which means i will lose adhoc again.
now everytime i want to use adhoc i will have to temp-root, then use root explorer to edit the wpa_supplicant.
since i used visionary to temproot and it has the permroot option, would doing so allow me to save all my file settings after root explorer?
would the permroot still be revertable using the unroot option?
all this for ad-hoc internet

thunder9111 said:
true. found that out the hard way.
sucks, even the wpa_supplicant that i editted will go back to the original which means i will lose adhoc again.
now everytime i want to use adhoc i will have to temp-root, then use root explorer to edit the wpa_supplicant.
since i used visionary to temproot and it has the permroot option, would doing so allow me to save all my file settings after root explorer?
would the permroot still be revertable using the unroot option?
all this for ad-hoc internet
Click to expand...
Click to collapse
If you're going to 'perm-root' then don't use visionary. Use the Gfree method, it's the most current and safest. I don't have the link to the G2 wiki right now but Google should find it for you. Rooting with Gfree is at the bottom section of the wiki.

I would use this method as it seems to be the quickess and user friendly one
http://forum.xda-developers.com/showthread.php?t=928160

noodles2224 said:
No point because you're temp rooted, after a reboot.. they come back.
Sent from my T-Mobile G2 using Tapatalk
Click to expand...
Click to collapse
I'm curious, even if you're only temp rooted, wouldn't remounting /system rw make any changes permanent?

noodles2224 said:
No point because you're temp rooted, after a reboot.. they come back.
Sent from my T-Mobile G2 using Tapatalk
Click to expand...
Click to collapse
Oh thats there was a way to disable them though so they wouldn't show up or even get ran. If memory serves you would go into terminal emulator, cd to the system/app directory, and then you would pm disable the apks that you didnt want

tan-ce said:
I'm curious, even if you're only temp rooted, wouldn't remounting /system rw make any changes permanent?
Click to expand...
Click to collapse
No. It's been a while since I've even thought about NAND locks and stuff but basically the system is protected from permanent changes unless the proper key is used. When you reboot your phone the system is compared to an image of it stored on the NAND and any changes are overwritten - sort of like a system restore on windows except it's automatic at every boot. That's how I understand it working from my memory.

KCRic said:
When you reboot your phone the system is compared to an image of it stored on the NAND and any changes are overwritten - sort of like a system restore on windows except it's automatic at every boot.
Click to expand...
Click to collapse
So do I correctly assume that s-off removes the locks?
Edit: Never mind the question, some searching paid off. Answer is yes.

Dpi

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

Screen resolution messed up -help needed!

Hi, playing around with an app called "Resolution Changer Pro", I set my phone to 350x350 in order to try a few things how my smartwatch would behave, which has also android and 400x400.
That went OK, and I was able to get back to fullHD fine.
Then I also changed the DPI accidentally to 100 and then the phone crashed.
Rebooting results in a black screen and I can´t do anything....
With adb I tried to set the resolution back to something usable, and the reply was that the window manger is not running.
Then I tried to get hold of the build.prop with adb and checked the DPI setting there, which was 480 .. the defailt setting.
Now my android knowledge is at the edge, and I don´t have an Idea how to reset the settings back to normal.
What could I do without deleting everything and re-flashing?
Pros.. what should I do ??? :crying::crying:

Flash same rom via recovery.

maitrot said:
Hi, playing around with an app called "Resolution Changer Pro", I set my phone to 350x350 in order to try a few things how my smartwatch would behave, which has also android and 400x400.
That went OK, and I was able to get back to fullHD fine.
Then I also changed the DPI accidentally to 100 and then the phone crashed.
Rebooting results in a black screen and I can´t do anything....
With adb I tried to set the resolution back to something usable, and the reply was that the window manger is not running.
Then I tried to get hold of the build.prop with adb and checked the DPI setting there, which was 480 .. the defailt setting.
Now my android knowledge is at the edge, and I don´t have an Idea how to reset the settings back to normal.
What could I do without deleting everything and re-flashing?
Pros.. what should I do ??? :crying::crying:
Click to expand...
Click to collapse
First you have to flash TWRP in order to use terminal in recovery.
Download AROMA Filemanager from here thanks to @amarullz
Go into recovery then flash it. (don't forget to mount system partition first.)
Guide to path /system/ then select Menu->open console
type in
vi build.prop
Click to expand...
Click to collapse
Once you open the build.prop with vi , you can now use the arrow button to guide to your section.
There's two mode in vi, edit mode and connamd mode.
You have to enter "i" first to enter edit mode
Once you finish editing, press Esc on top and now you are back to command mode
Enter following command to save the file and quit:
:wq
Click to expand...
Click to collapse
Now press Close on right top then press menu and exit file manager, reboot your device.
You are done.
TIPs: Here's an useful command to delete a line that you can't use delete to eliminate
In command mode, type in following command to delete a line:
:dd
Click to expand...
Click to collapse

1. Ok, flashing the same rom did not help... this was the first thing I tried.
2. I already tried to work with my build.prop, which I downloaded with adb from the device.. I already said that in my first post.
In the build.prop the dpi setting is at 480, like I said. Modyfiying it from twrp with vi is the same as downloading it via adb and then modyfiying it locally and uploading it again..... this did not help, dpi was at 480, like I said.
Strange... right?
Where is the screen resolution saved? Dpi is in build.prop, but where is the resolution saved at?
The problem must be somewhere in the data partition, since flashing does not help. I erased system and re-flashed. no help.

maitrot said:
1. Ok, flashing the same rom did not help... this was the first thing I tried.
2. I already tried to work with my build.prop, which I downloaded with adb from the device.. I already said that in my first post.
In the build.prop the dpi setting is at 480, like I said. Modyfiying it from twrp with vi is the same as downloading it via adb and then modyfiying it locally and uploading it again..... this did not help, dpi was at 480, like I said.
Strange... right?
Where is the screen resolution saved? Dpi is in build.prop, but where is the resolution saved at?
The problem must be somewhere in the data partition, since flashing does not help. I erased system and re-flashed. no help.
Click to expand...
Click to collapse
Then you should backup before flashing or doing root permission changes.
You can now do a fully backup , data, cache anything And then flash the stock firmware via SP_FlashTool.
If you boot, then try to restore the partition one by one.

jwchen119 said:
Then you should backup before flashing or doing root permission changes.
You can now do a fully backup , data, cache anything And then flash the stock firmware via SP_FlashTool.
If you boot, then try to restore the partition one by one.
Click to expand...
Click to collapse
Ok, I did that... made a backup of all partitions, erased everything and re-flashed latest dev firmware.
Off course, everything works fine now, but all my settings and stuff are lost.
going back to my old data partition, the problem is back.
How can I get back to my old settings? What do you mean one by one?

Change to build.prop not having any effect

I'm pretty confused... I'm running Cataclysm with regular root (not systemless) and I've modified the build.prop (shows the modified value even after reboot) to change my screen dpi but upon reboot my dpi stays unchanged. Any ideas? I've tried to change the dpi through the adb method and that works but it shows some odd behavior in play store (some icons being too large, etc.) that other people say don't occur if you modify build.prop.

bgymn2000 said:
I'm pretty confused... I'm running Cataclysm with regular root (not systemless) and I've modified the build.prop (shows the modified value even after reboot) to change my screen dpi but upon reboot my dpi stays unchanged. Any ideas? I've tried to change the dpi through the adb method and that works but it shows some odd behavior in play store (some icons being too large, etc.) that other people say don't occur if you modify build.prop.
Click to expand...
Click to collapse
I'm running cataclysm as well. Changing the build prop works fine for me. Maybe it's the file manager application? I've had it happen to me when I first got my 6p and tried using root explorer. Also, make sure that you are actually saving the new build.prop and the values change before doing a FULL reboot

I had this exact problem on stock. I ended up downloading one of those DPI changer apps on the play store and it worked.. I have changed bp many times in the past. Don't know what was happening.
Sent from my Nexus 6P using Tapatalk

I tried dpi changers and build.prop editor apps and nothing works. I can change the model name and see the change reflected in the "about phone" section of settings so I know that the build.prop is being successfully edited. It just seems like my phone refuses to read the lcd_density line.

An update in case someone else runs into this problem. I can get the desired proper scaling if I change the build.prop value and use adb shell wm density with the same value in the build.prop. This fixes the scaling annoyances that I see from using adb shell wm density only to make the dpi smaller. I'm guessing the reason I can't use build.prop only to change the dpi is because I first tried to change the dpi using adb. For some reason that must trigger something and both places have to be changed.

Any way to change dpi without adb ?

I have rooted my BTV-W09 model. When I use 'adb shell wm density 320' from my computer terminal, the dpi setting is adjusted correctly, but it doesn't survive a reboot.
I tried to change the dpi setting with a build.prop editor directly on the tablet and with the Textdroider DPI app, but it doesn't work, it goes back to whatever DPI settings was implied by the display settings (from Small-400dpi to Large-480dpi).
Is there a way to permanently change the DPI setting to 320, or at least a way to do it directly from the tablet (without a computer)?

Why you not reading neighbor topics? Install Xposed, install App Settings module from here for example, activate it and setup whatever DPI you wish.

Thanks Slavon, but I'm speaking of a system-wide change, not just app by app. English is not my first language, sorry if it wasn't clear.

Sorry if I was a bit rude. Try "Pimp my rom" utility. Find it on Google Play. I worked for me and now I'm thinking of how to revert
Edit: if I got it right, this utility adds (modifies?) this key in build.prop: ro.sf.lcd_density

Not at all, I understand how it seemed like I was asking a duplicate question without looking in others threads, sorry again
And thanks a lot for the advice, I'll try Pimp my rom right away !

wlausrsker said:
Not at all, I understand how it seemed like I was asking a duplicate question without looking in others threads, sorry again
And thanks a lot for the advice, I'll try Pimp my rom right away !
Click to expand...
Click to collapse
If you just need to change density, you'd better try changing the value in build.prop first. And in case of any problems after, change the value of the key I wrote previously or restore the original build.prop from backup. Good luck.

Slavon-93 said:
If you just need to change density, you'd better try changing the value in build.prop first. And in case of any problems after, change the value of the key I wrote previously or restore the original build.prop from backup. Good luck.
Click to expand...
Click to collapse
I've tried this morning to change ro.sf.lcd_density to 320 in the build.prop and reboot. After reboot, ro.sf.lcd_density is still set to 320 but the display is still at 400dpi.
It's like ro.sf.lcd_density has no impact on the display dpi except for the display mode (tablet, phone, etc.).
Screen settings/Small + ro.sf.lcd_density=320 -> tablet mode in Chrome and 400dpi
Screen settings/Small + ro.sf.lcd_density=400 -> phone mode in Chrome and 400dpi
Screen settings/Large + ro.sf.lcd_density=320 -> tablet mode in Chrome and 480dpi
Screen settings/Large + ro.sf.lcd_density=400 -> phone mode in Chrome and 480dpi
I think maybe the DPI setting from build.prop is replaced during boot with the screen setting (Small:400dpi, Medium:440dpi, Large:480dpi). Could a init.d script could change the value after boot? I'll try tonight if the tablet allows init.d scripts to run.

Well, ok. I only quickly looked through the decompiled code. Change dpi with the app then, it'll make a backup of build. prop and try to compare both files - new and backup. I could have missed something. Just to mention, I didn't like the way tablet had behaved after changing DPI. EMUI is not well-designed for this. It's much better to set DPI for apps and leave it unmodified for system.

@wlausrsker this is covered in the apps running in phone mode thread. I posted there that the adb dpi change settings will stick after rebooting if you run the command "adb shell wm density 340 && adb reboot"*
*Use whatever density works best for you, I have found that 330 works best for me with the view mode and font set to large.

Slavon-93 said:
Change dpi with the app then, it'll make a backup of build. prop and try to compare both files - new and backup. I could have missed something.
Click to expand...
Click to collapse
johje said:
@wlausrskerI posted there that the adb dpi change settings will stick after rebooting if you run the command "adb shell wm density 340 && adb reboot"
Click to expand...
Click to collapse
johje, thanks but I tried it first and it doesn't survive reboot ("./adb shell wm density 320 && ./adb reboot" since I'm on Mac, it reboots in 400dpi).
Slavon, I've compared the files from before and after changing the dpi setting with the app, only ro.sf.lcd_density is changed, so you didn't miss anything.
Since methods successfully used by you and others don't work for me, it must be something I did differently on setting up my tablet. I used greatslon mod of TWRP and then flashed via TWRP the latest SuperSU (v2.79-SR1). Finally, I installed XposedInstaller and got xposed-v87-sdk23-arm64. Did any of you with reboot-surviving custom dpi setting used something different? (like the SRK Tool)
I'm off this weekend but I'll try next week to start over from scratch.

the reason adb change dpi and even build.prop change doesn't work is because huawei has set lcd_density in boot image. check content of /init.6x.rc
these init files are part of boot.img and will be overwritten at every boot. so what u need is a modified boot.img where this set lcd_density line is removed. Once you install that boot, you can set whatever dpi in build.prop and it will work. even adb dpi change will be persistent.
if you are on b026, i can share my edited boot.img

Thanks for the explanation bark1234, I now understand why everything I tried didn't survive reboot!
Thanks also for proposing your edited B026 boot.img but I'm on BTV-W09C100B005 and I can't find any B026 download for BTV-W09. From what I understand from other threads the latest Chinese OTA for the BTV-W09 is the BTV-W09C233B022, so I couldn't use it. Nevertheless, if you could maybe share it for others, it could help someone with the same problem on a BTV-DL09.
I tried to edit my boot.img but I'm a newbie. I've tried to extract my boot.img but I have no result with "cat /proc/mtd", so I extracted mmcblk0boot0 as a best guess. I tried to install abootimg to edit it but there's not blkid.h on Mac OS so I can't build it. If I give you what I extracted, could you maybe edit it like you did with yours? You would save me from applying at random a bunch of tutorials like I just did and hoping it will result in something usable In the meantime, I'll try and learn how to edit a boot.ini with my setup.

bark1234 said:
the reason adb change dpi and even build.prop change doesn't work is because huawei has set lcd_density in boot image. check content of /init.6x.rc
these init files are part of boot.img and will be overwritten at every boot. so what u need is a modified boot.img where this set lcd_density line is removed. Once you install that boot, you can set whatever dpi in build.prop and it will work. even adb dpi change will be persistent.
if you are on b026, i can share my edited boot.img
Click to expand...
Click to collapse
Just as an FYI, the adb dpi change initiated along with the reboot command has stuck for me after multiple reboots.

wlausrsker said:
Thanks for the explanation bark1234, I now understand why everything I tried didn't survive reboot!
Thanks also for proposing your edited B026 boot.img but I'm on BTV-W09C100B005 and I can't find any B026 download for BTV-W09. From what I understand from other threads the latest Chinese OTA for the BTV-W09 is the BTV-W09C233B022, so I couldn't use it. Nevertheless, if you could maybe share it for others, it could help someone with the same problem on a BTV-DL09.
I tried to edit my boot.img but I'm a newbie. I've tried to extract my boot.img but I have no result with "cat /proc/mtd", so I extracted mmcblk0boot0 as a best guess. I tried to install abootimg to edit it but there's not blkid.h on Mac OS so I can't build it. If I give you what I extracted, could you maybe edit it like you did with yours? You would save me from applying at random a bunch of tutorials like I just did and hoping it will result in something usable In the meantime, I'll try and learn how to edit a boot.ini with my setup.
Click to expand...
Click to collapse
If you are rooted, use flashfire app to get ur current boot.img from ur phone. and then copy it out to edit.
The tool i use for editing works on windows. i too have mac only, i have windows on vm in it.
https://www.dropbox.com/s/x46q5nzv49iauwi/Android Image Kitchen.rar?dl=1
Use above link to download tool i use.
unpackimg.bat will unpack boot img.
your init.x files will be in ramdisk, edit it there.
and then use repackimg.bat, it will create new boot.img.

johje said:
Just as an FYI, the adb dpi change initiated along with the reboot command has stuck for me after multiple reboots.
Click to expand...
Click to collapse
bark1234 said:
If you are rooted, use flashfire app to get ur current boot.img from ur phone. and then copy it out to edit.
The tool i use for editing works on windows. i too have mac only, i have windows on vm in it.
https://www.dropbox.com/s/x46q5nzv49iauwi/Android Image Kitchen.rar?dl=1
Use above link to download tool i use.
unpackimg.bat will unpack boot img.
your init.x files will be in ramdisk, edit it there.
and then use repackimg.bat, it will create new boot.img.
Click to expand...
Click to collapse
johje, it won't stuck for me, no matter how I try. Did you root by flashing the latest SuperSU? Did you installed xposed framework?
bark1234, thank you very much for the detailled explanation, I'll use Flashfire app to extract my boot.img and I'll try tomorrow at work on my Windows machine to edit it.

@wlausrsker I have not yet rooted my tablet. Once I got the dpi/phone apps issue fixed, it reduced my urgency for rooting. However, I will be rooting it soon, since a way has been found to enable the 5Ghz wireless adapter for the US version of the tablet. I will let you know if I am able to keep the dpi settings after rooting.

bark1234 said:
If you are rooted, use flashfire app to get ur current boot.img from ur phone. and then copy it out to edit.
unpackimg.bat will unpack boot img.
your init.x files will be in ramdisk, edit it there.
and then use repackimg.bat, it will create new boot.img.
Click to expand...
Click to collapse
Thanks again for the link and the explanation, it was really a painless process.
I used Flashfire app on my tablet to backup my boot.img (it resulted in a boot.lz4 file).
On my Windows machine, in a cmd window:
Code:
lz4 boot.lz4
unpackimg.bat boot
I then opened in Notepad++ the /ramdisk/init.61262.rc file to remove the line setprop ro.sf.lcd_density 560 in the on early-init and on boot sections of the file and saved.
In the cmd window:
Code:
repackimg.bat
rename image-new.img boot.img
I now have an edited boot.img to flash in TWRP. Does it seems to you that I did the editing correctly? The edited boot.img is 13.35Mb (about the same as the boot.lz4) but the extracted boot file before the unpacking was 32.77Mb. Is it normal?

13.9 is correct size. install this boot.img

For those of us following along. Does the edited boot image have to be flashed by TWRP in zip form? Or can we use Fastboot to flash it? or both will work?
I've done the edit's and have what I believe is a flashable zip. I personally like to use fastboot.
I have DPI set and holding by adb as I mentioned before but this is still nice to have.
Thanks

OP - here's a really easy way to change dpi and make it stick: https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi
I'm using it on my MediaPad M3 without issues. PS - 320 is my preferred dpi as well, but I found it caused some issues like Settings would crash. I'm using 322 now without any issue for the last couple weeks. Enjoy