Database Develop

[MOD] Resolution (dpi) changer *now with zips for all (hopefully) legend ROMs*

I shall take no credit for any of this. Smartsreenath first put me onto the idea, and pretty much anyone if this forum could've managed it. I just had the time to do it all.
Woo! Snakehult, being a genius, has made a clever little zip that uses proper scripts to just change the required value, instead of the whole file. So! Instead of me making an insane number of zips every time ROMs are updated use these instead. Cheers Snakehult!
Attached is a zip file with a whole lot of flashable zips in it. Don't flash the zip you download, extract that one somewhere and look inside
How to use:
Download the attached zip file, and extract it to somewhere on your computer. Inside the zip are a bunch of folders, each folder named after a ROM for the HTC Legend. Navigate into the folder that shares the name of whatever ROM you are using and inside you will find 6 zip files. These zips are flashable. The the zips are names thus: xxx.zip, where xxx is a number. The lower the number, the higher the apparent resolution. Choose a zip, copy it to your SD card and flash it like any other zip. To revert back to how it was simply flash the "160.zip". This just flashes a completely un-modified version of build.prop for your ROM. Make sure you only use the zips form the correct folder for your ROM, or funny things *might* happen.
More info:
By editing the build.prop file it is possible to increase the dpi of an Android device. This essentially scales everything down, so you can fit more on the screen. This is especially nice for browsing the market and the internet; as well as improving, in my opinion, the overall Android experience. The lower the number in the name of the zip, the higher the apparent resolution. It's worth noting that this does *not* change the actual resolution of the Legend; it's still a HVGA device. So you still can't install apps designed for bigger, more powerful phones, like the HTC Desire or Nexus One. This is a somewhat flawed way of achieving this effect, and can have some ugly side effects:
Some apps simply don't scale
HTC-IME mod ends up screwed
Games *can* be rendered unplayable, but not always. Often the menu is the worst affected part.
A work around to fix a number of issues is to disable the built in compatibility mode of Android, and if I knew a way to do this through a zip, rest assured that I would. It'd save me having to explain how to do it. Alas, I don't know how, so here's how:
In your ROM look for an app called "Spare parts". If it's not there look for it in the market. If you open that app and scroll down to the bottom you will find a checkbox option for "Compatibility mode". Ensure that this is *un-checked*, then reboot. Most issues will be resolved. As I learn more about Android I shall keep an eye out for a way to force apps to scale correctly, and if I ever find one I'll update these.
I have also tried values higher than usual, just for kicks. I don't expect them to be useful, nor will I make actual zip files for them, but I went all the way up to 200; and it felt like I was using an HTC wildfire: everything was really quite cramped.
My personal favourite setup is as follows:
CM 6.1, with a 768MHz overclock
My "lcd-density" (this MOD) set to 130
Launcher Pro Plus with 5 icon rows

Below is a paste of what was the first post (when I was just trying to fix a ****-up on my part), and is now here for reference. It has all of the original build.prop files attached.
Attached is a .zip file, which you will need to extract somewhere. It's not for flashing. Within this zip are several folders, each containing a "build.prop". You'll notice that each folder is named after a ROM: Azure, NeonMOD etc. The "Based-on-stock" folder should cover these ROMs:
[ROM] Based on Official WWE_2.03.405.3 ROM + A2SD [Rev 03 - released]
[ROM] UPDATED Almost Stock Legend HTC WWE 2.03.405.3 Radio 7. 08.35.21
You'll need to use ADB to push these files, as I haven't had time to make flash-able zip's for them yet
Instructions:
1. Extract the zip to a suitable directory, and locate the appropriate build.prop
2. Copy the build.prop to your AndroroidSDK/tools folder
3. Reboot your phone into ClockworkMOD recovery and navigate the the "Partitions menu", then click "mount /system"
4. Connect your phone to the PC and start CMD/a terminal window in your AndroidSDK/tools folder
5. Run the command "adb devices" to ensure that the ADB server is running, and that the PC has detected your device correctly
6. Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
This will put your resolution back to default, but should fix everything else too. If you still want a higher resolution then follow the guides in posts 1 and 2 of the other thread. This one.
If you can't use ADB for whatever reason you'll just have to wait it out until myself or someone else create proper, flash-able, fixes. I have done this to try and quickly rectify the issue; assuming, of course, that most people in this forum can use ADB
I will make proper zips, but it's getting late for me...
Click to expand...
Click to collapse

