Success to port CM7 to XT701! - Milestone XT720 General

Hi guys!
I have successfully port CM7 to XT701
Here is the ROM
http://www.rayfile.com/zh-cn/files/6ac67519-7669-11e0-9deb-0015c55db73d/
Most of the functions work well.
But several problems are not fixed yet.
1.The camara focus and the flash work but when it save pictures. It will crash down.
2.The FM doesn't work
3.The DSP works but not so well
...
I think the xt720 xt701 xt711 have the same hardwares and systems. So I need cooperation to fix these problems. So if you want to help me or cooperate with me , just PM me.
Thanks

Good news, have you compiled cm from source or just ported from already compiled port?
Is there any journal about your work?
Will try to help with everything i can.

mirror plsss

videi\o please
Please post a video for proof!

mirror from Russia =)

So does this working xt720 as is? Idc if some stuff is broke I've been using miui and some stuff is broke but it works

Multiupload mirror:
http://www.multiupload.com/PQQ7SR57TE
I haven't tested it on XT720 yet. Stlifey's github is here: https://github.com/stlifey
BRB (hopefully), bleaching computer following RaySource.

I'm gonna try it out ill let u know how it goes

easye420 said:
So does this working xt720 as is? Idc if some stuff is broke I've been using miui and some stuff is broke but it works
Click to expand...
Click to collapse
Agreed. Not everything has to work, but I'll wait till the camera works before I try CM 7. The camera is one of the things I use a lot on this phone.

Great to hear this good news! As I know at the same time a new version of MIUI rom will also release soon.

fails....
code 4 aborted

hellmonger said:
fails....
code 4 aborted
Click to expand...
Click to collapse
I'm not going to have a chance to try this until next week (traveling, stupid work), but the updater script has a check for board name and refuses to install unless you're on choles. You should be able to unzip the files and edit META-INF/com/google/android/updater-script to remove this line:
assert(getprop("ro.product.device") == "choles" || getprop("ro.build.product") == "choles" || getprop("ro.product.board") == "choles");
Then delete the signature files META-INF/CERT.RSA META-INF/CERT.SF META-INF/MANIFEST.MF and rezip. It should then apply in OpenRecovery because it doesn't require signed updates.
Nevertheless, it probably won't boot until system/etc/rootfs/init.choles.rc is ported and merged with our init.mapphone_umts.rc to create a new system/etc/rootfs/init.mapphone_umts.rc
I think that's where we need to start anyway.

Mioze7Ae said:
I'm not going to have a chance to try this until next week (traveling, stupid work), but the updater script has a check for board name and refuses to install unless you're on choles. You should be able to unzip the files and edit META-INF/com/google/android/updater-script to remove this line:
assert(getprop("ro.product.device") == "choles" || getprop("ro.build.product") == "choles" || getprop("ro.product.board") == "choles");
Then delete the signature files META-INF/CERT.RSA META-INF/CERT.SF META-INF/MANIFEST.MF and rezip. It should then apply in OpenRecovery because it doesn't require signed updates.
Nevertheless, it probably won't boot until system/etc/rootfs/init.choles.rc is ported and merged with our init.mapphone_umts.rc to create a new system/etc/rootfs/init.mapphone_umts.rc
I think that's where we need to start anyway.
Click to expand...
Click to collapse
Please complete the rom to xt720/xt711
Sent from my XT720 using XDA Premium App

Mioze7Ae said:
I'm not going to have a chance to try this until next week (traveling, stupid work), but the updater script has a check for board name and refuses to install unless you're on choles. You should be able to unzip the files and edit META-INF/com/google/android/updater-script to remove this line:
assert(getprop("ro.product.device") == "choles" || getprop("ro.build.product") == "choles" || getprop("ro.product.board") == "choles");
Then delete the signature files META-INF/CERT.RSA META-INF/CERT.SF META-INF/MANIFEST.MF and rezip. It should then apply in OpenRecovery because it doesn't require signed updates.
Nevertheless, it probably won't boot until system/etc/rootfs/init.choles.rc is ported and merged with our init.mapphone_umts.rc to create a new system/etc/rootfs/init.mapphone_umts.rc
I think that's where we need to start anyway.
Click to expand...
Click to collapse
I noticed that too and you;re right i modified the Choles to Sholes pushed a Sholes config from another deleted certs reziped and did not boot...
Then i remembered the RAMDISK and of course right again the init.mapphone_umts.rc is different on xt701 so have to mod some more

hellmonger said:
I noticed that too and you;re right i modified the Choles to Sholes pushed a Sholes config from another deleted certs reziped and did not boot...
Then i remembered the RAMDISK and of course right again the init.mapphone_umts.rc is different on xt701 so have to mod some more
Click to expand...
Click to collapse
thanks for lookin at it. i took a look and i have no idea. hopefully you can get it working for us.

