Related
[Windows APP][I9070] --| TerminalKernel Beta 0.3 & Siri Settings |-- Flash JB Kernels
So guys this program might result kind of useless, still i had some free time and wanted to do something for all the owners of I9070.
This program only works with Windows and I9070!
So basically what does it do?
kernel Installing in the easiest way!
A little Quick Video on how Terminal Kernel Works!
http://youtu.be/fQs0ZwHneTo
Welcome Screen ----> Click Terminal Kernel
Select the Kernel
Select the Push Button
Select the Flash Button
That's IT!
With a new functionality now you can Activate or Deactivate Siri Kernel's features! Wifi Boost and Sound Boost!
I plan on adding Automatic Logcat retrieve etc so that EVERYONE will be able to help our developers EASILY!
Feedbacks would be welcome!
REQUIREMENTS :
Usb Debug ON
(Settings ---> Developer Option ---> Activate ----> Debug Usb)
Rooted Phone Thanks Shaaan!
Shaaan's Root Method for JB
.Net Framework 4.0
Net Framework 4.0
The kernel MUST be flashable from Terminal Emulator (Thunderzap, Siri Kernel and Cocore E)
That's IT!
Download is in NEXT TOPIC (Changelog)!!!
CHANGELOG
Beta 0,3b
Not many changes here really, just code rivisited
Download 0.3b
Beta 0.3
Some stability improvements Added Siri Settings functionality! Now you can switch siri's features on and off! Let me know how it goes guys, bugs are always around the corner!
Beta 0.2.6
Ok should be fixed the problem that papski2 had , but this is a Temporary Build.. With this i mean, you wont see any confirm of the flash, the confirm will be the Phone that Reboots! I'm sleepy and i don't have time to do more testing since i have to wake up early to go to work.. so guys See you tomorrow night!
Beta 0.2.4
Ok i should've fixed a little bug... And i've added Logs Reports! If anything goes wrong please send me the log i would really appreciate it!
Beta 0.2.3
A few more flash performance improvement, now this is a multithreaded app My first multithreaded application Beware guys! No more hangs!
Beta 0.2
Some performance improvement, now takes less time to flash
I guess this is Stable Enough to call it a Beta !
V0.1c
Changed layout, added some info, Soon there'll be a nice tool as well in here
V0.1b
BugFixing, no more Hangs at Flashing of the Kernel i hope!
V 0.1
Initial Release, Alpha build for testing purposes.
WOW!
So We can change kernels easily from PC? Sounds good!
not work for me, stuck after click "Flash This Da*n Kernel"
Re: [Windows APP][I9070] --| TerminalKernel |-- Flash JB kernels from WINDOWS!
To do this , is it necessary that the phone should be switched on. Coz when I flashed a kernel using phone I get in to a bootloop ( stuckb on splash screen)....so can this help.
Sent from my GT-I9070 using xda premium
fongandy said:
not work for me, stuck after click "Flash This Da*n Kernel"
Click to expand...
Click to collapse
Yeah sorry about that, that's a known bug.. uhm... perhaps i should let the user manually reboot his phone.. it's the "adb shell reboot" command that is giving me this issue actually...
Anyway if your phone rebooted you should've flashed it successfully!
atishey23 said:
To do this , is it necessary that the phone should be switched on. Coz when I flashed a kernel using phone I get in to a bootloop ( stuckb on splash screen)....so can this help.
Sent from my GT-I9070 using xda premium
Click to expand...
Click to collapse
Ye... the phone must be switched on and with usb debug enabled.. Uhm that's pretty weird, give it a shot .
Logen91 said:
WOW!
So We can change kernels easily from PC? Sounds good!
Click to expand...
Click to collapse
As long as the Kernel can be flashed via Terminal Emulator YES!
Yeah i have to add that to the first post...
Someone could please give me some feedbacks? I need it to improve the program! xD
Chry_Gigio said:
Someone could please give me some feedbacks? I need it to improve the program! xD
Click to expand...
Click to collapse
Flashed kernel with your application. Just that "Non responding" is little confusing. But you said it will be fixed.
Otherwise all fine.
Q: Where is kernel file pushed? What folder on phone?
shut_down said:
Flashed kernel with your application. Just that "Non responding" is little confusing. But you said it will be fixed.
Otherwise all fine.
Q: Where is kernel file pushed? What folder on phone?
Click to expand...
Click to collapse
Thank you shut_Down that's exactly what i needed a tester for I uploaded another version (0.2.1)... with Non responding you mean that it completely hangs and you have to kill the process? or just that during the flash it hangs? I mean.. do you see the MessageBox that says : "Everything should be fine"?
They are pushed on mtn/sdcard Internel Card... Though if needed i could place it pretty much everywhere..
Chry_Gigio said:
Thank you shut_Down that's exactly what i needed a tester for I uploaded another version (0.2.1)... with Non responding you mean that it completely hangs and you have to kill the process? or just that during the flash it hangs? I mean.. do you see the MessageBox that says : "Everything should be fine"?
They are pushed on mtn/sdcard Internel Card... Though if needed i could place it pretty much everywhere..
Click to expand...
Click to collapse
Not, thats where I put kernels to test. Just wanted to know.
And no, it do not hang. It is just untill flashing is finished. I do see "Everything should be fine", and kernel is flashed. After phone start to reboot app is responding normaly. :good::good::good:
V 0.2.1. is working same, flash went fine. Just it has that Not responding too. It is not problem, just not to pay attention on it.
shut_down said:
Not, thats where I put kernels to test. Just wanted to know.
And no, it do not hang. It is just untill flashing is finished. I do see "Everything should be fine", and kernel is flashed. After phone start to reboot app is responding normaly. :good::good::good:
Click to expand...
Click to collapse
Ok so i have to create a separate Thread in order to handle the flash without hang... Uuuhm.. then i'll upload another version that puts it in sdcard/TerminalKernel
Chry_Gigio said:
Ok so i have to create a separate Thread in order to handle the flash without hang... Uuuhm.. then i'll upload another version that puts it in sdcard/TerminalKernel
Click to expand...
Click to collapse
Ok. And this could be very helpfull, because last few days I flashed a lot of kernels for testing. :good: :good: :good:
With this will be - download kernel, open app, select kernel, flash - done.
shut_down said:
Ok. And this could be very helpfull, because last few days I flashed a lot of kernels for testing. :good: :good: :good:
With this will be - download kernel, open app, select kernel, flash - done.
Click to expand...
Click to collapse
Ok! Anf anf... Now the kernels go into /mnt/sdcard/TerminalKernels/
This is now a Multi-Threaded application so it wont hang anymore
Sorry for going off-topic but can you please tell me how you made this app? I don't want to make or copy your app just want to make an app.. I want to impress my friends and my teachers on my College by making an app similar to this...
Did you use Visual Basic and C++ by any chance... because it looks like that..
I got a problem, i got debug usb mode on but still program says that i don't have it turned on and when i connected phone to PC it still shows on notification bar that it's multimedia mode or something like this. JB XXLPZ + deodex
papski2 said:
I got a problem, i got debug usb mode on but still program says that i don't have it turned on and when i connected phone to PC it still shows on notification bar that it's multimedia mode or something like this. JB XXLPZ + deodex
Click to expand...
Click to collapse
Pull down notification and tap on that. Choose MTP.
shut_down said:
Pull down notification and tap on that. Choose MTP.
Click to expand...
Click to collapse
This is MTP also i tried both options and still not working
R: [Windows APP][I9070] --| TerminalKernel Beta 0.2.3 |-- Flash JB kernels from WINDO
Just got out of work, will answer you ASAP. Which os are you using?
Sent from my GT-I9070 using xda app-developers app
Windows 7 x64, just uninstalled Samsung drivers and installed naked ones, still nothing
R: [Windows APP][I9070] --| TerminalKernel Beta 0.2.3 |-- Flash JB kernels from WINDO
Ok just to make sure, your phone is rooted right? As soon as I get home I'll include a log section in the program and will upload the new one, if you can wait until tonight so that u can send me the log I would appreciate it
Sent from my GT-I9070 using xda app-developers app
Please read this carefully ! Don´t continue if you don´t understand the following easy statements !
1. I am not a Developer ! Nothing of the following Apps/Roms/Tools I post here are made by myself, I am just using them !
2. Do not follow this guide if you plan to use your SII the next 2 hours! (seriously)
3. If anything goes wrong, it is not my fault! It´s the way I made it...Please, think about every step you do, it´s your Phone
4. Do not follow this if you don´t know how to flash a Kernel or a custom Rom and you know that you will be to lazy to learn this with the help of this awesome XDA Forum (like I did)
5. If you find something confusing and can not find a Solution feel free to ask. But please, be nice !
6. English is not my Mom´s language and even tho I do like it, I am sure you will find mistakes. Sorry about this !
Click to expand...
Click to collapse
My Motivation
I do like Cyanogenmod as many of you do. Due to Samsung´s strange behaviour the CM Team still has a hard time with Google´s Jelly Bean on our Galaxy S2. It still causes troubles here and there, even tho the Developers did and do a amazing job on it. Many words, I know, ok, let me get the facts straight : I LOVE CM but I NEED some Samsung stuff.
In the past, with ICS it was possible, thanks to some very (very!!!!) good Developers, to dual boot Samsung ICS Rom and CM Roms. When Jelly Bean leak came out, we had to realize that this wasnt possible anymore as we now got the /preload partition because our /system partition wasnt big enough anymore to carry all needed files.
Even tho it is possible to use jazzk´s chameleon and CM Rom with DorimanX Kernel because jazzk didnt use the /preload partition, it was impossible to use another Stock or custom Samsung Rom.
That bugged me.
Thanks and Credits for all they have done to :
The Cyanogenmod Team for CM10.1
dorimanx for his awesome Kernels
tedascuen for sharing the stock XWLS8 Rom
_Sofos_ for sharing the XWLSD Rom
Goldieking and his Team for his awesome Mods
All those who helped me in this Thread (mentioned below)
Chainfire, of course for so much!
Jrummy Apps inc. for Root Browser Lite
The XDA Comunity for sooo much
My Wife for her Laptop and coffee
Forgot your Name ? Give me a hint!
Update 20.03.2013
I have been a bit lazy lately with all this but I tested some of the DorimanX Kernels. It seems that Kernel 8.3 and higher are more than OK now for booting both, CM and Sammy Roms. To me, as I didn´t follow all this very close, it got a bit confusing. Please read the last Pages, there are always some nice guys testing this & that AND they also give support.
Update 28.02.2013 Part 1
If you are looking for more different Setups / Videos & Tutorials, they are now in Post #6
Update 28.02.2013 Part 2
There has been a lot of confusion with several Updates in CM 10.1. While this is a very good Step ahead for Open Source Projects, it makes Dual Boot with Samsung based Roms a bit harder. dorimanx has been working hard to get it all running, even Dual boot between CM10.1 and XWLSD is possible but for me and many others, Camera and Video is broken in the Sammy Rom. I will edit this as soon as this is fixed because IMO his Version 8 is another Masterpiece.
But for now this will be a "dirty" or "faked" Dual Boot.
What you need :
- DorimanX 7.44 "LSD EDITION" (Thanks to THE RED BLUR for your help)
- Any AOSP/AOKP Rom you want to use
- PreLoadLSDrom.zip (More Details)
(This is an edited XWLSD Rom that fits into our /preload Partition. DON´T use as FIRST Rom, it has NO Kernel)
- Time
Now we start :
- Flash the AOSP/AOKP you want to use as FIRST (!) Rom
- Set it up and (optional if you need the boot.img or just to have a running System backed up) make a Backup from Recovery
- Flash the DorimanX 7.44 "LSD EDITION"
- Reboot into its Recovery and prepare 2nd Rom
- Install PreLoadLSDrom.zip
- Boot into 2nd Rom to see if it works
- Done for now
With this Setup you now have 2 independent Systems on your Phone. Flashing another Open Source Rom in FIRST will not touch your Sammy Rom as all (AFAIK) Open Source Roms don´t use/touch the /preload Partition.
Please note, flashing any Sammy Rom, that´s not edited for this, will delete this Setup.
As long as you are using one of the "older" Open Source Roms you can now boot both Roms from the DorimanX 7.44 "LSD EDITION"
If you use a Open Source Rom with the new Video Drivers (and all these things I don´t understand) you will now need to install the corresponding Kernel each time you want to switch between the Roms. For now, I can confirm that Dorimanx 8 runs perfect with CM10.1 (24th build) because I tested it. So, you may now flash the "LSD EDITION" for the LSD Rom or the DorimanX 8 Kernel for your AOSP/AOKP Rom. This is dirty for now but it´s safe and working. And I am sure there will be a fix for this, soon!
Update 28.02.2013 Part 3
I moved my first Tutorials to Post #3. This got way to confusing here.. Also, this Post is edited to make it easier for the People to find what they are searching for.
Greetings
Thomas
wow, that's amazing man! but dorimax gives me a lot of FC and reboots... I'll wait a week or two before doing this.
How it all began...
Please read this carefully ! Don´t continue if you don´t understand the following easy statements !
1. I am not a Developer ! Nothing of the following Apps/Roms/Tools I post here are made by myself, I am just using them !
2. Do not follow this guide if you plan to use your SII the next 2 hours! (seriously)
3. If anything goes wrong, it is not my fault! It´s the way I made it...Please, think about every step you do, it´s your Phone
4. Do not follow this if you don´t know how to flash a Kernel or a custom Rom and you know that you will be to lazy to learn this with the help of this awesome XDA Forum (like I did)
5. English is not my Mom´s language and even tho I do like it, I am sure you will find mistakes. Sorry about this !
Click to expand...
Click to collapse
My Motivation
I do like Cyanogenmod as many of you do. Due to Samsung´s strange behaviour the CM Team still has a hard time with Google´s Jelly Bean on our Galaxy S2. It still causes troubles here and there, even tho the Developers did and do a amazing job on it. Many words, I know, ok, let me get the facts straight : I LOVE CM but I NEED some Samsung stuff.
In the past, with ICS it was possible, thanks to some very (very!!!!) good Developers, to dual boot Samsung ICS Rom and CM Roms. When Jelly Bean leak came out, we had to realize that this wasnt possible anymore as we now got the /preload partition because our /system partition wasnt big enough anymore to carry all needed files.
Even tho it is possible to use jazzk´s chameleon and CM Rom with DorimanX Kernel because jazzk didnt use the /preload partition, it was impossible to use another Stock or custom Samsung Rom.
That bugged me.
What I had was :
- a stock deodexed and rooted Jelly Bean Rom by Samsung from here
- a CM 10.1 Rom from here
- THE DorimanX Kernel 7.44 from here
- Rootbrowser Lite from Market (don´t know how to link it, but you will find it)
- TIME
If you have what I had, you can try the following lines...
First of all, I flashed the stock deodexed and rooted Rom I mentioned above (thanks to tedascuen for sharing)
I finished the complete Setup of the Rom, including Google Account, WLAN settings..
Now :
- download Rootbrowser Lite from Market
- use Rootbrowser Lite (now called RB) to delete all apps from /system/apps that I don´t need/use
- after that, reboot into stock recovery by holding Volume up + Home + Power
- do a Factory Reset
- reboot the System and finish the Setup of the Rom (as above)
- download RB Lite from Market again
- use RB to copy big files from /preload/symlink/system/apps to a folder in /data/apps/ that I named "sysapps"
Big Files I moved :
- ClockPackage.apk
- MusicPlayer.apk
- SamsungIME.apk
- SecBrowser.apk
- SecContacts.apk
- SecEmail.apk
- SecExchange.apk
- SecGallery2.apk
- SecLauncher2.apk
- SecMms.apk
- SecPhone.apk
- VideoPlayer.apk
Click to expand...
Click to collapse
- now delete the old symlinks in /system/apps of the Files above (you will get some errors/FC while doing this)
- now switch to /data/apps/sysapps and start to create new symlinks with RB by longpressing the file and "create shortcut"
- switch to /system/apps again and paste the shortcut (important, do this one by one, show some patience)
- after you created all new symlinks, reboot the system, you will see, all apps work again!
- most of the other apps from /preload/symlink/system/apps will fit into /system/apps but don´t move useless apps like all apps containing "test" in their name or google plus (you can install that later from market) or "swype" or.... I am to lazy to write down all apps I didnt move but with a bit of common sense you will make it for sure.
- after moving the apps to /system/apps you will see that all apps you moved will be set to rw-r-r and all symlinks you created will be set to rwx-rwx-rwx, thats fine !
- reboot the phone, everything should work fine
If so...
- flash the DorimanX Kernel 7.44 and
- reboot into his recovery
- switch to dual-boot options and set up the 2nd Rom
- clone 1st Rom to 2nd Rom
- reboot into 2nd Rom just to check if it works (it will)
now...
- reboot into recovery and install the CM10.1 made by MCM from here
- after the installation has finished, reboot the system and let CM10.1 boot
(GAPPS are not needed, yet but you may install them before you boot into CM)
- I really hope the CM has booted fine, now open STweaks
- in STweaks, change OpenSource Gralloc to Samsung´s Gralloc
- reboot the system and check in STweaks if the change worked (Samsung´s Gralloc)
now...
- reboot into recovery and flash the DorimanX Kernel again (or use Odin)
- after that, reboot again and you will see the Dual Boot Screen, you can choose first or second Rom
- DONE !!!
Another Way was...
Due to my slow internet connection I will only provide the way and the updater script here. Anybody who likes to help may link the Rom with the updated files here, this would be very kind !
To do what I did I used this : Notepad++ and 7zip !
Ok, lets go !!
- copy the stock deodexed Rom I mentioned above (for the lazy people, Link) to your PC
- Use 7zip to unzip the Rom (or any other tool!)
- unzip the attached file and replace the updater-script in /META-INF/com/google/android/ (in the unzipped Rom)
- in the unzipped Rom, go to /preload/symlink/system and move the complete "app" folder to /data/app
- your data folder should look like this : /data/app/app
- delete the now empty /preload folder
- use 7zip to compress data+META-INF+system+temp folders again
- copy your new compressed ROM on your SD Card
- boot your phone into recovery and install your ROM
- done !
I just did this exactly that way (after editing the updater script) and it worked perfectly for me. I can´t tell about performance or problems as I just tested this to see if it will run. Any feedback is more than appreciated.
Click to expand...
Click to collapse
I didnt do this very often so please take it easy on me and don´t bash me to hell if it was a stupid idea or impossible to follow at all. It´s just the way it worked out for me after several hours of testing.
Credits and Thanks to :
The Cyanogenmod Team, especially mcm811 for CM10.1
dorimanx for his awesome Kernel
Chainfire, of course for so much!
tedascuen for sharing the stock Rom
Jrummy Apps inc. for Root Browser Lite
The XDA Comunity for sooo much
My Wife for her Laptop and coffee
Greetings
Thomas
Re: Dual boot Samsung Jelly Bean and Cyanogenmod 10 (my way to make it)
Nice work around :thumbup:
Sending...
CWM flashable .zip
Interesting approach!
Can someone try to make clean`n lite CWM flashable zip from XWLS8 to use it with dual boot?
I also miss some things from CM10.1 when same time there are some "must have" things on Sammy`s.
More tutorials / videos / links
MORE SETUPS / TUTORIALS / GUIDES / VIDEOS
A complete Guide to setup Resurrection Remix 3.1.3 and Omega v20 LSD made by jootanen is now here !
Thank you very much for this !!
A complete Guide to set up paranoidandroid 2.99 and NeatROM full LS8 made by jootanen is now here !
Thank you very much for this !!
A complete Guide to set up a modified XWLS8 with Amazing Rom DevDroid including Downloadlinks made by Urmas1 is now here !
Thank you very much for this !!
Now we even got a Video made by bombaybadboy ! Klick here to watch it!
Thank you very much for it !!
And yet another Video by bombaybadboy, DUALBOOT XYLON 4.2.2 with NEATROM FULL, klick here
Thank you very much for it !!
Thanks to THE RED BLUR for the Heads up, there is now a modified DorimanX Kernel to Dual Boot with XWLSD Sammy Rom!!! Klick here to find out how !!!
Once again, thank you and all the others very much !!!!
I made a very "lite" Version of XWLSD, if you like to see & test it, klick here
Please don´t forget to hit the "Thanks" Button if you like it. It is just a little Klick for you but, in my case, it leaves a big smile for us
22.02.2013
Thanks to the great Idea and work of hawkerpaul there is now another, way easier and more simple way to setup 2 Roms for Dual Boot ! (look here for his thread)
I will try to explain as good as I can with a Samsung Rom (XWLSD) that I modified to make it run with another, Kernel compatible AOSP Rom !
Once again, all Credits for the "Magic" of the ROMs go to their respective Developers. I just modified the Updater Script a little, removed a lot of "Bloatware" and moved as many Apps as possible to /system partition. The /preload/symlink/system/app folder only contains a few Apps and has only about 80MB now.
Now we can use the /preload partition with both Roms which gives us much more smoothness/speed and an overall more stable system!
Before you start please note !
- The "myLSDrom.zip" contains a modified DorimanX 7.44 Kernel that is able to run XWLSD Sammy Rom (Thanks to THE RED BLUR for the Heads up)(Post). So, for now, the 2nd Rom needs to be compatible with this Kernel or you need to search another Kernel for this by yourself. I can and will not support this as I am not a Developer but a simple User and I am very happy with this Setup right now.
- The "myLSDrom.zip" also contains Goldieking´s amazing TeamAllianceMod. Why ? Because I LOVE it.
- I removed as much Samsung Stuff as possible. Even Samsung IME got replaced by Xperia S Kexyboard from here. If you don´t like my Setup you can do this by yourself with a XWLSD Rom, just let me know if you need help. I will try to write down a Tutorial !
1. Download myLSDrom.zip from here
2. Download the Rom you like to have as second one
3. Download hawkerpaul´s GS2PreloadRestore v1.04 and GS2PreloadBackup v1.03 from here (Downloadlink not yet ready)
4. Put all Files somewhere on your SD Card (internal/external) where you will find it later
5. Install myLSDrom.zip as first Rom and set it up
6. Boot into Recovery and Backup the Rom
7. Run GS2PreloadBackup v1.03 to backup the /preload/symlink Folder (install zip from SD Card will start it)
8. Now install the 2nd Rom
- usually while we install a Rom, the /system partition gets formatted. When we install a ROM as second, the Kernel leads to /preload as system partition. That´s why we usually lose all Files inside /preload. Thanks to hawkerpaul, that´s no Problem anymore
9. Run GS2PreloadRestore v1.04 to restore the backup of our /preload/symlink
10. DONE !!!!
If you run into Problems, please do not quote this all!
Re: Dual boot Samsung Jelly Bean and Cyanogenmod 10 (my way to make it)
ohwarumbloss said:
I will provide a cwm Backup when I find the time, but this may take some time! Or maybe we find a Dev to make a real .zip to do the job
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I'm patiently waiting for the tests because I wondered use dual boot with the LS8 and CM10.
Sent from my GT-I9100 using xda premium
Updated
OP updated, please give me some Feedback, I hope it will work out !
Also, it would be very nice if someone could upload the modified ROM and provide a link (my internet is awesome slow...)
Thanks & Greetings
Thomas
ohwarumbloss said:
OP updated, please give me some Feedback, I hope it will work out !
Also, it would be very nice if someone could upload the modified ROM and provide a link (my internet is awesome slow...)
Thanks & Greetings
Thomas
Click to expand...
Click to collapse
Made by instructions, do not have time to test it today by myself.
link removed
Gimme feedback, share if slow etc.
EDIT: OP, you can put link to the first post.
Urmas1 said:
Made by instructions, do not have time to test it today by myself.
DOWNLOAD
Gimme feedback, share if slow etc.
EDIT: OP, you can put link to the first post.
Click to expand...
Click to collapse
Thank you very much !
Nevermind, I added it
Nice to see this, really !
Greetings,
Thomas
Sry guys, I got:
...
Opening package...
Flashing aborted
Seems not working this way
Re: Dual boot Samsung JB XWLS8 and CM10(.1) [Updater Script & TestRom added]
Looks like you proved me wrong about duel booting after all. Nice work :thumbup:
Sent from my GT-I9100 using xda premium
AW: Dual boot Samsung JB XWLS8 and CM10(.1) [Updater Script & TestRom added]
Urmas1 said:
Sry guys, I got:
...
Opening package...
Flashing aborted
Seems not working this way
Click to expand...
Click to collapse
I have made a "Lite" Version of the Stock Rom and will upload it now at my parents in law's home. Don't worry, give me 1 or 2 hours
Greetings!
Thomas
Sent from my GT-I9100 using xda app-developers app
AW: Dual boot Samsung JB XWLS8 and CM10(.1) [Updater Script & TestRom added]
bombaybadboy said:
Looks like you proved me wrong about duel booting after all. Nice work :thumbup:
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Nah, that was a complete different Situation and you were right
Sent from my GT-I9100 using xda app-developers app
The EASY way
Ok, now I think I got this running!
Please note, all warnings, thanks and credits are in the very first Post. Please make sure you have read and understand them all!!
Thanks for your Attention
Follow these few steps careful and you will end up like I did, with a CM10.1 and a Samsung Jelly Bean XWLS8 Rom on the same Phone.
1. Download your favorite CM 10 or CM 10.1 Rom
2. Download the modified Stock deodexed & rooted XWLS8 Sammy Rom from here or the FULL ROM provided by Troubadour666, thank you very much for this !!
- the modified Stock is very "Lite" but I will write down the way to get the missing files if you need them !
- the FULL ROM provided by Troubadour666 contains ALL FILES !
3. Copy both Roms and the DorimanX 7.44 Kernel to the root of your SD Card, or wherever, just make sure you´ll be able to find them later !
4. CAREFUL ! PLEASE DO THIS STEP BY STEP !!!
5. Install the "literom.zip" (the downloaded modified Stock Rom)
6. Let it boot completely (important) with the stock Kernel (important) (this may take a while but it will boot!!)
7. Now install the DorimanX Kernel and boot into its Recovery
8. Setup the 2nd Rom
9. Clone 1st Rom to 2nd Rom
10. Try to boot into 2nd Rom (I hope it will) and let it boot, just to make sure
11. Reboot into DorimanX Recovery, do a Factory Reset/Wipe all
12. Install the CM Rom of your choice (my choice : MCM´s builds, AWESOME!) and let it boot completely (Gapps are not needed right now)
13. CAREFUL ! PLEASE READ !!!
14. If you are using MCM´s CM 10.1 you need to (thanks to unexist6969 for that Info!!!!)
- start STweaks
- in systemsettings, change Gralloc to "Samsung Gralloc"
- exit STweaks and reboot once to check if Samsung Gralloc is applied
- if so, reboot into Recovery again
15. Install the DorimanX Kernel again (cwm or odin, I prefer CWM flash, never had problems or yellow Triangle)
16. Reboot, you just set up a nice running Dual Boot System ! Congratulations !!
Hint : If you run into a bootloop after step 16, hold Volume up+Home+Power till you enter Recovery and wipe cache and Dalvik cache, this will work
Click to expand...
Click to collapse
Please note : If you want to apply any visual Mod on this, you need to change a lot of things. An Example, I am using the Alliance AOSP Mod (AWESOME stuff,LINK) and I had to copy the Files manually because the Mod points to /preload..but don´t worry, copy n paste will do, they allready did all the MAGIC (seriously great stuff) !
If you miss Samsung Stuff follow these easy steps :
- Get the Full Rom from first Post
- inside you will find a Folder called "Preload" extract that on your PC
- copy the Apps you missed to your Phone SD Card
- now use Root Browser Lite to copy them to /data/apps/apps
- Longpress (RB Lite) the File and tap "create shortcut"
- Switch to /system/apps and paste the shortcut
- Do this with each File and reboot, DONE.
This may sound complicated but really, it isnt. Don´t be afraid to ask questions that are not answered here or in First Post!!
EDIT:
Important : All MIRRORS are very welcome as i don´t know how Google Drive handles Bandwith. Also, feel free to post your own Full or modded Versions here as long as you give propper Credits to the DEVELOPERS. Please keep in mind, we are nothing without them!
If your Version is confirmed to be working I will add it here (if you like).
Greetings & thanks for your Attention
Thomas
It Works
So as i say to you in MP, i download the files in post 9 (removed since)
and i repack it as a normal flashable ZIP , with WINRAR , i add last dori in too
and i flash it in second rom. before that i format second rom data and cache, wipe data/cache too.
so I boot and i m happy with my ls8n in rom2. thank's for that !
Re: Dual boot Samsung JB XWLS8 and CM10(.1) [ROM ADDED]
Script worked with neatrom full. Just needed rename sale to tmp.
Cloned 1st ROM to 2nd ROM and viewed current status and it didn't show 2nd ROM.
installed cm10.1 to 1st ROM and changed gralloc to Samsung.
Installed dorimanx 7.45 and booted but there wasn't any dual boot screen, just dorimanx logo.
I'll try this again later today with new steps
Sent from my GT-I9100
jootanen said:
Script worked with neatrom full. Just needed rename sale to tmp.
Cloned 1st ROM to 2nd ROM and viewed current status and it didn't show 2nd ROM.
installed cm10.1 to 1st ROM and changed gralloc to Samsung.
Installed dorimanx 7.45 and booted but there wasn't any dual boot screen, just dorimanx logo.
I'll try this again later today with new steps
Sent from my GT-I9100
Click to expand...
Click to collapse
Hey,
thanks for feedback!
I think the NeatRom Updater Script is very different to the Stock one but I seriously don´t know for sure. I can only tell that the way I described will work wih the Download I provided (tested by myself) and DorimanX 7.44. If you find the Time, try it with the Rom I provided (literom.zip) from Post #15 and follow the Steps again. If you run into Problems then, maybe me or another User will be able to help you.
But in generally I would expect the Problems in the different UpdaterScript.
If you want to use NeatRom you may still try my first way in First Post (manually moving the Files)
Hope that helped a bit!
Greetings
Thomas
Re: Dual boot Samsung JB XWLS8 and CM10(.1) [ROM ADDED]
OK, I'll test test ROM and see if it works. And test more with neatrom full
And do I have to do that gralloc thing? Can you explain why is this needed?
Sent from my GT-I9100
AW: Dual boot Samsung JB XWLS8 and CM10(.1) [ROM ADDED]
jootanen said:
OK, I'll test test ROM and see if it works. And test more with neatrom full
And do I have to do that gralloc thing? Can you explain why is this needed?
Sent from my GT-I9100
Click to expand...
Click to collapse
I can not really explain, I followed a hint from Unexist6969. Fact is, MCM's build will not run with DorimanX if you don't change it.
A wild guess is the Ram allocation to Graphics is different in Open Source Gralloc but if you want to go deeper into this you may ask a Developer.
Greetings
Thomas
Sent from my GT-I9100 using xda app-developers app
Easiest and best way to port CM7,CM9,CM10 Based ROMs to HTC Aria/Intruder/Gratia
Code:
I do not guarantee any successful porting.
I am not responsible for [B]bricked devices, dead SD cards, or a broken device[/B].
[B]YOU[/B] are choosing to make these modifications,
and if you point the finger at me for messing up your device,
I will laugh at you.
->Copied from some xda thread.
*****
But a rom, no matter how bad should *not* do any physical non recoverable harm to your device,flashing a rom or restoring a nandroid backup via cwm *should* immediately fix any problems what so ever.
And I will try to help in any ways I can.
I am NOT a developer, I can not code,compile,etc, I am only an android enthusiast with half a brain able to follow specific instructions.
This guide is actually somewhat a good combination of various "how to port roms"
guides found here on xda suited and very slightly modified for our beloved Aria.
Thanks to all of those threads and their writers.
Click to expand...
Click to collapse
Actual Tutorial starts here:
I will try to make this guide as straight forward as possible.
PORT ROM:
First you need to figure out what rom you are going to be porting.
For our Aria, The rom you want to port should belong to a device that has:
HTC brand (optional but recommended)
A ArmV6 CPU (VVVV important)
A HVGA Resolution (optional, any mdpi should do,if not just open the system apk files using 7zip and resize all the BIG images.)
The Rom needs to be:
CM7 BASED OR CM10 BASED OR CM9 BASED.
The full zip size less than 150MB(Recommended).
What Does Port Mean:
This simply refers to the rom you will be trying to port.
Recommended device to port from is the HTC Wildfire S a.k.a Marvel.
But any other device
BASE ROM:
What Does Based Mean:
It means that the rom should have similar sources and stuff,
Meaning you can only attempt to port a android 2.3 rom if you already have a 2.3 rom on the device.(In our case cm7).
So,
For porting 2.3 roms, chose cyanogenmod 7.2 as BASE.
For porting 4.0 roms, chose cyanogenmod 9 as BASE.
For porting 4.1 roms, chose cyanogenmod 10 as BASE.
ETC... I hope you get the point.
:fingers-crossed:
Thing you will need:
A good Zip extractor and compressor. (I use 7zip, its free. If you have winrar or something else,it will also do.)
Notepad++ (This thingy is awesome! And you need it for some stuff)
Android SDK(Not the whole thing, just adb zip from our sticky thread will do.)
Some Basic Android Knowledge, Root knowledge.
Mostly Common Sense.
Click to expand...
Click to collapse
Step 1:
Extract our device rom zip and name the folder AriaRom,
Extract our Port rom zip and name the folder PortRom.
Step 2:
Delete the following folders on the AriaRom/system folder:
App(You can keep some non conflicting indepent apps if you want)
Framework
Fonts
Media
Step 3:
Go to
Code:
PortRom folder/system
and copy:
App(You can keep some non conflicting indepent apps if you want)
Framework
Fonts
Media
and then paste them to AriaRom/system.
Step 4:
You need to open these two folders side by side(on windows, open both folders then right click on the task bar and click "Tile windows vertically").
The two Folders are:
Code:
[LIST]
[*]AriaRom/system/etc
[*]PortRom/system/etc
[/LIST]
In
Code:
etc/permission
folder copy all the permissions files in PortRom to your AriaROM folder except
Code:
platform
handheld_hardware
Then open init.d Folder in AriaRom and Delete Everything except
Code:
banner
and then copy all the files inside init.d folder of PortRom to init.d folder of AriaRom.
Step 5:
Now
Code:
AriaRom/system/buid.prop
and
PortRom/system/buid.prop
files using Notepad++
On AriaRom Build.prop make changes as you wish.
Code:
[LIST]
[*]ro.build.id=
[*]ro.build.display.id=
[*]ro.build.date=
[*]ro.modversion=
[/LIST]
Copy and replace these values from PortRom buildprop to Aria rom buildprop.
ro.config.ringtone=
ro.config.notification_sound=
ro.config.alarm_alert=
Also Copy anything you Find Extra and important-ish in ADDITIONAL BUILD PROPERTIES using common sense.(Not much major stuff, but if bootlooped, copy whole thingy.)
IMPORTANT Step of commons sense:
Open up both
Code:
META-INF/com/google/android/updater-script
using Notepad++.
Compare AriaRom AND PortRom line by line(on two tabs in notepad++ easily done).
Copy extra/additional lines from PortRom which are not present in AriaRom to aria roms updater script.
Step 6:
If You find any extra file or folder in system folder of PORTrom than copy them to your Ariarom system folder.
Finally, zip the
Code:
META-INF
system
boot.img
data(if exists).
folders/files togather and use "normal" compression if asked.
Name the zip to whatever you want, and walla you have successfully ported the rom!
:fingers-crossed:
Doing the above steps should land you a pretty solid rom, as solid as the base rom.
Still,Incase of problems:
If the ported rom does not boot:
Stuck at boot screen
Bootlooping
Then copy system/lib/
Code:
libandroid_runtime.so
libandroid_servers.so
libmedia_jni.so
files from PortRom to AriaRom system/lib.
It should boot, if it still doesnt, check the above steps and find out what you did wrong.
Common reasons could be:
Build.prop mess up
Updater Script mess up
Forgot to delete or copy file
After it boots,
Everything that worked on Base rom, should work on Ported.
Every problem on Base Rom will exist on Ported.
In case of root related problems(settings not being saved,system app FCs,etc), install a root app like titanium backup or something and check if it works,if it doesnt its surely root issue,just download and flash latest superuser zip.
If some FC,Port rom funciton not working,etc issues appear, you need to decompile framework-res.apk using apktool and change device specific xml files to ours.This is a part where I have the most trouble and suck at.
Just search xda for
How to Logcat,
Click to expand...
Click to collapse
this will help you to find the problems and search xda to solve them. Ask me if you want on this thread, & I will try to help, but I dont think I will be able to help much as I have very limited knowledge on compile De-compile stuff.
If someone is good at framework-res and framework decompile & recompile stuff, please help us.
Click to expand...
Click to collapse
Thanks for reading this,I hope you port over some awesome roms to our device.
:highfive:
I just tried to port the PACman ROM from Samsung Galaxy Ace to the Aria, but I am stuck at boot screen after following your tut, which is awesome by the way. Could you post a working build.prop and updater-script for this ROM? Maybe this will help me get it booting...
dansou901 said:
I just tried to port the PACman ROM from Samsung Galaxy Ace to the Aria, but I am stuck at boot screen after following your tut, which is awesome by the way. Could you post a working build.prop and updater-script for this ROM? Maybe this will help me get it booting...
Click to expand...
Click to collapse
That's an Armv7 device.
Still I'm gonna download it & try.
In the meantime take a look at bootclass path.
Why are SMARTphones soo... Freaking Dumb?
sifat3d said:
That's an Armv7 device.
Still I'm gonna download it & try.
In the meantime take a look at bootclass path.
Click to expand...
Click to collapse
I don't think so... the Samsung Galaxy Ace with device number S5830 should be Armv6, but in the Galaxy Ace Forums there is also a place for the Galaxy Ace II, which is Armv7. Maybe that's a bit confusing. But nims11 PAC-Man Rom is definitely for the Armv6 device.
hey man thnx for the tut but i tried porting the paranoid rom like you but i keep getting this error while flashing ( set_perm: some changes failed) i think it have something to do with the updater-script, could u upload the build.prop and the updater-script for me ? and btw why do we need the sdk ??
---------- Post added at 02:43 AM ---------- Previous post was at 02:03 AM ----------
actually now i tried not to change the updater-script and the rom flashed but stock at boot pleaaase help me i really want to try the paranoid rom (ive been trying to port the "pa_marvel-2.54-beta1-08NOV2012-164651" )
rami.ejle said:
hey man thnx for the tut but i tried porting the paranoid rom like you but i keep getting this error while flashing ( set_perm: some changes failed) i think it have something to do with the updater-script, could u upload the build.prop and the updater-script for me ? and btw why do we need the sdk ??
---------- Post added at 02:43 AM ---------- Previous post was at 02:03 AM ----------
actually now i tried not to change the updater-script and the rom flashed but stock at boot pleaaase help me i really want to try the paranoid rom (ive been trying to port the "pa_marvel-2.54-beta1-08NOV2012-164651" )
Click to expand...
Click to collapse
Here you go,
http://pastebin.com/62hbaQwL
on THAT ROM,
IF you follow the guide & use my posted script,
100% assurance rom will boot and work. except cm
The sdk is for getting the logcat when a problem occurs.
Why are SMARTphones soo... Freaking Dumb?
Nice tut very well done
XDA Moderator
dansou901 said:
I don't think so... the Samsung Galaxy Ace with device number S5830 should be Armv6, but in the Galaxy Ace Forums there is also a place for the Galaxy Ace II, which is Armv7. Maybe that's a bit confusing. But nims11 PAC-Man Rom is definitely for the Armv6 device.
Click to expand...
Click to collapse
In that case you'll need to unpack both boot.img aka the kernel , fix bootclass path in init.RC by replacing it with the value from port roms init.rc.
Ill try to port that rom soon and upload a fixed boot.img (if I can get it to boot),if you don't beat me to it. it looks cool.
Why are SMARTphones soo... Freaking Dumb?
Bootclasspath is the same on both roms. So there must be a mistake in updater-script and / or build.prop. I've just messed up my updater-script, I guess, so I'll make a new one and post it later together with the build.prop.
I got this pac rom booting & everything operational except per app dpi(exists in port rom).
This rom works with the guide.
http://forum.xda-developers.com/showthread.php?t=2118567
Why are SMARTphones soo... Freaking Dumb?
I'll try this and let you know if it worked.
Hi guys,
If you only want per app dpi,persistent apps,etc
Try this on winsuk bros cm10
http://forum.xda-developers.com/showthread.php?t=1574401
Its quite good.
...Devided by zero
dansou901 said:
I'll try this and let you know if it worked.
Click to expand...
Click to collapse
btw,
did it work?
...Devided by zero
Sadly, I didn't get any time to try so far. But on Sunday I lost my Gratia, so I won't continue this project; I've upgraded to the HTC Desire X.
dansou901 said:
Sadly, I didn't get any time to try so far. But on Sunday I lost my Gratia, so I won't continue this project; I've upgraded to the HTC Desire X.
Click to expand...
Click to collapse
That's a shame. Similar thing happened to me. I lost my Aria right before i had a chance to try this, and upgraded to the Nexus 4.
will this method work on cm10.1 and this http://forum.xda-developers.com/showthread.php?t=2297580 ??
Could work, just try... I would do it if I still had the phone...
dansou901 said:
Could work, just try... I would do it if I still had the phone...
Click to expand...
Click to collapse
rami.ejle said:
will this method work on cm10.1 and this http://forum.xda-developers.com/showthread.php?t=2297580 ??
Click to expand...
Click to collapse
It should pretty much work,
If it doesnt, just send me the
Updater script
Build.prop
files of BOTH roms, And I'll have a look.
I wouldve tried myself but my aria has no network and has random reboot issues due to falling hard.
I'm a beginner in AndroidModding, and the ways that I have found so far are boring (as well as my ability to describe my project).
Basically, I'm developing a visual tool to facilitate mods creation. I know there are already some, but I intend to make a better base for beginners as I don't make crap.
I'll leave out some screen shots and when I make the program more stable I'll upload a first test version.
I wish everyone who has any idea about what I can add in the project manifest and suggest the same. At the end I will give credit to all who help me improve things.
And also, if you guys think this is will be useless please tell me this too
[Change log]
14/10/13
Working features:
-Create and manage Devices and ROMs
--Auto framework change 90% complete
-Create multiple projects of same APK
-Import an APK via dialog box to avoid mistake at folder arrange
-Decompile, Build, Auto META-INF PATCH, Recompile and ZipAlign just at one click for each function.
-Shortcut to working folders
-Debug output
-Set zipalign compression option
Features i'm working on:
-Auto change framework for different devices
-Auto mod scripting
-Translation features
-Pull/Push files via ADB
Features that I already tought about:
-Multi-Framework capability: Switch between frameworks to mod apps of different Roms and devices without complication.
-Project creation: Create a new independent mod with just one click without losing your previous project.
-Auto patch: Select a Mod in a list, choose your preferences and watch while program do the hard work for you.
-Create a auto patch youself: If you are already experient and want automate your mods, you can create a list of actions to auto apply into an apk.
-Create a Zip file to install in recovery mod
-Default stuff to ApkTool like decompile, build, recompile, blabla
[add 06/10/13 18:30]
-Adb pull/push: send or get files from your phone by adb connection
-Smali code autopatch support
ps: I don't know speak english as well, so, sorry about any mistake
This is good and seems fun
will wait for a test release
Will it be Open Source ?
Then we could improve your work by submitting patches
Pixelvernichter said:
Will it be Open Source ?
Then we could improve your work by submitting patches
Click to expand...
Click to collapse
Its a good idea, I'll think aboit it
Sent from my GT-I9100 using xda app-developers app
Also, if you need an tester for your tool I have time and i would do it
That tool will be great for a nope like me thanks
Sent from my GT-I9100 using xda app-developers app
shfddi being
:good:
i'll help to test if u want to..
Live log would be good. To watch as phone boots into an inevitable bootloop when trying something new. Saves running log separately and lets you view as it happens. With filtering would be good. Adbmagic did something similar but you cant copy or search the log.
Sent from my GT-I9305 using Tapatalk 4
Solved!Does anyone know if a xml like instead when inner value is empty interferes something or just make file bigger? I mean to Android, because I know their same thing.
Also, who wants help me making me an logo? I was thinking about an android with Merlin's costume, but I don't have the skills to reproduce this
Goldieking said:
Live log would be good. To watch as phone boots into an inevitable bootloop when trying something new. Saves running log separately and lets you view as it happens. With filtering would be good. Adbmagic did something similar but you cant copy or search the log.
Sent from my GT-I9305 using Tapatalk 4
Click to expand...
Click to collapse
That's a good idea, i'll try implement that, thanks
Sent from my GT-I9100 using xda app-developers app
SkyaTura said:
Does anyone know if a xml like instead when inner value is empty interferes something or just make file bigger? I mean to Android, because I know their same thing.
Also, who wants help me making me an logo? I was thinking about an android with Merlin's costume, but I don't have the skills to reproduce this
That's a good idea, i'll try implement that, thanks
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Bump !
Logo in progress
( Android with Merlin Costum. lol xD )
New changes at thread!!!
I pretend to release a beta version this week yet
Pixelvernichter said:
Bump !
Logo in progress
( Android with Merlin Costum. lol xD )
Click to expand...
Click to collapse
Can we see a preview of our MerlinDroid?
(i would be annoying if i ask an icon version?)
Code:
/*
* ~ DO READ THIS BEFORE ATTEMPTING~
* Iam not here to guarantee any successful PORTING. nor i am responsible
for bricked devices, dead SD cards, or a broken device. YOU are
choosing to make these modifications, and if you point the finger
at me for messing up your device, I will laugh at you. But I will try
my best to explain all the necessities, so you won't mess up your Device.
*
~END
*/
Hello XDA'S Today i'm back with a useful guide/tutorial for ANDROID ROM PORTING
may have tried porting roms to their phones and has been succefull but most of the case is that we being end up in bootloops or cwm errors
So i'm dedicating this post for all users how are having a craze of rom porting or for atleast those wgo wanted to try rom porting
SO LETS START
There are two phases or rom porting
1) Its finding the correct port and source roms for ROM PORTING copying the files which is explained here
2) After a succefull port also the rom may not work properly ,we have to sort out the bugs to for a rom to become perfectly working
So with no more blahh blahh blahh Lets start the PORTING procedure :fingers-crossed: :fingers-crossed:
Click to expand...
Click to collapse
And lastly Before you a port a ROM, make sure you asked permission from the Developer!
What you'll need:
WinRAR/7zip
Notepad++ (When developing, always use this)
Android SDK (For Logcatting & DDMS)
Some basic knowledge about Android
If you are on Linux/Unix/BSD use your favorite Archiving Tool & Text Editor.
Click to expand...
Click to collapse
What is base Rom:
The ROM which is Developed For your Mobile..
You can use either CM or any other AOSP roms as your Base ROM
Click to expand...
Click to collapse
What is Port Rom:
The Rom Which you want to port to your Device.
Make sure that the rom has most of the hardware specifications as of your base rom
Click to expand...
Click to collapse
STEP1;
Take any clean CM9, AOSP, CM7, CM10 ROM which is running on your device as Base ROM
Click to expand...
Click to collapse
STEP2:
Extract it Using Winrar.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
STEP3:
Take the ROM you want to port. This Port ROM. Extract it also using Winrar.
Click to expand...
Click to collapse
STEP4:
Delete app, Framework, Fonts and Media folder in System Folder of Base ROM.
Click to expand...
Click to collapse
STEP5:
Now copy app, Framework, Fonts and Media folder in System Folder from Port rom to base rom system folder.
Click to expand...
Click to collapse
STEP6:
Now open etc folder in both the ROMs folder.
Click to expand...
Click to collapse
STEP7:
In etc folder of base ROM open permissions folder and copy all the permissions files in Port rom to your base ROM folder except platform and handheld_hardware
Click to expand...
Click to collapse
STEP 8: .And Then open init.d Folder in Base ROM and Delete Every thing except banner and then copy all the files inside init.d folder of port ROM to Base ROM.
Click to expand...
Click to collapse
STEP9:
Now open buid.prop file using Notepad++ and make changes to these of Base Rom as you wish.
ro.build.id=
ro.build.display.id=
ro.build.date=
ro.modversion=
Click to expand...
Click to collapse
STEP10:
In build.prop file change these to same as Port Rom build.prop values.
ro.config.ringtone=
ro.config.notification_sound=
ro.config.alarm_alert=
ro.cmversion=
ro.modversion=
Also Copy anything you Find Extra in ADDITIONAL BUILD PROPERTIES related to theme..
Click to expand...
Click to collapse
STEP11:
COPY THE set_perm Lines in META-INF/com/google/android/updater-script From Port to Base ROM After Deleting set_perm lines in Base ROM's Updater-Script.
Click to expand...
Click to collapse
STEP12:
If You find any extra file or folder in system folder of PORT rom than copy them to your base rom system folder.
Click to expand...
Click to collapse
STEP 13:
Last Step to ZIP THE FOLDERS IN ONE..
SELECT META-INF, system, boot.img(if it is having), data(if it is having).
Right Click and Select Add to Archive..
Select Zip..
Type the Name.
Click OK..
Click to expand...
Click to collapse
HERE THE BASIC ROM PORTING IS OVER BUT FOR SOME SPECIFIC COSTUME ROMS WE NEED LITTLE MORE STUFFS TO WORK ON ,THEY ARE SHOWN BELOW
ONLY FOR MIUI ROMS :
Copy telocation.db and yellowpage.db From /system/etc folder to yours..
Copy content-types.properties file From /system/lib to yours..
Copy invoke-as from miui4 rom to /system/xbin and give it permissions on updater-script
set_perm(0, 0, 06755, "/system/xbin/invoke-as");
Note:It is needed for backup & themes app to work
Copy liblbesec.so from miui 4 to /system/lib and give permission on updater-script
set_perm(0, 0, 0755, "/system/lib/liblbesec.so");
It is needed for superuser app from miui to work
Change values Some of the Values in build.prop of your ROM:
ro.build.id=MIUI
ro.build.display.id=MIUI
ro.build.version.incremental=2.x.x (version number)
ro.config.ringtone=MI.ogg
ro.config.notification_sound=FadeIn.ogg
ro.config.alarm_alert=GoodMorning.ogg
ro.config.sms_received_sound=FadeIn.ogg
ro.config.sms_delivered_sound=MessageComplete.ogg
Click to expand...
Click to collapse
FOR ParanoidAndroid And PAC:
Copy paranoid folder inside system/etc to yours..
Go to META-INF/com/google/android/Updater-Script of your base ROM and open it with Notepad++
Copy this line:
set_perm(1000, 1000, 0644, "/system/etc/paranoid/properties.conf");
Specially For PA:
Now Open Build.prop in /system with Notepad++
Copy these lines in Additional Properties of Build.prop:
Depends on Resolution Of your device can be pa_hdpi/pa_mdpi/pa_xhdpi. Change it according to your device.
ro.pa.family=pa_mdpi
Depend on pa version. Replace x.xx with the version of PA you are porting.
ro.pa.version=x.xx
Click to expand...
Click to collapse
Specially For PAC Rom:
Now Open Build.prop in /system with Notepad++
Copy these lines in Additional Properties of Build.prop:
Replace the x.x.x with your PAC Rom version
ro.pac.version=x.x.x
Customize these lines according to your wish.
ro.pacrom.version=mesona_PAC_jb-alpha-v19.0.0
ro.modversion=mesona_PAC_jb-alpha-v19.0.0
Depends on Resolution Of your device can be pa_hdpi/pa_mdpi/pa_xhdpi. Change it according to your device.
ro.pa.family=pa_mdpi
Depend on pa version. Replace x.xx with the version of PA you are porting.
ro.pa.version=x.xx
Modify this line according to your AOKP version
ro.aokp.version=mesona_jb-Milestone-1
Modify it according to your base ROM's build.prop
ro.cm.version=xxxxxxxxxxxx
Replace any line in Your build.prop which appear twice mainly ro.cm.version and ro.modversion
Click to expand...
Click to collapse
FOR SPECIFIC MANUFACTURE DEVICE
For HTC Devices:
To fix network auto select-
Decompile framework-res.apk
Go to \framework-res\res\values\bools.xml and change change <bool name="skip_restoring_network_selection">true</bool> to false
To Fix Graphichal issues:
Code:
Decompile framework.jar
Change these files with your base
smali\smali\android\os
Environment
SystemProperties
smali\smali\android\view
HardwareCanvas
HardwareRenderer$Gl20Renderer
HardwareRenderer$GlRenderer
HardwareRenderer
Click to expand...
Click to collapse
IF YOU ARE HAVING BOOTLOOP THEN COPY THESE LIB FILES TO BASE ROM FROM PORT ROM:
libandroid_runtime.so
libandroid_servers.so
libmedia_jni.so
Click to expand...
Click to collapse
IF YOUR BASE ROM HAS ISSUES LIKE CAMERA ISSUE THAN YOUR PORTED ROM TOO WILL HAVE ISSUES.
NOW ZIP YOUR ROM AND POST IT BUT DON'T FORGET TO GIVE CREDITS TO THE DEVELOPER OF PORT ROM..
TROUBLESHOOTING AFTER SUCCEFULL PORT
After a succefull port also there can be many bugs present which has to soved logically
here are somethings which can help in DEBUGGING
1) IF GALLERY FC :
open the system/framework and find framework-res.apk file[can use any extracting app]
in both the roms and go to res folder then to xml subfolder and copy and replace the storage_list.xml file from source to port rom
( framework-res.apk\res\xml\storage_list.xml)
Porting Wallpapers | Lockscreen Wallpapers | bootanimation
Usually you get a wallpaper/bootanimation that doesn't fit your device. Here's a quick tutorial on how to port it to your device.
Download & Install FreeImageConverter then launch it.
For Wallpapers & Lockscreen Wallpapers:
Click Add Folder... and add the folder were the wallpapers are
Then click Advanced Convert...
Select Exact Size and set the image quality to 100
Set your Width and Height resolutions for your device.
Uncheck Add "Converted by www.freeimageconverter.com"
Select Leave the same file name and leave the Postfix & Prefix empty. Then set your output in a folder.
For bootanimation:
Extract /system/media/bootanimation.zip OR /data/local/bootanimation.zip OR /system/customize/resource/bootanimation.zip (For Oxygen ROM, the bootanimation is built into the framework-res)
Do the steps above
Move the new resized folder(s) into your bootanimation workspace
Edit the desc.txt to match your device resolutions
Zip the contents ( folder_name desc.txt )
Set compression method to Store
Delete the extracted bootanimation files
Make sure this new bootanimation.zip is in PORTED
Click to expand...
Click to collapse
Sources
http://cleanimport.xda/index.php?threads/1598713/
http://cleanimport.xda/index.php?threads/1908008/
Click to expand...
Click to collapse
Credits & Thanks to
# rishabh.raj37
# Peteragent5
Happy porting!
:laugh:
Click to expand...
Click to collapse
reserved
for clarification
This method gives bootloop too often. It works only for very similar devices like Xperia J & Arc or Huawei u8818
Yes. This method gives a lot of bootloops. It only can be used on devices with hairline differences between specs.
Sent from my GT-N7000 using XDA Premium 4 mobile app
lozohcum said:
This method gives bootloop too often. It works only for very similar devices like Xperia J & Arc or Huawei u8818
Click to expand...
Click to collapse
not really ,,i have tried porting with this and it worked succefullyy
:laugh:
may be you have to try it perfectly
1c3_5n0w said:
Yes. This method gives a lot of bootloops. It only can be used on devices with hairline differences between specs.
Sent from my GT-N7000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
have you tried this methode,,iam sure it will work,,:laugh::laugh:
ArjunrambZ said:
have you tried this methode,,iam sure it will work,,:laugh::laugh:
Click to expand...
Click to collapse
I started porting roms about year ago so... yes I did, I tried many "methods". This works mostly for similar devices.
Now I'm trying to use source code
lozohcum said:
I started porting roms about year ago so... yes I did, I tried many "methods". This works mostly for similar devices.
Now I'm trying to use source code
Click to expand...
Click to collapse
yah trying with source code is the best way ,but this tut is for users who really cant get it using source :good:
Arjunramb456651 said:
Code:
/*
* ~ DO READ THIS BEFORE ATTEMPTING~
* Iam not here to guarantee any successful PORTING. nor i am responsible
for bricked devices, dead SD cards, or a broken device. YOU are
choosing to make these modifications, and if you point the finger
at me for messing up your device, I will laugh at you. But I will try
my best to explain all the necessities, so you won't mess up your Device.
*
~END
*/
Hello XDA'S Today i'm back with a useful guide/tutorial for ANDROID ROM PORTING
may have tried porting roms to their phones and has been succefull but most of the case is that we being end up in bootloops or cwm errors
So i'm dedicating this post for all users how are having a craze of rom porting or for atleast those wgo wanted to try rom porting
SO LETS START
And lastly Before you a port a ROM, make sure you asked permission from the Developer!
HERE THE BASIC ROM PORTING IS OVER BUT FOR SOME SPECIFIC COSTUME ROMS WE NEED LITTLE MORE STUFFS TO WORK ON ,THEY ARE SHOWN BELOW
ONLY FOR MIUI ROMS :
FOR ParanoidAndroid And PAC:
Specially For PAC Rom:
FOR SPECIFIC MANUFACTURE DEVICE
IF YOUR BASE ROM HAS ISSUES LIKE CAMERA ISSUE THAN YOUR PORTED ROM TOO WILL HAVE ISSUES.
NOW ZIP YOUR ROM AND POST IT BUT DON'T FORGET TO GIVE CREDITS TO THE DEVELOPER OF PORT ROM..
TROUBLESHOOTING AFTER SUCCEFULL PORT
After a succefull port also there can be many bugs present which has to soved logically
here are somethings which can help in DEBUGGING
1) IF GALLERY FC :
open the system/framework and find framework-res.apk file[can use any extracting app]
in both the roms and go to res folder then to xml subfolder and copy and replace the storage_list.xml file from source to port rom
( framework-res.apk\res\xml\storage_list.xml)
Credits & Thanks to
# rishabh.raj37
# Peteragent5
Happy porting!
:laugh:
Click to expand...
Click to collapse
Can you port an AOSP/CM based rom using a Manufacturer/maufacturer based ROM as the base (i.e. touchwiz rom)?
Click to expand...
Click to collapse
So i own a Galaxy Tab 2 10.1 from AT&T... If i wanted to port a 4.2.2 Touchwiz rom to my tablet, would the steps vary much from those you've listed?
Sent from my SGH-I337 using XDA Premium 4 mobile app
---------- Post added 16th November 2013 at 12:02 AM ---------- Previous post was 15th November 2013 at 11:59 PM ----------
Neozx25 said:
So i own a Galaxy Tab 2 10.1 from AT&T... If i wanted to port a 4.2.2 Touchwiz rom to my tablet, would the steps vary much from those you've listed? I would be using a rom that runs on another tab 2 10.1 but not for AT&T. Or even if i wanted an AOSP rom, would be that difficult?
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SGH-I337 using XDA Premium 4 mobile app
HitBobLer said:
Arjunramb456651 said:
Code:
/*
* ~ DO READ THIS BEFORE ATTEMPTING~
* Iam not here to guarantee any successful PORTING. nor i am responsible
for bricked devices, dead SD cards, or a broken device. YOU are
choosing to make these modifications, and if you point the finger
at me for messing up your device, I will laugh at you. But I will try
my best to explain all the necessities, so you won't mess up your Device.
*
~END
*/
Hello XDA'S Today i'm back with a useful guide/tutorial for ANDROID ROM PORTING
may have tried porting roms to their phones and has been succefull but most of the case is that we being end up in bootloops or cwm errors
So i'm dedicating this post for all users how are having a craze of rom porting or for atleast those wgo wanted to try rom porting
SO LETS START
And lastly Before you a port a ROM, make sure you asked permission from the Developer!
HERE THE BASIC ROM PORTING IS OVER BUT FOR SOME SPECIFIC COSTUME ROMS WE NEED LITTLE MORE STUFFS TO WORK ON ,THEY ARE SHOWN BELOW
ONLY FOR MIUI ROMS :
FOR ParanoidAndroid And PAC:
Specially For PAC Rom:
FOR SPECIFIC MANUFACTURE DEVICE
IF YOUR BASE ROM HAS ISSUES LIKE CAMERA ISSUE THAN YOUR PORTED ROM TOO WILL HAVE ISSUES.
NOW ZIP YOUR ROM AND POST IT BUT DON'T FORGET TO GIVE CREDITS TO THE DEVELOPER OF PORT ROM..
TROUBLESHOOTING AFTER SUCCEFULL PORT
Can you port an AOSP/CM based rom using a Manufacturer/maufacturer based ROM as the base (i.e. touchwiz rom)?
Click to expand...
Click to collapse
no i dont think so,because cm /pa have modified source code ,which differ from manufacture rom hence ,,not possible ,u will possibly end in boot loop
Click to expand...
Click to collapse
Neozx25 said:
So i own a Galaxy Tab 2 10.1 from AT&T... If i wanted to port a 4.2.2 Touchwiz rom to my tablet, would the steps vary much from those you've listed?
Sent from my SGH-I337 using XDA Premium 4 mobile app
---------- Post added 16th November 2013 at 12:02 AM ---------- Previous post was 15th November 2013 at 11:59 PM ----------
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Neozx25 said:
So i own a Galaxy Tab 2 10.1 from AT&T... If i wanted to port a 4.2.2 Touchwiz rom to my tablet, would the steps vary much from those you've listed?
Sent from my SGH-I337 using XDA Premium 4 mobile app
---------- Post added 16th November 2013 at 12:02 AM ---------- Previous post was 15th November 2013 at 11:59 PM ----------
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes of course ,this methode is for aosp or for cm roms and not for manufacture roms,,there are other guids for porting manufacture roms ,go search the forum
only boot loop no progress!!!
i had tried this method more then 4 times but it didnt worked....
rom is not booting up and its stucked on boot animation and shows no progress although i left it for an hour but still stucked....
any idea??
and for details...
i am porting chameleon OS built for htc one s just see this....-
android v is 4.2.2
so i used aokp 4.2.2(stable) first as base rom but i failed more then 2-4 times then i tried cm10.1 as base rom but still i am at bootanimation.
i had also used the three libs from the port rom and base rom as mentioned in the guide but still nothing is going good......:crying:
can you tell me that am i missing something or i should try other guides?
if your answer is that i should try other guides so please lead me to a guide.....
thanks.
regardslayboydroid
playboydroid said:
i had tried this method more then 4 times but it didnt worked....
rom is not booting up and its stucked on boot animation and shows no progress although i left it for an hour but still stucked....
any idea??
and for details...
i am porting chameleon OS built for htc one s just see this....-
android v is 4.2.2
so i used aokp 4.2.2(stable) first as base rom but i failed more then 2-4 times then i tried cm10.1 as base rom but still i am at bootanimation.
i had also used the three libs from the port rom and base rom as mentioned in the guide but still nothing is going good......:crying:
can you tell me that am i missing something or i should try other guides?
if your answer is that i should try other guides so please lead me to a guide.....
thanks.
regardslayboydroid
Click to expand...
Click to collapse
bro firstof all,, porting is not that easy as to read,,, here logcat is your only friends,,, get me the logcat
hmm
ArjunrambZ said:
bro firstof all,, porting is not that easy as to read,,, here logcat is your only friends,,, get me the logcat
Click to expand...
Click to collapse
okay just wait for a day...
and thanks for your quick reply..
playboydroid said:
okay just wait for a day...
and thanks for your quick reply..
Click to expand...
Click to collapse
okay
Good evening to all, first of all thanks for the guide.
The rom part, it works most of the things, porting is a rom for nexus 5 to take on g2.
I have problems with wifi, vpn and security in the setting menu.
Practically the vpn and security go on crash, while the wifi is active but can not find anything.
Do you have suggestions?
thanks
Sorry for my bad english
jokerpoker1 said:
Good evening to all, first of all thanks for the guide.
The rom part, it works most of the things, porting is a rom for nexus 5 to take on g2.
I have problems with wifi, vpn and security in the setting menu.
Practically the vpn and security go on crash, while the wifi is active but can not find anything.
Do you have suggestions?
thanks
Sorry for my bad english
Click to expand...
Click to collapse
it would only b possible if you could get a logcat about the problem,, and if the problem persist in the base rom,then its sure to be in ur port too,
ArjunrambZ said:
it would only b possible if you could get a logcat about the problem,, and if the problem persist in the base rom,then its sure to be in ur port too,
Click to expand...
Click to collapse
thanks for the reply, it is the first time I use logcat, this is what I said when I port ROM.un my friend was telling me That might be the update script.
Thanks
Inviato dal mio LG-D802 utilizzando Tapatalk
jokerpoker1 said:
thanks for the reply, it is the first time I use logcat, this is what I said when I port ROM.un my friend was telling me That might be the update script.
Thanks
Inviato dal mio LG-D802 utilizzando Tapatalk
Click to expand...
Click to collapse
yes when it coms to porting logcat is ur only friend,, well updater script doesn't have any relations with the rom actually its like a process to installing the rom as said, and fixing permision,,,
and please tell me when was this logcat obtained and this time get me a full logcat