yashsingh1/xdaforums huggingface dataset:
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] jokinawa:
Nobody can help me figure out how to put one ROMs internet connection into a cooked ROM? I dont know the password for the connection. I would like to "extract" the Softbank "April 1st" connection and "inject" it into the XDA-Live ROM.
[Galaxy S II General] koolkunz:
Welcome to the NOOB Friendly GUIDE to DUAL BOOT Lollipop with KitKat/JellyBean Roms on Samsung Galaxy S2!!

We have been fortunate enough to have 2 Working Lollipop Rom's (CM 12 and Omni 5.0) so I present to you the Guide on how to Dual Boot them with Kitkat/JB ROMs

Prerequisites :

1) Need Atleast 2.5 GB free on Internal Storage

2) Download the 1st Rom( LOLLIPOP - Primary Rom) and save it on any storage on your phone

3) Download Dorimanx Test Kernel v10.44.v004 from Here - http://dorimanx.casoncia.org/V10-MA...COMP-mv3-[10-30]-[29-09]-JB-SGII-PWR-CORE.zip

4) Download the 2nd Rom (Kitkat/JB - Secondary Rom) and save it on any storage on your phone

Steps :

1)Make sure you are on a Lollipop Compatible Recovery

2) Flash your Lollipop ROM (along with GAPPS etc.) you want as your Primary ROM

3) Reboot and check weather the ROM is working fine.

4) Reboot to Recovery

5) Flash Dorimanx v10.44.x004 Kernel you downloaded earlier

6) Go to Reboot Recovery

7) Go to dual boot options in new CWM and select Wipe 2nd ROM data/cache (takes 5-10 minutes)

8) Then select Wipe 2nd ROM dalvik-cache

9) After that Install 2nd ROM from Internal SD card or External SD card and flash the 2nd ROM (Kitkat/JB).

10) Reboot System and Boot to Secondary ROM (Press HOME button on DualBoot Screen)

NOTE : -Now you have both ROM's Installed but for now only 2nd ROM will boot. To see how to boot Lollipop ROM see next post

PLEASE HIT THE THANKS BUTTON :good:

Checkout my other thread for Kitkat/JB Roms Dualboot

Credits :

[MENTION=4704050]nik60[/MENTION] for his thread

[MENTION=4938461]eskriminal[/MENTION] and [MENTION=2376110]dorimanx[/MENTION] for Kernel

[MENTION=4775725]Troubadour666[/MENTION] for Helping Out/Patches

And any others i forgot to mention

​
[Galaxy S II General] koolkunz:
Boot to Lollipop Rom :

1) Download and Copy the latest Apolo Kernel Lollipop Version to your phone internal storage

2) Reboot to recovery from your Kitkat/JB ROM

3) In CWM Recovery flash the Apolo Kernel

4)Reboot System and Enjoy your Lollipop ROM

Note : You will have to Repeat these steps everytime you want to change from Kitkat/JB ROM to Lollipop ROM

Boot to Kitkat/JB ROM :

1)Boot into Recovery

2)Flash the Dorimanx Kernel again and Reboot System to boot to Kitkat/JB ROM

Note : You will have to repeat these steps everytime you want to change from Lollipop to Kitkat/JB ROM

​
[Galaxy S II General] koolkunz:
reserved
[Galaxy S II General] Troubadour666:
LOL :)

again, dualbooting thread ;)

thanks.
[Galaxy S II General] koolkunz:
I didnt want to make the old thread to much full..people will get confused...so i made another thread specifically for Lollipop.. I am sure this will help a lot of users
[Galaxy S II General] Troubadour666:
video review about dualboot :)

[YOUTUBE]jkso45x0Omg[/YOUTUBE]

sory, its not branch 10 i used from DorimanX builds, its branch 8, but for ppl, result will be same as describe in OP.

when i made this review, i never though someone will make a thread :)

link to download this personal omni rom with gapps inside used in video :

