I decided to check on CloudyG2 LP which requires 20 bootloader which went find. I decided to flash back to stock LP which requires 30b bootloader. After flashing back to stock (30b bootloader and stock zip file) I am stuck at T-Mobile boot screen. It seems like 30b bootloader isn't flashing but I didn't get any errors in TWRP when flashing it. Any suggestions?
Download Mode says 'secure boot error'
I can get into TWRP
I can flash the CloudyG2 rom again and it boots.
I have tried download mode and the LGFlashTool with the kdz as well as the flash tool with the TOT and they both fail.
Did you flash just bootloader or the whole bootstack zip? I would flash the whole stack just in case. We're you on stock lp before cloudy lp and did you make a backup? If you have one, restore it, it should have all the partitions working properly.
Related
Hi. After flash LP 5.0.1 i need to flash KDZ. Now i have old TWRP with JB bootloader.
1. What is defference between loki and bump ? What does that mean bumped
2. When i have bumped 2.8.4.0 i can upgrade to KK bootloader and flash all custom ROMs or only with BUMPED tag ?
For now i flash all roms on JB bootloader and 2.7 TWRP and all works well (stock, optimus, claudyfa)
witek_77 said:
Hi. After flash LP 5.0.1 i need to flash KDZ. Now i have old TWRP with JB bootloader.
1. What is defference between loki and bump ? What does that mean bumped
2. When i have bumped 2.8.4.0 i can upgrade to KK bootloader and flash all custom ROMs or only with BUMPED tag ?
For now i flash all roms on JB bootloader and 2.7 TWRP and all works well (stock, optimus, claudyfa)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=58770769
thanks a lot. I know now everything. So i flash KK bootloader and TWRP 2.8.4.0 now. Thread to close.
after install TWRP and KK bootloader i have SECURE BOOT error. I think problem is flash kk bootloader at stock rom from KDZ
witek_77 said:
thanks a lot. I know now everything. So i flash KK bootloader and TWRP 2.8.4.0 now. Thread to close.
after install TWRP and KK bootloader i have SECURE BOOT error. I think problem is flash kk bootloader at stock rom from KDZ
Click to expand...
Click to collapse
If you flashed KK bootloader, you had to flash bumped kernel too (or stock KK not bumped kernel if you are on stock firmware), did you it ? If you have flashed bumped recovery and kk bootloader, you can acces to recovery with hard key combo, and flash a bumped kernel now, for being able to boot your firmware.
For answering your question in my thread, my 20H for bumped recovery contains the bootloader and the modem, as mentionned in this OP thread, so, with it, no need to flash kk bootloader manually.
You had a secure boot error because in your situation (stock D80220H with JB booloader + lokified patched kernel), to migrate to a bumped recovery, you needed to return to 20H originals bootstack (bootloader + others partitions => aboot,tz,sbl1,rpm,persist,laf,dbi) + originals 20H kernel with original 20H system/lib/modules (or bumped custom kernel).
now i know I flash KK bootloader AFTER clean KDZ. I didn't reflash boot after KK bootloader. Thanks a lot. My education was stopped on loki a year ago so now i need to reeducation
So, first got my LG G2. Was on 4.4.2. Managed to get custom recovery on it, cool. Attempted flashing resurrection remix. Success, bootloop.
TOT'd back to stock firmware, 4.2.2. Managed to root device, and place custom recovery on it after multiple apps because I don't understand what the f*** "Loki" Is, or anything. So I attempted to flash 4.4.2 ROM, failed. Cool. Attempted to flash resurrection remix again, got aboot error, and loki-ifying failure of some stuff. Rebooted device, bootloop. Cool. So, how do I place lollipop on the LS980 4.2.2?
@edit, got LiquidSmooth 4.4.4 ROM on there from 4.2.2. Had audio error, flashed newer nightly of LiquidSmooth, got bootloop. Flashed KK Baseband from Cloudy's thingy for the LS980, ran CloudyG2 LP Rom, installed via aroma, now I'm stuck in fastboot. gg.
Are you sure you're flashing the right versions? i.e. D801 for T-Mobile, etc
zeeebs said:
Are you sure you're flashing the right versions? i.e. D801 for T-Mobile, etc
Click to expand...
Click to collapse
Yeah, it was stated on by the pages of which, LS980 (Sprint), VS980(Ver) 802, int.. Etc.
Now I'm having to attempt to modify tot files to change model versions because my phone
Appears to be model LG-F320S in Download mode, but it's not. I flashed CloudyG2 3.0, and his LS980 KK Baseband
And that's what occured me to get stuck in fastboot mode. Now I've been reflashing stock firmware img's and I can't
Get back into fastboot mode, so I'm stuck in Downloading Mode but as I modify the hex, and try to do the tot file, I
Continuously get wrong model number. It's kinda aggravating...
@edit, managed to get back to 4.2.2 stock firmware with this http://forum.xda-developers.com/sprint-g2/general/dll-to-bypass-lg-flash-tool-model-check-t2990665
Now how do I upgrade to Lollipop?
Okay, so I have a Sprint LG G2 (LS980). I haven't used it in awhile so I flashed it to ZVE (Latest KK release.) via LGFlashTool. Well, I rooted via Stump Root, then I tried flashing a recovery via Flashify. It was Loki'd or anything, just the standard recovery.img from TWRP 2.8.6.0. This is where things started going bad. Recovery did not boot, nor did the ROM (for whatever reason), so I went back and tot'd ZVE again. When I booted up this time, I found a guide on how to flash the ZV7 aboot so I wouldn't need a patched recovery anymore. When I flashed this customer aboot, I also flashed the TWRP 2.6.3.3 (first version for G2 that was loki'd). I rebooted and all I got was a fastboot error...booted into TWRP and I had 2.6.3.3 TWRP, so I installed latest TWRP 2.8.6.0 inside recovery and now I can't get my ROM to boot anymore. I've tried numerous times to flash different firmwares for different releases on the LS980, but none of them overwrite my aboot. Download mode also does not work anymore. I'm lost at what to do. I have access to TWRP, but that's it. I want to get it back onto ZVE stock and I'll leave it at that if I can get it fixed.
(Use autorec app to downgrade bootloader and flash recovery. Flashify does disasters on G2.)
Flash blastagator bumped recovery and reboot recovery.
Flash dorimanx kernel and reboot recovery.
Flash the attacked zip and reboot to system.
https://mega.co.nz/#!o59iAC6J!DhhmN4krLZkqhoo6g2SDRn9gW3sgg_-Vih9ryxqGXwM
_____________________________________Read more write less and be smart
so got d802, rooted, used autorec for twrp, flashed cloudy 3.3 and now have the dreaded black screen,
managed to get into TWRP but pc not recognising phone?
what can i do, i presumed because phone was on kitkat it automatically had a kitkat baseband....
on further reading infact it does not, cant find any of the basebands to flash it,,
managed to get OTG working
any help
cheers
sutty86 said:
so got d802, rooted, used autorec for twrp, flashed cloudy 3.3 and now have the dreaded black screen,
managed to get into TWRP but pc not recognising phone?
what can i do, i presumed because phone was on kitkat it automatically had a kitkat baseband....
on further reading infact it does not, cant find any of the basebands to flash it,,
managed to get OTG working
any help
cheers
Click to expand...
Click to collapse
you were on kit kat and flashed a stock based LP rom ? not sure but didnt you have to be on stock LP then flash cloudy.
maybe flash a KDZ theres flasjable ones as zip for LP.
what i done from kitkat is
root/autorec. update twrp 2.8.7.3/bootstacks 5.02. bumped KK. you know you must reboot recovery into recovery again from recovery to take effect. during update of twrp and bootsacks then flash LP KDZ stock. then just wipe and flash cloudy.
Cheers managed to flash cloudy g2.2 over it,
Gps is terrible though
Prerequisites: D802, 32 GB, Stock 4.4.2. I believe "Int" version (original motherboard was replaced)
I tried to upgrade stock 4.4.2 with CM13 and failed with the brick result (LG logo for a couple of seconds and the black screen then).
Now the recovery mode is available (TWRP 3.0.2 bump blastagator) but there is no android image loaded except CM 13.0 snapshot 20160418 which causes the brick state.
The questions are following:
What was wrong?
What proper android image can be used to unbrick?
How to load image on the phone?
Since I found Mount->USB-OTG checkbox in the TWRP, then I hope the OTG cable can be used to load image from USB flash drive. Unfortunately I can check it now.
Will be appreciate for the help.
KK bootloader, that's the reason. If you want to have stock bootstack you need to update to 5.0.2 stock, root and then flash TWRP and CM13. Everything'll work fine.
edi194 said:
KK bootloader, that's the reason. If you want to have stock bootstack you need to update to 5.0.2 stock, root and then flash TWRP and CM13. Everything'll work fine.
Click to expand...
Click to collapse
Thanks edi.
Do I need to replace TWRP bootloader with another one (I guess stock) and then update to 5.0.2 or I can start updating 5.0.2 with TWRP?
If you want to stay with stock bootstack:
You need to flash 5.0.2 KDZ file with download mode.
If you want to do it fast:
You need to flash hybrid bootstack.
Thanks a lot.
Fixed.