hi
here is a zip for neonmod 0.21 with 135lcd, flashed it on my legend today with rom manager

Wow do we have a lot of ROMs...
Anyhoo, I am currently working on appropriate flashable zips for each ROM, and each ROM will have the following versions:
110
120
130
140
150
160 (original)
I'm doin' 'em as fast as I can..
EDIT:
Current thoughts:
All build by Ali Ba have nice, short build.prop files. The current record for the longest one it held by MyTouch Legend...

TheGrammarFreak said:
Wow do we have a lot of ROMs...
Anyhoo, I am currently working an appropriate flashable zips for each ROM
Click to expand...
Click to collapse
Awesome!
All our lovely ROMs are actively being used, and its great.
Thx for all hard work!

No worries, I hope I haven't missed one
Now to sign 50 60 zip files...
EDIT:
DONE! All finished. I really hope they work. I can't test them all, but there is no reason why they won't work. Lemme know either way.

nice job
thanks bro

nice
spare parts is also in neonmod

xennr3 said:
nice
spare parts is also in neonmod
Click to expand...
Click to collapse
Cool, and you can turn compatibility mode off?

TheGrammarFreak said:
Cool, and you can turn compatibility mode off?
Click to expand...
Click to collapse
sure
1234

TheGrammarFreak said:
Cool, and you can turn compatibility mode off?
Click to expand...
Click to collapse
thanks for your work! i just tried 130 dpi and it seems really good.. i'll try also others zip asap!
yes with compatibility mode off all softwares i tried work really well!

xennr3 said:
sure
1234
Click to expand...
Click to collapse
Cool, thanks for the info. I'll update the OP when I'm home
Sent from my Legend using XDA App

Wow, really cool mod Love it!
Good job!

Cool, glad you like it

Just flashed 130 for SpeedLegend and it worked like a charm
HTC_IME works here (this isnt the mod)
images dont look so good anymore and stuff, but alright
works fine
edit; TBH I find the 140 to be 'more' compatible overall, and show a better picture (ive tried all the flashables)
thats besides the orgnal setting btw, it gives the best picture by far.

Im on the same DPI and rom as you TheGrammarFreak. works great. Too bad there is no function for more icons on the homescreens with LauncherPro...

SimDroid said:
Im on the same DPI and rom as you TheGrammarFreak. works great. Too bad there is no function for more icons on the homescreens with LauncherPro...
Click to expand...
Click to collapse
Yeah it does. On your homescreen press menu, then preferences. In advanced options there is something for it.
Sent from my Legend using XDA App

i glad to hear that someone like you got the idea from my thread........good work ...........and nice job.....you will get all help from me and from my friends
FOLLOW ME http://smartsreenath.blogspot.com/

TheGrammarFreak said:
Yeah it does. On your homescreen press menu, then preferences. In advanced options there is something for it.
Sent from my Legend using XDA App
Click to expand...
Click to collapse
yeah, that is for 5 rows on a screen, but you still can't have 5 icons on a row... That's what I want. I tried ADWLauncher again, but it feels so god damn slow.

Ummm, I have 5x5 icons on my desktop with the stock ADW launcher. Just check out "Settings > ADW > Screen prefs > Desktop cols/Desktop rows"

[DISCUSS] General Questions/Problems with Theming

There seems to be a lot of things that are new when it comes to theming the Nexus S and Gingerbread in general.
A lot of us have run into various problems.
The purpose of this thread is to discuss the problems we're facing and to ask general questions regarding theming.

