Related
I have a Galaxy S2 GT-I9100G (bought in China 2 years ago).
In the past I have changed it's rom to SuperROM#v1.1 found here : http://forum.xda-developers.com/showthread.php?t=1374135.
The current Android version is 2.3.6 (oldddd )
Kernel version is : 2.6.35.7
Baseband version : I9100GZCKI1
I also have CWM-based Recovery v5.0.2.6 for GS2.
I would really like to upgrade to JellyBean.
I have seen a couple of versions here:
* http://www.ibtimes.co.uk/articles/4...100g-android422-jellybean-aokp-mr1-build6.htm
* http://www.ibtimes.co.uk/articles/4...-android422-jellybean-vanilla-rootbox-rom.htm
* http://www.ibtimes.co.uk/articles/4...droid422-jellybean-update-slimbean-build5.htm
and of course all the ROMs here on the site (too much to choose from !)
My question is : can my *Chinese* device be upgraded to JellyBean ?
If so - I have read on some forum threads that I need to somehow get the stock roms first, but I have no idea where to get them for the Chinese device.
Any help would be very much appreciated...
S2User said:
I have a Galaxy S2 GT-I9100G (bought in China 2 years ago).
In the past I have changed it's rom to SuperROM#v1.1 found here : http://forum.xda-developers.com/showthread.php?t=1374135.
The current Android version is 2.3.6 (oldddd )
Kernel version is : 2.6.35.7
Baseband version : I9100GZCKI1
I also have CWM-based Recovery v5.0.2.6 for GS2.
I would really like to upgrade to JellyBean.
I have seen a couple of versions here:
* http://www.ibtimes.co.uk/articles/4...100g-android422-jellybean-aokp-mr1-build6.htm
* http://www.ibtimes.co.uk/articles/4...-android422-jellybean-vanilla-rootbox-rom.htm
* http://www.ibtimes.co.uk/articles/4...droid422-jellybean-update-slimbean-build5.htm
and of course all the ROMs here on the site (too much to choose from !)
My question is : can my *Chinese* device be upgraded to JellyBean ?
If so - I have read on some forum threads that I need to somehow get the stock roms first, but I have no idea where to get them for the Chinese device.
Any help would be very much appreciated...
Click to expand...
Click to collapse
officially yes, unofficially(none samsung) yes
official:
take a look at this: http://forum.xda-developers.com/showthread.php?t=2171269 (thanks to hacbaoklhh for posting this thread)
unofficial (none samsung)
first you need to do the official thing (so you can get the ics/jb boatloader in), if you wish to stick with the official then you're done, no need to continue.
then you need to do this: http://forum.xda-developers.com/showthread.php?t=2113545 flash via stock recovery (thanks to Ryuinferno for his great work)
then you can flash whatever rom you want (AOSP, AOKP, MIUI)
to revert back to original:
take a look at this: http://forum.xda-developers.com/showthread.php?t=1916623 (thanks to Harchaoui for his hard work) or you can do the official thing again via odin, end of story
but i wouldnt revert back to chinese stock rom, we have the best developers and our 4.2.2 has become so stable
good luck
xtachix said:
officially yes, unofficially(none samsung) yes
official:
take a look at this: http://forum.xda-developers.com/showthread.php?t=2171269 (thanks to hacbaoklhh for posting this thread)
unofficial (none samsung)
first you need to do the official thing (so you can get the ics/jb boatloader in), if you wish to stick with the official then you're done, no need to continue.
then you need to do this: http://forum.xda-developers.com/showthread.php?t=2113545 flash via stock recovery (thanks to Ryuinferno for his great work)
then you can flash whatever rom you want (AOSP, AOKP, MIUI)
to revert back to original:
take a look at this: http://forum.xda-developers.com/showthread.php?t=1916623 (thanks to Harchaoui for his hard work) or you can do the official thing again via odin, end of story
but i wouldnt revert back to chinese stock rom, we have the best developers and our 4.2.2 has become so stable
good luck
Click to expand...
Click to collapse
Wow, that was fast !
Thanks so much for the response.
I have 3 questions if you could answer:
1. In your first link it says "Instructions For Flashing ICS:".
Does it mean that is will flash ICS or that I need to have ICS to flash it ?
because I don't have ICS... I have Gingerbread ...
2. Does the process in both your links change the Kernel or the Rom ?
(I managed to forget all this stuff since I last did this 2 years ago)
3. Which ROM would you recommend to use ? (out of the AOPS, AOKS and MIUI)
Thanks !
S2User said:
Wow, that was fast !
Thanks so much for the response.
I have 3 questions if you could answer:
1. In your first link it says "Instructions For Flashing ICS:".
Does it mean that is will flash ICS or that I need to have ICS to flash it ?
because I don't have ICS... I have Gingerbread ...
2. Does the process in both your links change the Kernel or the Rom ?
(I managed to forget all this stuff since I last did this 2 years ago)
3. Which ROM would you recommend to use ? (out of the AOPS, AOKS and MIUI)
Thanks !
Click to expand...
Click to collapse
1. its ok, that's probably just a typo, the android version there is 4.1.2. should state JB. via odin you can flash that and you will have official JB
flashing via odin doesnt care which version of android you currently have
2. the process of the first link will basically put a whole new kernel and rom in your system. you will have official JB kernel from samsung along with official rom from samsung. your version will be 4.1.2. (this is required to get the ics/jb bootloader which you dont have)
the purpose of the second link is to change the kernel so that it has cwm or twrp recovery integrated in. this will allow you to flash mods and roms and all that. but it is not necisary if you are not willing to use AOSP AOKP MIUI. if you'd like to stick with the official and see how it performs then you don't have to do the second link
3. personally i think the simpler the better, i use CM10.1 (CyanogenMod 10.1) <----- thanks to codworkerx, i also like Thinking Bridge http://forum.xda-developers.com/showthread.php?t=2199527 (thanks to Black_Prince for his great work)
couple any of those roms with http://forum.xda-developers.com/showthread.php?t=2251840 kernel (thanks to biagio7xD) and you will have a super fast rom with no SOD
xtachix said:
1. its ok, that's probably just a typo, the android version there is 4.1.2. should state JB. via odin you can flash that and you will have official JB
flashing via odin doesnt care which version of android you currently have
Click to expand...
Click to collapse
Thanks for the info.
2. the process of the first link will basically put a whole new kernel and rom in your system. you will have official JB kernel from samsung along with official rom from samsung. your version will be 4.1.2. (this is required to get the ics/jb bootloader which you dont have)
the purpose of the second link is to change the kernel so that it has cwm or twrp recovery integrated in. this will allow you to flash mods and roms and all that. but it is not necisary if you are not willing to use AOSP AOKP MIUI. if you'd like to stick with the official and see how it performs then you don't have to do the second link
Click to expand...
Click to collapse
I would like to go with custom ROMs. do I have to do the chapter 'Instructions For Changing CSC' that is in your first link ?
It says that it will wipe my device.
3. personally i think the simpler the better, i use CM10.1 (CyanogenMod 10.1) <----- thanks to codworkerx, i also like Thinking Bridge http://forum.xda-developers.com/showthread.php?t=2199527 (thanks to Black_Prince for his great work)
couple any of those roms with http://forum.xda-developers.com/showthread.php?t=2251840 kernel (thanks to biagio7xD) and you will have a super fast rom with no SOD
Click to expand...
Click to collapse
Thanks for the info. I don't think I will use the simple CM10.1 . I will look for a nice-looking UI rom.
By the way - do all the ROMs work with the Kernel that I will install in step 1 ?
S2User said:
Thanks for the info.
I would like to go with custom ROMs. do I have to do the chapter 'Instructions For Changing CSC' that is in your first link ?
It says that it will wipe my device.
Thanks for the info. I don't think I will use the simple CM10.1 . I will look for a nice-looking UI rom.
By the way - do all the ROMs work with the Kernel that I will install in step 1 ?
Click to expand...
Click to collapse
Dont worry about CSC.
every rom comes with its own kernel, if you're refering to step one as in the official then that's the kernel for official and nothing else
the blazing kernel is also for official and nothing else (or official based roms)
the kernel link i gave you last was for aosp aokp based roms
xtachix said:
Dont worry about CSC.
every rom comes with its own kernel, if you're refering to step one as in the official then that's the kernel for official and nothing else
the blazing kernel is also for official and nothing else (or official based roms)
the kernel link i gave you last was for aosp aokp based roms
Click to expand...
Click to collapse
So I am a bit confused now ...
You say 'don't worry about CSC'.
Does that mean I don't have to install CSC ?
Or that I do have to install it, but not worry about it...
also - I understood from your 1st comment that I have to go through the official kernel & rom, before I can put a custom rom.
Did I get it right ?
Because now from your last comment - I am understanding that if I want a custom rom - I can go ahead and just install it with its own kernel, without having to go through the first step of installing the official rom and kernel.
xtachix said:
officially yes, unofficially(none samsung) yes
unofficial (none samsung)
first you need to do the official thing (so you can get the ics/jb boatloader in), if you wish to stick with the official then you're done, no need to continue.
then you need to do this: http://forum.xda-developers.com/showthread.php?t=2113545 flash via stock recovery (thanks to Ryuinferno for his great work)
then you can flash whatever rom you want (AOSP, AOKP, MIUI)
Click to expand...
Click to collapse
Another question : I looked at this link - isn't CWM6 old ? I thought that the latest version is 10.1
S2User said:
So I am a bit confused now ...
You say 'don't worry about CSC'.
Does that mean I don't have to install CSC ?
Or that I do have to install it, but not worry about it...
also - I understood from your 1st comment that I have to go through the official kernel & rom, before I can put a custom rom.
Did I get it right ?
Because now from your last comment - I am understanding that if I want a custom rom - I can go ahead and just install it with its own kernel, without having to go through the first step of installing the official rom and kernel.
Click to expand...
Click to collapse
dont worry about the csc means really dont worry, every official rom, custom rom, comes with csc. some of them have multiple csc.
S2User said:
Another question : I looked at this link - isn't CWM6 old ? I thought that the latest version is 10.1
Click to expand...
Click to collapse
CWM = clockworkmod (this is the recovery integrated with the kernel. you have a few main types- cwm, twrp, official). this recovery allows you to install roms and such. version 6 is the latest. if i'm not mistaken the version you have for gingerbread would be (if you have cwm) 4 or 5.
cm = cyanogenmod (this is the rom)
they are two different things.
let us go through the basics:
what does a ROM have?
it has a kernel (this allows you to do the basic io stuff, it has cwm or twrp >> if custom, or official recover if official)
it has a bootloader (this allows you to get into a specific version of roms), official roms have the bootloader
it has system files (this is the actual rom base, it has all the modules)
it has basic apps (well, these are the apps, dialer, messaging, etc..)
it has csc
it has baseband and ril
let us elaborate a little bit:
your phone currently has gingerbread bootloader. so it is version 2.0+
to use Icecream sandwich you need the icecream sandwich bootloader. 4.0+
different version means different bootloader
this is where flashing a rom via odin comes in handy. it will install that specific bootloader into your phone
ofcourse along with other things, like the kernel, actual rom, apps. so you will have a full 4.1.2 system.
notice: ics and jb bootloaders are the same, reason is simple, the base version of both is 4, if there they introduce a version 5 android then everyone has to get the newest bootloader for version 5 to use it.
it doesnt matter where the 4.x+ comes from, if it is aosp aokp official miui, the bootloader is REQUIRED to run any of those
now your first step is to install the official rom (this way you ensure that you have the proper bootloader, and at the same time you get the official 4.1.2). now if you want to keep the official then there is nothing else to do, if by any chance you need to change csc then the steps there are simple, but it is not required. look up what is csc
next you need to install a kernel that has either cwm or twrp (this way you prepare yourself to install custom roms)
next you select the rom you would like to install, download it and put it in your sdcard
next you boot into recover (notice it is different from the official one, it has many options)
install the rom from the sdcard location
and in many cases you will have to install gapps (google apps, and do not make a mistake and install the wrong one, every version of android has its own gapps, if you have 4.2.2 install ONLY 4.2.2 gapps)
done!
as i mentioned above, every rom comes with whatever that it comes with. a kernel, csc, blah blah blah.
so basically what happens when you flash the custom rom?
simple, you change the kernel (zImage) it has its own and that's what it needs to run, and official kernel cannot run an aosp rom. period.
you put a whole new framework, system, apps, based on the android version they have been developed in.
next if you want to modify things, you can get into themes, installing another kernel, changing baseband and ril(Radio Interface Layer), and so on.
well i hope this helps
xtachix said:
dont worry about the csc means really dont worry, every official rom, custom rom, comes with csc. some of them have multiple csc.
CWM = clockworkmod (this is the recovery integrated with the kernel. you have a few main types- cwm, twrp, official). this recovery allows you to install roms and such. version 6 is the latest. if i'm not mistaken the version you have for gingerbread would be (if you have cwm) 4 or 5.
cm = cyanogenmod (this is the rom)
they are two different things.
let us go through the basics:
what does a ROM have?
it has a kernel (this allows you to do the basic io stuff, it has cwm or twrp >> if custom, or official recover if official)
it has a bootloader (this allows you to get into a specific version of roms), official roms have the bootloader
it has system files (this is the actual rom base, it has all the modules)
it has basic apps (well, these are the apps, dialer, messaging, etc..)
it has csc
it has baseband and ril
let us elaborate a little bit:
your phone currently has gingerbread bootloader. so it is version 2.0+
to use Icecream sandwich you need the icecream sandwich bootloader. 4.0+
different version means different bootloader
this is where flashing a rom via odin comes in handy. it will install that specific bootloader into your phone
ofcourse along with other things, like the kernel, actual rom, apps. so you will have a full 4.1.2 system.
notice: ics and jb bootloaders are the same, reason is simple, the base version of both is 4, if there they introduce a version 5 android then everyone has to get the newest bootloader for version 5 to use it.
it doesnt matter where the 4.x+ comes from, if it is aosp aokp official miui, the bootloader is REQUIRED to run any of those
now your first step is to install the official rom (this way you ensure that you have the proper bootloader, and at the same time you get the official 4.1.2). now if you want to keep the official then there is nothing else to do, if by any chance you need to change csc then the steps there are simple, but it is not required. look up what is csc
next you need to install a kernel that has either cwm or twrp (this way you prepare yourself to install custom roms)
next you select the rom you would like to install, download it and put it in your sdcard
next you boot into recover (notice it is different from the official one, it has many options)
install the rom from the sdcard location
and in many cases you will have to install gapps (google apps, and do not make a mistake and install the wrong one, every version of android has its own gapps, if you have 4.2.2 install ONLY 4.2.2 gapps)
done!
as i mentioned above, every rom comes with whatever that it comes with. a kernel, csc, blah blah blah.
so basically what happens when you flash the custom rom?
simple, you change the kernel (zImage) it has its own and that's what it needs to run, and official kernel cannot run an aosp rom. period.
you put a whole new framework, system, apps, based on the android version they have been developed in.
next if you want to modify things, you can get into themes, installing another kernel, changing baseband and ril(Radio Interface Layer), and so on.
well i hope this helps
Click to expand...
Click to collapse
Thanks so much for the information !
I've managed to install 10.1 and now have 4.2.2 !
Thanks so much !
S2User said:
Thanks so much for the information !
I've managed to install 10.1 and now have 4.2.2 !
Thanks so much !
Click to expand...
Click to collapse
you're most welcome,
enjoy your newly flashed rom
Hello ! I recently rooted my Samsung Galaxy S4 Mini 4.2.2 JB but i still use my custom rom. Now i am aware that i cant use the full features of GravityBox module on Xposed because it doesnt support Samsung TouchWiz. Can you guide me on how can i flash Vanilla Android (I'm not exactly sure what this is) on my galaxy device, so i could benefit on 100% from the GravityBox.
Vanilla Android usually refers to an Android system with no modifications by manufacturers or ROM devs. You should find such ROMs and lots of explanations in your devices forum: http://forum.xda-developers.com/galaxy-s4-mini. For example you could try Cyanogenmod (which is not vanilla but close enough that Xposed should work well): http://wiki.cyanogenmod.org/w/Serranoltexx_Info The installation guide there should also work for most other ROMs. Whatever you do, keep in mind that gathering as much information as possible before doing something prevents most problems
Hwyl.Fawr said:
Vanilla Android usually refers to an Android system with no modifications by manufacturers or ROM devs. You should find such ROMs and lots of explanations in your devices forum: http://forum.xda-developers.com/galaxy-s4-mini. For example you could try Cyanogenmod (which is not vanilla but close enough that Xposed should work well): http://wiki.cyanogenmod.org/w/Serranoltexx_Info The installation guide there should also work for most other ROMs. Whatever you do, keep in mind that gathering as much information as possible before doing something prevents most problems
Click to expand...
Click to collapse
Thank you. One more question, when i flash the new rom everythink in the phone erases, right ?
Yes! Before flashing you will need to wipe everything in your custom recovery (you'll easily find out what that exactly means). But since you seem to be rooted you can backup your apps and data by Titanium Backup.
Hwyl.Fawr said:
Yes! Before flashing you will need to wipe everything in your custom recovery (you'll easily find out what that exactly means). But since you seem to be rooted you can backup your apps and data by Titanium Backup.
Click to expand...
Click to collapse
Alright, so i go under recovery mode, wipe everything out and then i can flash the new rom vie Odin. Then i just make backup with my titanium and I'm ready to go ?
You first make the backup with titanium, after flashing you restore it. But, yes, thats in general the procedure to follow. Anyway, since I have no experience with your device, I gave you the two links. Just in case there is something special to keep in mind.
Yes i will take a closer look to the whole process these days before doing it. Thank you for the help :highfive:
My specs:
SCH-I545
Android 4.2.2
Baseband: I545VRUAMDK
Kernel: 3.4.0-562219
[email protected] #1
Build Number: JDQ39.I545VRUAMDK
Rooted
CWM Recovery Installed
My questions:
1. I've found many threads and great instructions for installing CyanogenMod. I'm still having difficulty separating the wheat from the chaff - Which version should I use for my phone, given that I'm an MDK still running 4.2.2?
2. Which version of Gapps will I need for that version of CyanogenMod?
3. If the answers to the previous questions are NO YOU CAN'T DO THAT, is there a way for me to update my Android Version to the most current, and THEN flash CyanogenMod?
I understand that there are resources out there to get this done. I've searched and found most of them. I'm just not entirely clear on which version is most appropriate for my phone, which by most standards here is somewhat pristine in that it's still running MDK, and a bit outdated in that it's running on 4.2.2. Please be gentle with me. I'm just trying to get up to speed and be productive in this forum. Thanks for your help!!
onearmsysiphus said:
My specs:
SCH-I545
Android 4.2.2
Baseband: I545VRUAMDK
Kernel: 3.4.0-562219
[email protected] #1
Build Number: JDQ39.I545VRUAMDK
Rooted
CWM Recovery Installed
My questions:
1. I've found many threads and great instructions for installing CyanogenMod. I'm still having difficulty separating the wheat from the chaff - Which version should I use for my phone, given that I'm an MDK still running 4.2.2?
2. Which version of Gapps will I need for that version of CyanogenMod?
3. If the answers to the previous questions are NO YOU CAN'T DO THAT, is there a way for me to update my Android Version to the most current, and THEN flash CyanogenMod?
I understand that there are resources out there to get this done. I've searched and found most of them. I'm just not entirely clear on which version is most appropriate for my phone, which by most standards here is somewhat pristine in that it's still running MDK, and a bit outdated in that it's running on 4.2.2. Please be gentle with me. I'm just trying to get up to speed and be productive in this forum. Thanks for your help!!
Click to expand...
Click to collapse
1) You need to download a nightly version of CM, I would advise reading the thread over there to see which one is the most stable before flashing. From what I've heard though CM has been very buggy.
http://download.cyanogenmod.org/?device=jflte&type=nightly
2) You should download the latest version of KitKit's GApps
https://goo.im/gapps/ ( gapps-kk-20140606 )
3) Happy flashing.
onearmsysiphus said:
My specs:
SCH-I545
Android 4.2.2
Baseband: I545VRUAMDK
Kernel: 3.4.0-562219
[email protected] #1
Build Number: JDQ39.I545VRUAMDK
Rooted
CWM Recovery Installed
My questions:
1. I've found many threads and great instructions for installing CyanogenMod. I'm still having difficulty separating the wheat from the chaff - Which version should I use for my phone, given that I'm an MDK still running 4.2.2?
2. Which version of Gapps will I need for that version of CyanogenMod?
3. If the answers to the previous questions are NO YOU CAN'T DO THAT, is there a way for me to update my Android Version to the most current, and THEN flash CyanogenMod?
I understand that there are resources out there to get this done. I've searched and found most of them. I'm just not entirely clear on which version is most appropriate for my phone, which by most standards here is somewhat pristine in that it's still running MDK, and a bit outdated in that it's running on 4.2.2. Please be gentle with me. I'm just trying to get up to speed and be productive in this forum. Thanks for your help!!
Click to expand...
Click to collapse
Make sure you have a CWM that is Kitlat capable!!!!
scrillakev said:
1) You need to download a nightly version of CM, I would advise reading the thread over there to see which one is the most stable before flashing. From what I've heard though CM has been very buggy.
http://download.cyanogenmod.org/?device=jflte&type=nightly
2) You should download the latest version of KitKit's GApps
https://goo.im/gapps/ ( gapps-kk-20140606 )
3) Happy flashing.
Click to expand...
Click to collapse
Scrillakev:
1. Ok. Does CM 11 differ from 10.x in that it isn't compatible with kit Kat? Does it matter what OS I'm running in terms of what version of CM I flash? Can you recommend any particularly stable Roms?
2. Thank you!
3. Thank you again!
npjohnson:
I installed clockworkmod recovery 6.0.4.7 through the flashify app. Can you point me towards a place I can verify that this is the correct version for kit Kat?
Thank you for your help!
onearmsysiphus said:
Scrillakev:
1. Ok. Does CM 11 differ from 10.x in that it isn't compatible with kit Kat? Does it matter what OS I'm running in terms of what version of CM I flash? Can you recommend any particularly stable Roms?
2. Thank you!
3. Thank you again!
npjohnson:
I installed clockworkmod recovery 6.0.4.7 through the flashify app. Can you point me towards a place I can verify that this is the correct version for kit Kat?
Thank you for your help!
Click to expand...
Click to collapse
6.0.4.7 is kitkat comp.
Personally, I run the Google Edition ROM, but Ive run CM11, and it works equally well, and had all the CMish stuff. *Some* issues with mms on cm.
In the CM11 thread is a link for CWM 6.0.5.0. I have successfully flashed CM11 with versions as early as 6.0.4.4. There are no KK compatible (meaning they work with everybody) but the most up to date is recommended. The latest nightlies have been very good. The only issue I currently experience is compass orientation is off by 180°. Maps and navigation work properly. I would recommend using the NC5 or NG6 modem only for best results. Don't flash a modem+nonhlos later than MDK, flashing a later modem only is fine and will cause no problems. Because of the kernel and code changes over the last couple months you will want a newer modem to prevent BT/WiFi/Mobile Data issues. Before you flash make a nandroid and be sure to clean flash since you are coming from a different ROM. As for Gapps they are all written by Google so Gapps are Gapps. I use the Paranoid Android flavor, they have also been updated just a few days ago.
Happy Flashing!!
FernBch, thank you for the excellent summary. That is all very useful info, and I feel way more confident about doing all this now thanks to you all.
OK last question - Is there a way for me to update my OS to 4.4 without losing my MDK status? If so, where can I find a procedure for doing that??
You guys rock. Seriously. Thank you!!
onearmsysiphus said:
Scrillakev:
1. Ok. Does CM 11 differ from 10.x in that it isn't compatible with kit Kat? Does it matter what OS I'm running in terms of what version of CM I flash? Can you recommend any particularly stable Roms?
2. Thank you!
3. Thank you again!
npjohnson:
I installed clockworkmod recovery 6.0.4.7 through the flashify app. Can you point me towards a place I can verify that this is the correct version for kit Kat?
Thank you for your help!
Click to expand...
Click to collapse
For a stable ROM I would recommend either the Google Play Edition ROM or The Dan's CM ROM.
Also you asked about not losing MDK, you won't lose MDK when flashing those ROMs just be sure to NOT take any OTA updates and you should be fine.
Thank you SkrillaKev! I've hunted a bit to find a thread that explains how to disable OTA but can't seem to find it.
I'm sure it'll pop up.
Hopefully soon - those daily OTA reminders are super annoying!
FernBch, regarding your 180deg compass issue, have you tried third party kernels? I've been fighting this issue for over a year and gave up. I had with stock, stock based, and any other roms I ever tried. Been running GPE rom for some time now, decided to give ktoonsez kernel a try. Compass problem solved! Worth a shot if you haven't tried it yet.
gpz1100 said:
FernBch, regarding your 180deg compass issue, have you tried third party kernels? I've been fighting this issue for over a year and gave up. I had with stock, stock based, and any other roms I ever tried. Been running GPE rom for some time now, decided to give ktoonsez kernel a try. Compass problem solved! Worth a shot if you haven't tried it yet.
Click to expand...
Click to collapse
None of the third party kernels work with the latest CM nigbtlies that I know of. When CM made the code and kernel changes they all quit working. As far as I know no one has updated them to work with the latest versions.
^^Good point. Completely forgot that change took place.
Maybe this device will get the support it needs at some point. Maybe not.
BOOTSTACK (KK and L) for G2 Mini
Supported variants: D618, D620, D620R
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! 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.
*/
What is BOOTSTACK ?
Bootstack is a bunch of files placed deep inside your phone. They are responsible for turning your phone ON and OFF, they are providing download mode which allows you to flash official KitKat and Lollipop .kdz files. Bootstack is ensuring SIM support so you could make calls, send texts and access mobile internet. Those files also allows you to fix your bricked phone after flashing bad ROM. Bootstack is basically making you phone work. If those files get corrupted you may have to send your phone to repair.
YOU SHOULD NOT MESS AROUND WITH DOES FILES !!!
Bootstacks available in download section are meant for advanced users who know what they are doing.
Which BOOTSTACK do I need ?
Usually you do NOT need and should NOT touch those files.
They are being updated when you flash .kdz file.
When you're updating your G2 Mini to Lollipop using .kdz you are also updating bootstack to a newer version. After that update you can only use stock LG Lollipop. So if you want to go back to stock KitKat or install any customROM you have to downgrade your bootstack.
You can do this in two ways:
1. Use .kdz file with KitKat in LG Mobile Support Tool. After that update you may lose all your data, your bootloader will be locked, your recovery will be restored to original and you will lose ROOT privileges. Your entire phone will be restored to factory state. (Safer and recommended for inexperience users)
2. Use bootstack zips provided here. After flashing one of the zip available below you will downgrade or upgrade your bootstack (depending on which zip will you use). You will get unlocked bootloader and your recovery will change to TWRP. ROOT privileges will NOT be affected.
If you decide to use second option check out this description:
- If you want to use official LG stock Lollipop choose Lollipop zip
- If you want to use official LG stock KitKat or customROM choose KitKat zip.
I still don't understand what is BOOTSTACK for
If you updated your stock software from KitKat to Lollipop using .kdz file (or official OTA) you also (unwillingly) updated your BOOTSTACK to Lollipop version which is good. It's how it supposed to be. But if you decide to restore your KitKat backup from recovery or install customROM while being on stock Lollipop you will NOT be able to make calls, send texts or access mobile internet. To have SIM support you need KitKat BOOTSTACK and you can find it in this thread. Read again "Which BOOTSTACK do I need ?" to make sure you know what you are doing. If you have never updated your phone to official stock Lollipop from LG you don't need to change anything.
If you still have questions about BOOTSTACK ask them in Q&A section here:
NONE
You will need ROOT, unlocked bootloader and custom recovery (TWRP recommended) to flash this.
If you decide to use my bootstacks, please let me know if it worked correctly for you (please include variant number and name of zip you used) !!!
Download:
If you want to use official LG stock Lollipop choose Lollipop zip
If you want to use official LG stock KitKat or customROM choose KitKat zip.
Click to expand...
Click to collapse
It's STRONGLY advised to less advanced users to read sections: "What is BOOTSTACK ?" and "Which BOOTSTACK do I need ?" before doing anything.
They should also choose ONLY files labeled as STABLE. They are confirmed as working properly for most of the people.
You should NOT forget that even stable files can work incorrectly for some users.
Click to expand...
Click to collapse
D618
Disclaimer:
Information and files published here may be incorrect. Using files provided in this thread may lead to complete, irreversible device damage. STABLE status is ONLY a suggestion NOT a fact. Every file available here, even files marked as STABLE might be faulty and may cause serious damage to software and/or hardware. I'm not responsible for bricked devices.
YOU ARE USING THOSE FILES AT YOUR OWN RISK !
Click to expand...
Click to collapse
KitKat: http://forum.xda-developers.com/g2-mini/general/d618-kk-bootstack-d618-fix-sim-support-t3142587
Version: Unknown - THIS BOOTSTACK WAS PROVIDED BY @numpea. Please contact him about KK BOOTSTACK for D618 !
Status: untested, use at your own risk !
Lollipop: https://www.androidfilehost.com/?fid=24052804347764481
Version: 2.5
Status: untested, use at your own risk !
D620
Disclaimer:
Information and files published here may be incorrect. Using files provided in this thread may lead to complete, irreversible device damage. STABLE status is ONLY a suggestion NOT a fact. Every file available here, even files marked as STABLE might be faulty and may cause serious damage to software and/or hardware. I'm not responsible for bricked devices.
YOU ARE USING THOSE FILES AT YOUR OWN RISK !
Click to expand...
Click to collapse
KitKat: https://www.androidfilehost.com/?fid=24052804347764465
Version: 1.5
Status: untested, use at your own risk !
Lollipop: https://www.androidfilehost.com/?fid=24052804347764471
Version: 2.5
Status: untested, use at your own risk !
D620R
Disclaimer:
Information and files published here may be incorrect. Using files provided in this thread may lead to complete, irreversible device damage. STABLE status is ONLY a suggestion NOT a fact. Every file available here, even files marked as STABLE might be faulty and may cause serious damage to software and/or hardware. I'm not responsible for bricked devices.
YOU ARE USING THOSE FILES AT YOUR OWN RISK !
Click to expand...
Click to collapse
KitKat: https://www.androidfilehost.com/?fid=24052804347764466
Version: 1.5
Status: STABLE. Confirmed as working by user: Martiz
Lollipop: https://www.androidfilehost.com/?fid=24052804347764467
Version: 2.5
Status: untested, use at your own risk !
Installation instructions:
0. Make sure you have ROOT privileges, unlocked bootloader and custom recovery (TWRP recommended) installed on your device.
1. Download correct zip and place it on you SDcard.
2. Go to you custom recovery, chose INSTALL and select zip file with the bootstack
3. Confirm your choice and wait. That's it !
If the installation fail do NOT leave recovery. Connect your charger, write in this thread and wait for help.
Information about content:
- Both KitKat and Lollipop versions
- Unlocked bootloader and TWRP included
Status:
UNTESTED*
Using files provided in this thread may lead to complete, irreversible device damage. I'm not responsible for bricked devices. You are using this files at your own risk.
* - STABLE status is given after confirmation that everything is OK from users who used the ZIP files on their variants of G2 Mini. I do NOT test those files. Be aware that in some cases some ZIPs may be marked as STABLE by mistake so even STABLE ZIPs may be faulty. USE AT YOUR OWN RISK !
Credicts / Thanks:
LG - for releasing .kdz files
@shoxxy - for TWRP for L90 (the original thread)
@Зевс - for unlocked bootloaders for L90 (the original thread)
@Zaaap72 - for unlocked bootloaders for G2 Mini
@powermetza - for TWRP recovery for G2 Mini
@numpea - for helping me getting all G2 Mini necessary files
@myllo.setya - for TWRP recovery for G2 Mini
...if I forget about someone then go ahead and contact me !
ITS NOT ALLOWED TO MIRROR MY FILES , IF YOU WANT TO SHARE , ASK ME , AND ONLY LINK TO THIS ORIGINAL THREAD !!!
This thread was created originally for LG L90.
I'm providing ONLY a limited support for LG G2 Mini.
---------------------------------------------------------------------------------------------------------------------------
If you like what I'm doing. Please use Thanks! button below.
Great work !!! :good:
so basically this http://forum.xda-developers.com/g2-mini/development/rom-v20c-flashable-zip-t3122821 hence the Rom and kernel.
So just a smaller zip. Good work if works correctly though
Tse™ said:
so basically this http://forum.xda-developers.com/g2-mini/development/rom-v20c-flashable-zip-t3122821 hence the Rom and kernel.
So just a smaller zip. Good work if works correctly though
Click to expand...
Click to collapse
Yes, kinda. My files do not change your system or data partitions so after flashing customROM you can flash my bootstacks without needing to flash a ROM again or do a wipe.
That would be EXTREMELY bad action should you choose a wrong bootstack. I think you can and should add an android version check to your script to prevent flash over incompatible versions. From L to KK for example.
I'll give a try in next days on my D620r, just let me get this straight: I have Lollipop, I do have to flash the KitKat bootstack in order to make custom ROMs work, right?
Cafi96 said:
I'll give a try in next days on my D620r, just let me get this straight: I have Lollipop, I do have to flash the KitKat bootstack in order to make custom ROMs work, right?
Click to expand...
Click to collapse
To make SIM card and mobile data works
when you flash a custom rom (cm12, blisspop) via stock 5.0.2 you'll get unknown baseband and no sim support
so yo need to get back to stock kitkat and flash custom rom through it or you can just flash the kitkat bootstack without going back to stock and root and unlock bootloader.....
numpea said:
To make SIM card and mobile data works
when you flash a custom rom (cm12, blisspop) via stock 5.0.2 you'll get unknown baseband and no sim support
so yo need to get back to stock kitkat and flash custom rom through it or you can just flash the kitkat bootstack without going back to stock and root and unlock bootloader.....
Click to expand...
Click to collapse
That is not correct at all. When you are on stock 5.0.2 and flash a custom 5.x rom there is no problem at all except the bugs lying in the rom it self.
The problem is when you are on for example stock 5.0.2 and want to flash lets say CM11(4.4.4 that is). Due to the incompatible bootstacks your phone most likely won't boot or if it boots there will be problems.
Another example is when you are on stock 4.4.2 and want to flash-upgrade to stock 5.0.2. Then you have the OP's mentioned problems.
Please provide correct information otherwise those files can lead to bootloops or even bricks.
Tse™ said:
That is not correct at all. When you are on stock 5.0.2 and flash a custom 5.x rom there is no problem at all except the bugs lying in the rom it self.
The problem is when you are on for example stock 5.0.2 and want to flash lets say CM11(4.4.4 that is). Due to the incompatible bootstacks your phone most likely won't boot or if it boots there will be problems.
Another example is when you are on stock 4.4.2 and want to flash-upgrade to stock 5.0.2. Then you have the OP's mentioned problems.
Please provide correct information otherwise those files can lead to bootloops or even bricks.
Click to expand...
Click to collapse
You can go ahead and flash CM12 or CM12.1 or BlissPop on stock 5.0.2 you will see what i'm talking about :good:
Tse™ said:
That is not correct at all. When you are on stock 5.0.2 and flash a custom 5.x rom there is no problem at all except the bugs lying in the rom it self.
Click to expand...
Click to collapse
Nope.
I tried twice some weeks ago. I am on stock 5.0.2.
I unlocked bootloader and installed TWRP, then I tried to flash some ROMs. Even CM12, PAC and Resurrection Remix (everyone of these based on 5.0.2) used to have the SIM issue.
Cafi96 said:
Nope.
I tried twice some weeks ago. I am on stock 5.0.2.
I unlocked bootloader and installed TWRP, then I tried to flash some ROMs. Even CM12, PAC and Resurrection Remix (everyone of these based on 5.0.2) used to have the SIM issue.
Click to expand...
Click to collapse
And with this is fixed?
Tse™ said:
And with this is fixed?
Click to expand...
Click to collapse
Not tried yet.
Tse™ said:
That would be EXTREMELY bad action should you choose a wrong bootstack. I think you can and should add an android version check to your script to prevent flash over incompatible versions. From L to KK for example.
Click to expand...
Click to collapse
I will NOT do that because at some point developers may start to support newer BOOTSTACKS and having this script would create a lot of mess. There should be no problems with running the device on wrong bootstack as long as it's for the same variant. For example flashing KK bootstack instead of L for D618 while on stock Lollipop. On L90 this never created any damages for device. Not sure for G2 Mini. The best decision is to choose the correct bootstack and avoid any potential problems.
Cafi96 said:
Not tried yet.
Click to expand...
Click to collapse
My best guess is no. I imagine the problems are caused from the roms them selves having been built from 4.4.2 sources, bootstacks etc.
As the op said above the developers must use the latest sources.
Tse™ said:
That is not correct at all. When you are on stock 5.0.2 and flash a custom 5.x rom there is no problem at all except the bugs lying in the rom it self.
The problem is when you are on for example stock 5.0.2 and want to flash lets say CM11(4.4.4 that is). Due to the incompatible bootstacks your phone most likely won't boot or if it boots there will be problems.
Another example is when you are on stock 4.4.2 and want to flash-upgrade to stock 5.0.2. Then you have the OP's mentioned problems.
Please provide correct information otherwise those files can lead to bootloops or even bricks.
Click to expand...
Click to collapse
The first post explains everything. There are also LOTS of warnings.
If you want to use official LG stock Lollipop or LG stock Lollipop based ROMs choose Lollipop zip
If you want to use official LG stock KitKat, LG stock KitKat based ROMs or customROM choose KitKat zip.
Click to expand...
Click to collapse
Information on the top is pretty straight forward. Don't know if it's good for G2 Mini CustomROMs but it's correct for stock KK and L.
If you're not sure which BOOTSTACK choose for your customROM then ask your ROM developer. He should know it !
You can also tell your developers to include information in their ROMs thread about which BOOTSTACKs to install.
All the g2m custom ROMs are based on KitKat bootstack (as of time of writing) and, thus, the bugs will appear when you flash a custom ROM on Lollipop bootstack.
The ROMs have to be updated to support the new (Lollipop) bootstack.
Sent from my D620r [Stock 4.4.2 , -V- Kernel]
I've used the Kk bootstack on Lollipop stock rom on my D620r to flash cm 12.1, and everything went perfect. Now the mobile network works flawlessly.
Installed the KK bootstack on my D620r with Lollipop, everything worked fine for me too.
Just, i have to add ro.wifi.channels=14 to my build.prop in order to make my network recognised, but I guess that it's a ROM issue.
I have successfully reverted from lollipop to kitkat.
Full wipe
Flashed kk bootstack
Restored kk backup.
All working fine.
Many thanks for your work.
D620R Lollipop Bootstack working, used to move from custom cm12 to stock 5.0.2 (.zip file).
This:
Lollipop: https://www.androidfilehost.com/?fid=24052804347764467
Version: 2.5
Status: untested, use at your own risk !
OK. I'm on stock 4.0.4 , ucll6 and I wanna directly root and install LP and mm roms. What's best method? All threads seem to be unmaintained and outdated. Thanks.
Did root via arogon method. Now what recovery do I flash? Figuring kernels are flashed with it.
My name says it all. That said I'm pretty sure that you are going to have to increase your space to be able to install MM with the appropriate gapps package. Same holds true for most LP roms on here.
You might can try this thread for a LP rom with a pico gapps package http://forum.xda-developers.com/gal.../cyanogenmod-12-unofficial-i777-call-t3211103 (note: I'm not sure it requires resizing partitions since it does not specify.) Should be able to also find a version of TWRP 2.7.1.0 or newer floating around here. I also add that though lots of these threads on here haven't been posted in in a couple of years, the information you find is still uptodate. GL
AnotherFreakinNoob said:
My name says it all. That said I'm pretty sure that you are going to have to increase your space to be able to install MM with the appropriate gapps package. Same holds true for most LP roms on here.
You might can try this thread for a LP rom with a pico gapps package http://forum.xda-developers.com/gal.../cyanogenmod-12-unofficial-i777-call-t3211103 (note: I'm not sure it requires resizing partitions since it does not specify.) Should be able to also find a version of TWRP 2.7.1.0 or newer floating around here. I also add that though lots of these threads on here haven't been posted in in a couple of years, the information you find is still uptodate. GL
Click to expand...
Click to collapse
If I flash that twrp 2.7, wouldn't I need a certain kernel?
Honestly man I can't say for sure. Sorry.
I'm running a s959g and followed the guide in the help forum laid out by Mr.cook (you'd likely find more/better help in the help forum). I will say that from what I gathered the kernel and recovery are linked in the S2. That said when I flashed my 1st recovery I was on stock 2.3.6 Gingerbread and went straight to the TWRP 2.7 version. From there I flashed Rogersb11's 4.4.4 ROM that had the shift kernel (awesome kernel btw check it out) built in. GL
ETA: I'd almost say that as long as you find a i777 version of the TWRP and installed it you'd be good to go.