I've owned and rooted quite a few android phones from various companies (SONY, HTC, Nokia, Motorolla, Samsung) but the I find the whole process most confusing with the LG.
I bought my device 2nd hand and it was already on LP (some nameless custom rom) rooted, with recovery. It didn't even list baseband... it said unknown. So I flashed CLoudy 2.2, used it for a few hours, than flashed CM12.1.
Now, about my confusion. I read everywhere that you need the JB bootloader for CM/AOSP, because the loki exploit was patched with kk/LP, however, as per the instructions in the rom's OP, prior to flashing CM12.1 I flashed an LP bootstack, and according to my understanding, a bootstack is a collection of partitions that include basebend, bootloader etc.
So then... If CM/AOSP need the JB bootloader, how is it that the OP recommends an LP bootstack, and everything works perfectly fine with it.
What am I missing?
Are there any apps, or any way I can see what bootloader, what baseband I have installed on my device?
shy_bump.png
Not sure about "how to know which one are you using". You flashed it, so you should've remembered it. Anyways, if you need a specific bootstack for a specific rom, just flash the one you need (stated in the op). Doing that before every Rom flash assures you don't end up with the wrong one, mess up your partitions and brick your phone. I like doing it manually so I know exactly what I have, but you can use apps like autorec.
I am not into aosp so I don't follow it as much, but some of the recent builds are using lp bootstacks because they use CAF sources which allow/require use of lp bootstack.
Related
Hi guys, i've been reading this term "BUMPED" all over the thread and makes me curious of what it is? I've never encounter this term before since KITKAT days. So.. What is it?
marshygeek said:
Hi guys, i've been reading this term "BUMPED" all over the thread and makes me curious of what it is? I've never encounter this term before since KITKAT days. So.. What is it?
Click to expand...
Click to collapse
In the begining...
http://forum.xda-developers.com/lg-...mp-unlock-lg-g3-twrp-d852-d852g-f400-t2900614
http://forum.xda-developers.com/lg-g2/orig-development/bump-sign-unlock-boot-images-lg-g2-t2935396
And later:
http://forum.xda-developers.com/lg-g2/orig-development/tool-bump-sign-boot-images-t2950595
Before we had loki patch, but it worked only with JB bootloader. Since Bump!, custom kernel (and custom recovery) can work on KK bootloader.
6ril1 said:
In the begining...
http://forum.xda-developers.com/lg-...mp-unlock-lg-g3-twrp-d852-d852g-f400-t2900614
http://forum.xda-developers.com/lg-g2/orig-development/bump-sign-unlock-boot-images-lg-g2-t2935396
And later:
http://forum.xda-developers.com/lg-g2/orig-development/tool-bump-sign-boot-images-t2950595
Before we had loki patch, but it worked only with JB bootloader. Since Bump!, custom kernel (and custom recovery) can work on KK bootloader.
Click to expand...
Click to collapse
So, does it concern the end user before flashing or returning to Kitkat? Or we should not be worrying about this?
watching
I will follow your post, because useful information come.
marshygeek said:
So, does it concern the end user before flashing or returning to Kitkat? Or we should not be worrying about this?
Click to expand...
Click to collapse
Try to flash a not bumped custom recovery and/or not bumped custom kernel on a KK bootloader, and you will have a pretty good idea of what how this concern end users (nevertheless, I do not recommend you try, unless you want to experiment a secure boot error).
(you have a nice signing )
---------- Post added at 07:30 AM ---------- Previous post was at 07:11 AM ----------
ErivandoNascimento said:
I will follow your post, because useful information come.
Click to expand...
Click to collapse
shortly:
LG G2 bootloader is locked. It means that it prevents custom recoveries / custom kernel to be installed.
To bypass this protection, two workarounds exists.
The first solution ,loki https://github.com/djrbliss/loki has been patched by LG with the KK update, so it doesn't work anymore with KK bootloader. With loki, when KK arrives, we had to downgrade bootloader in its JB version for being able to install custom recovery (autorec by @Cloudyfa do it automatically).
Loki bypass the lg sign verification and permit to boot.
This thread where was found a solution for a custom recovery for KK is very instructive:
Maybe new KK recovery soon?
After, codefire team made bump!. It injects original LG signature in the kernel (and in custom recovery that has a kernel), so the bumped custom kernel/recovery can boot behind kk bootloader (Unlike loki, this workaround works with KK bootloader).
So, with bump, you can have a custom bumped kernel and/or bumped custom recovery behind a kk bootloader, but with loki you can just boot behind a JB one.
Ok, so we need Bumped material to use a KK Bootloader.
But, what are the benefits of the KK Bootloader ?
If the goal is just to avoid downgrading the Bootloader, isn't it easier to launch AutoRec ?
miljbee said:
Ok, so we need Bumped material to use a KK Bootloader.
But, what are the benefits of the KK Bootloader ?
If the goal is just to avoid downgrading the Bootloader, isn't it easier to launch AutoRec ?
Click to expand...
Click to collapse
An example of evolution that I enjoyed:
autorec, while it downgrades the bootloader (it flashes JB aboot), flashes a patched stock kernel too, because stock kernel can only boot behind a JB bootloader if the kernel is a little modified (patched, see my post: http://forum.xda-developers.com/showpost.php?p=56082714).
And for patching it, we need the open sources kernel . The last published kernel sources by LG are not those of the last available kernel.
By example , with the d802, the last kernel sources published are the 20D (http://opensource.lge.com/osSch/list?types=ALL&search=d802), but the last kernel available is the 20H.
So a bumped recovery TWRP is the only way to have complete pure stock 20H rom with custom recovery (with original untouched 20H kernel, bootloader and all bootstack) (http://forum.xda-developers.com/showpost.php?p=58575725).
Seems that this is a right place for some clarifications
I'm on Cloudy 2.2, and I have TWRP 2.7.0.0 and I want to update to latest TWRP version.
I'm not planning to upgrade bootloader from JB to KK, so if I just want to continue to use Cloudy 2.2 as it is, should I flash blastagator's TWRP with F2FS & Thermal Control, or some other version?
Is blastagator's TWRP compatible with my current configuration?
draskome said:
Seems that this is a right place for some clarifications
I'm on Cloudy 2.2, and I have TWRP 2.7.0.0 and I want to update to latest TWRP version.
I'm not planning to upgrade bootloader from JB to KK, so if I just want to continue to use Cloudy 2.2 as it is, should I flash blastagator's TWRP with F2FS & Thermal Control, or some other version?
Is blastagator's TWRP compatible with my current configuration?
Click to expand...
Click to collapse
Yes you can flash it from your recovery and it's ok for your configuration.
Cloudyg2 2.2 has its kernel bumped, it can work both from JB or KK bootloader (as the bumped TWRP can too).
Question
Hi, i am using bumped Recovery and official cm12.1 on my lg g2. I think i have jb bootloader, because i never upgraded it since autorec downgraded it to jb. I am not sure about the cm-kernel. Does cm12.1 support bump? Is it save to upgrade the bootloader to kitkat?
xXRapToRiXx said:
Hi, i am using bumped Recovery and official cm12.1 on my lg g2. I think i have jb bootloader, because i never upgraded it since autorec downgraded it to jb. I am not sure about the cm-kernel. Does cm12.1 support bump? Is it save to upgrade the bootloader to kitkat?
Click to expand...
Click to collapse
Yes, Rashed pushed the files a while a go to official builds.
hi there!
i recently looked for some roms for my 9515 phone
unfourtunantly, i read here: http://forum.xda-developers.com/galaxy-s4/general/galaxy-s4-value-edition-gt-i9515-t3190176
that there are no roms for this device..
so i found another thread- http://forum.xda-developers.com/galaxy-s4/i9505-develop/kernel-s4-value-edition-i9515-t3031044
which told me to download kernels, modems and other things in order 9505 roms to work.
tried it- but with no sucess.
BTW i tried to use this rom: http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-albe95-lollirom-official-1-0-t3049564
any help will be appriciated- THANX SO MUCH
ps- sorry for my english..
psII- i know that this is the forum for the 9500 and 9505 only, but i couldnt find any forum for the 9515.
psIII- i can use the phone only through PC- im using MyPhoneExplorer to mirror and control my phone.
Are you flashing a kernel right after flashing the ROM?
audit13 said:
Are you flashing a kernel right after flashing the ROM?
Click to expand...
Click to collapse
yes..
is that a prob?
edit: if i will flash stock, than kernel, and then rom- will it work?
Make sure the phone is running the latest bootloader and modem. Once that has been confirmed, perform a complete system wipe (system, cache, data) before flashing ROM, flash the ROM, and flash the kernel. Don't boot the phone out of recovery until after flashing the kernel.
audit13 said:
Make sure the phone is running the latest bootloader and modem. Once that has been confirmed, perform a complete system wipe (system, cache, data) before flashing ROM, flash the ROM, and flash the kernel. Don't boot the phone out of recovery until after flashing the kernel.
Click to expand...
Click to collapse
thanks so muchhhhh u saved my asss
how do i check my bootloader & modem version?
I suggest flashing a stock ROM from here: http://www.sammobile.com/firmwares/database/GT-I9515/
Once that is done, you can flash TWRP from here: http://forum.xda-developers.com/galaxy-s4/general/galaxy-s4-value-edition-gt-i9515-t3190176
With TWRP, you can create a nandroid backup. If you flash a ROM that doesn't work properly, boot into TWRP and restore your nandroid backup and start over.
Sometimes, you may fine a ROM that will work without further modification. If not, a custom kernel may be required.
What are you talking about? The first link you posted linked to various rom threads for the I9515.
There is unofficial CM13 for the I9515, also known as jflteve.
There also was an unofficial SlimLP..
Unofficial CM13
Unofficial CM12.1
Unofficial SlimLP
As you can see, there are some roms. No need to mess around with patchers. Unless you really want touchwhiz..
GDReaper said:
What are you talking about? The first link you posted linked to various rom threads for the I9515.
There is unofficial CM13 for the I9515, also known as jflteve.
There also was an unofficial SlimLP..
Unofficial CM13
Unofficial CM12.1
Unofficial SlimLP
As you can see, there are some roms. No need to mess around with patchers. Unless you really want touchwhiz..
Click to expand...
Click to collapse
want TW. SO BADLY
Hi there,
I'm using 4.4.2 wanamlite 2.9 rom on a i9505 with twrp 2.8.
Recently I encountered lot of problems like modem not working properly, rebooting, videos playing in slowmo, no sound etc... weird stuff...
I'm convinced to upgrade to (lets say) marshmallow (any custom rom) but I dunno how to do it properly. So here my questions:
- should I flash the stock rom and start again with root / custom rom etc? Or...
- should I upgrade with odin to stock modem and bootloader first, and after that install a custom rom via twrp? Which way is the correct one?
Btw. Should I upgrade to lolli, marsh or 7.x? Dunno whats better. I'm using touchwiz with xposed framework. I dont need tw but i find xposed very helpful. Any advice or link to guides?
Thanx
Upgrade the individual components. In your case, that means recovery, bootloader, and modem via Odin. Your copy of TWRP is ancient and the newer versions of Android need a newer version of TWRP to properly flash them. Once you've upgraded the components, download any Android 6.x ROM for your device - since you want Xposed - and flash it via TWRP. Android 7.x ROMs are available for your device, but Xposed does not work on them, and I don't expect it to work any time soon.
Strephon Alkhalikoi said:
Upgrade the individual components. In your case, that means recovery, bootloader, and modem via Odin. Your copy of TWRP is ancient and the newer versions of Android need a newer version of TWRP to properly flash them. Once you've upgraded the components, download any Android 6.x ROM for your device - since you want Xposed - and flash it via TWRP. Android 7.x ROMs are available for your device, but Xposed does not work on them, and I don't expect it to work any time soon.
Click to expand...
Click to collapse
Thanx Stephron.
Yesterday I updated via .img the recovery (TWRP 3.2).
Now I'll look for bootloader and modem. Should I use the stock ones or are on xda some threads with better modems and bootloaders?
I think I'm going for resurrection remix or for some aosp. Any experience?
Best and happy new year .
foongaz said:
Thanx Stephron.
Yesterday I updated via .img the recovery (TWRP 3.2).
Now I'll look for bootloader and modem. Should I use the stock ones or are on xda some threads with better modems and bootloaders?
I think I'm going for resurrection remix or for some aosp. Any experience?
Best and happy new year .
Click to expand...
Click to collapse
There are no custom modems and bootloaders.
Pwnycorn said:
There are no custom modems and bootloaders.
Click to expand...
Click to collapse
:good:
Really appreciate your help folks. I didnt follow xda for a while and I felt obsolete somehow heheheh
I've been running Cloudy G2.2 for a year an a half. It's given the phone enough legs to mostly make it through 2017. However, about every other week I have to restore my latest backup when Bluetooth stops working because it saw too many devices. This wouldn't be terrible if it wasn't for Authy refusing to sync my newer 2-Factor auth accounts. I think I've convinced myself that the G6 (US997) is my next phone, but now is a silly time to buy as the price should drop like a rock as the next wave of flagships come out.
I'm hoping to make it another couple months and was wondering anyone's experiences moving from Cloudy G2.2 (or other ROMs) to the latest lineage? From what I've read, it's very stable. However, I'm on Kit Kat bootloader, so it doesn't seem like this will be a straightforward process. I was hoping to get some experiences from people who made the same move before starting.
I currently have:
LG G2 D800
Root using stumproot (I think, it's been a while) with supersu installed
TWRP 2.7.0.0 installed by autorec
Cloudy G2.2 KOT49I
So, after some research, I set off to install LineageOS. In hindsight, this might have been a bad idea since it specifically only mentions the D802 in the title. However, it listed links for D800 builds, though they were crossed out.
I updated TWRP to this version by Blastagator and that was painless. I then wiped the phone, made a fresh backup and flashed the latest nightly of LineageOS, and the latest GApps (Mini) for 7.1. That was disappointing since I got the quick "LG logo" followed by a blank screen, that I later found was mentioned in the same Lineage post. Should've read farther.
I think the issue is that I'm on the wrong bootloader. I thought I was on KitKat which the post requires, but in order to enter recovery, I have to press enter three times (rather than using volume buttons to navigate), which indicates I'm on JellyBean bootloader.
So, this is the scary step that I was hoping to avoid. My big fear is that I run Linux on my desktop, so I can't use the LG Flash Tool. As long as I can keep a working recovery, I have backups, so I'm fairly safe. Following the Blastagator bootloader post, I'm not really sure how you go back and forth between bootloaders so easily as it suggests. Is that really as simple as loading the zip file on the phone and installing it in TWRP?
Is there a safer way to handle this?
From my experience, it is that easy. Simply install the zip file and you have loaded a new boot loader. Also, I was in the same boat as you with Cloudy rom and moved to Nougat with crDroid. However it's not stable and I am considering looking for something else more stable but fast like crDroid.
ernie young said:
I was in the same boat as you with Cloudy rom and moved to Nougat with crDroid
Click to expand...
Click to collapse
When you updated your bootloader, were you still able to run the Cloudy ROM before you switched to crDroid? Once I flash the KitKat bootloader, am I only able to use the Nougat ROMs? My big concern is that there might be something a bit off with my bootloader, so I won't be able to get back to TWRP.
I think there's something a bit off with my bootloader as is, because about a year ago I flashed back to stock Jellybean, and took all the OTA updates. However, when the phone tried to take the KitKat update, it softbricked, and could only be recovered using the LG Update Tool, which I don't have access to anymore. Because of this, I'm a little worried that just dropping on the Blastagator KitKat bootloader may have some atypical issues.
i m using it for a while. u know, on Los you won't be able to use lg features such as qslide, qmemo, plug&pop, knockcode etc. Only worth it if you want your phone to look a little bit fresher and lighter or you need a newer android version for some reason. Else, don't take the risk if you can't use flashtool. You can consider installing another kitkat rom. There are lots and they are nice :]
S YILDIRIM said:
or you need a newer android version for some reason.
Click to expand...
Click to collapse
My primary issue is that KitKat (or whatever Cloudy G2.2 is?) has the old Android bluetooth bug where once it sees too many devices, it stops connecting to anything. I have to make sure to turn off my phone if I go somewhere like an airport, and have been having to restore my clean Cloudy backup about once a month. It's getting pretty frustrating. On the other hand, I'm hoping to upgrade to an LG G6 (US997) in a month or two when the V30 release pushes down on prices. So, if it's a case of potentially hard-bricking my G2 at the worst possible time, I should hold off flashing.
I think you need hybrid bootstack for android 7.
WORF84 said:
I think you need hybrid bootstack for android 7.
Click to expand...
Click to collapse
That makes sense, but will I not be able to use my Cloudy 2.2 backup after that? It says that the hybrid bootstack will only boot CM 12.1, CM13, and LP stock roms.
superlou23 said:
That makes sense, but will I not be able to use my Cloudy 2.2 backup after that? It says that the hybrid bootstack will only boot CM 12.1, CM13, and LP stock roms.
Click to expand...
Click to collapse
These questions if this works with that or that are easier to answer for yourself by reading what goes with what.
Just Google LG G2 bootstack and you can probably find the ones you need for any available rom.
I use hybrid on Marshmallow 6.0.1 but I tried Nougat 7.1.2 too, it works.
hey ! i want to flash fastboot rom , currently im on custom rom. please tell me what is the latest firmware for indian varrient & link also of firmware.
If you're on a custom rom, and that rom is an Oreo rom, you will need to apply the persist fix to make sure you don't have any problems when moving to stock (e.g. lost IMEI, no Volte, no 4G, etc). For the guide here:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
If you know what you're doing, here's a link to NPNS25.137-92-14, the latest for the retin channel.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Edit: Also, do you really need the fastboot roms? Unless you're looking to lock your bootloader, maybe you'll be fine with the TWRP flashable stock roms - available for both Nougat and Oreo (soak test, not yet official).
NZedPred said:
If you're on a custom rom, and that rom is an Oreo rom, you will need to apply the persist fix to make sure you don't have any problems when moving to stock (e.g. lost IMEI, no Volte, no 4G, etc). For the guide here:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
If you know what you're doing, here's a link to NPNS25.137-92-14, the latest for the retin channel.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Edit: Also, do you really need the fastboot roms? Unless you're looking to lock your bootloader, maybe you'll be fine with the TWRP flashable stock roms - available for both Nougat and Oreo (soak test, not yet official).
Click to expand...
Click to collapse
Thanks for your reply bro , one last ques is it worthy to move to proper stock again?? or flashable builds are better ?
zooreo said:
Thanks for your reply bro , one last ques is it worthy to move to proper stock again?? or flashable builds are better ?
Click to expand...
Click to collapse
Comes down to what you want to do with your phone. If you want to keep root access, then you may as well stick with the TWRP flashables, as the full stock firmware will not install OTAs if you are rooted. Quite often the TWRP flashable builds will be available sooner than a lot of people receive OTAs through official channels. That is, once one person receives the OTA and shares it with me, I build the next flashable zip normally within a couple of days (I'm the maintainer). The modifications are minimal - just disabling dm-verity and forced encryption (the latest Oreo flashables built on the Aroma installer make that optional).
If you want to lock the bootloader for any reason (e.g. in order to sell your phone, or you want to ensure the highest level of security) then you only really have one choice - full fastboot stock.
Anyway, you can have a read in the two threads for Nougat and Oreo:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
[Oreo][Stock][Rom] TWRP Flashable Stock Builds