Issues:
1. [SOLVED] I can't flash anything unless it is the full ROM. I tried jabbawalkee's base zip but no luck.
Solution: Post 12. Thanks to ogdobber.
2. If I make a nand of a themed ROM and try to restore it, I get a bootloop. Unthemed ROM works fine.
Temporary Solution: Don't use ROM Manager to restore your themed Nandroids. Go to recovery and restore the Nand and don't reboot.
Flash the pertinent ROM again without wiping anything, then reboot. Flash the theme again.
3. How to get out of a bootloop? I've been doing the battery pull and volume up + power button does not work during a bootloop.
Solution: adb reboot recovery
4. [SOLVED] Nexus S loses signal after reboot.
After unlocking the bootloader, I used paul's Superboot to get root and used ROM manager to flash the latest CWM. All is well except every-time I reboot, I lose the signal (it shows emergency calls only) and I have to search for available networks in Mobile network settings.
Solution:
In the dialpad enter *#*#4636#*#*
Select phone information
Scroll down to preferred networks
Select "WCDMA only"
Click on Update
You need to re-enter the SMSC Carrier number. For WIND Mobile Canada, SMSC is 16135009000
Android requires you to enter this info in Hex.
Hex = 07916131059000F0
For Mobilicity Canada Hex = 07916174080001F6
In the dialpad enter *#*#4636#*#*
Select phone information
Scroll down to SMSC field, enter 07916131059000F0 and done. Then reboot.

Theming Guide:
Master™ started a guide where we could post useful stuff like the transparent notification bar & anything else in a simple Nexus S (or gingerbread guide...)
https://docs.google.com/document/d/1nZSTpSuFg_ox7cEzn5YZSx3P8nXMgly4Q-AvVRC8Lfw/edit?hl=en#
If you guys want to edit it, PM him so he can add you.
Click to expand...
Click to collapse

Stuck this useful thread

theimpaler747 said:
Stuck this useful thread
Click to expand...
Click to collapse
Thanks a lot!
Issue number 2 has been confirmed by another users. Maybe its a bug in CWM.

sonnysekhon said:
Thanks a lot!
Issue number 2 has been confirmed by another users. Maybe its a bug in CWM.
Click to expand...
Click to collapse
Could be that, I remember on my hero I tried to restore a recovery of my theme and it looped too

sonnysekhon said:
Issues:
1. I can't flash anything unless it is the full ROM. I tried jabbawalkee's base zip but no luck.
2. If I make a nand of a themed ROM and try to restore it, I get a bootloop. Unthemed ROM works fine.
3. How to get out of a bootloop? I've been doing the battery pull and volume up + power button does not work during a bootloop.
4. Nexus S loses signal after reboot.
After unlocking the bootloader, I used paul's Superboot to get root and used ROM manager to flash the latest CWM. All is well except every-time I reboot, I lose the signal (it shows emergency calls only) and I have to search for available networks in Mobile network settings.
Anyone else having this issue? Any fixes?
If you guys can provide some insight, I will be most thankful.
Click to expand...
Click to collapse
In regard to #1, you're right about that. The mount line is incorrect, I believe it needs to be changed to ext4 instead of mtd but I haven't gotten the line just right yet. I contacted PaulOBrien and Koush for assistance but didn't have much luck getting it right.
In terms of #4, I actually didn't have that same issue with his Superboot...but perhaps I overlooked it.
Hopefully we can get a theme zip base to work from. I'm hoping one of the ROM devs can jump in and maybe push us in the right direction. I'm not a code type of guy so I let the coders do the update script stuff . In the meantime, we'll just have to use the full ROM.
Thanks for this thread sonny!

On the Galaxy S I can find the data and wifi icons for the notification bar no problem, but I can't seem to find them anywhere for the Nexus S (along with a couple of others). Sorry if the answer is obvious, but I'm stuck. Could someone please point me in the right direction?

Dean-O said:
On the Galaxy S I can find the data and wifi icons for the notification bar no problem, but I can't seem to find them anywhere for the Nexus S (along with a couple of others). Sorry if the answer is obvious, but I'm stuck. Could someone please point me in the right direction?
Click to expand...
Click to collapse
system/app/SystemUI.apk

Great, thanks.

Found a solution to issue number 4, updated the post.

sonnysekhon said:
Issues:
1. I can't flash anything unless it is the full ROM. I tried jabbawalkee's base zip but no luck.
Click to expand...
Click to collapse
this is a solution to problem 1.
in the META-INF\com\google\android needs to have updater-script and update-binary
the updater-script needs the following line
Code:
run_program("/sbin/busybox", "mount", "/system");
attached is a meta-inf. use it in place of your current one for flashing themes

Thanks ogdobber.

