*Updated to Sensation fingerprint*
Can't download or even play certain apps or games such as Gameloft's N.O.V.A.3?
Follow the below steps to make your HTC ETO 4G LTE disguise itself as a HTC Sensation to get the best of the Google Play Store.
Tested working on stock ROM with Root and SU.
Modern Combat 3, N.O.V.A. 3 tested to work perfectly. All other Gameloft games should work and show up in market.
Please note, if you have a custom ROM, you probably do not want to use this. It will overwrite your ROM creator's settings. It will probably work, but it will take away certain features of their build.prop tweaks.
Users are saying that this kills Google Wallet. I cannot confirm this since I don't use it. Use at your own risk. Please update us if it does or not.
You must be rooted!
BACKUP YOUR CURRENT BUILD.PROP
1. Clear Google Play Store Data (Settings, Apps, All, Google Play Store, Clear Data)
2. Download the build.prop I have attached at the end of this post.
3. Unzip it
4. Use a file explorer such as ES File Explorer and navigate up to /system
5. Copy and paste it over your current build.prop in/system
6. Reboot phone
Clear as mud
*Edit*
Removed manual way to update (Hardcore DIY'ers can Google it)
Updated build.prop to HTC Sensation (pyramid). Apps were showing up before with the Galaxy SII build.prop changes, but downloaded files weren't compatible with our phone. Sensation makes for a better fingerprint.
Thanks for this! Only one thing:
People need to understand that if they're not on the stock ROM (that this build.prop is based off of) that they are risking losing whatever modifications their ROM devs added into build.prop.
Different devs do different things in there....blindly replacing your ROM's build.prop is usually a bad idea.
smw6180 said:
Thanks for this! Only one thing:
People need to understand that if they're not on the stock ROM (that this build.prop is based off of) that they are risking losing whatever modifications their ROM devs added into build.prop.
Different devs do different things in there....blindly replacing your ROM's build.prop is usually a bad idea.
Click to expand...
Click to collapse
True... which is why it's important to manually make the change to the build.prop on your rom. Takes a little work, but worth it.
If you follow these instructions, you cant mess it up.
smw6180 said:
Thanks for this! Only one thing:
People need to understand that if they're not on the stock ROM (that this build.prop is based off of) that they are risking losing whatever modifications their ROM devs added into build.prop.
Different devs do different things in there....blindly replacing your ROM's build.prop is usually a bad idea.
Click to expand...
Click to collapse
Meaning such as CM and MIUI and such? Anything based off of 1.13 or even 1.12 is OK right? Im just curious about that, thats all. Ive been wanting to plat Tigers Woods, and for a $5.24 game, im pretty pissed they wont even remburse me for that ****. Thannks brotha. Thanks to the OP as well
reverepats said:
Meaning such as CM and MIUI and such? Anything based off of 1.13 or even 1.12 is OK right? Im just curious about that, thats all. Ive been wanting to plat Tigers Woods, and for a $5.24 game, im pretty pissed they wont even remburse me for that ****. Thannks brotha. Thanks to the OP as well
Click to expand...
Click to collapse
Meaning anything that's not stock. Viper, PokeROM, Fresh, whatever.
Each developer tends to make their own build.prop edits. If you just make the changes to the stock build.prop that the OP attached and you're running any custom ROM you're overwriting whatever they may have done. Unless your Dev puts the change into his/her ROM, or someone makes a flashable zip for you, for your ROM, just grabbing a random build.prop and using it because it has the edits you want is a bad idea.
I'm using Joelz9614 rom just manually edit. A safe rule is never paste over the prop when you can do the edits yourself if you're not sure if it's modded
Sent from my GT-P6210 using Tapatalk 2
Oh and great post op. You're a life saver!
Sent from my GT-P6210 using Tapatalk 2
Kidromulous said:
I'm using Joelz9614 rom just manually edit. A safe rule is never paste over the prop when you can do the edits yourself if you're not sure if it's modded
Sent from my GT-P6210 using Tapatalk 2
Click to expand...
Click to collapse
Exactly.
One more note guys this will kill google wallet mine was still stuck so not sure about those already set up but changing your device to a non wallet device means no wallet. Just thought I'd add this though we are bound to see people ask about it anyway. Perhaps that can be added to the op
Sent from my GT-P6210 using Tapatalk 2
so i screwed up! i edit manually didnt work maybe i mis spelled.. and then thought i could just flash that build prop posted...and i had just flashed FRESH 5.0 and just kinda now read that i should have changed the build prop with that rom untill the developer had that built in.. any ideas what the hell i can do now?
BAttitude7689 said:
so i screwed up! i edit manually didnt work maybe i mis spelled.. and then thought i could just flash that build prop posted...and i had just flashed FRESH 5.0 and just kinda now read that i should have changed the build prop with that rom untill the developer had that built in.. any ideas what the hell i can do now?
Click to expand...
Click to collapse
OPen the zip for the Fresh ROM, go to /system and pull out build.prop. Push that to your phone, and change the permissions.
Or, flash Fresh over your current installation without wiping.
You could push the original build.prop to your phone from the Rom you are using or reflash
Not Sent
Kidromulous said:
One more note guys this will kill google wallet mine was still stuck so not sure about those already set up but changing your device to a non wallet device means no wallet. Just thought I'd add this though we are bound to see people ask about it anyway. Perhaps that can be added to the op
Sent from my GT-P6210 using Tapatalk 2
Click to expand...
Click to collapse
Won't Gameloft eventually make the market change so that the One-X variants are downloading the HD versions? I would only do this if you have to have it now...
BAttitude7689 said:
so i screwed up! i edit manually didnt work maybe i mis spelled.. and then thought i could just flash that build prop posted...and i had just flashed FRESH 5.0 and just kinda now read that i should have changed the build prop with that rom untill the developer had that built in.. any ideas what the hell i can do now?
Click to expand...
Click to collapse
You could reflash your ROM or ask the dev for this build.prop file to paste over your corrupted one.
it was a damn brick and i could even get to recovery screen... i did volume down and power and the bottom buttons would flash and then finally stopped i then press volume down and power and magiclly i got to the bootloader then the recovery and reflasheed
You removed the changes that needed to be made manually? I applied the Samsung changes and now would like to apply the new sensation changes. I guess I'll dig through the build.prop and check which lines are different
To the OP, why would you remove the changes to the file that can easily be done manually??? It's a simple mod that can be done. Users NOT in the know will replace their their file with yours, only to end up with a mess because they are on a different rom that has somewhat different parameters than what's in your attachment.
gpz1100 said:
To the OP, why would you remove the changes to the file that can easily be done manually??? It's a simple mod that can be done. Users NOT in the know will replace their their file with yours, only to end up with a mess because they are on a different rom that has somewhat different parameters than what's in your attachment.
Click to expand...
Click to collapse
Well I hope these heed his warning or perhaps the thread and they should be ok.
Sent from my EVO using Tapatalk 2
Deleted
fldash said:
Won't Gameloft eventually make the market change so that the One-X variants are downloading the HD versions? I would only do this if you have to have it now...
Click to expand...
Click to collapse
I have nova 3 now so I needed to do it before this it didn't work on my phone
Sent from my EVO using Tapatalk 2
Related
*** This thread is now outdated ***
Please follow this link for a much better solution - Also, be sure to hit the Thanks! button to show your support for DizzyDen's excellent work!
********************************************************************************
I have removed all the files from this post and I encourage everyone to migrate to DizzyDen's superior solution. If for some reason you are unable to use Dizzy's tool you can PM DizzyDen or myself (Martian21) and one of us should be able to get you want you need.
********************************************************************************
[Original Thread]
I have seen several threads regarding this topic and thought I'd try to consolidate as much as I can in one place.
Credit for the original IMEI work goes to mthe0ry His original thread is here.
Because the NOOK Color is not a phone it does not have an IMEI number. This is why some apps that check for an IMEI number do not work on the NOOK.
Thanks to the work of mthe0ry and now DizzyDen it is possible to modify the framework.jar file in order to create a fake IMEI number on the NOOK Color. Doing so will allow programs such as Swype Beta, the free version of the XDA app, HBO GO, and the Xfinity app to work on the NOOK Color.
Unfortunately you need to have a framework.jar file that matches the ROM you are running as changes to the framework between ROMs can (and probably will) cause problems.
[See DizzyDen's thread for the IMEI generator tool]
*** This is mostly obsolete now that Dizzy's tool handles replacing the framework.jar file and backs up your original file - but I will leave it here just in case it is still useful to someone. ***
Installation:
You will need a file manager with Root access such as Root Explorer.
Download the framework.jar file for your Rom.
Unzip the file and transfer the framework.jar file to your NOOK Color.
Navigate to /System/framework using Root Explorer.
Mount the /System/framework folder R/W.
Rename the original framework.jar to framework.jar.bak.
Using Root Explorer, copy the new framwork.jar file.
Paste the modified framework.jar into /System/framework.
Long press the newly copied framework.jar and select "Permissions".
Change the permissions to match framework.jar.bak [rw-r--r--].
Mount the /System/framework folder R/O.
I recommend you reboot your NOOK although resetting the launcher may be enough.
For those that used my original files or the ones from mthe0ry, the original IMEI used in those files is "12-34567-89012-45". If you wish to continue using this IMEI number [NOT RECOMMENDED] you can manually enter it into Dizzy's tool.
Martian21
Request pls
I know that nightly 78 was the last nightly that runs on .29 kernel all the new nightlys 80,82,83 and 84 need uboot 1.2 and .32 kernel. I have read that some people have been experiencing problems on these builts. Also being that .32 kernel is still label beta i would like to ask you if you could please make a framework for nightly 78. I have attached the framework file from my nightly 78. Thank you
Finally was able to reboot after copying framework82. Was able to sign in but have yet to play a movie. I get stuck in the spinning circle.
Sent from my Vision using XDA Premium App
MACLUIS1 said:
Finally was able to reboot after copying framework82. Was able to sign in but have yet to play a movie. I get stuck in the spinning circle.
Sent from my Vision using XDA Premium App
Click to expand...
Click to collapse
I did a total wipe, stock 1.2 install, then a second total wipe before n82. I then added the modded framework and HBO GO worked really well! But, after adding Dal's 5/13 OC, I then got the spinning circle problem you describe.
I tried re-flashing just n83 to fix it (without Dal's OC), and re-installing the modded framework, but the spinning circle problem remains.
I can't say for sure that the OC kernel broke it -- it could be one of a dozen apps I installed? -- but it's certainly the leading culprit in my case. The 5/13 OC kernel also appeared to break a few of my other apps as well (360 Live failed too, but started working again after I returned to vanilla n83).
I'm going to start the entire process over again tonight to try and narrow down the problem...
I have the 5/13 OC installed but HBO GO is now working on my Nook. Just need to uninstall and reinstall HBO GO. Worked like a charm for me.
Sent from my Vision using XDA Premium App
MACLUIS1 said:
I have the 5/13 OC installed but HBO GO is now working on my Nook. Just need to uninstall and reinstall HBO GO. Worked like a charm for me.
Sent from my Vision using XDA Premium App
Click to expand...
Click to collapse
Didn't work for me -- still stuck on spinning circle after intro clip plays.
I used TiBu to wipe data, uninstall, then install app. Did you reboot in between, or take any other steps?
martian21 said:
I am using the same IMEI of "12-34567-89012-45" that mthe0ry used.
Click to expand...
Click to collapse
So every one gets the same IMEI?
We are going to fix this in CM soon. Please don't break every other program that uses IMEI to identify a UNIQUE device! I suggestion that no-one uses this. You are really playing with fire here.
nemith said:
So every one gets the same IMEI?
We are going to fix this in CM soon. Please don't break every other program that uses IMEI to identify a UNIQUE device! I suggestion that no-one uses this. You are really playing with fire here.
Click to expand...
Click to collapse
I do appreciate your warning (and, as always, all your hard work), but Dal came out and stated plainly that an IMEI solution would not get added to cm7 builds, so the rest of us took his word for it and had to solve the problem some other way.
Now, if you're saying that the solution WILL be built into one of the next few nightlies -- with unique IMEI's -- then that's fantastic!!
However, without it, there's currently no other way to run HBO GO, Swype, etc -- unless we compile our own framework.jar... which isn't an option for some of us noobs.
Has work already begun on a better solution?
paleh0rse said:
I do appreciate your warning (and, as always, all your hard work), but Dal came out and stated plainly that an IMEI solution would not get added to cm7 builds, so the rest of us took his word for it and had to solve the problem some other way.
Now, if you're saying that the solution WILL be built into one of the next few nightlies -- with unique IMEI's -- then that's fantastic!!
However, without it, there's currently no other way to run HBO GO, Swype, etc -- unless we compile our own framework.jar... which isn't an option for some of us noobs.
Has work already begun on a better solution?
Click to expand...
Click to collapse
I meant the static IMEI hack as presented in this thread. This hack will not be added to CM7.
We are working on a real solution as we speak.
dalingrin said:
I meant the static IMEI hack as presented in this thread. This hack will not be added to CM7.
We are working on a real solution as we speak.
Click to expand...
Click to collapse
You're a good man, thank you!
dalingrin said:
I meant the static IMEI hack as presented in this thread. This hack will not be added to CM7.
We are working on a real solution as we speak.
Click to expand...
Click to collapse
This is great news!!!
I will cease and desist as soon as it it completed. Obviously the best thing would be for people to follow mthe0ry's instructions and do this themselves (it's really not that hard) using their own unique IMEI number. That said I'm happy to continue the "hack" method for those who don't wish to do it themselves.
Yes, having multiple devices with the same IMEI could become problematic but so far it's worked for the apps people want. I do appreciate the warning as I probably wasn't as clear about the "hack" nature of this in the OP as I should have been.
Martian21
jzibit17 said:
I know that nightly 78 was the last nightly that runs on .29 kernel all the new nightlys 80,82,83 and 84 need uboot 1.2 and .32 kernel. I have read that some people have been experiencing problems on these builts. Also being that .32 kernel is still label beta i would like to ask you if you could please make a framework for nightly 78. I have attached the framework file from my nightly 78. Thank you
Click to expand...
Click to collapse
Attached:
enjoy
slide it
please disregard below. in reading the thread better I can see it's not for swype at all but for setting the nook up with an IMEI.
I don't mean to be rude, but why not just use slide-it? I'm cognisant of the simplicity of swype as I use it daily on my Galaxy S, but slide-it is nearly as good and works without fault on the nook (rooted stock and CM7) without any mods.
smiley1960 said:
please disregard below. in reading the thread better I can see it's not for swype at all but for setting the nook up with an IMEI.
I don't mean to be rude, but why not just use slide-it? I'm cognisant of the simplicity of swype as I use it daily on my Galaxy S, but slide-it is nearly as good and works without fault on the nook (rooted stock and CM7) without any mods.
Click to expand...
Click to collapse
Many of us use this hack for HBO GO, not just Swype...
First zip file is for which Rom?
Sent from my NookColor using Tapatalk
RASTAVIPER said:
First zip file is for which Rom?
Click to expand...
Click to collapse
Opps - Typo. It is for CM7 Stable 7.03
I added a note to the first post. I'll try to fix the file name when I get home tonight. I'm sure there will be 1 or two more nightly builds as well.
paleh0rse said:
Many of us use this hack for HBO GO, not just Swype...
Click to expand...
Click to collapse
It's also needed for a number of Gameloft titles.
Rodney
Concerns about unique devices make me wonder... I have a broken HTC Kaiser sitting on a shelf above my desk. It will never again be a functional device, but yet it has it's own unique IMEI.
Does the IMEI alone tell apps anything about what sort of device belongs to the number? If not, then it seems that I could use the IMEI from that Kaiser or the broken G1 I have.
It doesn't seem like these apps know anything about the device from the IMEI alone, given that people have been implementing this fix with no repercussions. That means apps probably don't check any hypothetical IMEI-device info against what's recorded in the build.prop, so this seems like a safe, workable solution for those of us with defective devices on our shelves.
Is there a way to make this work on a ManualNootered nook with 1.2, or does it only work if you have a custom rom.
Thanks
integrate in CM7
could you not ask the maintainers of CyanogenMod to integrate this in the future nightlies?
they would probably welcome the added functionality
So I updated all of the mods I use in my ROM for the new 2.17.651.5 base. I thought it might be helpful to others if I put them all in one place. Most of these mods were made using threads by SteelH and others who actually tell you how these things are done. If anyone wants to know how a certain mod is made (of those listed below), PM me or post and I'll explain how I did it.
Flash these at your own risk (good idea to make a backup of /system and /data before flashing).
The mods in this post are for deodex ROMs.
You can find mods for odex ROMs here. Thanks Rydah805!
7in1_Reboot_2.17.651.5.zip adds Power menu and reboot options (not sure if hot restart works correctly).
Download DEODEX
HDR_Panorama_2.17.651.5.zip adds HDR and Panorama modes to HTCCamera.
Download DEODEX
MMSSize_SMSBackup_SMSSecureBox_2.17.651.5.zip adds the mirror entry back to the app drawer, adds 1M, 2M, 5M MMS, adds SMS backup option, and SMS Secure Box option. The MMS size should be flashable to make it work thanks to Vin255764. The mirror app will still require you to place default.xml from the flashable .zip into /system/customize/MNS/ of your ROM before you flash your ROM. I'll try to find how to add the mirror app to a current ROM. If you really want all of these features and know how to backup/restore your stuff, just clear /data after flashing the .zip and it should work ok from my limited understanding (I just make my own ROMs ).
Download DEODEX
RemoveUSBDebugging_2.17.651.5.zip removes the USB debugging icon.
Download DEODEX
RoamOnlyOption_2.17.651.5.zip adds Roam Only under Settings-Wireless&Networks-Mobile Network Settings-Roaming.
Download DEODEX
SprintHotSpotHack_2.17.651.5.zip changes two 0's to 1's so you can use this without paying for it.
Download DEODEX
SystemUI_mods_2.17.651.5.zip removes GPS recticle, removes recent apps from pulldown, changes to display 3G/1x properly, and adds extended quick settings.
Download DEODEX
SystemUI_mods_WithRecentApps_2.17.651.5.zip is the same as above without recent apps removed.
Download DEODEX
Please post if something doesn't work and ALSO if things do work .
Thanks to everyone who has figured out how to do these mods and Brut.all for making apktool so easy to use.
<3
Sent from my NookColor using Tapatalk
thank you! i've come to rely on roam only now that i spend part of my day in a spotty sprint area.
How hard would it be for you to make that systemui.apk but with recent apps?
Might be silly question but I'm guessing it doesn't matter whether I'm using an odex or deodex version of .5 right? I can flash these on either one? Haven't quite figured out the odex/deodex thing but I believe that only affects themes. Thanks
chrisfales said:
Might be silly question but I'm guessing it doesn't matter whether I'm using an odex or deodex version of .5 right? I can flash these on either one? Haven't quite figured out the odex/deodex thing but I believe that only affects themes. Thanks
Click to expand...
Click to collapse
Sorry, these are all deodex. I'll update OP. I think if you delete the .odex and use the deodex, it may work (but I don't know to be honest).
Thanks for these mods and your quick response!!! Any chance for odex versions? My phone seems to really like odex roms for some reason. Probably placebo but what can ya do. If not, no biggy. Just awesome to have great devs here sharing their hard work! Mucho appreciated
mwalt2 said:
Sorry, these are all deodex. I'll update OP. I think if you delete the .odex and use the deodex, it may work (but I don't know to be honest).
Click to expand...
Click to collapse
crucial929 said:
How hard would it be for you to make that systemui.apk but with recent apps?
Click to expand...
Click to collapse
Not very. Just change a 2 to a 0 in StatusBarFlag.smali inside SystemUI.apk. Added to original post as SystemUI_mods_WithRecentApps_2.17.651.5.zip.
chrisfales said:
Thanks for these mods and your quick response!!! Any chance for odex versions? My phone seems to really like odex roms for some reason. Probably placebo but what can ya do. If not, no biggy. Just awesome to have great devs here sharing their hard work! Mucho appreciated
Click to expand...
Click to collapse
I can probably do that since the decompiled .smali's are all the same. I'll try to do it some time when I'm bored .
Thank you mwalt2 for the mods. Your contribution is much appreciated.
so flashing "MMSSize_SMSBackup_SMSSecureBox_2.17.651.5.zip" alone will give me the option to have up to a 5mp mms?
i still see 300k,600k,1m even after flashing
crucial929 said:
so flashing "MMSSize_SMSBackup_SMSSecureBox_2.17.651.5.zip" alone will give me the option to have up to a 5mp mms?
i still see 300k,600k,1m even after flashing
Click to expand...
Click to collapse
It's supposed to, but I may have messed something up. Where is the option at? I can't seem to find it at the moment .
edit - I found the setting. Mine shows 1M, 2M, and 5M. I'll look at the .zip and try to get it fixed.
edit #2 - I had an error in the updater scripts to set the permissions. They should all be fixed and you can flash again or just fix permissions on \system\customize\default.xml and \system\app\Mms.apk with a root file explorer.
mwalt2 said:
It's supposed to, but I may have messed something up. Where is the option at? I can't seem to find it at the moment .
edit - I found the setting. Mine shows 1M, 2M, and 5M. I'll look at the .zip and try to get it fixed.
edit #2 - I had an error in the updater scripts to set the permissions. They should all be fixed and you can flash again or just fix permissions on \system\customize\default.xml and \system\app\Mms.apk with a root file explorer.
Click to expand...
Click to collapse
ok mine is still showing the 300k,600k,1m but sending full size pics .. good enough lol
thanks again
crucial929 said:
ok mine is still showing the 300k,600k,1m but sending full size pics .. good enough lol
thanks again
Click to expand...
Click to collapse
That's the xml then. I'm pretty sure it's probably a permissions issue. As you have it now, the 300k will correspond to 1m, 600k to 2m, and 1m to 5m. I'll try to test it more tomorrow (has it worked for anyone else?).
i flashed the mms zip and the sizes dont change (which i dont care about lol) and i also cannot get the mirror app to show up in my app drawer. how do i fix it?
if its not too much trouble could you make a separate zip that just adds the mirror app to the app drawer??
I flashed the boot menu, HDR/pan cam,sysUI with recent apps,MMS on stock ROM with latest updates with twrp2.0 recovery and none of the 4 worked....
Thanks. They all seem to work great. Test them tomorrow. Actually came back to 2.17.651.2 from fresh 4.1 just to try these.
Flashed them all at once. Smooth
It's so late, I only wish I had some espresso ....
mnomaanw said:
I flashed the boot menu, HDR/pan cam,sysUI with recent apps,MMS on stock ROM with latest updates with twrp2.0 recovery and none of the 4 worked....
Click to expand...
Click to collapse
they all worked for me. the mms zip didnt seem like it did anything but i did notice it gave me the secure box (but it didnt give me the mirror app in the app drawer like it said).
alexnaoumi said:
i flashed the mms zip and the sizes dont change (which i dont care about lol) and i also cannot get the mirror app to show up in my app drawer. how do i fix it?
if its not too much trouble could you make a separate zip that just adds the mirror app to the app drawer??
Click to expand...
Click to collapse
me neither....running stock 2.17 hboot 1.40. Gonna try again....
oooops,just noticed these are for deodexed roms. Mine is odexed.
Thanks sent, gotta ha e them extended quick settings!
Sent from my PG86100 using xda premium
So, my phone is just the stock update from HTC that i unlocked and rooted...hboot 1.5. Does that mean I'm deodoxed? Can I flash these or do I have to to flash a stock ROM that is odexed or deodoxed?
Sent from my PG86100 using xda premium
hey guys this is a cwm recovery flashable zip of my bootleg buildprop for the Photon
i have one version for blur based/stock roms and a version for cm7 please make sure and use the correct file cause the blur version on cm7 causes havoc. If on cm7 use the cm7 version if on stock based use blur version.
cm9, electrify, and miui not supported yet
has:
overmind's speedyv7
rocko's rom tweaks
balltounge's mashup
motcher's flow control changes
nok0763, Notorious544d for the raindrop fix and moonzbabysh for showing us the way
seanzscreams multitouch mod
zep's v6 and 3g
and several adjustments made by yours truly
instructions:
before going into recovery make sure wifi is turned off and you have either a fresh nandroid or have renamed your buildprop to buildprop.bak
reboot into recovery
wipe cache and dalvivk cache
flash bootleg zip
reboot phone
let phone boot completely then reboot phone
let it reboot and everything should be super slick
first boot should take a relatively long time, but the second boot should be roughly half the time you are used to seeing
enjoy and as always with anything make a back up
using a file explorer navigate to system and put it into rw rename your build prop to be buildprop.bak just in case things arent the way you like it so you can restore back quicker
download linkS:
BLUR PHOTON VERSION
http://dev-host.org/xV6
CM7 PHOTON VERSION ( just seen cougar updated so will have a new update again for the cm7 version this is based off of 2/10/2012j )
http://dev-host.org/sir
* lots of problems in the cm7 version flash at your own risk when I get time will try fixing it up better sorry for any issues or problems this has caused you leaving link up so if anyone wants it can have it
let me know of any issues or maybe something you would like added.
i realize that alot of these mods are already out there you can download them one at a time or you can try this bootleg buildprop and save yourself some time
I'll be the "guinea pig"
Will be giving this a go too
Also, just wanted to let you know that I didn't create or mod the raindrop fix, I just tested it on my MoPho and was happy to report it. The actual creator is linked in the thread I made for it, don't want to have anyone think I'm taking someone else's credit.
MoPhoACTV Initiative
moonzbabysh said:
Will be giving this a go too
Also, just wanted to let you know that I didn't create or mod the raindrop fix, I just tested it on my MoPho and was happy to report it. The actual creator is linked in the thread I made for it, don't want to have anyone think I'm taking someone else's credit.
MoPhoACTV Initiative
Click to expand...
Click to collapse
thanks so much for bringing that to my attention i dont want anyone getting upset either ill reread thread and edit with appropriate creds.
All it did was kill my services
Sent from my MB855 using xda premium
pbedard said:
All it did was kill my services
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
? kill your services can you be more descriptive, what rom are you using are you locked unlocked cm7, cm9 miui?
Flashed with cm7.2 and wifi doesn't work anymore. Runs smooth though.
Sent from my Motorola Electrify
nate6138 said:
Flashed with cm7.2 and wifi doesn't work anymore. Runs smooth though.
Sent from my Motorola Electrify
Click to expand...
Click to collapse
is it not working at all? or just doing the whole works then cuts off then works then disconnected then uncheck and it works the disconnects? thats not an issue with the prop but now if it killed wifi entirely thats another thing idk why would kill wifi .
the prop is based off blur maybe has something to do with it i have another one im going to release for cm7 users several lines need to be changed sorry you are having these issues only method to remove is to restore your backed up prop file or rename bootleg's prop to buildprop.bak and it should create a new one after you reboot. Or can extract the buildprop from the ROM you flashed and replace it to revert
about to go to sleep any more q's ill have to catch in the am
for now if on a non blur rom its not fully working ill have a cm7 version by monday of course can always make a backup of builprop and try for yourself gl
It killed everything even with 3 reboots nothing
Sent from my MB855 using xda premium
pbedard said:
It killed everything even with 3 reboots nothing
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
What rom are you using how did you install are you Photon or electrify to revert you can restore your backed up prop or can extract from the ROM you flashed and use it to replace the one it installed or can rename it to .bak and restart should create a new one once you reboot
Sent from a [email protected] in the night
http://forum.xda-developers.com/showthread.php?t=1506250
make one of these for CM9 also does this include the SD card fix? where we had to change a number from 2 to 3.. i dont remember the line but im sure you know what i mean.
It errors the wifi out.
Sent from my Motorola Electrify
nate6138 said:
It errors the wifi out.
Sent from my Motorola Electrify
Click to expand...
Click to collapse
what rom are you using plus I see your sig says electrify IDK the differences but I would think thats why. its made for Photon on a stock based rom. To revert extract build prop from ROM you flashed and replace it. Sorry didn't work for you. Will be trying to get this worked out/ up for cm7 & 9 miui and electrify since they are 2.3.5 will need an electrify buildprop though anyone willing to zip it and send to me
Sent from a [email protected] in the night
http://forum.xda-developers.com/showthread.php?t=1506250
tsdeaton said:
make one of these for CM9 also does this include the SD card fix? where we had to change a number from 2 to 3.. i dont remember the line but im sure you know what i mean.
Click to expand...
Click to collapse
wont work on cm right now so far all that tried on cm has had issues as for the sd thing not sure what you mean if you referring to the cm9 fix then no it has no fixes for 9 the one I make for 9 ill try to incorporate what I can so it can be a one stop shop for what will work. for now if not on Photon blur based rom id stay away unless just wanting to test for yourself if thats the case make sure to back up your buildprop or have the ROM you are using zip handy to extract the prop from it really sorry guys that are having issues I'm going to edit the crap out op to make it more clear as to who this is working for after work
Sent from a [email protected] in the night
http://forum.xda-developers.com/showthread.php?t=1506250
Using a photon with cm7?
Sent from my MB855 using xda premium
pbedard said:
Using a photon with cm7?
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
cm7, cm9, and miui not supported yet will be soon you can try it see if it will work but so far people reporting issues.... So unless on a blur based ROM on the Photon use knowing it might cause issues so make sure you can revert
Sent from a [email protected] in the night
http://forum.xda-developers.com/showthread.php?t=1506250
So am home now going to be trying to get the cm7 version whipped up
So far has been Wifi and data issues
Question?
Anyone using this on blur roms having these issues from what the replies have been I'm seeing only electrify and cm roms having issues if anyone on a blur based ROM could confirm having issues or not so I know if I need to be working on the original also.
Anyone wanting this made for electrify can get me the buildprop for it id be happy to make one
Well I've went on enough see ya
Sent from a [email protected] in the night
http://forum.xda-developers.com/showthread.php?t=1506250
Ill send you a build.prop of the electrify. how do you want me to send it?
BHermes21 said:
Ill send you a build.prop of the electrify. how do you want me to send it?
Click to expand...
Click to collapse
however you are able to would rather through pm or email so it doesnt link in thread
hey
i just flashes the latest cm7 rom ,
should i flash this buildprop too ?
what does it do?
thanks
http://forum.xda-developers.com/showthread.php?t=991276
Devs, can anyone look into if this could be good use to our prime?
I Dont have much time to look into this, but hopefully someone capable will..
This was implanted in the WSG rom (now discontinued), from what I saw, it did help a lot, everything became smoother compared to the stock rom.
I tried v6 supercharger on my LG Optimus 2x and it made the difference. Would it be dangerous trying it on a simply rooted TFP on stock?
jason1993 said:
I tried v6 supercharger on my LG Optimus 2x and it made the difference. Would it be dangerous trying it on a simply rooted TFP on stock?
Click to expand...
Click to collapse
No, just don't set Script Manager to run it on boot until you've confirmed that it works. There's nothing to lose.
ZebTheCalvinist said:
No, just don't set Script Manager to run it on boot until you've confirmed that it works. There's nothing to lose.
Click to expand...
Click to collapse
Yeah it would be nice to have this running on stocked, rooted primes untill better updates come out.
From what i understand you have to de compile service.jar and edit a file in there.
Re pack the file n replace the original service.jar with it
Then run the supercharge script.
Doesnt seem to be too complicated.
I will def be looking into this when i have the time, was just hoping someone with better knowledge can look into this sooner.
alanhzl said:
Yeah it would be nice to have this running on stocked, rooted primes untill better updates come out.
From what i understand you have to de compile service.jar and edit a file in there.
Re pack the file n replace the original service.jar with it
Then run the supercharge script.
Doesnt seem to be too complicated.
I will def be looking into this when i have the time, was just hoping someone with better knowledge can look into this sooner.
Click to expand...
Click to collapse
That is all you have to do. I personally use it on all of my devices. I would attach my services.jar for you but I'm not 100% sure the one on Wookie will be identical. It is a pretty painless process but if you need any assistance send me a pm.
ZebTheCalvinist said:
No, just don't set Script Manager to run it on boot until you've confirmed that it works. There's nothing to lose.
Click to expand...
Click to collapse
Really? No file system managed at all?
alanhzl said:
Yeah it would be nice to have this running on stocked, rooted primes untill better updates come out.
From what i understand you have to de compile service.jar and edit a file in there.
Re pack the file n replace the original service.jar with it
Then run the supercharge script.
Doesnt seem to be too complicated.
I will def be looking into this when i have the time, was just hoping someone with better knowledge can look into this sooner.
Click to expand...
Click to collapse
Is it necessary that work on the service.jar? I've always run supercharger without it, simply using terminal emulator.
jason1993 said:
Really? No file system managed at all?
Is it necessary that work on the service.jar? I've always run supercharger without it, simply using terminal emulator.
Click to expand...
Click to collapse
as the tutorial suggested (from the original dev thread), post ICS roms has the app's "priority"(for lack of better explanation) built-in to service.jar.
so unless you are running a deodex rom (which is not the case for our stock prime), you will have to re-compile service.jar in order to take full
benefit of this super charge script.
i think i will try to looking to it tonight, to see if i can get something going lol. i'm no dev by any mean.
alanhzl said:
as the tutorial suggested (from the original dev thread), post ICS roms has the app's "priority"(for lack of better explanation) built-in to service.jar.
so unless you are running a deodex rom (which is not the case for our stock prime), you will have to re-compile service.jar in order to take full
benefit of this super charge script.
i think i will try to looking to it tonight, to see if i can get something going lol. i'm no dev by any mean.
Click to expand...
Click to collapse
I'll upload a modified odexed service.jar if someone provides me with one.
Sent from my SGH-I747 using Tapatalk 2
Not sure on the purpose of the OP .
has he even tried it on the prime?
i've been using this for a while now and it works fine.
Just try it rather than requesting Dev help.
jiffy1080 said:
I'll upload a modified odexed service.jar if someone provides me with one.
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
And what can we do with that modified odexed service.jar? Replace the stock one with the modified one?
Sent from my Transformer Prime TF201 using xda premium
After reading more into the tutorial, i think that the script that the original supercharge dev is providing has the service.jar patching included.
Meaning we dont have to manually edit the file etc etc, just run the script and everything is automated.
But i 'm not comfortable of running the script on my prime, as mine is locked and i have no way of creating a backup incase something go south and i
Ended up with a boot loop....
So i guess if anyone has done this on their locked prime with success, please post and share, sorry for calling for devs, as i initially thought this
Would involved some modification to system files..
P.s. i'm by no mean trying to encourage anyone to run this if they are not comfortable, just that i havent seen anyone bring this up, and thought it may
Be able to give our primes a little bit more boost if confirmed that is safe and working.
alanhzl said:
After reading more into the tutorial, i think that the script that the original supercharge dev is providing has the service.jar patching included.
Meaning we dont have to manually edit the file etc etc, just run the script and everything is automated.
But i 'm not comfortable of running the script on my prime, as mine is locked and i have no way of creating a backup incase something go south and i
Ended up with a boot loop....
So i guess if anyone has done this on their locked prime with success, please post and share, sorry for calling for devs, as i initially thought this
Would involved some modification to system files..
P.s. i'm by no mean trying to encourage anyone to run this if they are not comfortable, just that i havent seen anyone bring this up, and thought it may
Be able to give our primes a little bit more boost if confirmed that is safe and working.
Click to expand...
Click to collapse
Maybe you can recover from a potential bootloop could by installing the whole original firmware via the sdcard method. It could be done, right?
Sent from my Galaxy Nexus using xda premium
jason1993 said:
Maybe you can recover from a potential bootloop could by installing the whole original firmware via the sdcard method. It could be done, right?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I m not sure.. it maybe possible.
jiffy1080 said:
That is all you have to do. I personally use it on all of my devices. I would attach my services.jar for you but I'm not 100% sure the one on Wookie will be identical. It is a pretty painless process but if you need any assistance send me a pm.
Click to expand...
Click to collapse
Thanks jiffy for trying to help, is your prime locked and do u currently have super charge running?
alanhzl said:
I m not sure.. it maybe possible.
Click to expand...
Click to collapse
When i first rooted my prime i uninstalled some system apps (asus's bloatware) and, since i wasn't able to update to .21 (dead droid screen during the installation) i did a factory reset: during setup configuration, at one point, after signing in my google account, setup configuration force closed everytime, so i had to send it to Asus to fix. After i had RMAed it, somebody suggested me the update from sd trick. So i think (but i'm not 100% sure) that if that trick can work without system apps it should also work with managed system files, since it doesn't matter your system at all.
Sent from my Galaxy Nexus using xda premium
I used it only prime with the virtuous prime ROM. It made it just that much better.
Sent from my Transformer Prime TF201 using xda app-developers app
hi im currently in process of porting a stock deodexed rom.
i have changed system files and the update script.for out i9305. at moment i am able to install the rom fine and loads up with or without wipe. i also included the ee modem.
my issue is that when the rom starts all is ok and there are no force closes however i get no network and imei shows null. to resolve this i just flash param.tar in odin and stock file and all is back to original with imei restored.
any ideas on whats causing the loss of imei number
in setting imei and baseband showbas unknown
edit whilst restoring to stock i did not have to restore imei backups so am asuming efs part is fine
Sent from my GT-I9305 using Tapatalk 2
Check 9500 partition layout and update install script. Dont rewrite the efn part.
Sent from my GT-I9305 using xda app-developers app
have done that part rom installs fine baseband is unknown
Sent from my GT-I9305 using Tapatalk 2
I think u need to Flash a baseband from our i9305 after flashing The Potter rom
but wouldnt that be the modem file iv tried flashing it on radio partition
Sent from my GT-I9305 using Tapatalk 2
right iv ported wanam lite rom to our device, the aroma works i boot up fine but baseband still unknown so annoyin
Sent from my GT-I9305 using Tapatalk 2
i am really into this thread. I opened a thread similar at the beginning but they moved it, hope this one stays in here otherwise it will get lost in the i9300 section...... this is really good lets all try get into this, like i said I am going to play around on monday when i return home, so far we got everything going exceept the Modem is not connecting to the Imei correctly, We need an experienced dev.
---------- Post added at 09:25 AM ---------- Previous post was at 09:14 AM ----------
Just think how many roms we can have if we get this going
Sent from my GT-I9305 using xda app-developers app
Try merging our system and framework so it picks it up as our xxali5 or xxali9 you have to get rid of there base and put our base instead but leave the edited files so maybe the system apps folder stays the i9300 as the apps are the same i think but change the rest into our firmware hmmmm so maybe a better idea would be to have a blank deodexed and zipaligned xxali5 rom move and overwrite our files with the edited files of the i9300 that way all our efs and imei doesnt get touched
Sent from my GT-I9305 using xda app-developers app
going to check ril today see if that sorts it
Sent from my GT-I9305 using Tapatalk 2
Great thread, wish I could contribute more.
At the moment I'm hanging to see what the more clued up guys around here work out!
added the ril files and qualcom ril files but basebands the same
also the serail number has changed on device tried reflashing modem but doesnt help
chwads2k8 said:
right iv ported wanam lite rom to our device, the aroma works i boot up fine but baseband still unknown so annoyin
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
Basically there are some intensely different changes within the services.jar, framework.jar, android-policy.jar and so forth. 4G LTE is sooo much different than the stock i9300. I am not saying it CAN'T be done. But I am saying it is going to be a complete bastard to do. Put it this way, you'd be better off looking into all of the modifications that have been done to create these ROMS and re-doing them to the i9305.
Trust me, I have looked into doing this with a "customised" build to from sources for ICS for the P7320T tablet that I had. It is the only 4G tablet released here in Australia. The closest I could find in sources for being able to make the connection was grabbing settings systemUI and the others I have listed above ^^^ from the S2 4G LTE. Then I was going to have to modify the systemUI specifically for tablet mode.
I no longer have the tablet nor the patience to want to take on anything like it again.
All I can say is good luck. Feel free to check my threads to confirm that my choices are not a conflict of motivation or lack of determination...god I can assure you that much
Just for a tip. I started today with decompiling the android-policy.jar file to see if I could enable the torch app double click home from lock screen feature....this has been done on i9300 right? Go take a look at the full guide on how to do it...go decompile 1 file that I am talking about and you will see just how different the methods are in all of the smali code. JOY!
---------- Post added at 03:34 AM ---------- Previous post was at 03:23 AM ----------
chwads2k8 said:
added the ril files and qualcom ril files but basebands the same
also the serail number has changed on device tried reflashing modem but doesnt help
Click to expand...
Click to collapse
What tools are you using to "port" this ROM to our device?
I have tools that can port ROMs in about 30-40min.
What have you got in the build.prop for this thing? Do you want to upload the ROM for me to take a look at? The least I could do is offer some help before raining on your parade lol.
Have you considered doing maybe a "splice" of the ROM. Rather than porting the full version, you could do a diff/compare of the modded ROM against it's stock counterpart. Then you migrate those changes over to your "stock i9305" base. That is going to be your best chance of doing this I reckon? also you won't be able to copy across the firmware version. That won't work. Your framework and the firmware version are going to be device specific.
The absolute best thing I can think of suggesting is to go with a known base equivilant?? Like it seems that there is a release of XXALI5 (for touchwiz at least?) on both devices. That would be where I would start first and foremost. I would port with that common version using what I described above and then migrating any further or additional functionality (developer made i.e. Wanams mods) that have been done since the XXALI5 release.
That is going to be your best bet.
Or you guys could just wait for me to release my ROM haha...subtle promotion? I think not.
btemtd said:
Try merging our system and framework so it picks it up as our xxali5 or xxali9 you have to get rid of there base and put our base instead but leave the edited files so maybe the system apps folder stays the i9300 as the apps are the same i think but change the rest into our firmware hmmmm so maybe a better idea would be to have a blank deodexed and zipaligned xxali5 rom move and overwrite our files with the edited files of the i9300 that way all our efs and imei doesnt get touched
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Exactly
I have a methodology that does this very easy. I wanted the OP to upload his work so far to save me a download. But I might just go ahead and do it anyway.
Have you guys got permissions from Wanam to use his work? I will ask on your behalf if not. He is a great contributor to this forum, I don't wish to have him offside.
What I mean is that I will go ahead and play, but I won't re-upload any test files to the forum without his consent This shouldn't be too hard
---------- Post added at 12:40 PM ---------- Previous post was at 11:53 AM ----------
Contacted Wanam. I will wait to see what he says and recommends. I have claimed I am not releasing anything of his, so this can be owned by you guys who want it. I am happy to help get the ball rolling to help yous though. I have my own dev team that I work with so that makes me kinda busy. That is why I haven't released my own ROM on here yet lol
Downloaded XXLAI5 Wanam, Downloaded XXLAI5 stock i9300, have already downloaded XXLAI5 stock i9305 and I am currently deodexeding it as we speak.
Will deodex i9300 XXALI5 next and then do a comparison to Wanams. Segregate changed files - > port to stock deodexed base = Wanam i9305 for you guys
That's if Wanam approves of course?
EDIT: Hey Mr OP can you please contact me? I cannot send you PMs? Holy smokes you've been around this place since 09!
Ok Analysis done on Wanam compared to stock XXALI5 and have all the of the files seperated and within their directory structure that had changes.
There is going to be some work needed to be done on these main files:
/system/framework/android.policy.jar
/system/framework/framework2.jar
/system/framework/services.jar
/system/app/systemUI.apk
As I expected
Now the fun n games start I will decompile all of these files and then diff them against the standard i9300 smali coding and then *attempt* (and I say that with all great intension too) to migrate the changes across into decompiled i9305 files.
I can tell this is going to be a head ache!
Otherwise though....I can honestly say that what I have got so far I know for certain will boot and you will not have baseband issues. You won't however have 15 toggle mod as it stands. Services.jar and Android policy.jar both control this feature. I see that this *IS* available as a mod already on this forum but I am not certain that the creators realise that these modifications (mentioned here) actually do need to be performed.
Lidroid-res.apk within framework will have no rights to control the toggle on the systemUI cause it won't have permissions due to conflicting signature checking. note...toggles may appear, but they won't do anything when you touch the widget toggle, it will be non-responsive.
Thanks guys
Thats what i said we should just try copying over the whole system app folder and replacing it with our deodexed rom. Try doing that as the firstt step
Sent from my GT-I9305 using xda app-developers app
btemtd said:
Thats what i said we should just try copying over the whole system app folder and replacing it with our deodexed rom. Try doing that as the firstt step
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
System app is fine, but that isn't where the changes are that make Wanams ROM. You'd have your self a standard ROM otherwise. As in no difference. Or if you just copied the system/app folder ROM would boot but systemUI would force close. You would also have no reboot menu and no USB read from the phone. That would equal disasterous....cause as we all know we don't have SD mount in recovery do we?
Fancy doing an adb push on a phone that doesn't install USB connection files?
See I wouldn't be stupid enough to do that without having at least a clockwork recovery backup lol.
It's ok. for the android.policy.jar they are identical (well for XXALI5 they are anyway) to the i9300. So simple trade in there.
Only 4 more files to go and I will have you guys a port
Wanam still has not contacted me back yet though so I we need approval before anything.
Reset scrolling caches. In framework2.jar
This took a bit of work because my notepad++ kept crashing running compare. If you guys ever have this issue, right click the executable in program files go to properties and compatibility and then check the boxes for:
- disable visual themes
- disable desktop composition
- disable high dpi scaling.
Apply.
No more crashing. Windows 7 aero apparently doesn't like the compare dll?
Anyway not related. I am back on track. last jar file and then it should be ready to package up and it will be the same as Wanam ROM XXALI5
Got approval from Wanam. Just about to test flash now. Will upload it here if everything works out
Well, I had a few mishaps with my own device. Namely no root access and also lost hardware ID...meaning no Android Market. This all happened sometime during my lengthy list of modifications so I was not sure where. That mean flash back to stock and restore my data bit by bit until I was set up again. This take for EVER!
So yeah no real feedback from anyone in here so have decided to finish off my own ROM instead. XXALI9 (newer) and a heap more mods than stock Wanam. So far so good.
I can upload what work I did on getting Wanam's up and running (I have not flashed it yet) but will wait till someone actually wants before I go ahead and do that.
Thanks guys
James