Should I flash the latest KK image to ensure the modem and bootloader are latest version..
The baseband says: M8974A-AAAANAZM-1.0.190082
I received it with 2.7.0.0 twrp and there were custom rom zips all over.. so I can not tell when it was rooted..
Open to suggestions..
Hey mystique
If you want to start with a clean slate I recommend getting your stock image from here
And use the lg flashtool in the back to stock guide to flash it.
Incidently, since your on twrp 2.7 I assume that you're on the jb boot loader
What was that "phone info tool" to find the bootloader version..
Looks like the device was initially rooted in July 2014..
Assuming that they had kk and such..
Related
Tried to flash a rom using TWRP and now I'm stuck on the Samsung Custom screen??? Seems like a soft brick. Need the phone to function......
Looks like you didn't flash the proper version of TWRP and flashed one for one of the other versions of the S4, 9500 or 9505 which have unlocked bootloaders. A special version of TWRP is made for the SGH-I337 because of its locked bootloader which contains the Loki exploit to allow it to boot.
Download Odin and the Stock Firmware, install USB drivers for phone, drivers are included in Samsung Kies or you can get them seperately
Put phone into Download mode
Restore stock firmware.
Use this to Root your phone and install the proper TWRP in one blow. http://forum.xda-developers.com/showthread.php?t=2297900
Use TWRP to flash any SGH-I337 Rom you want if thats what you were going to do, as long as it has the Loki patch. (Current CM10.1 does).
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 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.
Hi Gurus,
I am dusting off my old AT&T branded S4 (SGH-I337/jflteatt) which still runs KitKat (4.4.2) to Lineage (I think 14.x images are available). The BaseBand version is: I337UCUFNI1. It is out of contract, so no worry about getting any official updates.
The thread here about TWRP for this phone made it look easy to install with the official app from the PlayStore. But after installing TWRP, I get an error 'System software not authorised by AT&T has been found" when I boot either to recovery or to ROM. I am guessing Secure Boot is still actively preventing custom images from booting.
So, how do I bypass this and go about successfully installing Lineage? Will Loki help me do it? Once I install TWRP, is it just a matter of installing official Lineage, or should I make other considerations?
Thanks in advance.
You have to be on the jelly bean MDL bootloader in order to install any custom recovery or ROM. Once you have upgraded to kit kat, you cannot go back. Only the MDL bootloader can take advantage of loki, all other bootloaders (including yours) can't as the exploit was patched in the MK3 firmware I think.