*** 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
Related
I decided that since enough people asked about it, then it probably deserves it's own thread. This thread contains information on how to set up the V6 super charger script on the galaxy note.
**PLEASE FOLLOW ALL INSTRUCTIONS TO ENSURE SUCCESSFUL INSTALLATION/OPERATION OF SCRIPT**
CREDITS:
**ZeppelinRox** Creator of V6 and many great scripts!
WHAT YOU WILL NEED:
A. Rooted phone (duh)
B. Busybox 1.81.1 DOWNLOAD Via GOOGLE PLAY app - **BUSYBOX INSTALLER** https://play.google.com/store/apps/d...N0YWxsZXIiXQ.. (Thanks Capite for the link)
C. (optional) Root Explorer (to mount /system to r/w) can use script manager too
D. V6 supercharger PDF file... which is linked below
*****ICE CREAM SANDWICH USERS**** don't forget to first supercharge your SERVICES.JAR via website....http://android.mimic.ca**********
Flash in Clockwork...... Cache Wipe X2 - Wipe Dalvik - Flash Zip.
Installation Instructions:
Please follow ZEPPELINROX thread here: http://forum.xda-developers.com/showthread.php?t=991276 -
Per his request, i will not create installation instructions...... But if you have questions i will try to help you out since i have used it forever.
________________________ zOOm zOOm _______________________________________
*
*
*
*
SCRIPTS
MOST SCRIPTS CAN BE FOUND HERE: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
Hey just a quick heads up...zeppelin is very clear in his thread that he does not want those files posted up in other threads and to link back to his thread. Did you talk to him about creating this thread?
Sent from my SAMSUNG-SGH-I717 using XDA App
00mred00 said:
Hey just a quick heads up...zeppelin is very clear in his thread that he does not want those files posted up in other threads and to link back to his thread. Did you talk to him about creating this thread?
Sent from my SAMSUNG-SGH-I717 using XDA App
Click to expand...
Click to collapse
hmm... no i didn't read up .. i'll check it out and delete if that's the case. i been helping a lot of ppl install because they cannot - def. not taking credit for his work.
edit: he says not to duplicate his install instructions, but he is okay with sharing. so i guess i'll just share and help with questions.
Its not so much that but by going to the original thread it ensures the user gets the most up to date script. The how to is an excellent idea but some of your steps conflict his steps
Another note....#5 suggests we get a paid app via warez....that I know is against the rules you might remove that
BigBison420 said:
hmm... no i didn't read up .. i'll check it out and delete if that's the case. i been helping a lot of ppl install because they cannot - def. not taking credit for his work.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I717 using XDA App
well, i believe it's a free app... or maybe i meant "file explorer" i forget. but my market is jacked up because of a ROM issue. (can't access market)
00mred00 said:
Its not so much that but by going to the original thread it ensures the user gets the most up to date script. The how to is an excellent idea but some of your steps conflict his steps
Another note....#5 suggests we get a paid app via warez....that I know is against the rules you might remove that
Sent from my SAMSUNG-SGH-I717 using XDA App
Click to expand...
Click to collapse
Hi,
Since RC7 does not work.
What version should be used?
V6_SuperCharger_for_Android-Update9_RC6.9.sh.pdf ?
Thanks
Is anyone else really confused about the options in the script and what each one brings? I'm sitting looking at a menu, unsure what to pick :/
BigBison420 said:
ATTACHMENTS - updates/scripts FROM **ZeppelinRox**
**removed attachement update9_RC7 because it was not working on my Gnote**
MOST SCRIPTS CAN BE FOUND HERE: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
Click to expand...
Click to collapse
What's wrong with RC7? I installed it successfully on my phone, and it runs. Can't tell much of a difference though.
Is there something specific installation error that you are running into, or do you have a way to check if the script is running correctly? If I try to run /data/99Supercharger.sh again, it tells me the my phone is already supercharged and to verify that "Ran_Supercharger" exists in /data, which it does.
After installing Balance 3, I see no difference in the Go Launcher. LauncherPro is better than ever, and my battery life is now really good.
So... it sort of worked.
re
hey guys,
well i'm just trying to help galaxy note users out (apparently a lot of you are new to this scripting thing).
what personally works for me i recommend. That would be option 13 (bulletproof launcher) and also 768+hp settings.
keilbaca said:
After installing Balance 3, I see no difference in the Go Launcher. LauncherPro is better than ever, and my battery life is now really good.
So... it sort of worked.
Click to expand...
Click to collapse
I use go launcher and the new 2.85 Beta is available. There is a noticable increase in optimization. Lag has lessened a bit. and i'm running SauROM with Da_G's OC kernel.
BigBison420 said:
I use go launcher and the new 2.85 Beta is available. There is a noticable increase in optimization. Lag has lessened a bit. and i'm running SauROM with Da_G's OC kernel.
Click to expand...
Click to collapse
I got the latest script to run on my Note, on stock.
I seen no difference at all.
I'm throwing SauROM on it tonight, because I am having other issues too that the rom should fix, I hope. Citrix wants to auto delete the first thing it sees in Active Directory. I don't think my work would appreciate me if I deleted the entire Servers column in AD.
I would love to install this. But.your instructions differ greatly..you suggest a busting install along withal file explorer install.. He suggests script manager.
And there is some question as to which pdt we should be using.
I have a seperate thread with his install instructions linked. I referenced file explorer because i didn't realize u could mount rw. If your THAT confused u should probably not install it.
Sent from my SAMSUNG-SGH-I717 using XDA
In not confused. To the contrary, i understand almost wholly. But what isnt clear, is whether his instructions are sufficient or that they work with out note.
Its not clear which version of the script we need...or which set of instructions we should use.
Listing a set of instructions in a note specific forum (ones that differ from those elsewhere) implies that the others wont work on our device....or that something could be easier or go wrong.
Thank you for pointig the supercharger mod out. I was unaware of it. With that said, id still like to install it.
Which PDF do we use?
Jamesyboy said:
In not confused. To the contrary, i understand almost wholly. But what isnt clear, is whether his instructions are sufficient or that they work with out note.
Its not clear which version of the script we need...or which set of instructions we should use.
Listing a set of instructions in a note specific forum (ones that differ from those elsewhere) implies that the others wont work on our device....or that something could be easier or go wrong.
Thank you for pointig the supercharger mod out. I was unaware of it. With that said, id still like to install it.
Which PDF do we use?
Click to expand...
Click to collapse
i got u completely - i just listed my walkthrough because some people truly need step by step instructions lol. but the DEV's instructions are plenty IMO
my thread was designed to link instuctions for setup and also discuss which scripts are working for the Gnote (case and point, my experience with update 9RC7 which isn't working for me, but does for another user). for me update 9rc6 works fine.... i would try RC7 too - lot of nice features
keilbaca said:
After installing Balance 3, I see no difference in the Go Launcher. LauncherPro is better than ever, and my battery life is now really good.
So... it sort of worked.
Click to expand...
Click to collapse
IN GoLauncher ---> make sure you set icons to "Default Size" because using LARGE or CUSTOM is one of the main Culprits to lag.... also get the 2.85 version
I have no lag.
Anyone tried this on the ICS leak builds?
Super charger us the best mod to improve speeded etc. however this is my second phone that after super charging my phone doesn't shut down all the way. If i power off then plug it in., it reboots. Also wifi constantly looses data connection. Both issues are related to one of the supercharger tweaks just not sure which one is causing it. Maybe home bullet proof.
Sent from my SAMSUNG-SGH-I717 using xda premium
*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
WANTED: Users to port SGS roms to the 4.0. You will need to know how to complete a full restore if something goes wrong, but that's it. I cannot go through the forums searching for good SGS roms, as I have several threads to manage, and a rom to work on. The steps are easy for you though, and if you port a rom I will add it in the OP.
First of all, I want to say that I take NO credit on any of these roms. All I did was port them over and add speed tweaks, or added ones that users have ported. If the rom creators or mods have any issue whatsoever with this thread, I will happily take it down, even though I think it would be a large contribution to the 4.0 community. I will continue to update this forum with info as I go along.
I, after a fortunate afternoon of boredom, have managed to successfully begin porting I9000 roms to our devices! Fortunately, they are similar enough that it boots without any modifications. I will put up here any ports that I make, and any that the users create. Note that these WILL NOT BE UPDATED! These are one-time ports, to be used and improved upon by the community. Anything that is broken now will stay broken, unless a user decides to fix/update it, then I will include it in the OP.
What *should* work in all ported roms:
wifi
GPS
home buttons
everything else
What will probably *not* work on ported roms:
Bluetooth
Camera
backlight on buttons
Ported roms:
~GamerzRom odexed V11-~
Link to original thread: http://forum.xda-developers.com/showthread.php?t=1656081
Added:
V6 supercharger, and build.prop tweaks from it.
init.d tweaks from my rom
ext4 filesystem
Advanced mount options
Auto zipalign and Database optimize
Removed apps that do not work on our Player (such as the Dialer)
Download:http://www.mediafire.com/download.php?ctuu2w295w2xlk6
~Saurom~
Original thread:http://forum.xda-developers.com/showthread.php?t=1388342
Ported download link:http://www.mediafire.com/download.php?csua40hkg1r3m86
~JellyBeanRom~
Original thread: http://forum.xda-developers.com/showthread.php?t=1260709&highlight=gb
Ported download link:http://www.mediafire.com/download.php?mgec81f3ifck221
~Ario Rom (ported by ChaosChris)~
Ported thread link : http://forum.xda-developers.com/showthread.php?p=29950015#post29950015
Original thread: http://forum.xda-developers.com/showthread.php?t=1536558
To use these Roms:
You MUST use a Gplayer kernel! GT-I9000 kernels will not boot!
A full wipe may be necessary with some roms if you encounter issues.
Converting (for porters)
Steps:
1. Download wanted rom (must be GB)
2.Move the zip to the internal sdcard
3.Reboot into recovery
4.Flash zip, then boot into download mode
5.Flash a SGP kernel
6. apply my mod pack to the rom, by either copying/pasting the system directory over the SGS rom's system directory, or by pushing it via adb, (eg. adb push /path/to/modpack /system).
7. Profit!
NOTE: after applying this, porters may want to remove non-working packages such as the dialer and mms, as they may cause issues with the end result if they are kept in. Do not delete phone.apk though!! This is required for the camera and some other things, and breaks stuff on certain roms. You have been warned.
NOTE: If you use this modpack, please give me credit, and link back to this thread so that more people can use it. Also, you should probably link back to the ported rom's thread as well, to avoid "ripping off" those devs.
Modpack:
Changelog
V1-
Preliminary release
Fixes wifi and GPS
Includes v6 supercharger and init.d tweaks
V2-
fixed vold.fstab so sdcard is mounted properly.
Download:
ModpackV1:
http://www.mediafire.com/download.php?diaq6im4i18ktf7
NOTE:Note that this is preliminary. It fixes everything listed, and attempts to fix some broken things. Your mileage may vary. This is not a cwm flashable zip! you much extract and adb push this over the existing system directory. This is mainly intended for porters, so users apply at your own risk. This will work, but is a very early release.
Modpack V2 (thanks to ChaosChris):
https://docs.google.com/open?id=0B9OVlH2Pl76DZk5Pa3lJVXlrYzA
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
iJimaniac said:
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
Click to expand...
Click to collapse
Yeah, it says that because it includes semaphore's kernel, which raises the max rom to 380, which we could do on our kernel's, but apparently that breaks a lot of stuff if you go much further then 350 (according to klin).
is the wifi fixed in your port or do we have to do your fix after flashing?
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
check over in the operation: ics for the 4.0 thread I believe they are already attemping to use the cm7 kernel to boot a cm9.
daniel644 said:
is the wifi fixed in your port or do we have to do your fix after flashing?
Click to expand...
Click to collapse
Yeah, it is fixed before you flash. Once I manage to iron out a few more bugs, I will probably release a "conversion pack" that fixes all the issues. I already have one that fixes wifi and gps, but bluetooth and camera have me stumped, and I do not want to replace the entire hw/lib folder, because some of these roms have lib optimizations, but I may have to.
Sent from my GT-I9000 using xda app-developers app
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that zaclimon has tried it, and he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable. I also believe that he said the issues may have been rom based, so here it goes, and wish me luck.
Sent from my GT-I9000 using xda app-developers app
hanthesolo said:
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that daniel has tried it, abd he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
zaclimon said:
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
Click to expand...
Click to collapse
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course . A lot farther out there, but maybe I can use a SGP5.0 kernel to get it booting. A LOT less likely, but hey, i'm experimenting .
EDIT: I cannot try ICS, since I need to reboot into recovery a second time, and I cannot do that, as I have the intl bootloader on my US device, and it would require it to be booting first.
hanthesolo said:
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course .
Click to expand...
Click to collapse
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
zaclimon said:
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
Click to expand...
Click to collapse
Well, thet camera shows a preview, but fails when a pic is taken, for some reason. Bluetooth does turn on, but is not seen by any other devices, and cannot scan for others either. I did do a little tweaking with Gamerz, so it will be even faster than it was already, which is pretty blazing! I have 2 more that I can put up (I have a preliminary package that I just adb push over the system files that works for now). I have also gotten the camera apk onto my rom, and it works really well! It doesn't take 5 MP pics, or record 720p video (which may be because I am using Terrasilent, which reduces the amount of Vram the system can have), but tap to autofocus and everything else works pretty well. I have a sneaking suspicion that the camera is soft limited, not hard-limited.
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
zaclimon said:
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
Click to expand...
Click to collapse
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
hanthesolo said:
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
Click to expand...
Click to collapse
Here's the vold.fstab if you need it
Okay, it seems that the zip hosed my partitions (converted them to yaffs2 and mtd), so I am going to perform a full restore, and just keep porting GB roms. As soon as you can get the usb gadget driver working, zaclimon, I guess I can keep working on it, but for now I will just keep to GB.
Two more roms up! I will probably not port any other unless I see an especially good one, but I will put up my mod pack tomorrow.
has anyone found out if the ported roms enable tv out or has someone found out if tv out support is in the i9000 kernal?
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
iJimaniac said:
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
Click to expand...
Click to collapse
what hardware does the galaxy s i9000 have that allows for tv out? I thought the galaxy s i9000 and the galaxy player 4.0 had the same gpu?
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
Hey guys, my question is essentially what the title says. I find that in CM10 based roms, that whenever I use the stock cyanogen mod browser, it automatically goes into desktop mode (and is stuck there. The desktop mode checkbox, however, is unchecked.) I'm fairly sure it worked before I used the touch pad fix here - http://forum.xda-developers.com/showthread.php?t=1893343 - So I think it might be a framework/build.prop issue, but I'm not sure. I've been looking to fix this problem everywhere but haven't really been able to find a solution. Do you guys have any idea what the fix might be?
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
smokerman said:
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
Click to expand...
Click to collapse
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
fishvtt said:
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
Click to expand...
Click to collapse
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Hey, smokerman, would you know how to mess with .jar files. I kinda want to go exploring to see if I can do anything.
you have here a simple guide by @CriGiu
http://forum.xda-developers.com/showthread.php?t=2322231
could help you.:good:
fishvtt said:
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
Click to expand...
Click to collapse
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
Oh ok, I'll try testing that out.
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
All right, well that seems to do the trick. When I try to use the touchpad activator app, it gives me the "error 5 expected reciever of type android.view.ViewRoot, but got android.view.ViewRootImpl". But, Dead Trigger works perfectly how it's supposed to, and the stock browser is using the mobile version now. Just remember to make the necessary build.prop changes as outlined in Fahrenheit's guide.