Ok so here's the newb in me. I was trying to get Netflix working on my rooted NC. I made a backup of build.prop by making a copy and renaming it build.prop.bak. I went into build.prop to change the product model and manufacturer. I did that, saved and rebooted but Netflix still did not work...whatever.
I decided to give up for the night, so I went back into /system and renamed build.prop.bak back to build.prop. At this point I had 2 build.prop files. I deleted the modified one to find out that both had been deleted.
i thought a reboot (again newb mistake) would magically restore the build.prop file (hind-sight says obviously it wasn't going to). It reaches the "n" screen and then the screen flashes black.
Is there a way to fix this without reflashing? I know there this thread:http://forum.xda-developers.com/showthread.php?t=949699
I did use Titanium Backup to back up all my "stuff" on the SD card if that means anything. Again, sorry for the dumb questions.
Any help would be appreciated!
Easy method - re-flash your ROM without clearing data. Will also overwrite any other tweaks.
More difficult method. Extract the build.prop from the ROM you are using. Boot into CWM and push the build.prop using ADB.
Sent from my NookColor using XDA App
martian21 said:
Easy method - re-flash your ROM without clearing data. Will also overwrite any other tweaks.
More difficult method. Extract the build.prop from the ROM you are using. Boot into CWM and push the build.prop using ADB.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
so for easy method, are you referring to setting up a bootable SD card with Clockwork Mod and reflashing ManualNooter?
NookyLov3r said:
so for easy method, are you referring to setting up a bootable SD card with Clockwork Mod and reflashing ManualNooter?
Click to expand...
Click to collapse
My bad. I assumed you were on CM7.
Since you are on stock B&N, your options now are pretty much flash one of the stock images (and lose everything - ie. return to stock) or extract the build.prop from the stock image, boot into CWM, and ADB push the build.prop.
Sent from my NookColor using XDA App
Yeah. This is what I ended up doing...such a PITA. Oh well, at least it can be done this way. Thanks for the help!
First off this work is based on Digiblur's PRL Write Enabler from the Sprint Galaxy S3 forum. I simply modified it & packaged it for our Sprint Galaxy S4 devices.
Here is the original S3 post that this was found in... http://forum.xda-developers.com/showthread.php?t=2159054
Also, post #8 below provides additional info.
I tested it by flashing with TWRP and it worked on my stock, rooted S4 with the MDC and MDL releases.
If you're on a stock rooted Rom and not using TWRP, you can just copy the HiddenMenu.apk from inside the zip file downloaded into /system/app/ and overwrite the one that's there. (You'll need a root enabled file browser to do this of course).
Thanks to Unknownforce here is a version for MJA...
http://www.androidfilehost.com/?fid=23212708291676468
Enjoy!!
This certainly will save me from having to use CDMA WS to switch like I just did yesterday. 55014 was not working well for me in my market so I switched back to 25014.
What is write enabler?
Keeps aborting for me
THEGAMEPLAY94 said:
Keeps aborting for me
Click to expand...
Click to collapse
You mean the install of the zip?
If so, you can pull the APK out of the zip and replace HiddenMenu.apk in the system folder (make a backup first). You may want to also set the permissions to rw-r-r after replacing the system app. Reboot, then you should be good to go.
@ChadH42,
I know it seems like I'm harping on you but I'm really not..
You need to update the OP on - 1. What is this? 2. What does this do? 3. Why is this in the Development Section.. ?
A good OP leads to less questions.. Development Sections aren't for information. That would be considered a Discussion Thread that belongs in General.
Let's keep the Dev section clean from the start.
My suggestion - Edit the OP on the What's/Why's?/How To's and you won't get posts like mine.
To the OP, updated your title as [WIP], and I suggest you provided additional information so that folks aren't bricking their new devices.
I will check in, if you need anything, let me know.
What this MOD does (in case the OP takes a little while to chime in)
What this MOD does is modifies our ##DATA# (select View) menu to allow for the PRL Write option to appear and function. With this menu option, the user can change their PRL on the fly from the device itself by placing a copy of the desired PRL in the root directory of Internal Storage and name it "test.prl" (no quotes), dial ##DATA# (choose View), tap Write PRL, tap the sub-menu option Write PRL ---wait--- and then the device reboots with the test.prl PRL applied upon reboot. Not every PRL works and sometimes it takes a couple of tries.
A tip for multiple PRL options is to, of course, keep a folder of the PRLs you like and keep them labeled in there. Copy the desired PRL to proper place as needed and just remember to rename the copy to "test.prl". Switch back and forth as you please. I hope this helps clear some confusion and helps some find purpose with the MOD like I have.
For a clear set of instructions that I did not want to just copy verbatim, check the link below. Also, if you are having issues with the zip not installing in CWM, just extract the APK from the ZIP (inside the system/app folder), use Root Explorer or your favorite root-access file explorer to place the APK in the APP folder, apply the proper permissions and reboot.
Ref from the GS3: http://forum.xda-developers.com/showthread.php?t=1748516
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
jayjay7411 said:
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Did you clear Cache when you rebooted?
What ROM are you using?
ChadH42 said:
Did you clear Cache when you rebooted?
What ROM are you using?
Click to expand...
Click to collapse
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
lilmikeyv said:
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
Click to expand...
Click to collapse
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
O okay. Its currently not a necessary thing for me at the moment, just nice for when I travel to Alabama. Hopefully later on someone gets it working on deodex.
Sent from my Nexus 4 using Tapatalk 2
ChadH42 said:
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
Click to expand...
Click to collapse
I am actually running it on the Rooted Stock DeOdexed ROM. So I don't think it is an Odex/DeOdex issue...might be a Force ROM issue.
Also, moot point for Force ROM (1.0+) anyway because the PRL Write mod is already included with that.
I'm also having this problem and I'm pretty sure it was working this morning. I haven't flashed anything since then.
edit-- I tried:
1. wiping both cache's
2. killing background process "OIThiddenmenu"
neither fixed it.
I reinstalled the stock odex ROM and flashed this again and it worked.
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Unknownforce said:
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Click to expand...
Click to collapse
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
ChadH42 said:
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
Click to expand...
Click to collapse
I think TWRP can read the non Unix type characters, which is why it works on a different recovery.
I'm hoping it's a mod issue and I can just modify the mod to work universally regardless of the rom. But we'll see.
Sent from my SPH-L720 using xda app-developers app
fails in recovery for me.
says error executing updater binary in zip
in stock rooted...
Hey all,
Today is not my day...just not paying attention. I accidentally replaced my build.prop file with a modified version but forgot to change the permissions so now I am boot looping. I can still access TWRP, so I was curious if there is any way to get a new build.prop file onto the phone so I do not have to do a full wipe. Any help would be appreciated.
Also, if its possible to flash onto the phone, does anyone have the build.prop file I can use? Thanks in advance.
I guess I can also access the bootloader for fastboot, if that makes a difference. Thanks.
JustROLLIN said:
I guess I can also access the bootloader for fastboot, if that makes a difference. Thanks.
Click to expand...
Click to collapse
You can either use mfastboot to flash the entire system. IMG for the rom you are using (easiest). Or use adb from within recovery to fix permissions on the build.prop....
Good luck :good:
Edit: re flashing just system will not affect you data. Only any modifications made to /system. For instance: if you are using xposed, it will need to be reinstalled. All other apps will be unaffected.
samwathegreat said:
You can either use mfastboot to flash the entire system. IMG for the rom you are using (easiest). Or use adb from within recovery to fix permissions on the build.prop....
Good luck :good:
Edit: re flashing just system will not affect you data. Only any modifications made to /system. For instance: if you are using xposed, it will need to be reinstalled. All other apps will be unaffected.
Click to expand...
Click to collapse
Your idea spurred me to use a method I used the other day, from this thread:
http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
Worked great and saved all data, thank you!
Folks
I'm rooted and running Shamu 3.97. I used ADB to wrongly change my DPI. I ran the command
adb shell wm density 560480 (was using up arrows and by mistake didn't clear out the 560 before inputting 480)
Immediately, the phone rebooted and is stuck at the boot - little circles going around but doesn't move beyond that. Is there a battery pull that can be done on this device and what's my resolution? Do I have to somehow get into recovery and change the DPI to native 493?
Thx
You dont change DPi in bootloader or recovery, you need to edit it in build.prop or you can download dpi changer from play store
I got access to recovery but cannot boot the phone up since it just gets stuck on the rotating color circles. Any way to edit build.prop from recovery? I can see my Internal storage on my computer but can't find the build.prop file anywhere
did u do a backup on ur phone before dpi change? it could be u changed to the wrong dpi. Worst case scenario is flash back stock rom ...
sam008 said:
I got access to recovery but cannot boot the phone up since it just gets stuck on the rotating color circles. Any way to edit build.prop from recovery? I can see my Internal storage on my computer but can't find the build.prop file anywhere
Click to expand...
Click to collapse
Just re-flash the rom
Sent from my Nexus 6 using XDA Free mobile app
Dear helpful XDA-devs,
I ran into some weird display bugs which I did not experienced before. I've had the N5 and other phones and did often change my dpi without any side effect. However when I did it with my new Nexus 6 now I discovered some icons in the Play Store and "Locus Maps", for example, being oversized (see attachments).
What I did was to try to change my DPI using "Texdroider DPI" which let to an instant bootloop. So I reflashed /system from the stock image. Then I used the Nexus Root Toolkit to change the dpi via adb, what I thought worked perfectly back then (I changed it from default 560 to 530 in the end but tried a few other values as well). However, now I discovered these weird display issues in these two and one or two other apps. Any ideas what might be the reason, if it is DPI related at all, or if it worked fine when you did it yourself? Changing it back to default now does not solve the issue for me now, of course.
I'm on MOB30I, by the way. And I use TWRP+SuperSU on it. I did allow TWRP to make the /system partition writable to prevent Android from replacing TWRP. Might that be a reason why the adb-DPI-change let to bugs? Thanks for the help! :good:
To prevent people messing with the dpi many apps and Google are hard coding the sizes into the apks. I would just leave the dpi stock
zelendel said:
To prevent people messing with the dpi many apps and Google are hard coding the sizes into the apks. I would just leave the dpi stock
Click to expand...
Click to collapse
Thanks for your input. I just decides to reflash /system again (overwriting it via fastboot). But the problem persists!? How is this possible? Reflashing /system should reset DPI changes, right? Man, do I really have to reinstall all of Android? .. :crying:
karlo12 said:
Thanks for your input. I just decides to reflash /system again (overwriting it via fastboot). But the problem persists!? How is this possible? Reflashing /system should reset DPI changes, right? Man, do I really have to reinstall all of Android? .. :crying:
Click to expand...
Click to collapse
No not completely. That maybe your best bet. Also could try deleting the cache files.
You need to also change the dpi in build.prop, or you'll get those large icons.
Or if you want to go back to the old dpi, just do what you did in NRT, but change it to 560 this time.
change it in your build.prop file, then reboot for it to take affect. anyways, you will probably see other bugs with the dpi changed properly(but maybe not).