omni-5.0-20141202-i9100-HOMEMADE-GAPPS_inside.zip - 267.19 MB

thanks
[Galaxy S II General] Yakap:
Omni 5.0 with gapps,it's working? Thanks
[Galaxy S II General] koolkunz:
http://d-h.st/gIf

these gapps work
[Galaxy S II General] Troubadour666:
tip for dualbooters :)

Hi,

try :) its a test , i assume you know what you do with your device, if you dualboot, you know that !

For this tweak, on your good 2nd rom , install Nandroid Manager from Store :

https://play.google.com/store/apps/details?id=com.h3r3t1c.bkrestore

tweak details:

if you have a good running lollipop on 1rst rom, then flash your DorimanX kernel with TWRP or ODIN, reboot DorimanX recovery and using it, make a nandroid of your 1rst lollipop rom.

- NOW, with DorimanX kernel, reboot and run your KitKat or JB 2nd rom and ,

- copy nandroid backup from clockworkmod folder on device (int or ext card) to PC ("omni-02122014-2014-12-02.19.02.55" for example) .

- from this nandroid, make an another safe copy in another folder of your PC.

- from folder named "test-omni-02122014-2014-12-02.19.02.55"

- with 7zip , open system.ext4.tar.a and delete all things except build.prop in /system/. close system.ext4.tar.a.

- with 7zip , open data.ext4.tar.a and

in data/data , delete :

com.andrew.apollo

com.bel.android.dspmanager

com.svox.pico

jp.co.omronsoft.openwnn

net.nurik.roman.dashclock

all folder with :

org.omnirom.*

com.android.*

com.cyanogenmod.*