Hi,
I'm a newb to theming. Can anyone point me to the right direction to change my stock news widget to transparent?
Thanks in advance

cyc1120 said:
Hi,
I'm a newb to theming. Can anyone point me to the right direction to change my stock news widget to transparent?
Thanks in advance
Click to expand...
Click to collapse
start with the 2 links below, you basically need to change the transparency level on the widget_background in the drawable(hdpi) folder. but it is not that easy because it is a .9 png (unless you go 100%)
[GUIDE] Want to learn how to theme?
The Ultimate Android Themeing Guide
Here is a thread by rori that he themes a bunch of stuff to transparent smoke http://forum.xda-developers.com/showthread.php?t=731625

I can't for the life of me try to figure out how to make an object in photoshop have a transparent background. I make the background transparent, add the object (eg: a number) and everything looks great. Then once I flatten the image the transparency disappears. What I don't get is up until I flatten it, the whole background is transparent. I'm completely baffled, can anyone offer an idiot some help?

kenvan19 said:
I can't for the life of me try to figure out how to make an object in photoshop have a transparent background. I make the background transparent, add the object (eg: a number) and everything looks great. Then once I flatten the image the transparency disappears. What I don't get is up until I flatten it, the whole background is transparent. I'm completely baffled, can anyone offer an idiot some help?
Click to expand...
Click to collapse
What image is it? And by flatten it, do you mean you are making it an indexed image?

theimpaler747 said:
What image is it? And by flatten it, do you mean you are making it an indexed image?
Click to expand...
Click to collapse
Its a number for a Beautiful widgets clock skin. By flatten it I mean in photoshop CS5 when you make an image with multiple layers (the layers get created automatically when I try to add anything, in this case text) in order to save it as anything but a .psd you have to flatten it (IE force all of the layers into one).

kenvan19 said:
Its a number for a Beautiful widgets clock skin. By flatten it I mean in photoshop CS5 when you make an image with multiple layers (the layers get created automatically when I try to add anything, in this case text) in order to save it as anything but a .psd you have to flatten it (IE force all of the layers into one).
Click to expand...
Click to collapse
Never save it as a psd for edits on android Save it as a .png

theimpaler747 said:
Never save it as a psd for edits on android Save it as a .png
Click to expand...
Click to collapse
Exactly, I'm trying to save it as a png but in order to do that I have to flatten the image which causes the transparency of the background to disappear.

[MOD/HOW-TO] Remove hard key vibes via android.policy.jar

