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.
Related
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.
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Devc100 said:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Click to expand...
Click to collapse
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Ph4nToM_Z3rO said:
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
Click to expand...
Click to collapse
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
aadi50 said:
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
Click to expand...
Click to collapse
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Ph4nToM_Z3rO said:
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Click to expand...
Click to collapse
We have both stable RR and CM13.
CM is simple and clean and less loaded.... RR is most feature rich Custom rom we have alongwith stability...
Rest depends on what type of user, u are... If u like trying differnt ROMs... Start with CM13...
If u just want to have a feature rich longtime setup, U can use RR directly without wasting time... It is based on CM, So it obviously have everything CM has.... :good:
Ph4nToM_Z3rO said:
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Click to expand...
Click to collapse
Latest Stock Marshmallow:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-21.40.1220.1877-user.zip
Stock RecoveryRestore it using TWRP)
https://drive.google.com/open?id=0B2BGto29cXq1NjYySjRES21yOTg
Last Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.17.40.1531-user.zip
First Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.11.40.299-user.zip
First Do A nandroid backup of your phone. So that if any thing goes wrong, U can recover it.
Then Download both the Stock MM and Recovery file named TWRP.zip.
Extract TWRP.zip.
Then take both the MM software and Xtracted TWRP folder in a memory card.
Then Open TWRP recovery in ur phone and restore the stock recovery.
Then Erase Every Thing including System.
Then Restart The recovery. Now you will see that the recovery has gone back to the stock recovery.
Now flash the stock marshmallow from your memory card.
Then flash TWRP from fastboot and thn u can flash any supported custom Android MM or Android N.
N.B. If it dosent work. Then you have to first install the last lollipop Zenfone 2 Laser(Z00LD) software then install the marshmallow.
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
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
I'm currently on latest stock Nougat with BL unlocked and rooted + ElementalX kernel. I want to upgrade to stock Oreo but after a ton of reading it looks like everything can go wrong with efs and persist. Is the following process correct:
- flash [Oreo][Stock][Rom] TWRP Flashable Stock Builds.
- flash ElementalX latest version for Oreo
- Root with Magisk
Would this process keep my bootloader unlocked, with signal and safe from bricks?
Thank you for your help.