delete contents in data/dalvik-cache/*

delete contents in data/users/*

you can try to clean some other folders if you want.

then close data.ext4.tar.a

- now, copy "test-omni-02122014-2014-12-02.19.02.55" from PC to your device, in same folder as original.

- reboot your 2nd rom again

- run nandroid manager and find your "test-omni-02122014-2014-12-02.19.02.55" in list of backups and tick it

- launch MD5 buton on screen and choose "generate MD5". When done, reboot recovery.

wait for new lollipop build.......

when , one day, one lollipop build appears (CM12 ALPHA, OMNI or CodeRom), then

- with DorimanX recovery, restore the modified nandroid backup "test-omni-02122014-2014-12-02.19.02.55" on your 1rst rom.

- then , go in mount and storage Menu, follow "mount /system" and go to "format system" partition.

- flash the NEW LOLLIPOP Build ROM now and enjoy to find your DATA APPs from precedent LOLLIPOP BUILD INSTALLED.

thanks
[Galaxy S II General] koolkunz:
Guys if you want i can make Omni Recovery file for you guys...just someone send me the boot.img from latest build...im using bugaaty build
[Galaxy S II General] Troubadour666:
take my friend, no flashable ;)

boot.img-5.0-20141202-i9100-HOMEMADE.rar - 5.86 MB
[Galaxy S II General] koolkunz:
So all those using Omni latest build(20141202) by asimovi..use these 2 files :

CWM Flasher : http://d-h.st/qD6

Omni Recovery : http://d-h.st/rdH

YOU DO NOT NEED TO EDIT THE FILES FOR 20141202 OMNI 5.0 BUILD!!
[Galaxy S II General] koolkunz:
have also added files for Bugatty build...check the 2nd post of the thread :D
[Galaxy S II General] Yakap:
Tried omni rom 5.0 internal storage not work, any help, tnx in adv.
[Galaxy S II General] koolkunz:
that is problem of rom by asimovi...download the build by bugatty
[Galaxy S II General] koolkunz:
The guide has been updated and is now working for all Lollipop roms...even CM12 now :D

Now the method is very simple...everything can be done on phone...no need to copy replace files in winrar etc
[Galaxy S II General] insigma28:
Will this work on 5.0.1 build? As the only way I can dual boot is if I backup l rom when I change from kk I have to restore l.
[Galaxy S II General] koolkunz:
Yes it will....
[Galaxy S II General] Yakap:
Always boot into recovery when you change the rom?
[Galaxy S II General] koolkunz:
you need to boot into recovery to flash the respective kernels if you want to change roms
[Galaxy S II General] koolkunz:
but why do you want to use these...you can easily do it by using apolo kernel now
[Galaxy S II General] AAA118:
Sgh i777

I have at&t sgh i777 can i still run this ?
[Galaxy S II General] koolkunz:
No you need to have dorimanx and apolo kernel for your phone as well
[Galaxy S II General] insigma28:
This was way before apolo was released on omni rom mate, Now I have my LG G3 don't need to do it anymore lol rip my s2.
[Galaxy S II General] Troubadour666:
Little tuto

Hi all :)

tell me what you think about this ;)

[YOUTUBE]cgUbN6iUaqw[/YOUTUBE]

thanks
[Galaxy S II General] Lister Of Smeg:
Hi [MENTION=5262182]koolkunz[/MENTION] / All,

So how does this method work then?? What storage does it use??

1) Does it mess with any of the existing partitions??

2) As I've used a PIT file to extend my /data partition to 4Gb. So will this method work with that ok, or will it mess things up?? Or does it just store files on the Internal SD (now down 9.5Gb, with 5Gb spare).

3) Is it quick to switch (other than just flashing the respective kernels) OS's on the fly, boot up... Or does it take several minutes booting each OS/rom after flashing kernels?

4) If I get bored, and wished to switch back to just single boot / rom, is it just a case of not using the dual boot kernel, and wipe all the normals with a standard kernel....?

Cheers, Lister
[Galaxy S II General] Lister Of Smeg:
Hi All,

Anyone able to provide the answers below, as I'd like to try this in the next couple of hours as I am going out in a bit and would like to show my brother this... if it works!!!

But not at the risk if it messes with partition tables, or damages the phone... I'm not a noob, and know the risks... Just I didn't see in the instructions how this feat was managed, if its merely pointing to a storage location on the existing partition layout. Or where it removes some storage by re-partitioning, to allow for the second rom... As I am curious to know what happens if you wish to go back to standard booting....

Thanks, Lister
[Galaxy S II General] koolkunz:
Answer to 3- Booting time is normal....only the first boot when you install the 2nd rom it is long...as it should be whenever you install a new rom...after that normal quick booting..

Answer to 4- Yes you cn easily remove the 2nd rom//there is an option in dori kernel to remove 2nd rom and then you can switch backt to single boot with any rom or kernel..

Answer to 1-It will not delete any of your data on internal and external storage...

answer to 2-It stores files of 2nd rom on internal sd...there should not be any problem with your pit...but this i can not confirm..as i have never used pit files
[Galaxy S II General] Lister Of Smeg:
Hi [MENTION=5262182]koolkunz[/MENTION],

Thanks for getting back to me, unfortunately it was after the time I was due to meet up with my brother, so couldnt show him it.. But tried it as soon as I got back, and with your clear explanations and instructions, it went smoothly... / thank you!!! :)

1) I see that it doesn't alter any of the partitions, or lose any data... which is cools!! :) I still don't get or see how it is doing this magic... As can't seem to find the files at the moment. My guess is that they are hidden on the internal storage, will have a look after I posted this...

2) It seems ok with my PIT... In Lollipop (my main / 1st) rom, I still see my 4GB /Data partition for all the Apps and this works fine. However when I install the 2nd Rom, it only shows me having 2GB for /Data partition. Which is fine, as I'm only messing and testing with... so space is not really an issue here...

However, under my second partition, which I've tried 2x builds of KitKat rom, every so often I get a message about errors found on my partitions, and would I like them to be repaired.... Is this normal, and why is it doing it...?? Is there any way I can avoid that message, and still run this device safely, or is there a risk it will corrupt my partitions if it tries to fix them...??

3) Yeah booting times seem normal to me, the very first time it seemed to get stuck or summit?? Not sure what or why? I pressed the home button it it just sat there... However when I rebooted and pressed the Vol Down key, it booted fine..... (2nd Rom that is). However I tried to flash the Apolo kernel afterwards and its not letting my Lollipop rom boot... The only way to get that to boot, is to flash the rom over the top of itself, then it boots with all my lollipop data still intact....

4) I shall try this when I've finished messing around and testing dual booting, for now this is a great experience... Able to test both OS's at same time... :)

Any help or advice on the above issues, gratefully received, and thanks for all your help and making this happen... :)

Cheers, Lister
[Galaxy S II General] koolkunz:
have never experienced that issue..so cant help srry
[Galaxy S II General] Lister Of Smeg:
Hi [MENTION=5262182]koolkunz[/MENTION],

I have a feeling my issue may arise, due to the fact I am using PIT files... And I must be one of the first to do PIT and dual booting....?

Still not sure how it achieves this dual boot, how the files are accessed, moved, or swapped about...? (its all very hidden). Although the partitions/volumes look a bit odd on the second rom when booted and using a file manager.

I am guessing the way it does it, is it was designed with stock setup in mind. So some how it is cloning (or using) 2Gb /data for the 2nd (as it should officially be), however as my Lollipop has a 4GB /Data, it must be confused as to whats the right volume.... I'd imagine if I ran my phone in stock mode again, it'll work fine... And maybe why Lollipop doesn't boot back up when installing the Apolo kernel. May try it on a mates untouched phone... As don't want to lose my 4GB partition.

There isn't a newer version of that Dual Boot kernel is there, that is a little more tolerant now, due to people playing with their PIT partitions...??

Cheers, Lister
[Galaxy S II General] koolkunz:
There are newer versions...but they don't have any changes related to pit partitions...the one I have provided in the link is the most trusted and stable version
[Galaxy S II General] lohtse:
is it possible to have JB as primary as would like to play with lollipop but not as a primary os....
[Galaxy S II General] Troubadour666:
no :(

but you can have a good 2nd rom JB like NeatROM or WIzzedKat , made for dualboot (by me too in their thread) and swap beetween any Lollipop 1rst ROM that work with Apolo beta4 or 5 and use Dorimanx kernel to run sometimes your 2nd rom.

Your 2nd rom can be any KitKat too, depends your preferencies ;)

thanks
[Galaxy S II General] lohtse:
thank you but don't want lp as primary...as would be on JB most of time whilst I get use to LP am not keen to move to LP yet till I understand how the apps that allow write to sd work and make sure they actually work fully..
[Galaxy S II General] sur-ya:
can't boot to 2nd rom

No 2nd rom

After repeating the procedure for whines

I have flashed Kernel_Dorimanx-V10.44-LP-SGII-PWR-CORE- 08-01 - 2
[Android General] d3adEye:
Hi guys, can i suggest to have a development of a device named SKK PLATINUM..

Here are the Specs..

Phone Type	Smartphone

Smart Phone OS	Android

Smart Phone OS ver.	4.2 Jelly Bean

Shape	Bar	SIM	Dual SIM

Processor Speed	1.2GHz Quad Core

Internal Storage	16GB ROM

RAM	1GB	External Storage

SD card up to 32GB

Screen Size	5inch

Resolution	1280x720

Touch Screen	yes

Screen Type	LCD

Network

Speed	Wireless LAN	yes

Bluetooth	yes

Hotspot/Tethering

Camera

Pixels	13mp / 8mp (front)	Flash	yes

Image Stabilization

GPS

it's a good phone but bloated.

Battery is also an issue 1800mAh only.

PS. can u please also add method for rooting and flashing recovery for this one.

Thank You very much in advance...

Norman Jermaine

Encoder / A3 Department

東隆五金工業股份有限公司

Tong Lung (Phils.) Metal Industry Co., Inc.
[Verizon Samsung Galaxy S III] Droidriven:
[MENTION=3691964]rixter13[/MENTION] so you're telling us that what we already suspected was true, we have figured out that the verizon device the roms are for requires a SIM so that's why we needed it also, we have suspected that the rom is trying to drive our device the same way it does the verizon, now, how do we remove the 4g function from the ROM so it bypasses needing the SIM or 4g function and just go straight for 3g as our phones normally would? or how do we mod the stock MMS apk so it plays nice with our 3g

also I consulted with motorhead at AA51 and explained what was happening with the roms on our device and he mentioned that the rils were gonna be a b****h, we've all been digging at this trying to get it surrounded, we've approached from every angle we can think of, its to the point that its gonna take some dev to fix

or call straight talk and get them to enter the APNs because they can't be entered manually on straight talk so we need a volunteer to call them and see if them doing the APNs will fix our issue, I have a feeling it won't because if the sim is required for the rom to work then even if the APNs are done by straight talk the SIM might mess that up because with the SIM in the system pulls the APNs from the SIM, so what is on the SIM might wipe out the APNs that straight talk enters from their end. I've stopped trying to think like the phone and started trying to think like the ROM, its gonna follow its programming unless we change the ROM, I no longer think the data tricks and edits are gonna work unless the ROM is cracked open and things for our phone spliced in and the verizon stuff taken out. Can this be done?
[Verizon Samsung Galaxy S III] rixter13:
Well, unless StraightTalk (or someone else) comes out with android 4.4.4 rilblobs that don't force a SIM check we are stuck with the SIM card hack. The cm patches from 9/3/14 on are what caused our phones radio's to stop working properly.

As for the MMS issues, I haven't yet had the time to dig through the code to see what changed where (I am assuming I would be looking for a pre Unified commit 2/26 or around that time). I will try to tear apart that apk and look around in there for a smoking gun, but currently my PC is dead (lightening wiped out my motherboard) and I don't have any android tools on my wifes machine. So it may be a few days before I can get that done.

I will keep you posted on any progress (or lack thereof) on this, if anyone tries anything in this area (even if it doesn't work) I'd like to know about it so we don't waste more time running down the wrong path.
[Verizon Samsung Galaxy S III] Droidriven:
how about we have everybody pull logs, would that help?
[Verizon Samsung Galaxy S III] rixter13:
So the radio logs often have the IMEI number in them, so we need to be careful there posting them, I can pull logs from a VM I have on my work computer and compare them to my wifes 'virgin' ST S3.
[Verizon Samsung Galaxy S III] Droidriven:
so users with non SIM compatable devices are screwed, I've got 4.4.4 on my KFHD7 and my S2E4GT and neither one of them are SIM compatable so how do they run 4.4.4 without one?

wait! let me guess, those devices have an internal SIM?

so you're saying that even if we strip all the verizon stuff we'll still need the SIM for anything 4.4.4 and up?

there's even a 5.0 for the S2E4GT
[Verizon Samsung Galaxy S III] rixter13:
Not exactly, you are comparing separate things here. Are either of those verizon phones? Also do they have a 'unified' build? If you look above at some of the commits for the d2lte unified build that I posted earlier, the proprietary file list changed around that time, which is where things like the gps, radio, camera, and barometer (along with other hardware specific) 'drivers' come from. We can go back and branch off of the cm build from early September which still uses the 4.1.2 rils from ST, but we would also have to modify certain other things that have changed from that point on to get to where CM is today. There is quite a bit of work involved trying to maintain a separated branch from them, a LOT of roms are based on CM and then they put their 'tweaks' on top of that.
[Verizon Samsung Galaxy S III] Droidriven:
so you're saying this only applies to verizon and the unified d2lte builds? Gotcha

---------- Post added at 08:46 PM ---------- Previous post was at 08:43 PM ----------

has anyone got anything from the ST S3 with 4.4? could we work with the ST 4.4 instead of the 4.1.2 to go off of? I think that model is the AT&T version instead of the verizon version of ST S3
[Verizon Samsung Galaxy S III] rixter13:
The good news (if there is such a thing) is we get a fresh start with Lollipop. It looks like the first efforts for the SIII was to DE-Unify the rom :). The flipside of this coin is that the Lollipop builds are still buggy. Once I get my main machine back up and running, I may try to roll my own rom for the SCH968. I have compiled CM and Liquid roms, but never ventured out on my own yet.
[Verizon Samsung Galaxy S III] rixter13:
So RIL stands for Radio Interface Layer (essentially the radio drivers), so even if you could get them for the AT&T, they don't help us since our phone uses Verizon towers. And as far as I know, they are closed source and carrier specific, which is what makes this an almost impossible feat.
[Verizon Samsung Galaxy S III] Droidriven:
its a good thing that anything is possible, the trick is HOW? I'm actually kind of enjoying the challenge with this phone, my other devices have been easy compared to this one, this things like a finicky @$$ cat that got rubbed the wrong way! I'm actually learning something from you guys on this one, I might just go get another pain in the @$$ device when we get this one beat, I know everyone has tried with the H2 device but I'd like to find an exploit to root it so we can get what is in the H2 because its not available, I thought about just pulling what I can from it before I downgrade to root, kinda why I've waited to root it, gotta be a way to root this one

Question, does anyone know what part of the H1 had the vulnerabilities and is there a way to take these parts out of H1 while leaving everything else and apply those parts to the H2 to give it the same vulnerabilities so that stock H2 can be rooted, I've been trying to track down every root method I can find, I've read about rooting devices with another rooted device but they both have to be OTG capable, I've also wondered if there's a way to use the s-beam feature on this device to root it since it is another way to push or pull data to and from it, I know nothing of these things though, I'm just a thinker, but I do wonder about that and if anyone has tried even if its only remotely possible its worth a shot but it would take someone that knows way more than I, I learn fast but I wouldn't know where to start with that.
[Verizon Samsung Galaxy S III] heXacode:
Chainfire could root the H2's. It'd be best to ask him.
[Verizon Samsung Galaxy S III] Droidriven:
how do I go about doing that? He's a complete stranger to me, I've used plenty of things that are his though
[Verizon Samsung Galaxy S III] rixter13:
Speaking of the H2, what android version is on it?
[Verizon Samsung Galaxy S III] heXacode:
You could find his profile here. Or G+. He will probably be extremely busy and probably has 100's of people talking to him.

4.1.2.

As stated by Straight Talk they never push out new android versions. Whatever phone you get is gonna stay on that version for good.
[Verizon Samsung Galaxy S III] Droidriven:
yeah its 4.1.2 why?

the H1 and H2 are identical except for the patched kernel and the fact that H2 has two different versions itself, a qcom and a exynos
[Verizon Samsung Galaxy S III] heXacode:
No explanation as to why. They just don't handle that kind of thing which sucks.
[Verizon Samsung Galaxy S III] Droidriven:
yeah I know, I'd rather try myself than bother him, he has bigger fish to fry than a prepaid ST, even if it is one of the better S3's (H2/qcom anyways)

---------- Post added at 10:37 PM ---------- Previous post was at 10:33 PM ----------

Im gonna like seeing what I can do with CM on 2Gb RAM with no bloat!
[Verizon Samsung Galaxy S III] rixter13:
So to give an idea of what we need, here are the ST (older) rilblob files (ignore the dates listed below):

-rw-r--r-- 1 root root 3.7M Dec 3 19:46 libril-qc-qmi-1.so

-rw-r--r-- 1 root root 49K Dec 3 19:45 libril.so

and here are the new ones (VZW):

-rw-r--r-- 1 root root 2.5M Feb 28 2008 libsec-ril.so

-rw-r--r-- 1 root root 53K Feb 28 2008 libril.so

(the same files as the later ones are found on Lollipop as well)

I am looking into how to decompile a .so file at the moment.