I thought I'd offer my solution to disabling the hard key vibrations on the Atrix since other people might find this useful. This method differs from the other solutions in that it doesn't tamper with your Silent Mode vibrations (like StreakVibrations does) and it's code based, so it shouldn't tamper with any themes you have installed (like the framework-res.apk method). It is firmware dependent though since it's a code modification.
You'll need an android.policy.jar modified for your firmware.
What I'm doing is I'm modifying the method called performHapticFeedbackLw, and telling it to skip triggering the vibrate pattern for all effects (there are 5) except for keyboard taps. Long press vibe, virtual key vibe, safe mode disabled vibe, and safe mode enabled vibe will no longer trigger... Incidentally, does anyone know what safe mode on this phone refers to?
To use the file, you need to be on Bell, Telstra, GingerBlur, Gladiatrix or stock ATT 1.8.3 firmware, and be deodexed. Can you copy the file to your phone without being deodexed? I don't know. I'm a programmer, but an Android newbie so just to be safe it's best if you're deodexed.
Before you try anything, obviously make sure you are backed up. At least copy your existing android.policy.jar so that you can restore it if necessary.
All you need to do is either:
a) Run the novibes.bat script packaged in the zip. There are a couple prerequisites:
1. Make sure to set your USB connection to "None" on your phone.
2. On your phone, go to Settings > Applications > Development and make sure USB debugging is turned on.
3. Plug your phone into your PC and let it install any necessary drivers.
4. Then you can run novibes.bat.
or
b) Follow the steps outlined below to do it manually:
1. Replace /system/framework/android.policy.jar with the one that I've attached.
2. Make sure the permissions of the file are set to rw-r--r-- (thanks for reminding me, Meloy and for correcting, natboy!). The easiest way is to use Root Explorer, long press the file, choose permissions, and set owner: read/write, group:read, others:read. Otherwise, use Terminal and type "chmod 644 /system/framework/android.policy.jar" without the quotations.
3. Reboot.
For those not on stock Bell, I'd be willing to modify your android.policy.jar and post it here if you provide somewhere for me to download it, and specify what firmware it comes from. It's quite quick to do once you're set up so I don't mind. Alternatively, make the change yourself:
1. Download baksmali and smali (both .jars and scripts, total 4 files).
2. Copy /system/framework/ from your phone to your computer.
3. Copy all the files from step 1 to the framework directory from step 2 on your computer.
4. Unzip android.policy.jar and copy its classes.dex file to the framework directory on your computer.
5. From the command line, navigate to the framework directory and run "./baksmali classes.dex". It will create a directory named "out".
6. Open "out/com/android/internal/policy/impl/PhoneWindowManager.smali" in a text editor.
7. Search for a method called "performHapticFeedbackLw". Go to near the bottom of that method, and you will see the Dalvik bytecode representation of a switch statement:
Code:
.sparse-switch
0x0 -> :sswitch_27 #This is for long press vibe
0x1 -> :sswitch_35 #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :sswitch_3b #This is for safemode disabled vibe
0x2711 -> :sswitch_3e #This is for safemode enabled vibe
.end sparse-switch
8. Here's an example of how you might want it to change. Basically you want to replace the original goto labels with one that causes the method to step out without triggering a vibe, and that notifies the calling method there was no vibe by returning false. The label to use is called ":cond_1d":
Code:
.sparse-switch
0x0 -> :cond_1d #This is for long press vibe
0x1 -> :cond_1d #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :cond_1d #This is for safemode disabled vibe
0x2711 -> :cond_1d #This is for safemode enabled vibe
.end sparse-switch
9. From the command line in the framework directory, run "./smali -o classes.dex out". You now have a new classes.dex that has your modification.
10. Zip up the classes.dex with the META-INF directory from your original android.policy.jar. Rename the zip to android.policy.jar.
11. Copy the new file to your phone and reboot.
12. At this point you should be done.

Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App

n1ckr0th said:
Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.

bearsfan172 said:
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.
Click to expand...
Click to collapse
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.

n1ckr0th said:
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.
Click to expand...
Click to collapse
Yes, this would work perfectly fine on ATT. You can either follow the instructions I provided, or if you like you can post /system/framework/android.policy.jar from your phone somewhere and pm me the link so I can download it and I'll do it for you. Also mention what firmware you're on. I just don't want to download hundreds of MB of firmwares which is why I didn't set one up for all the ATT firmwares.
That other method requires editing a file that is guaranteed to change with any theme you install. That means anytime you change themes you'll need to edit that .apk yourself, or wait for someone to bring the change over. android.policy.jar is unlikely to change for themes.

Ok, I've posted a version for ATT 1.8.3 that was given to me by n1ckr0th.
n1ckr0th, let me know whether it works fine or not. There should be no problem, it looked just like the other 2 versions I modified.
Incidentally, he's using GingerBlur 3.5 so anyone on stock be careful (ie. copy your original file to somewhere else on your phone). It shouldn't matter at all because from what I see, there aren't any resources to modify in android.policy.jar so GingerBlur's should be the same as stock. At any rate, it won't brick your phone if you put the wrong one on. I put Telstra's on my phone by accident and it just messed up the the graphics on screen (maybe because the addresses were all wrong for my phone). You can still use adb, or sshdroid to copy and replace with your original android.policy.jar.

please delete

meloy said:
Don't use this on AT&T 1.83!
After the replace and reboot my phone was really laggy and some applications doesn't start anymore (camera, contacs for example). After i have replaced it with the original file i have still the same problem.
My phone config:
- SBF 1.83
- rooted (GingerBreak 1.20)
- sideloading enabled (GladEnabler)
- GladiAtrix 3 b0.2 ROM
- LauncherPRO
- GingerBread Theme only
Click to expand...
Click to collapse
What? That can't be right, if you still have the same problem after copying the original file, that means that you must have done something wrong. It's a single file change, provided you returned the file to the original, it will be back to the way it was. How did you copy the file? And also, are you deodexed? As mentioned in the original post, you have to be deodexed, because I don't know the results of using it on a non-deodexed system. Your posted config makes it sound like you might not be.

Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.