hellmonger said:
I noticed that too and you;re right i modified the Choles to Sholes pushed a Sholes config from another deleted certs reziped and did not boot...
Then i remembered the RAMDISK and of course right again the init.mapphone_umts.rc is different on xt701 so have to mod some more
Click to expand...
Click to collapse
This ROM uses a slightly "cleaner" hijack than what we've been using (this cleaner hijack seems to be widely used in the Milestone ROMs). If you're familiar with Dexter's XT720 hijack the translations are roughly:
Dexter: 2nd-init controlled by /system/bin/mod_boot_mode.p1.sh
Milestone: 2nd-init managed by /system/bin/sh_hijack.sh
Dexter: ramdisk updated for 2nd-init from /system/ramdisk.tar
Milestone: ramdisk updated for 2nd-init from /system/etc/rootfs/
On the recent Milestone ROMs (including nadlabak's CM6, CM7 and TheFroyoMOD) all the hijacks go through skrilax's /system/bin/sh which is what controls entry to OpenRecovery. /sytem/bin/sh will either boot openrecovery or execute /system/bin/sh_hijack.sh or simply continue with normal boot. On Dexter's ROM the sh_hijack pathway is not used for 2nd-init (Dexter used a mot_boot_mode hijack later in the boot process for 2nd-init instead)
I've been working on porting Dexter's 1.3 to use the sh_hijack.sh instead of mot_boot_mode thinking that will help port Milestone ROMs, but at the moment for some reason I can't get USB to work when using sh_hijack.sh. Probably something simple. But maybe these hints can help someone beat me to the punch.

go guys!!! i will support you!!!

hi guy,i have get a XT720 from a friend

stlifey said:
hi guy,i have get a XT720 from a friend
Click to expand...
Click to collapse
you got xt720? so did you try to port the CM7 to xt720? can you share your experience..

So is this Cyanogen Mod 7 with Gingerbread ??
probably with a port we can get gingerbread on our xt720 even if the bootloader is locked, right?

Related

[Q] Include Bali Kernel in a ROM I'm building?

I'm attempting to build my first ROM and I'm curious how to add a kernel to the ROM.
(more specifically, Bali)
Any help is appreciated.
i cant answer your question, but if you need any help, let me know and i will help out any way i can
In updater script
Code:
set_perm(0, 0, 755, "/tmp/updates/redbend_ua");
ui_print("++ Installing kernel");
run_program("/tmp/updates/redbend_ua", "restore", "/tmp/updates/zImage", "/dev/block/bml7");
You'll need redbend_ua and zImage which you can find in the updates folder of other roms. I'd ask a dev if you can use them. I can't believe it's not butter uses them.
FBis251 said:
In updater script
Code:
set_perm(0, 0, 755, "/tmp/updates/redbend_ua");
ui_print("++ Installing kernel");
run_program("/tmp/updates/redbend_ua", "restore", "/tmp/updates/zImage", "/dev/block/bml7");
You'll need redbend_ua and zImage which you can find in the updates folder of other roms. I'd ask a dev if you can use them. I can't believe it's not butter uses them.
Click to expand...
Click to collapse
Alright, but before doing that...I'm getting an error when trying to flash the custom ROM in CWM.
E: Error in /scard/test1.zip
(status 6)
Installation aborted.
Any ideas?
http://lmgtfy.com/?q=cwm+status+6
First thread 3rd post
FBis251 said:
http://lmgtfy.com/?q=cwm+status+6
First thread 3rd post
Click to expand...
Click to collapse
Yeah I saw that, except I have no idea how to fix it.
If you use notepad++, open the updater script, go to Edit > EOL Conversion > Unix format. Do that for any other text files/scripts you have.
Thanks, but where is the updater script?
hahah sorry this is my first time making a ROM
META-INF\com\google\android\updater-script
Thank you!

[MOD] DSIXDA kitchen v0.202 updated tools 24.09.2012 NEW option to use SuperSU NEW

1st post: updates by others
2nd post: updates by me
I present you my package of recent updates for DSIXDA kitchen v0.202
This package is for Windows, Linux and Mac.
To use the updates, replace kitchen files with files from package.
Dk202u23092012; this package includes:
* added support for endeavoru credits to theintelligent
* updated wireless tether to v3.2-beta2 credits to harald
* updated busybox to v1.20.2 credits to Denys Vlasenko
* updated Superuser to v3.2-RC3 credits to ChainsDD
* updated zipalign to vR20.0.3 credits to Google
* updated apps2sd to v2.7.5.3 Beta 04 credits to tkirton
* updated unyaffs to v0.9.4 credits to ehlers
Click to expand...
Click to collapse
I take NO credits for these tools, only for sharing my package with the community, happy cooking!
Here you'll find experimental mods made by me. Please test it and give me some feedback.
NEW em2Dk202u24092012; this package includes:
* NEW added option to root your rom with chainfire's SuperSU v0.96 NEW
* removed option "old" incl. Superuser.apk and su binary
Click to expand...
Click to collapse
To use this update, replace su_files folder and do_root file from your kitchen with su_files folder and do_root file from package.
Plz test and report me back, enjoy!
emDk202u24092012+; this package includes:
* added support for primo aka HTC One V
* added support for ville aka HTC One S
Click to expand...
Click to collapse
To use the updates, add files from package in kitchen folder.
Remember these updates are experimental! I don't own these devices so can't test them myself!
I hope this helps you !:angel:
updated post 2, enjoy!
I can use this to build for the Samsung galaxy tab 2 7.0
Sent from my SGH-T679 using Xparent Blue Tapatalk 2
hatememarkz said:
I can use this to build for the Samsung galaxy tab 2 7.0
Sent from my SGH-T679 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Samsung Galaxy Tab 2.7.0 not supported yet...
updated 2nd post, added a great new experimental option! plz test it and give me feedback.
i dont know what im doing wrong here.. im getting this error
E: Error in /sdcard/Arquivo/roms/MIUI_X/MIUI_X_2.9.21_RC1.zip
(Status 6)
Installation aborted.
ill descrive my steps
1. Copyed endeavoru (without .txt extension) to tools/edify_defs/
2. Extracted ROM and converted updater-script to update-script like kitchen recomends
3. Made my changes
4. Builded ROM in interactive mode (1) in kitchen
5. Kitchen converted automaticaly to updater-script
6. Selected option "Proceed: updater-script and update-binary will be moved to the ZIP file.."
7. sign, copy to phone, etc
and when i go to flash it, i got that error ...
im using your kitchen...
this in HTC ONE X (enderavou)
any clue about this ?
3. Made my changes
Click to expand...
Click to collapse
What changes? tell me in detail plz
im using your kitchen...
Click to expand...
Click to collapse
not mine, kitchen owner is DSIXDA
l3inky said:
What changes? tell me in detail plz
not mine, kitchen owner is DSIXDA
Click to expand...
Click to collapse
nothing special ... deleted some apks in system/app (bloatware) and added some (gaaps) and edited build.prop with notepad++ just to change timezone
sorry .. your kitchen mod
im going now to build and untouched rom .. just to see if the problem is from my changes .. but i didnt changed anything special .. so i supose thats not the problem .. but just in case.. im going to test it ..
im going to extract the rom "miuiportugal_OneX_2.9.21_Signed.zip" and build it with kitchen defaults
convert updater like it recomends on extract..
and convert again to updater in building like it recommends
just to see if the problem is in the kitchen or my changes
---------- Post added at 07:48 PM ---------- Previous post was at 07:24 PM ----------
same problem .. same error ...
didnt change anything this time ...
just extracted rom and build it again with kitchen defaults
dont understand .. kitchen recognizes the device when converting scripts ...
maybe because the source rom its MIUI ? i tryed miui eng / pt / ch / rd .. and same problem ..
maybe java path invalid (\Java\jre7\bin) dont know if kitchen uses java ..
maybe cygwin version ?
lol .. what a strange thing ... do i need to change more files in kitchen ? i just downloaded the last kitchen release and applyed your mod ...
btw i founded this on changelog
Version 0.190 (March 26, 2012):
Change end-of-line characters in update(r)-script to proper format when building ROM. This gets done in case a noob modified the file with non-Unix compliant editor. Prevents 'Status 6' error when flashing ROM in custom recovery.
but it doesnt make sense because im not doing edits and i dont have < 0.190 kitchen
ruizit0 said:
nothing special ... deleted some apks in system/app (bloatware) and added some (gaaps) and edited build.prop with notepad++ just to change timezone
Click to expand...
Click to collapse
You don't need the kitchen for these changes mate!
+ I don't know what goes wrong with you, aosp and kitchen not a good match i guess
Mayb you can contact dsixda for your problem but again, if these are the only changes you wanna make you don't need the kitchen!
l3inky said:
You don't need the kitchen for these changes mate!
+ I don't know what goes wrong with you, aosp and kitchen not a good match i guess
Mayb you can contact dsixda for your problem but again, if these are the only changes you wanna make you don't need the kitchen!
Click to expand...
Click to collapse
yeah i know .... but i dont plan to make only that changes
it was only to test the kitchen ... i cant contact dsixda he stopped development of the kitchen :\
dont know what to do .. do you have an HOX ? i need to find someone with an hox to zip me the kitchen folder and send me just to see if it works ... or if its from my computer setup ...
i installed everything with a tutorial i saw here on forum .. maybe it wasnt the best tutorial to setting up the kitchen .. dont know :| damn
just in case someone can give me a clue...
here's some info and logs .. i think kitchen is converting wrong the updater-script... but why .. i dont know.. differente HOX versions ?
the part of flashing
Code:
-- Installing: /sdcard/Arquivo/roms/MIUI_X/endeavoru_signed_092512_200944.zip
Finding update package...
I:Update location: /sdcard/Arquivo/roms/MIUI_X/endeavoru_signed_092512_200944.zip
Opening update package...
Installing update...
line 4 col 20: syntax error, unexpected STRING, expecting $end
1 parse errors
E:Error in /sdcard/Arquivo/roms/MIUI_X/endeavoru_signed_092512_200944.zip
(Status 6)
Installation aborted.
and here's the full log
https://www.dropbox.com/s/f5b97a4tt2rlbqu/recovery.log
and here's the updater-script created by the kitchen
https://www.dropbox.com/s/7h8wl5a5vizen08/updater-script
For now use this workaround: when rom is builded replace meta inf folder with original, when im home i,ll take a look at it.
Sent from my HTC One X using xda app-developers app
l3inky said:
For now use this workaround: when rom is builded replace meta inf folder with original, when im home i,ll take a look at it.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thanks l3inky!
detailed problem in here if you can check logs and specs etc
i didnt mentioned your mod in there to not cause more confusion .. but using your mod or not, the problem is the same, so the problem is not from your mod
http://forum.xda-developers.com/showthread.php?t=1906605
thanks again
Can u plz send me this: original updater-script, converted update-script and final updater-script.
Problem solved thanks to "backfromthestorm" hint!!
The problem is the Kitchen update to updater conversion.
The kitchen doesnt make correctly the conversion.
So the solution is:
not give any script to kitchen for conversion, remove META-INF folder from original zip and let kitchen create a fresh updater..
It doesn't fix the converting problem does it, also very interesting you prefer removing meta inf en make a new one then just changing 2 lines in updater script, 2 workarounds in my opinion, anyway can u send me those 3 files i asked for cause i wanna fix this problem.
Sent from my HTC One X using xda app-developers app
l3inky said:
It doesn't fix the converting problem does it, also very interesting you prefer removing meta inf en make a new one then just changing 2 lines in updater script, 2 workarounds in my opinion, anyway can u send me those 3 files i asked for cause i wanna fix this problem.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
you are right .. but i prefer to create a new one because its less work, i have to remove the ui_print and other symlinks, so for me its easyer create a new one.
but the perfect is if the kitchen can make correctly the conversion ...
here it is what you asked
https://www.dropbox.com/s/7fd3kboz0htiur7/updaters.zip
it will be great if you can fix that.. if you need something from me just ask!
thanks
made another test .. but this time with other rom...
the kitchen converts the updater bad again but with other errors ..
this time it add spaces to lines
here is the files from the another test ...
https://www.dropbox.com/s/vim2rpgrgmij3j9/updaters_2.zip
the kitchen is all messed up when converting updater .. i think the best is to stick to the original updater dont make conversion and make manual changes on the end ..
and hope DSIXDA gets back to kitchen development, or maybe someone makes another kitchen and give support to it :\
EDIT: found some bugs when removing META-INF folder from original zip and let kitchen create updater by his own .. for example in MIUI rom some functions stop working ... like theme applying etc... i think kitchen jumps something maybe permissions .. when creating updater
for now, and for me, the best option is to let META-INF in original zip, and when extrating rom when kitchen asks to convert updater to update, dont convert, and after edit original updater mannualy and make the changes
ruizit0 said:
made another test .. but this time with other rom...
the kitchen converts the updater bad again but with other errors ..
this time it add spaces to lines
here is the files from the another test ...
https://www.dropbox.com/s/vim2rpgrgmij3j9/updaters_2.zip
the kitchen is all messed up when converting updater .. i think the best is to stick to the original updater dont make conversion and make manual changes on the end ..
and hope DSIXDA gets back to kitchen development, or maybe someone makes another kitchen and give support to it :\
EDIT: found some bugs when removing META-INF folder from original zip and let kitchen create updater by his own .. for example in MIUI rom some functions stop working ... like theme applying etc... i think kitchen jumps something maybe permissions .. when creating updater
for now, and for me, the best option is to let META-INF in original zip, and when extrating rom when kitchen asks to convert updater to update, dont convert, and after edit original updater mannualy and make the changes
Click to expand...
Click to collapse
You probably have a problem with mount points & update binary. Make sure your device is supported by kitchen else manually create edify_defs for your device or Replace update binary in kitchen cooked meta inf folder with the one from original rom and edit kitchen updater script - change the lines with mount(...........) in new updater script to look exactly like the one in original rom's updater script. You can search xda forum for more info on edify language used in updater scripts. Most of changes you need make in updater sript will be within first 5lines. You can pm me if problem but also post response here
Sent from my GT-B5512 using Tapatalk 2

[Rom][Aroma]AllInOneCM10 [Team Legacy]

Cyanogenmod 10
By Team Legacy
Please test, logcat, feedback, and hit thanks
This is a port from the CM10 nightlys which are being built by shelnutt2 for the hero cdma.
This rom uses Aroma installer in order to make it boot on the following devices; HTC Droid Eris, HTC hero GSM, HTC Magic and HTC hero CDMA making it easier and faster to port the nightlys. It was originally created by whoshotjr2006 and then tweaked and maintained by me, all thanks goes to him!
Github
https://github.com/Jordfaz/AllInOne-Cyanogenmod-10
Features
- Jelly bean (4.1.1)
- Jelly bean trebuchet
- Google now
- Theme chooser
- Customisable lockscreen and statusbar
- Performance settings
Bugs
- Doesn't boot.
- You tell me.
Credits
- Mongoosehelix
- Shelnutt2
- Whoshotjr2006
- Cyanogen
- Dsixda
- Hero CDMA crew
- Hero GSM crew
- Droid Eris CDMA crew
- Amarullz
- Benjamingwynn
- Powerplop
- Kemoba
Download
Download from Mediafire
Note: Im only going to put in the changelog things done by me, and not the CM team.
Note: Always backup your rom before installation.
Changelog
01/10/2012
- Initial release
Screenshots
Soon.
hello, I'm glad someone spend time with our old HTC Magic, now my HTC Magic is more alive than ever.
I can not install, the following error appears:
SINTAX ERROR!!! aroma-config on line 15 col 1
So sorry, ill correct it tonight
I have a 32A Magic/Sapphire and I want to help testing this ROM, is it working at all for 32A? or do you want to know the errors it makes when installing?
Cheers!
I just made a mistake in the script, correcting right now
I can't install this rom on my Magic 32A because the aroma touch screen doesn't work and so I can't check the license agreement of aroma.
I have the latest recovery for Magic 1.7.0.1 but no touch screen possibility...
Anyone got help?
Getting this error
not sure if its showing attached images.. so heres a link directly to the image
http://www.timelord83.com/mytoucherror.jpg
Timelord83 said:
Getting this error
not sure if its showing attached images.. so heres a link directly to the image
http://www.timelord83.com/mytoucherror.jpg
Click to expand...
Click to collapse
getting the same error
katurras said:
hello, I'm glad someone spend time with our old HTC Magic, now my HTC Magic is more alive than ever.
I can not install, the following error appears:
SINTAX ERROR!!! aroma-config on line 15 col 1
Click to expand...
Click to collapse
The same error :/
6.35.16.19 & 1.76.2007
CWM 5.5
Ye its an error in my script, ill correct it tonight!!!
Oh and try toggling signature verification.
Error at line 15 col 1? I'll have a look at aroma now, it doesn't seem too hard to use in ROMs after all
Btw does it boot, are things working? If not, are they kernel related or something else?
kanttii said:
Error at line 15 col 1? I'll have a look at aroma now, it doesn't seem too hard to use in ROMs after all
Btw does it boot, are things working? If not, are they kernel related or something else?
Click to expand...
Click to collapse
Sorry i dont have a htc magic:laugh::laugh:
To fix install errors, unzip the attatched file and replace the Meta-inf folder in the rom and replace it with the attached one
jordfaz said:
Sorry i dont have a htc magic:laugh::laugh:
To fix install errors, unzip the attatched file and replace the Meta-inf folder in the rom and replace it with the attached one
Click to expand...
Click to collapse
updated the META-INF same error as before.. no idea
Timelord83 said:
updated the META-INF same error as before.. no idea
Click to expand...
Click to collapse
The same syntax error line 15 Col 1?
jordfaz said:
Sorry i dont have a htc magic:laugh::laugh:
To fix install errors, unzip the attatched file and replace the Meta-inf folder in the rom and replace it with the attached one
Click to expand...
Click to collapse
Not line 15 col 1, but line 199 col 10 this time :/ (aroma-config)
SYNTAX ERROR !!! aroma-config on line199 col 10
jordfaz said:
The same syntax error line 15 Col 1?
Click to expand...
Click to collapse
Dear Jordfaz,
I've just applied new "META-INF" into the rom but cannot install completely.
SYNTAX ERROR !!! aroma-config on line199 col 10.
L.X.Phuong
jordfaz said:
The same syntax error line 15 Col 1?
Click to expand...
Click to collapse
no my same error as before no signature found stuff
E:No signature (1301 files)
E:Verification failed..
i am using the RA-1.7.0 recovery does that matter?
You need CWM recovery in order to install.
My laptops playing up so you'll have to wait for another fix, but you could try fixing it yourself with notepad++, just go into the meta-inf folder and find aroma-config, look for the line 199 column 10 (which is the error), and trying changing it
otherwise wait patiently

[GUIDE]Step by step guide file edits to port I9300-I9305+ CWM .zip Jkay mod for I9305

Hey guys,
**TESTING ONLY** ALPHA WARNING...NOT TESTED AS YET! PLEASE MAKE A BACKUP IN RECOVERY FIRST!!!!!
Tested and working. Some settings not implementer fully though? Unsure if this is a bug or if this is due to my mods, but will be investigating further.
*UPDATE* Updated the updater script to check the build.prop AFTER the file system has been mounted, this was causing a failure due to write protect and booting us out of the installation tested and the script is working fine
*UPDATE* updated the android.policy.jar to Jkay deluxe version as the main base. I will be looking into how the deluxe settings app checks this file to ensure it is the correct version, If this is smali textual based then we have no problems for future releases, however if it is somehow checking against MD5 hashes for this file and we make edits as what is descibed below then this is always going to break the settings app and put it in demo mode. I will report back here when I have more information.
Attached are some downloads for everyone. One is the Jkay Mod for XXELKC (only) port to our devices GT-I9305. I haven't had a chance to test it yet as I am very busy. The flashable zip does NOT include the Deluxe settings apk (it doesn't delete it from system app if you do have it though, must be version 14.3x to work though) you will still need to purchase this from the Google Play store.
Hence another reason why I have not tested this package (a long story) anyways...cause I don't have access to the Deluxe Settings apk.
Currently been testing this and its working fine but with some bugs? Unsure if these are port related or the fact that Jkay deluxe is alpha and buggy?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
There is a step by step process on how to EDIT FILES jar files that are required for porting GT-I9300 ROMs to I9305. All other steps and configurations that a required for porting that do not involve file edits (only swapping files in and out) are not covered by this guide. There are many additional steps not covered by this guide that are required in addition to these steps in order to make full port of a ROM. Additional,libraries, binaries, build.prop edits, apks and permissions xmls are required
The above are mentioned additional requirements for a full port are outside the scope of this guide but maybe included in following updates
**UPDATE** please do not migrate or change anything in the android.policy.jar file for Jkay settings files if you are wanting to port them in the furture, The Deluxe settings application checks this file to ensure you are running the correct version and running the Jkay framework. If you are receiving framework mismatch type errors this is due to running an illegal copy of the Jkay Deluxe Settings application. The application checks back to GooglePlay store to see if your google account is a registered user or not, when this fails the app defaults into demo mode. Clearing application data results in settings being wipe and a reconfigure is required. Note: That none of your settings are retained by the deluxe settings app after a reboot if it has failed license checking.
I have also included all the smali and baksmali files and wrapper scripts along with the add and replace files to port the necessary files to make GT-I9300 ROMS work on our devices.
YOU MUST DO IT IN THIS ORDER!
*** please please do the remove smali files processes first!***
NOTE: The remove folders e.g framework2-remove are here *ONLY* as a references for you! What I mean is that you now have to navigate the folders of your decompiled files and remove these specific smali references from the GT-I9300 jar files.
There are 4 main files to change and several changes to be done, so please make sure you give thanks to developers like AusDim for his ahard work. When you see the amount of files you may appreciate this
I was working this port myself, but it wore thin on my patience, alas I diverse....
android.policy.jar please disregard the edits to this file as we have found that the standard Android.policy.jar file from standard I9300 seems to be all in order to work on the LTE device. More information regarding this file may come in future updates
framework.jar
framework2.jar
services.jar
HOW TO:
Use the open_commandprompt_here to launch cmd in the current directory.
decompile the specific file like following, in this example I have chosen services.jar file. NOTE: You may also wish to perform any other modifications to the services at this time i.e. V6Supercharger multi-tasking update for JB (thanks to zepplinrocks)
e.g
Code:
decompile services.jar
open the folder services-add and copy the "com" folder
open the out folder and you will see another "com" folder inside; hit paste. Accept any prompts to overwrite smali files or folders. click yes to all bla bla bla
recompile the smail code like this:
e.g
Code:
recompile out -o classes.dex
Right click your services.jar file and open it with say 7zip or WinRAR or what ever archive application you currently use; inside you will see a classes.dex file. You are now going to drag and drop your new compiled classes.dex file in over the top of the existing one.
Close your services.jar file
and you are done!
Now repeat to the other remaining jar files and Bob's ya aunty you're good to go
Special thanks goes out to:
_Jkay_ first and foremost for the awesome Jkay Deluxe framework
Thanks to AusDim who put in the hard yards to getting the initial port done for us I9305 users. Your work is very much appreciated by me mate.
Thanks to txr33 for his work in the back ground in the early stages as we both tried to nut out what the f#*% was going on with our stupid port :silly: ...
If I have left anyone off this list, then please contact me and I will be more than happy to add you (thats if you have helped and don't just want to be famous jks)
Thanks guys
Tutorial
HOW_TO_PORT_GT-I9300_TO_I9305.zip
Jkay deluxe for I9305 Note this link will produce a 404 error until such time as it has completed upload
XXELKC_JKay_Deluxe_v14_3_PORTI9305.zip
PS: I have a feeling that my dropbox account is going to get smashed after this, so can someone please re-upload and mirror after they have tested it? ThanksEDIT: *correction* I have a feeling that my dropbox is going to be a ghost town with zero downloads cause this is the I9305 section so no need to mirror as part of my initial request
reservered.
May take a while to actually be on dropbox, so please be patient
This was a rushed job. Please report any issues and I will do the best I can to sort them out for you. Please don't make any demands or tell me I have broken your phone or what ever. This is a developer forums, this is a place where people can come to share their work.
Jarmezrocks said:
reservered.
May take a while to actually be on dropbox, so please be patient
This was a rushed job. Please report any issues and I will do the best I can to sort them out for you. Please don't make any demands or tell me I have broken your phone or what ever. This is a developer forums, this is a place where people can come to share their work.
Click to expand...
Click to collapse
Good to see things start to pick up in the I9305 therad. Thanks.
stian230 said:
Good to see things start to pick up in the I9305 therad. Thanks.
Click to expand...
Click to collapse
There's still tumbleweeds blowing around this place (man it's the longest uptake that I have seen yet for a new device....that's not even new anymore) but we will get there eventually
Not surprised at all that your 1 comment is the only comment post so far lol.
This is awesome, thank you for the info
Sent from my GT-I9305 using xda app-developers app
Jarmezrocks said:
There's still tumbleweeds blowing around this place (man it's the longest uptake that I have seen yet for a new device....that's not even new anymore) but we will get there eventually
Not surprised at all that your 1 comment is the only comment post so far lol.
Click to expand...
Click to collapse
I bet it's more activity in the HTC G1 forum end this place and I'm still kinda surprised that we didn't get a dedicated forum for the I9305
Hi man you are as rock as your name!
P.S. I've seen you in Galaxy S Android Development before!
First of all, many thanks for this
Now for the noob questions
Can I flash this over the top of say Pandorium then use JKAY from the market or will I have to wait for one of the excellent ROM guys to make a JKAY compatible build ?
Thanks for this
Quick question though; what are these 'lte settings apks' that you speak of?
Ok, had some problems and need your help.
Im on xxelkc ausdim port.
First i booted into cwm and tried to flash the framework, but everytime cwm said that it cant find /system/build.prop
After serveral tries, i realized that i had to mount /system manually. Then it worked without problems.
Then i downloaded the deluxe settings from the play store and installed it. But when i run the apk, i tells me that no compatible framework is found. At the about screen it shows me:
Deluxe settings 14.4
Framework 14.3
SystemUI ?
ExtVersion ?
Android Policy ?
Can someone tell what i have to do to make it work?
Ok, i found out that the updater-script doesnt copy any of the files. After copying them manually in the right folder, everything worked well...
So the updater-script needs to be rewritten and with a mount /system command at the beginning.
MrGubby said:
First of all, many thanks for this
Now for the noob questions
Can I flash this over the top of say Pandorium then use JKAY from the market or will I have to wait for one of the excellent ROM guys to make a JKAY compatible build ?
Click to expand...
Click to collapse
Yes, you should be able to flash this over the top of Pandorium if you are using the latest XXELKC version. And yes the Jkay Settings app on the market from 14.3 upwards. I think there is only 14.3 and 14.3.1? No earlier versions will work for this framework.
I have noted that there is an issue with the Settings app not detecting the framework and it says you must be running Jkay framework. I was reading a few posts in Jkays thread and this does lead me to believe that there are still bugs in the alpha framework....hence it's alpha status.If you get this fault the XDA member mentioned that he just applied some of the settings anyway and then rebooted his phone and everything appeared as normal after a reboot.
Hope this helps
glowfinger said:
Ok, i found out that the updater-script doesnt copy any of the files. After copying them manually in the right folder, everything worked well...
So the updater-script needs to be rewritten and with a mount /system command at the beginning.
Click to expand...
Click to collapse
Um there is a mount command at the start of the script? all that I have changed in my updater script is that it does a grep for the build.prop to ensure that the user flashing this mod is flashing it to an LTE device, as they have a different partition layout to the stock I9300 as we are all aware. I knew that partition 13 is where we locate our system partition but was not aware of what this refers to on the I9300? Meaning that if the ways were reversed I didn't want someone accidently flashing this zip file and bricking or loosing the IMEI number due to corrupted efs directory or something like that.
Other than that, I just pasted my fancy bit of test above it (with no commands affecting it what so ever) and removed the delete command that tells the script to delete Jkay settings if it is in system already located. I assume that this was put in place to ensure that when a new framework was released by Jkay that the correct Deluxe settings app was used with it - or else you get SystemUI status bar crashes until it is removed. I removed it cause like me some users side load their apks and its a pain in the arse to re-add the Jkay settings app into system again .
here is the updater script
Code:
show_progress(0.500000, 0);
ui_print("");
ui_print("");
ui_print("");
ui_print("");
ui_print("");
ui_print("");
ui_print("");
ui_print("");
ui_print("");
ui_print("");
ui_print("**********************************************");
ui_print("* *");
ui_print("* *");
ui_print("*.... JARMEZ'S SGS 3 LTE Jkay Port ....*");
ui_print("* *");
ui_print("* For the I9305 LTE SGS 3 only *");
ui_print("* *");
ui_print("**********************************************");
ui_print("* Checking your build.prop... *");
assert(file_getprop("/system/build.prop", "ro.product.model") == "GT-I9305");
ui_print("* Congrats your running I9305 AusDim Port *");
ui_print("* Deleting Old System Files... *");
run_program("/sbin/mount", "/dev/block/mmcblk0p13", "/system");
run_program("/sbin/mount", "/dev/block/mmcblk0p16", "/data");
show_progress(1.000000, 0);
ui_print("* Deleting JKay Deluxe data... *");
sleep (1);
run_program("/sbin/mount", "-t", "ext4", "-o","rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard","/dev/block/mmcblk0p12", "/data");
set_progress(0.100000);
run_program("/sbin/rm", "-rf", "/data/dalvik-cache/[email protected]@com.jkaysoft.icsdeluxe*");
run_program("/sbin/rm", "-rf", "/data/app/com.jkaysoft.icsdeluxe*");
delete("/data/dalvik-cache/[email protected]@[email protected]");
delete("/data/dalvik-cache/[email protected]@[email protected]");
delete("/data/dalvik-cache/[email protected]@[email protected]");
delete("/data/dalvik-cache/[email protected]@[email protected]");
delete("/data/dalvik-cache/[email protected]@[email protected]");
set_progress(0.200000);
run_program("/sbin/rm", "-rf", "/data/data/com.jkaysoft.icsdeluxe");
run_program("/sbin/rm", "-rf", "/data/dalvik-cache/[email protected]@com.jkaysoft.icsdeluxe*");
run_program("/sbin/rm", "-rf", "/data/app/com.jkaysoft.icsdeluxe*");
set_progress(0.300000);
run_program("/sbin/sync");
sleep (1);
set_progress(0.400000);
run_program("/sbin/umount", "/data");
package_extract_dir("system_common", "/system");
sleep (1);
set_progress(0.600000);
ui_print("Setting Permissions");
set_perm_recursive(0, 0, 0755, 0644, "/system/framework");
set_perm_recursive(0, 0, 0755, 0644, "/system/app");
sleep (1);
set_progress(0.700000);
sleep (1);
set_progress(0.800000);
sleep (1);
set_progress(0.900000);
sleep (1);
set_progress(1.000000);
show_progress(1.000000, 0);
ui_print("* Your device should reboot... *");
unmount("/system");
unmount("/data");
run_program("/sbin/sleep", "6s");
run_program("/sbin/reboot");
EDIT: I have just realised the issue. The grep command to assert the build.prop is before the system has been mounted, so recovery cannot locate the build.prop file when it asserts
rbimdxe said:
Thanks for this
Quick question though; what are these 'lte settings apks' that you speak of?
Click to expand...
Click to collapse
Umm unless you have attempted to port a ROM your self already then it's really not necessary for you to know. The LTE settings along with a string of different librarys and binary files as well as build prop edits, the jar file edits (described) in order to port non-LTE I9300 ROMs to LTE. If you have a snoop around in /system/app and look at the difference between the two devices you will notice that there are several apks that appear different/are different, among them are the aforementioned LTE settings.
glowfinger said:
Ok, had some problems and need your help.
Im on xxelkc ausdim port.
First i booted into cwm and tried to flash the framework, but everytime cwm said that it cant find /system/build.prop
After serveral tries, i realized that i had to mount /system manually. Then it worked without problems.
Then i downloaded the deluxe settings from the play store and installed it. But when i run the apk, i tells me that no compatible framework is found. At the about screen it shows me:
Deluxe settings 14.4
Framework 14.3
SystemUI ?
ExtVersion ?
Android Policy ?
Can someone tell what i have to do to make it work?
Click to expand...
Click to collapse
I think you will find that it does work, it's just that it is very buggy and alpha still and sometimes the settings don't stick after a reboot? Anyway it should improve in time. I am not certain if this is an issue with the Jkay Deluxe settings it's self or the framework....either way it is an issue that will still need to be resolved? Keep an eye on the Jkay thread for updates to this?
Jarmezrocks said:
EDIT: I have just realised the issue. The grep command to assert the build.prop is before the system has been mounted, so recovery cannot locate the build.prop file when it asserts
Click to expand...
Click to collapse
This is what i wanted to say....
Sorry for my bad english...
And yes, after putting the files manually in the right folder, its working fine for me... thanks for this :thumbup:
Hey guys,
I have updated the Jkay zip file. I had used the port base android.policy,jar file and this is what is needed to register against the Deluxe Settings app so I have found out. So with that I have reverted the android.policy.jar file to stock Jkays, however I am going to try port back the other way and see if that has any affects?
Is anyone experiencing framework type mismatch error in Deluxe Settings?
I may need to speak to Jkay about this as there maybe something within the framework.jar files that his app is dependent on for I9300 that we have changed or removed for our devices?
JRock... Big ups for creating this thread bro. Its got some great information and a wonderful place for ppl to start. We have some documents to share 're compiling , github, basic sysadmin stuffs etc. Pm me or talk me and id be happy to share ! [email protected]. (Yes the liquidsmooth port is still in works!
Sent from my GT-I9305 using xda premium
I almost tried to to flash the original jkay mod but then did a search on whether it is compatible with the i9305 at all. Glad I found this
Soo, is jkay mod working as intended with our device? I'm reading about issue here but the thread seems a bit deserted... anyways I'm eager to try this out and hope OP will continue to do ports! Thank you very much, good sir!

sense 4+ JB

here you go.
just download and flash.
thanks to Jonny for being so co-operative and giving me his dev-host details to upload this.
MOD EDIT: Link removed, Looking into it.
(i am not responsible for anything that may go wrong or happen to your device, make nand backup 1st)
Let me try this.
EDIT: All the important stuff you need to know about this 'ROM' is located here:
http://forum.xda-developers.com/showpost.php?p=36349768&postcount=14
http://forum.xda-developers.com/showpost.php?p=36349876&postcount=15
http://forum.xda-developers.com/showpost.php?p=36350178&postcount=24
http://forum.xda-developers.com/showpost.php?p=36350523&postcount=30
THIS ROM IS FAKE. DON'T DOWNLOAD IT, IT WON'T EVEN FLASH (and if it would it wouldn't boot).
Da **** ... this is crazy!! ...
why do I have the feeling that there is something wrong with this ? :\
Let's check it!
Really sick, downloading atm. We'll see it in 5 minutes :good:
Is this legit? Im not going to risk it.
Jonny (Respectable Mod & Dev) has been helping the guy with his dev-host details so why would it not be legit.
avarage of 110KB/s takes 1hour and a half, if someone gets to boot it first... tell us Thanks!
Downloaded succesfully, will report back soon..
Check this post in a few min.
______
I don't think it'll boot since the /system/app/ is still odexed.
At last....
Sent from my HTC Sensation using Tapatalk 2
~600kb/s for me. 10mins left.
~1277kb/s 3 minutes... I'm excited as hell:laugh:
I'm pretty sure it won't boot by looking at all the files, etc..
---------- Post added at 12:40 PM ---------- Previous post was at 12:38 PM ----------
updater-script:
Code:
# Htc Script Version: J1.2
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" , "HTC__621") == "t");
);
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_mid("full", "PJ4020000") == "t");,
assert(check_mid("simple", "PJ4020000") == "t");
);
assert(getprop("ro.product.device") == "villec2" ||
getprop("ro.build.product") == "villec2");
Since we don't have the right bootloader, it won't work, so guys don't attempt...
Well I tried to flash it, but recovery couldn't which isn't too crazy if you look inside the zip file. OP I don't know how you built this, but the META-INF folder is supposted to be OUTSIDE all the others. And there are a lot of those OSX file system files inside the zip too.
TL;DR: THIS DOESN'T WORK.
V1k70r said:
Well I tried to flash it, but recovery couldn't which isn't too crazy if you look inside the zip file. OP I don't know how you built this, but the META-INF folder is supposted to be OUTSIDE all the others. And there are a lot of those OSX file system files inside the zip too.
TL;DR: THIS DOESN'T WORK.
Click to expand...
Click to collapse
^ ^ this, very weird folder structure.. and everywhere .DS_Store files.
Solar_ said:
Downloaded succesfully, will report back soon..
Check this post in a few min.
______
I don't think it'll boot since the /system/app/ is still odexed.
Click to expand...
Click to collapse
You're probably right. Which RUU does this come from? VilleC2?
Why is there a Venom folder in the ROM?
gabryel48 said:
You're probably right. Which RUU does this come from? VilleC2?
Click to expand...
Click to collapse
Code:
ro.build.product=villec2
ro.build.description=3.14.709.102 CL142363 release-keys
ro.build.fingerprint=htc_asia_tw/villec2/villec2:4.1.1/JRO03C/142363.102:user/release-keys
ro.build.project=VILLEC2_U_JB_45_S:303220
ro.product.version=3.14.709.102
ro.build.sense.version=4.5
The RUU is 3.14.709.102.
Could the OP give us some more info about the rom?
What base, what works and doesn't etc...

Categories

Resources