Related
Hi all, i'm pleased to share my work with you.
Here you have the latest official lollipop firmware for D855 ( v. 20A - LRX21M) packed in a zip flashable file.
I made this because all of us want to keep the old bootloader that is - at the moment - the only one who accept the bumped TWRP provided us by team Codefire.
I made also a step further and found a way to root this ROM.
Here you go:
First of all i suggest you to install the TWRP modded by me to allow the backup of the modem.
Be sure you select also the modem partition before taking the backup. ( If you want to restore the backup then restore also the modem )
1- download the two files and put them into the sdcard;
2- reboot in recovery and do a factory reset;
3- install the ROM and the supersu ZIP;
4- reboot the device and enjoy your rooted Lollipop ROM.
If you come from an earlier lollipop firmware you can dirty flash, it might work.
I spend a lot of time developing this so if you think i deserve you can donate ( look at my sign )
DOWNLOAD
SUPERSU flashable ZIP
ROM
MIRROR
KK MODEM ( you need this only if you downgrade from lollipop to kitkat and you don't need if you backed up before with the modded TWRP recovery)
DONATORS:( really tnx guys)
GTMoraes, tobitege, shaboogen, pRo_lama, hnyuk49, rossonero82, spotlight79, TeamSlayr, Vegard Helland, Mishaal Almashan, Sagar Singh, PAPPL, ArubidCo, bigmupps
CREDITS:
teamcodefire, chainfire
Changelog:
- 13.11.2014 - updated to the official LRX21M - 20A ( poland FW )
Q&A
What this ROM include?
In the ROM zip you can find only the system, modem and kernel (bumped) image
What do i need to flash this?
You need only to have the TWRP recovery installed
If i flash this i will lose the bumped recovery?
Nope. The bootloader will not be changed.
If i want go back to KK roms ( stock or AOSP) what i have to do?
Just flash your ROM or restore a previous nandroid backup. But, after that, flash the zip with the KK modem you can find in the 1st post.
I really need to flash the root files?
Must i answer????
Cannot write to internal SD?
With adb or a terminal emulator do:
Code:
su
restorecon -v -R /data/media
Your statusbar and navbar are gone?
This is a issue reported from some user.
Try to format manually data in TWRP before install the rom.
If this doesn't work try flashing the kdz of the H firmware ---> root ----> twrp ----> install this rom ( sperimental).
Doesn't have the option to enable LTE?
Go with a root browser to system/app/Lteconfigs/, click and install the apk, then reboot and you will have the option for LTE.
Wwooiootttttt?????
Things to do today: f5
@Skin1980: You definitely deserve some beers (or whatever you like ) 0F714082VL945954E
THANK YOU!!
You absolutely rule. Thank you
tobitege said:
@Skin1980: You definitely deserve some beers (or whatever you like ) 0F714082VL945954E
THANK YOU!!
Click to expand...
Click to collapse
Like i said in the other post really tnx. My wife and my childs are gonna kill me for the time spent on the PC!
Now this is the stuff. Maybe this G3 wasn't a bad choice after all. Beer (or some wine to keep the wife happy) incoming when I'm not at work
beast.
thank you! could you possibly link to the tot/kdz you used to downgrade from lollipop to kitkat?
What kernel do you use for rooting? 4.4 or custom?
Wait wut? So this is all done in the stock recovery? No root, no custom recovery needed? Just bang it all on the sd card and go?
rhystagram said:
beast.
thank you! could you possibly link to the tot/kdz you used to downgrade from lollipop to kitkat?
Click to expand...
Click to collapse
exactly this http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW784506432109876543213/D85510H_00.kdz
agelus69 said:
Wait wut? So this is all done in the stock recovery? No root, no custom recovery needed? Just bang it all on the sd card and go?
Click to expand...
Click to collapse
TWRP is needed my friend
yocasta said:
What kernel do you use for rooting? 4.4 or custom?
Click to expand...
Click to collapse
I patched the stock kernel...
5PP44527BR123160Y
Beer your way mate. Thanks for your help.
D.S
super work :good:
But be careful at the modem!!! It was not compatible with our country
Skin1980 said:
I patched the stock kernel...
Click to expand...
Click to collapse
Sweet, great news!
Sorry for this question but after flashing this rom via bump twrp can we go back to KK Aosp by flashing it back? Or do we need to connect to a PC to restore back to stock fw?
Rman666 said:
super work :good:
But be careful at the modem!!! It was not compatible with our country
Click to expand...
Click to collapse
The D855 is the international version.
The modems are interchangeable.
D.S
Nice job. Thank you. (ID: 6MC15224ET241474H)
I keep getting this error which says, "boot certification vertify". when I try to go into recovery mode. To begin with, I have updated my vs985 to 5.01 lollipop and then I had my device rooted. From this I have tried using apps like Flashify or using adb to flash TWRP 2.8.6.1 touch recovery for vs985. When I flash it I then boot into recovery to see that boot certification error. Can someone please help me fix this? If you need any more info just ask.
rokyle said:
I keep getting this error which says, "boot certification vertify". when I try to go into recovery mode. To begin with, I have updated my vs985 to 5.01 lollipop and then I had my device rooted. From this I have tried using apps like Flashify or using adb to flash TWRP 2.8.6.1 touch recovery for vs985. When I flash it I then boot into recovery to see that boot certification error. Can someone please help me fix this? If you need any more info just ask.
Click to expand...
Click to collapse
You need to upgrade with jasmine or skydragon stock roms from a kk build, if you want to keep twrp and root. You have some partitions that need to be replaced, that's why you get the error.
bweN diorD said:
You need to upgrade with jasmine or skydragon stock roms from a kk build, if you want to keep twrp and root. You have some partitions that need to be replaced, that's why you get the error.
Click to expand...
Click to collapse
So I would just flash the Jasmine rom then I could reroot my device and flash twrp or do I have to root and flash twrp, install partitions and then upgrade with Jasmine rom?
rokyle said:
So I would just flash the Jasmine rom then I could reroot my device and flash twrp or do I have to root and flash twrp, install partitions and then upgrade with Jasmine rom?
Click to expand...
Click to collapse
flash any KK version (12b preferred), root and twrp, flash skydragon or jasmin L upgrade rom, profit!
Your using the wrong TWRP for verizon.
Use this one. http://downloads.codefi.re/thecubed/lg_g3/bump/twrp-2.8.0.0_vs985-signed.img
Sent from my VS985 4G using XDA Free mobile app
what version of trwp should i use i just downgraded to 12b have root and have twrp manger downloaded just dont know witch one to use lil new to the g3 thanks for any help
Sorry for the delay,but thanks what you did worked! Now I have twrp on my g3, thanks!
rokyle said:
Sorry for the delay,but thanks what you did worked! Now I have twrp on my g3, thanks!
Click to expand...
Click to collapse
Did you flash to a KK 12b version method?
Using the image that Sublime posted resulted in the same issue.
I upgrade my phone to 12B then I rooted and flashed the newest version of twrp which happens to be then 2.6.8.1 version I think. Then I flashed the Jasmine rom....
phoenixaldana01 said:
what version of trwp should i use i just downgraded to 12b have root and have twrp manger downloaded just dont know witch one to use lil new to the g3 thanks for any help
Click to expand...
Click to collapse
Use the latest version that TWRP Manager offers, then use TWRP to flash the latest one on XDA made for the G3.
Sent from my VK810 4G
Hey guys,
My SGS2 just got soft-bricked, stuck on samsung logo. I didn't do nothing actually, just restarted my phone.
I have rooted phone with stock OS (latest one) on it a long time ago.
I can enter into recovery mode. Tried to wipe data with no luck.
BUT I want to make a backup. I read that if I install CWM recovery I will be able to mount USB storage to make backups. Is it possible to backup contacts using USB?
I also read that on SGS2 devices CWM will update OS's kernel so I will have to install new OS. Is it true?
Anyway, is it possible to make a full backup in this case?
GrigoryS said:
Hey guys,
I also read that on SGS2 devices CWM will update OS's kernel so I will have to install new OS. Is it true?
Click to expand...
Click to collapse
"A recovery is a kernel and a kernel is a recovery"
If your current OS supports the new kernel then there won't be a need to install a new OS.
Kevin3014 said:
"A recovery is a kernel and a kernel is a recovery"
If your current OS supports the new kernel then there won't be a need to install a new OS.
Click to expand...
Click to collapse
How to check if my OS supports new kernel?
What is more important is that if I install CWM breaking my current ROM and make a full backup will I be able to restore this backup on new ROM?
I ask this because I found the following warning:
"Warning: For GT-i9100 and SGH-i777, installing CWM or TWRP recovery also installs kernel. This is only recommended to install when installing a new custom ROM. Installing CWM/TWRP recovery will most likely break the ROM you are running currently as it overwrites the ROM’s kernel."
GrigoryS said:
How to check if my OS supports new kernel?
Click to expand...
Click to collapse
Simple. Just read the information provided by the threads. If you are on official jelly bean, use Apolo Kernel 4.15b or Siyah Kernel (Although this is outdated now). For Lollipop, you can either use DorimanX kernel 11.0 or CM12.1 kernel with TWRP by Lysergic acid (If you want to use CM12.1). For kitkat, you can use DorimanX kernel 10.45 by Me or 10.44 by Cybernetus, Gustavo kernel (make sure you install KK version) or Apolo Kernel 7.3.
---------- Post added at 02:40 PM ---------- Previous post was at 02:38 PM ----------
GrigoryS said:
I ask this because I found the following warning:
"Warning: For GT-i9100 and SGH-i777, installing CWM or TWRP recovery also installs kernel. This is only recommended to install when installing a new custom ROM. Installing CWM/TWRP recovery will most likely break the ROM you are running currently as it overwrites the ROM’s kernel."
Click to expand...
Click to collapse
It depends on what ROM you are using. If you install the correct kernel, the ROM will not break at all.
gsstudios said:
It depends on what ROM you are using. If you install the correct kernel, the ROM will not break at all.
Click to expand...
Click to collapse
Hi! Is there any way to check the version of ROM I use on this phone? Maybe from recovery mode?
P.S.: I used latest OS which came through official update on SGS2 in Europe. It was something like 4.2.3 or 4.3.3.
If it was the last/latest/final official update, it would have been 4.1.2 Jellybean.....
http://i.imgur.com/rVnFwJM.jpg
Hm... That's strange... I was pretty sure I had 4.3.3 .
OK, let's imagine I install CWM with newer kernel breaking my ROM... what if I install older version after that? Will my ROM be back to work?
It *might* well be ok.....but having never intentionally installed the wrong kernel, I'm not going to stake my life on that as I have ZERO experience of that scenario....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
It *might* well be ok.....but having never intentionally installed the wrong kernel, I'm not going to stake my life on that as I have ZERO experience of that scenario....
Click to expand...
Click to collapse
OK I'll wait for someone who can confirm that. Thanks, anyway!
GrigoryS said:
OK I'll wait for someone who can confirm that. Thanks, anyway!
Click to expand...
Click to collapse
GrigoryS said:
Hm... That's strange... I was pretty sure I had 4.3.3 .
OK, let's imagine I install CWM with newer kernel breaking my ROM... what if I install older version after that? Will my ROM be back to work?
Click to expand...
Click to collapse
Stock 4.3.3 doesn't exist
Samsung only provided android version 4.1.2 as the last version.
If you install a older kernel after flashing the wrong kernel, your ROM should work again. Once again, the "older" kernel needs to be the correct version for the ROM.
If you do install the wrong kernel, your ROM will not boot and will either give you black screen or bootloop or phone constantly rebooting. So you need to quickly get to the recovery using the button combinations.
Hi everyone. I was read a lot off discussions about i9100 with CM12.1 but I still don't know how to do it without some problems.
My phone actually running CM13.1 latest nightly build with Team Win TWRP recovery v 2.8.XXX and maybe DorimanX kernel? I don't know how to find Kernel name and version... I would like to ask you how to go to Cm12.1 build with pico or nano GAPPS (And what build I should download). I need the most stable build for daily use. Next how to replace CM recovery with TWRP 3.0.2. . I am totally confused. I'll be glad for any help.
Oh. I have that problem too. CM 13.1 not stable!
Jaccob25 said:
Hi everyone. I was read a lot off discussions about i9100 with CM12.1 but I still don't know how to do it without some problems.
My phone actually running CM13.1 latest nightly build with Team Win TWRP recovery v 2.8.XXX and maybe DorimanX kernel? I don't know how to find Kernel name and version... I would like to ask you how to go to Cm12.1 build with pico or nano GAPPS (And what build I should download). I need the most stable build for daily use. Next how to replace CM recovery with TWRP 3.0.2. . I am totally confused. I'll be glad for any help.
Click to expand...
Click to collapse
Firstly look under settings -> about device and it will tell you the kernel version. If it says 3.0.101-CM------, you have the stock CM13 kernel. You said you have TWRP 2.8.x.x and not CM recovery?? This means you already have the isorec recovery enabled. All you need to do is flash the 3.0.2-1 .img from this recovery and you will have the newer one installed. And just do normal backup/wipes and install CM12.1 as you would any other rom. Just remember to use 5.1 gapps(arm;5.1;pico/nano)
Here is the last official CM12.1 I uploaded
Here is a more up to date unofficial CM12.1
noppy22 said:
Firstly look under settings -> about device and it will tell you the kernel version...
Click to expand...
Click to collapse
Yes I have stock cm13 kernel and TWRP flashed. Can I flash new TWRP via Odin?
Thank you very much!
Jaccob25 said:
Yes I have stock cm13 kernel and TWRP flashed. Can I flash new TWRP via Odin?
Thank you very much!
Click to expand...
Click to collapse
I don't think you can flash a .img file with odin. Honestly if you want to downgrade to 5.1.1 it would be easier to do it in one go.
Flash CM12.1, gapps, then TWRP 3.0.2-1.img all from TWRP 2.8
noppy22 said:
I don't think you can flash a .img file with odin. Honestly if you want to downgrade to 5.1.1 it would be easier to do it in one go.
Flash CM12.1, gapps, then TWRP 3.0.2-1.img all from TWRP 2.8
Click to expand...
Click to collapse
Ohh I thought that TWRP can't flash img file.
Thanks for advice. I try it today.
So I try that and almost everything works fine. Only GPS fixing seems like a little bit problematic. But I don't know my testing was short. I will see.
May I ask a supplementary question - I am in a similar position, I have an i9100 which I upgraded from stock 4.1.2 Jelly Bean to CM13 following (most of) djibe's guide here
So I now have CM13 ROM with kernel version 3.0.101, re-partitioned with Lanchons repit, and with recovery TWRP 3.1.0 installed and functioning.
I want to revert from CM13 to CM12.1. From above, I believe that I can simply backup, wipe, then flash the CM12.1 ROM (I'll be using the last nightly, cm-12.1-20160203-NIGHTLY-i9100.zip) - is that correct?
My question/confusion is, do I also need to flash an isorec-compatible kernel (ie kernel-Lanchon-TRIM-IsoRec-20160111-cm-12.1-i9100.zip)? The isorec thread (here) says that the "Official CyanogenMod 12.1 and 13 kernels are now IsoRec-compatible", so it seems to me unnecessary, but many threads/guides on XDA say to flash one of Lanchon's kernels.
Please could someone advise, and my apologies for what is probably an ignorant question.
teraghik said:
May I ask a supplementary question - I am in a similar position, I have an i9100 which I upgraded from stock 4.1.2 Jelly Bean to CM13 following (most of) djibe's guide here
So I now have CM13 ROM with kernel version 3.0.101, re-partitioned with Lanchons repit, and with recovery TWRP 3.1.0 installed and functioning.
I want to revert from CM13 to CM12.1. From above, I believe that I can simply backup, wipe, then flash the CM12.1 ROM (I'll be using the last nightly, cm-12.1-20160203-NIGHTLY-i9100.zip) - is that correct?
My question/confusion is, do I also need to flash an isorec-compatible kernel (ie kernel-Lanchon-TRIM-IsoRec-20160111-cm-12.1-i9100.zip)? The isorec thread (here) says that the "Official CyanogenMod 12.1 and 13 kernels are now IsoRec-compatible", so it seems to me unnecessary, but many threads/guides on XDA say to flash one of Lanchon's kernels.
Please could someone advise, and my apologies for what is probably an ignorant question.
Click to expand...
Click to collapse
You are correct. Isorec support was implemented before that last nightly iirc. No need to flash any kernels.
Note: Only use the official TWRP 3.1 from the TWRP website or the.gangster's one which is basically the same. They are compatible with the earlier android versions.
Hi Noppy,
Thanks very much for taking the time to reply and help - I am using "the gangsters" TWRP 3.1 from djibe's thread, appreciate the heads up. I can confirm that I flashed CM12.1, and it works fine!
Why don't you follow my tutorial to get the perfect smooth Android 7.1 for SGS2 ?
Here it is : https://forum.xda-developers.com/galaxy-s2/help/guide-tutorial-samsung-galaxy-s2-i9100-t3538601
So, I won't go into too much details how I got into this one but, in nutshell:
I had CM 12 on my SGS II, tried to flash some ROM's and now when I try to boot my phone it's stuck at Samsung logo.
I can acess recovery (but my PC does not recognize it or it just recongizes it as Android ADB Recovery Interface) and I can acess download mode but I don't know what's the best way out of this mess.
Can someone give me quickest route to some kind of light at the end of the tunnel?
skunky90 said:
So, I won't go into too much details how I got into this one but, in nutshell:
I had CM 12 on my SGS II, tried to flash some ROM's and now when I try to boot my phone it's stuck at Samsung logo.
I can acess recovery (but my PC does not recognize it or it just recongizes it as Android ADB Recovery Interface) and I can acess download mode but I don't know what's the best way out of this mess.
Can someone give me quickest route to some kind of light at the end of the tunnel?
Click to expand...
Click to collapse
Did you by chance make any nandroid backups in TWRP? If so, restore one if them.
Have you tried flashing a smaller Gapps package with your ROM? You probably don't have the system space to fit the larger Gapps packages, that's why the i9100 has to use the re-PIT before flashing CM12, you might need to use the re-PIT with all ROMs newer than CM12, I'm not sure about that though.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Did you by chance make any nandroid backups in TWRP? If so, restore one if them.
Have you tried flashing a smaller Gapps package with your ROM? You probably don't have the system space to fit the larger Gapps packages, that's why the i9100 has to use the re-PIT before flashing CM12, you might need to use the re-PIT with all ROMs newer than CM12, I'm not sure about that though.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I didn't do any backups because Cyanogen mod recovery didn't support making and restoring backups! =((((
Well, man, I can't even find a way to transfer files to my PC right now so I don't know how to flash that thing that's why I need solution for that problem first.
skunky90 said:
I didn't do any backups because Cyanogen mod recovery didn't support making and restoring backups! =((((
Well, man, I can't even find a way to transfer files to my PC right now so I don't know how to flash that thing that's why I need solution for that problem first.
Click to expand...
Click to collapse
If you have access to download mode, enter it and flash CWM Kernel recovery and then boot into recovery and wipe data and format system flash cm12 to get isorec support and then flash Isorec TWRP and then reboot recovery again, you should now have twrp 3.0.X.X, now connect your phone to pc and it should recognise your device and you would be able to transfar your files to pc..
After that try rebooting -...as you already have cm12 installed...- and see if it still stuck, then try wiping all including system and internal sdcard and reflash again and see what happens
Edit: use cm11 instead of cm12 as suggested by @TriboDoP
MigoMujahid said:
If you have access to download mode, enter it and flash CWM Kernel recovery and then boot into recovery and wipe data and format system flash cm12 to get isorec support and then flash Isorec TWRP and then reboot recovery again, you should now have twrp 3.0.X.X, now connect your phone to pc and it should recognise your device and you would be able to transfar your files to pc..
After that try rebooting -...as you already have cm12 installed...- and see if it still stuck, then try wiping all including system and internal sdcard and reflash again and see what happens
Click to expand...
Click to collapse
Hi
I would do it also als you described but would not flash cm 12 because this old rom has no isorec Kernel
You could use this cm 11 which has Isorec kernel:
https://www.androidfilehost.com/?fid=673368273298924336
Regards!
Sent from my ME173X using XDA-Developers Legacy app
TriboDoP said:
Hi
I would do it also als you described but would not flash cm 12 because this old rom has no isorec Kernel
You could use this cm 11 which has Isorec kernel:
https://www.androidfilehost.com/?fid=673368273298924336
Regards!
Click to expand...
Click to collapse
Cm12 has no isorec support and cm11 has it???!!!
Well..that....is....WEEEEIRD !! :laugh:
I mean cm12.1 is newer, right?
MigoMujahid said:
Cm12 has no isorec support and cm11 has it???!!!
Well..that....is....WEEEEIRD !! [emoji23]I mean cm12.1 is newer, right?
Click to expand...
Click to collapse
Last official cm12.1 ist from 2015.
Isorec started 2016.
The link is for unofficial cm11 from 2017.
I tried this one and i am 100% Sure.
Sent from my ME173X using XDA-Developers Legacy app
TriboDoP said:
Hi
I would do it also als you described but would not flash cm 12 because this old rom has no isorec Kernel
You could use this cm 11 which has Isorec kernel:
https://www.androidfilehost.com/?fid=673368273298924336
Regards!
Click to expand...
Click to collapse
Cm12.1 has isorec support mate:
TriboDoP said:
Last official cm12.1 ist from 2015.
Isorec started 2016.
The link is for unofficial cm11 from 2017.
I tried this one and i am 100% Sure.
Click to expand...
Click to collapse
Ok, maybe the last build that support isorec isn't available to download but the screenshot i attached is from the official thread
TriboDoP said:
Last official cm12.1 ist from 2015.
Isorec started 2016.
The link is for unofficial cm11 from 2017.
I tried this one and i am 100% Sure.
Sent from my ME173X using XDA-Developers Legacy app
Click to expand...
Click to collapse
Of course there could be some unofficial cm12 from 2016 and newer.
Sent from my ME173X using XDA-Developers Legacy app
TriboDoP said:
Of course there could be some unofficial cm12 from 2016 and newer.
Click to expand...
Click to collapse
I have the latest official cm12.1 nightly, it was released in 23/1/2016 and it supports isorec , any way it's ok, it won't matter cm11 from cm12.1 the most important is to solve the problem, then he can flash what ever he wants
MigoMujahid said:
I have the latest official cm12.1 nightly, it was released in 23/1/2016 and it supports isorec , any way it's ok, it won't matter cm11 from cm12.1 the most important is to solve the problem, then he can flash what ever he wants
Click to expand...
Click to collapse
Perfectly allright!
Now we sorted it out together.
Cm12 release ist 2015 and nightly 2016.
Any rom from 2016 and newer has isorec.
I did not want to interfere with your help but i noticed quite a number of people here which are on release build having trouble to Install isorec Recovery.
Cheers!
Sent from my ME173X using XDA-Developers Legacy app