meloy said:
Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.
Click to expand...
Click to collapse
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?

maledyris said:
Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.

meloy said:
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.
Click to expand...
Click to collapse
Interesting, that never occurred to me. I usually go into terminal and type in reboot to reboot my phone. I think I'll add that to my phone too...

maledyris said:
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.

n1ckr0th said:
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.
Click to expand...
Click to collapse
Hmm, how far does it get? Do you at least get to the boot animation? I notice that it may sit at the boot animation for a really long time after changing a file sometimes. Probably updating the cache or something. It's odd that it wouldn't work for you considering it's your file and it worked for meloy. How did you copy the file over?
If you try again, delete the original file, so you can be sure it's no longer there, then try the copy again.

I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?

I have no problems with this mod. It works all fine.

Been waiting on this mod. Streakvibrations has me missing my notification vibes. Thank you

It gave me a red light on boot, stuck at Motorola logo for infinity. I booted into recovery and reflashed gb 3.5 to fix it. Ill try your idea of deleting it then moving the new one.
Sent from my MB860 using XDA App
EDIT: still didnt boot, had to flash again..

I'm getting the flashing red light and rebooting as well. I can't get into CWM though, going to have to flash a SBF. Only think I can think of is maybe the Dalvik cache needs to be wiped before rebooting?
Edit: I'm on an AT&T phone and used GB to deodex as well.. maybe it's not catching all the files..

lurchbyrep said:
I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?
Click to expand...
Click to collapse
Are you on stock 1.83? Now that we know that android.policy.jar has some mods built into it for Gingerblur pseudo rom, the att 1.83 file I posted probably isn't ideal for stock users.
If you're on stock, maybe you could post your android.policy.jar somewhere and pm me the link to download. Then I could put together a pure stock att one when I get home.
Sent from my MB860 using XDA App

[MOD] PRL Write Enabler for Sprint Galaxy S4 [MDC][MDL][MJA]

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...

Phone turns off after boot screen

So I was trying to follow a tutorial for installing Japanese apps on a non-JP phone, but after I modified the values and rebooted the system, the phone started turning off after the boot screen. I still have access to recovery and download mode. Any idea of what could have gone wrong? Thank you in advance.
Since I can't post images or outside links, I'll paste the text up to what I did here:
1. Run RootExplorer and navigate to /system. Click the button to remount as r+w.
2. Long press on build.prop and select Copy. Paste it into the same folder or another folder to make a backup. You DO NOT want to lose this.
3. Long press on build.prop and select Edit in Text Editor.
4. Find and modify the following values (jacked from an NTT DoCoMo SHARP SH12C). Be aware they may not be grouped logically, so search the whole file if need bed. If a value doesn't exist, you will need to create it:
ro.build.id=S7140
ro.build.display.id=01.01.02
ro.build.version.incremental=01.01.01
ro.build.version.release=2.3.3
ro.product.model=SH-12C
ro.product.brand=DOCOMO
ro.product.name=SH12C
ro.product.device=SH12C
ro.product.board=SH12C
ro.product.manufacturer=SHARP
ro.product.locale.language=ja
ro.product.locale.region=JP
ro.mtp.manufacturer=NTT DOCOMO, Inc.
ro.sh_build.id=S7301
ro.sh_build.version.incremental=01.01.02
ro.build.product=SH12C
ro.build.description=SH12C-user 2.3.3 S7140 01.01.01 release-keys
ro.build.fingerprint=DOCOMO/SH12C/SH12C:2.3.3/S7140/01.01.01:user/release-keys
5. Close Root Explorer.
6. Open System->Applications->All and scroll down to Market. Click Force Close and Clear Cache.
7. Power off your phone. You absolutely must reboot your phone in order to populate the new values we just made in the RAM.​

bunnyrice said:
So I was trying to follow a tutorial for installing Japanese apps on a non-JP phone, but after I modified the values and rebooted the system, the phone started turning off after the boot screen. I still have access to recovery and download mode. Any idea of what could have gone wrong? Thank you in advance.
Since I can't post images or outside links, I'll paste the text up to what I did here:
1. Run RootExplorer and navigate to /system. Click the button to remount as r+w.
2. Long press on build.prop and select Copy. Paste it into the same folder or another folder to make a backup. You DO NOT want to lose this.
3. Long press on build.prop and select Edit in Text Editor.
4. Find and modify the following values (jacked from an NTT DoCoMo SHARP SH12C). Be aware they may not be grouped logically, so search the whole file if need bed. If a value doesn't exist, you will need to create it:
ro.build.id=S7140
ro.build.display.id=01.01.02
ro.build.version.incremental=01.01.01
ro.build.version.release=2.3.3
ro.product.model=SH-12C
ro.product.brand=DOCOMO
ro.product.name=SH12C
ro.product.device=SH12C
ro.product.board=SH12C
ro.product.manufacturer=SHARP
ro.product.locale.language=ja
ro.product.locale.region=JP
ro.mtp.manufacturer=NTT DOCOMO, Inc.
ro.sh_build.id=S7301
ro.sh_build.version.incremental=01.01.02
ro.build.product=SH12C
ro.build.description=SH12C-user 2.3.3 S7140 01.01.01 release-keys
ro.build.fingerprint=DOCOMO/SH12C/SH12C:2.3.3/S7140/01.01.01:user/release-keys
5. Close Root Explorer.
6. Open System->Applications->All and scroll down to Market. Click Force Close and Clear Cache.
7. Power off your phone. You absolutely must reboot your phone in order to populate the new values we just made in the RAM.​
Click to expand...
Click to collapse
You just added those lines or you replace its values on already existing?

shut_down said:
You just added those lines or you replace its values on already existing?
Click to expand...
Click to collapse
I replaced the ones that already existed and added the rest. I think the ones that had to be added were
ro.mtp.manufacturer=NTT DOCOMO, Inc.
ro.sh_build.id=S7301
ro.sh_build.version.incremental=01.01.02

bunnyrice said:
I replaced the ones that already existed and added the rest. I think the ones that had to be added were
ro.mtp.manufacturer=NTT DOCOMO, Inc.
ro.sh_build.id=S7301
ro.sh_build.version.incremental=01.01.02
Click to expand...
Click to collapse
We use ro.build.id, not ro.sh_build.id. Try to remove that sh_.
ro.mtp.manufacturer=NTT DOCOMO, Inc.
ro.build.id=S7301
ro.build.version.incremental=01.01.02

shut_down said:
We use ro.build.id, not ro.sh_build.id. Try to remove that sh_.
ro.mtp.manufacturer=NTT DOCOMO, Inc.
ro.build.id=S7301
ro.build.version.incremental=01.01.02
Click to expand...
Click to collapse
Thank you very much. Can I edit it through my computer, or will I have to do a reset?

bunnyrice said:
Thank you very much. Can I edit it through my computer, or will I have to do a reset?
Click to expand...
Click to collapse
You can edit, and put it back in system, where it was. But permissions must be 644, you will get a bootloop if it is not like that.

shut_down said:
You can edit, and put it back in system, where it was. But permissions must be 644, you will get a bootloop if it is not like that.
Click to expand...
Click to collapse
My computer's no longer recognizing the phone when I plug the USB in. I tried wiping the user data and cache, but that didn't work either... Is there any other way to edit it?

bunnyrice said:
My computer's no longer recognizing the phone when I plug the USB in. I tried wiping the user data and cache, but that didn't work either... Is there any other way to edit it?
Click to expand...
Click to collapse
Go to recovery, and use this:
http://forum.xda-developers.com/showthread.php?t=2105707

shut_down said:
Go to recovery, and use this:
http://forum.xda-developers.com/showthread.php?t=2105707
Click to expand...
Click to collapse
Thank you so, so much. I will now try modifying the values the way you've said.

bunnyrice said:
Thank you so, so much. I will now try modifying the values the way you've said.
Click to expand...
Click to collapse
You can change permissions in that app by selecting build.prop and hit Files>Change attributes. To 644.

shut_down said:
You can change permissions in that app by selecting build.prop and hit Files>Change attributes. To 644.
Click to expand...
Click to collapse
It worked! I really can't thank you enough, both for saving my phone from my inexperient hands and actually making it work. Thank you.