I attempted flashing a ZVA zip earlier that uses `qcom.install_radio`. Unfortunately, this somehow causes my LS980 to loop in fastboot mode. I've seen a few other people talking about this happening to them as well, so decided I would share this.
Thanks to http://direct.xda-developers.com/showthread.php?t=2451426, I was able to get the original *.img files and drop them in with fastboot.
You'll need to go to http://downloads.codefi.re/autoprime/LG/LG_G2 and download the partitions that you need. After that is done, run the following (replacing with your file names along the way):
Code:
fastboot flash aboot aboot.img
fastboot flash boot boot.img
fastboot flash tz tz.img
fastboot flash rpm rpm.img
fastboot flash modem modem.img
fastboot flash laf laf.img
fastboot flash sbl1 sbl1.img
You can continue flashing the rest of the files, but these were the files that were effected by the zip I used and sufficed for getting it back online.
After that's done, you need to flash the *.img file for the recovery that you want. For instance, mine would be:
Code:
fastboot flash recovery twrp.img
You'll need to turn the phone completely off, then reboot it while holding power and volume down. This will get you into your recovery and allow you to recover from a backup, or whatever you'd like to do at that point.
Related
I have a rooted Verizon LG G2 and have been trying to install a recovery mod. I somehow got rid of the stock recovery, but couldn't setup a new one. Now my phone is stuck on the fastboot screen. I've been able to get it to the stock recovery screen, but when it starts to wipe the drive, it just takes me back to the fastboot screen. I'm very new to this and haven't been able to figure this out through any other threads. I'm using Ubuntu. Any help would be greatly appreciated!
joshuascan said:
I have a rooted Verizon LG G2 and have been trying to install a recovery mod. I somehow got rid of the stock recovery, but couldn't setup a new one. Now my phone is stuck on the fastboot screen. I've been able to get it to the stock recovery screen, but when it starts to wipe the drive, it just takes me back to the fastboot screen. I'm very new to this and haven't been able to figure this out through any other threads. I'm using Ubuntu. Any help would be greatly appreciated!
Click to expand...
Click to collapse
I'm in the same boat. I tried to install TWRP using the Autorec but accidentally used the one for the LS980, and now I'm stuck at the fastboot screen. Did you ever solve this?
eye_rule said:
I'm in the same boat. I tried to install TWRP using the Autorec but accidentally used the one for the LS980, and now I'm stuck at the fastboot screen. Did you ever solve this?
Click to expand...
Click to collapse
Code:
1. download fastboot
2. download laf.img boot.img aboot.img for your variant
(or download your kdz, download kdz/tot extractor and extract partitions --and rename them from boot_45465757.bin to boot.img)
* boot_45465757.bin is just an example.
3. fastboot flash aboot aboot.img
4. fastboot flash boot boot.img
5. fastboot flash laf laf.img
-> download mode should be back
sorry for jumping back on this thread but im having the same problem...phone boots up to just fastboot....ive been reading for 4 days now trying to find any possible way to fix my phone...it really sucks not having a phone...so now im able to connect the phone to the laptop via fastboot but im looking for this laf.img, boot.img etc files. where can i find them?
Also vs980?
robledjl said:
sorry for jumping back on this thread but im having the same problem...phone boots up to just fastboot....ive been reading for 4 days now trying to find any possible way to fix my phone...it really sucks not having a phone...so now im able to connect the phone to the laptop via fastboot but im looking for this laf.img, boot.img etc files. where can i find them?
Click to expand...
Click to collapse
This can be fixed .
1. You Will need to Download the Stock KDZ/TOT file for your phone , find the right KDZ or TOT file from here .
2. Now you would have to extract the KDZ/TOT file that you downloaded above using WindowsLGFirmwareExtract-1.2.1.0-Release.zip , this is available in the guide here.
3. Extract all the files fro the KDZ/TOT .
4. Now flash the extracted files , based on the fastboot method , which is described here.
Code:
fastboot flash aboot aboot.img
fastboot flash boot boot.img
fastboot flash dbi dbi.img
fastboot flash laf laf.img
fastboot flash misc misc.img
fastboot flash modem modem.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm.img
fastboot flash sbl1 sbl1.img
fastboot flash tz tz.img
Let me know if you need more help.
Why so many partitions. Be sure to flash same version as your current android is at least.
I have tried to install twrp recovery via fastboot and I get this error
1.C:\fastboot>fastboot flash recovery recovery.img
2.target reported max download size of 1526722560 bytes
3.error: cannot load 'recovery.img': No error
All other commands work to erase, reboot etc, but cannot flash recovery twrp on to my LGG2 D803 , any help will be appreciated.
Got it to work but flashed 3 different twrp and cm mod img and will not boot into recovery
Well if you ever Brick your phone to the point that the only thing that works is Fastboot, I was able to recover my phone using this procedure, It was a lifesaver. The phone works perfectly now, follow the Youtube instructions, I also typed the procedure out too. Always type fastboot flash then the command
https://www.youtube.com/watch?v=hQVTc2m6U-I
Use above link to completely redoo your LGG2 from fastboot, re loading all the partitions.
fastboot flash boot boot.img
aboot aboot.img
recovery recovery.img
laf laf.img
dbi dbi.img
modem modem.img
persist persist.img
PrimaryGPT PrimaryGPT.img
rpm rpm.img
stli stli.img
tz tz.img
fastboot flash reboot
after flashing all the partitions it should load so you can flash the tot/kdz file via flash utility 2014 in the command mode, by holding the volume up mode and plugging in the usb into the phone. then reload the original firmware and install twrp and if you want wipe it and reload one of the custom roms.
Well if you ever Brick your phone to the point that the only thing that works is Fastboot, I was able to recover my phone using this procedure, It was a lifesaver. The phone works perfectly now, follow the Youtube instructions, I also typed the procedure out too. Always type fastboot flash then the command
https://www.youtube.com/watch?v=hQVTc2m6U-I
Use above link to completely redoo your LGG2 from fastboot, re loading all the partitions.
fastboot flash boot boot.img
aboot aboot.img
recovery recovery.img
laf laf.img
dbi dbi.img
modem modem.img
persist persist.img
PrimaryGPT PrimaryGPT.img
rpm rpm.img
stli stli.img
tz tz.img
fastboot flash reboot
after flashing all the partitions it should load so you can flash the tot/kdz file via flash utility 2014, in the command mode, by holding the volume up button and plugging in the usb into the phone. then reload the original firmware and install twrp and if you want wipe it and reload one of the custom roms.
This method is for Kitkat, and lollipop.
Now i'm going to introduce how to unbrick your G3 Cat.6.
First, you need to download these files.
1. TOT,KDZ files
http://forum.xda-developers.com/lg-g3/general/lg-g3-cat-6-f460-kdz-tot-download-t3470250
2. Windows LG Firmware Extract
http://forum.xda-developers.com/showthread.php?t=2600575
3. LG United Driver
https://drive.google.com/file/d/0B2UHjr8om-8QT1RFME9UOHBEaTQ/view?usp=sharing
4. Debrick.img (You should download all)
http://1drv.ms/1LnSioU
5. Win32Diskimager
https://sourceforge.net/projects/win32diskimager/?source=directory
6. LG Flash Tool 2014
https://drive.google.com/file/d/0B1NxfQr9J2JUZnFQbGlaaU11Mmc/view?usp=sharing
7. ADB Fastboot
https://drive.google.com/file/d/0B1NxfQr9J2JUWExQdnk2RVlENXc/view?usp=sharing
Second, Put debrick.img files into Micro SD Card!
Extract the Zip file, and you can see
5 Debrick files.
and open the 'Win32DiskImager' Program.
and select the debrick file. and write.
After, the progress finished,
insert Micro SD card into G3 Cat.6
And Turn On your phone.
(Or Press Power + down button)
If you can see ADB Download mode, you can go to next method!
And If you can't see nothing on screen,
Try flash another file.
(like debrick 220-> debrick200 -> debrick180->...)
But if you can't see nothing (if you flashed these 5 files)
then you can't unbrick your G3 Right now...
Third, Extract your KDZ Files!
Open 'WindowsLGFirmwareExtract' Program,
and extract your KDZ files.
then you can see .dz file.
now go back to program,
Select Dz file, and Extract DZ files.
(Make sure you should check all boxes!)
And you can see .bin files.
Finished!
Fourth, Flash .bin Files into G3 Cat.6 (with using ADB)
Move ADB Fastboot files and Extracted Files into one file...
Like this.
http://imgur.com/a/8rRzV
Click SHIFT+M2 (Right mouse)
And click 'Open Command Window Here' on folder.
Then you can see the CMD.
Now Connect USB to your Phone.
and type 'adb devices'
after you can see demon started sucessfully, move on to next method.
NOW you need to replace your .bin files.
First, erase files in your phone,
and Flash all .bin files.
After you typed 'adb devices'
Type these all commands
fastboot erase aboot
fastboot erase BackupGPT
fastboot erase boot
fastboot erase factory
fastboot erase laf
fastboot erase misc
fastboot erase modem
fastboot erase persist
fastboot erase PrimaryGPT
fastboot erase recovery
fastboot erase rpm
fastboot erase sbl1
fastboot erase sdi
fastboot erase sec
fastboot erase tz
If you finished, type these commands
fastboot flash aboot aboot.bin
fastboot flash BackupGPT BackupGPT.bin
fastboot flash boot boot.bin
fastboot flash factory factory.bin
fastboot flash laf laf.bin
fastboot flash misc misc.bin
fastboot flash modem modem.bin
fastboot flash persist persist.bin
fastboot flash PrimaryGPT PrimaryGPT.bin
fastboot flash recovery recovery.bin
fastboot flash rpm rpm.bin
fastboot flash sbl1 sbl1.bin
fastboot flash sdi sdi.bin
fastboot flash sec sec.bin
fastboot flash tz tz.bin
IF YOU FINISHED TYPE/FLASH THESE FILES,
REBOOT YOUR PHONE (must eject the micro sd card)
AND IF YOU CAN SEE LG LOGO,
YOUR PHONE CAN ALIVE
Now you must do this last method.
Final, Flash KDZ File.
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
If you sucessed to flash KDZ file...
now you can see your phone is alive...!
congratulation!
Q&A
Q. Why theres no debrick files for marshmallow?
A. I'm sorry, i only found debrick files for Kitkat,Lollipop.
(Now I'm Trying to find debrick for MM)
Q. Why i can't see my phone in ADB?
A. If you can't see, try to install LG United Driver.
Q. Your Grammar is SO BAD.
A. Sorry. I'm from South Korea... and that's why I CAN'T SPEAK ENGLISH WELL (Somebody Help Me..)
Q. Your explanation is SO BAD.
A. I'm sorry. I can mistake, and it's hard to write this method.
If you find Something WRONG, please Help me!
I'll Appreciate to your help!
Thanks For reading!
Asking...Hoping...
Vega_Kangmin said:
This method is for Kitkat, and lollipop.
Now i'm going to introduce how to unbrick your G3 Cat.6.
First, you need to download these files.
1. TOT,KDZ files
http://forum.xda-developers.com/lg-g3/general/lg-g3-cat-6-f460-kdz-tot-download-t3470250
2. Windows LG Firmware Extract
http://forum.xda-developers.com/showthread.php?t=2600575
3. LG United Driver
https://drive.google.com/file/d/0B2UHjr8om-8QT1RFME9UOHBEaTQ/view?usp=sharing
4. Debrick.img (You should download all)
http://1drv.ms/1LnSioU
5. Win32Diskimager
https://sourceforge.net/projects/win32diskimager/?source=directory
6. LG Flash Tool 2014
https://drive.google.com/file/d/0B1NxfQr9J2JUZnFQbGlaaU11Mmc/view?usp=sharing
7. ADB Fastboot
https://drive.google.com/file/d/0B1NxfQr9J2JUWExQdnk2RVlENXc/view?usp=sharing
Second, Put debrick.img files into Micro SD Card!
Extract the Zip file, and you can see
5 Debrick files.
and open the 'Win32DiskImager' Program.
and select the debrick file. and write.
After, the progress finished,
insert Micro SD card into G3 Cat.6
And Turn On your phone.
(Or Press Power + down button)
If you can see ADB Download mode, you can go to next method!
And If you can't see nothing on screen,
Try flash another file.
(like debrick 220-> debrick200 -> debrick180->...)
But if you can't see nothing (if you flashed these 5 files)
then you can't unbrick your G3 Right now...
Third, Extract your KDZ Files!
Open 'WindowsLGFirmwareExtract' Program,
and extract your KDZ files.
then you can see .dz file.
now go back to program,
Select Dz file, and Extract DZ files.
(Make sure you should check all boxes!)
And you can see .bin files.
Finished!
Fourth, Flash .bin Files into G3 Cat.6 (with using ADB)
Move ADB Fastboot files and Extracted Files into one file...
Like this.
http://imgur.com/a/8rRzV
Click SHIFT+M2 (Right mouse)
And click 'Open Command Window Here' on folder.
Then you can see the CMD.
Now Connect USB to your Phone.
and type 'adb devices'
after you can see demon started sucessfully, move on to next method.
NOW you need to replace your .bin files.
First, erase files in your phone,
and Flash all .bin files.
After you typed 'adb devices'
Type these all commands
fastboot erase aboot
fastboot erase BackupGPT
fastboot erase boot
fastboot erase factory
fastboot erase laf
fastboot erase misc
fastboot erase modem
fastboot erase persist
fastboot erase PrimaryGPT
fastboot erase recovery
fastboot erase rpm
fastboot erase sbl1
fastboot erase sdi
fastboot erase sec
fastboot erase tz
If you finished, type these commands
fastboot flash aboot aboot.bin
fastboot flash BackupGPT BackupGPT.bin
fastboot flash boot boot.bin
fastboot flash factory factory.bin
fastboot flash laf laf.bin
fastboot flash misc misc.bin
fastboot flash modem modem.bin
fastboot flash persist persist.bin
fastboot flash PrimaryGPT PrimaryGPT.bin
fastboot flash recovery recovery.bin
fastboot flash rpm rpm.bin
fastboot flash sbl1 sbl1.bin
fastboot flash sdi sdi.bin
fastboot flash sec sec.bin
fastboot flash tz tz.bin
IF YOU FINISHED TYPE/FLASH THESE FILES,
REBOOT YOUR PHONE (must eject the micro sd card)
AND IF YOU CAN SEE LG LOGO,
YOUR PHONE CAN ALIVE
Now you must do this last method.
Final, Flash KDZ File.
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
If you sucessed to flash KDZ file...
now you can see your phone is alive...!
congratulation!
Q&A
Q. Why theres no debrick files for marshmallow?
A. I'm sorry, i only found debrick files for Kitkat,Lollipop.
(Now I'm Trying to find debrick for MM)
Q. Why i can't see my phone in ADB?
A. If you can't see, try to install LG United Driver.
Q. Your Grammar is SO BAD.
A. Sorry. I'm from South Korea... and that's why I CAN'T SPEAK ENGLISH WELL (Somebody Help Me..)
Q. Your explanation is SO BAD.
A. I'm sorry. I can mistake, and it's hard to write this method.
If you find Something WRONG, please Help me!
I'll Appreciate to your help!
Thanks For reading!
Click to expand...
Click to collapse
Sir vega, have you found debrick image for Marshmallow.
t0m0y0143 said:
Sir vega, have you found debrick image for Marshmallow.
Click to expand...
Click to collapse
No, not yet.
I'm still find that files.
But it's gonna hard to find.
Or Someone (or me) need to make Derrick files, but that's very hard.
Thanks
Vega_Kangmin said:
No, not yet.
I'm still find that files.
But it's gonna hard to find.
Or Someone (or me) need to make Derrick files, but that's very hard.
Click to expand...
Click to collapse
Okay. If ever you find something please PM me? Thank You Very Much.
Asking
Vega_Kangmin said:
No, not yet.
I'm still find that files.
But it's gonna hard to find.
Or Someone (or me) need to make Derrick files, but that's very hard.
Click to expand...
Click to collapse
Can you please search it in here Sir Vega Kangmin? I cannot enter it as I cannot understand korean.
bbs.sonyue.com
Hi, thanks for sharing this info
t0m0y0143 said:
Can you please search it in here Sir Vega Kangmin? I cannot enter it as I cannot understand korean.
bbs.sonyue.com
Click to expand...
Click to collapse
that site is from China.. not korea...
Vega_Kangmin said:
that site is from China.. not korea...
Click to expand...
Click to collapse
Oh sorry, I did not know Forgive my ignorance.
Does anyone have Nougat debrick images? LOL
BTW, im guessing that with the correct kdz and tot files, this would also work in the d855 right?
And finally, my phone bricked when i was updating the firmware to stock, the furthest it got was 38% with the lg flash tool, so will the phone need 4.4.2 or 7.1 debrick img?
BoardDiag2014
someone developed new boarddiag which can detect our broken LG G3 Cat6 F460 S K L
but price is high for me he asks 60 dollar for the new BoardDiag
http://www.lgbbs.com.cn/forum.php?mod=viewthread&tid=1107
i hope someone can put it with low price we can pay we are just a single users not a repairing shops
I have successfully repaired my F460S with debirck img MM! Although my phone run lollipop before
Thanks
Got this working with Lineage ok but decided to go back to stock. I downloaded the stock recovery rom from NV and set everything up. Inside the recovery bundle is a bat file. Usually I would flash all files manually but this time I used the bat file. It manged the first 3 or 4 commands then came up with error. The box is now stuck in a boot loop and I am unable to access over adb.
Can anyone please suggest a way around this.
Thanks
Here is the bat file
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash dtb mdarcy.dtb.img
fastboot flash vbmeta vbmeta.img
fastboot oem lock (optional step: required for certain functionality)
fastboot reboot
EDIT:
Eventually managed to flash lineage zip again. Used USB keyboard to access recovery
may i ask, what kind of keyboard did u use?
thanks in advance
I've MSM'ed about 8 times today. Every single time I attempt to flash recovery, no matter which recovery, it overwrites the system and upon rebooting to recovery through fastboot, it permanently stays in fastboot. I can MSM out of it. I've tried conversion MSM, temporarily booting recovery, flashing firmwares, resetting, wiping. I cannot fix this. I have spent over 11 hours trying to troubleshoot this. Google comes up with useless results. This is the first time I've not been able to recover from a situation with this phone. Please, if you have any ideas, shoot. The model is kb2007.
Reserved.
try a fastboot boot twrp ( https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases ) and try factory resetting it then see if you can switch your partition from a to be or b to a then try msm flashing ( https://androidfilehost.com/?fid=17248734326145733797 )
Nimiskiv said:
try a fastboot boot twrp ( https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases ) and try factory resetting it then see if you can switch your partition from a to be or b to a then try msm flashing ( https://androidfilehost.com/?fid=17248734326145733797 )
Click to expand...
Click to collapse
I can't even boot TWRP, it just shows the Oneplus logo and the"fastboot mode" thing forever. It's been 10 minutes now.
If you've used MSM then you're on OOS 11.
I assume the phone boots properly after MSM.
On OOS 11 you can only use TWRP 11 from https://dl.twrp.me/kebab/
And you can only use TWRP 12 on OOS 12 from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/
PS: and you should have posted this in the 8T Q&A forum.
BillGoss said:
If you've used MSM then you're on OOS 11.
I assume the phone boots properly after MSM.
On OOS 11 you can only use TWRP 11 from https://dl.twrp.me/kebab/
And you can only use TWRP 12 on OOS 12 from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/
PS: and you should have posted this in the 8T Q&A forum.
Click to expand...
Click to collapse
nope, still cant boot into twrp
Version of OOS?
Version of TWRP?
Does OOS boot cleanly?
What's your phone?
BillGoss said:
Version of OOS?
Version of TWRP?
Does OOS boot cleanly?
What's your phone?
Click to expand...
Click to collapse
OOS is 11.1.0.2.KB09CB
I've tried TWRP 3.6.1, 3.6.0, and 3.6.2
OOS does boot cleanly.
Phone is KB2007.
The bootloader is unlocked.
I've truly never had this problem before.
You'll probably have to upgrade to the latest version of OOS 11 (or 12) before TWRP will boot.
I have an idea, if you are in fast boot mode then you can flash everything manually. ( https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/ ) there's only international version (kb2005) it can work with that. Just use payload dumper to extract all the .img by dragging and dropping the payload.bin unto payload dumper after extracting them all into a folder then use the commands to flash them all with adb. Then reboot to recovery, factory reset, and MSM tool back to TMO.
do these commands one by one replacing the .img with the location of the .img. actually, just drag and drop the file after. ( ex: fastboot flash logo C:\Users\???\Desktop\???.img )
Just an extra recommendation to wipe the device
( Fastboot -w )BEFORE THE OTHER COMMANDS but you don't need to if it works without wiping.
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash recovery recovery.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
I'm way too inexperienced with this but if anything goes wrong you can MSM tool back to fastboot.
honest recommendation, just use TMO to International MSM tool after. unless you want to keep it TMO (kb2007)
Nimiskiv said:
I have an idea, if you are in fast boot mode then you can flash everything manually. ( https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/ ) there's only international version so we got to work with that. Just use payload dumper to extract all the .img by dragging and dropping the payload.bin then use the .bat to flash them all onto the phone. Then reboot to recovery, factory reset and MSM tool it back to tmo. do these commands one by one replacing the .img with the location of the .img. actually just drag and drop the file after. ex: fastboot flash app (file)
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash recovery recovery.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
Ex: fastboot flash app ( c:/????/desktop/payload_dumper/extracted/app.img ) idk
Just an extra recommended to wipe the device
Fastboot -w but you don't need to if it works without.
I'm way to inexperienced with this but if anything goes wrong you can MSM tool back to fastboot.
Click to expand...
Click to collapse
MirageSteezyBoi said:
I've MSM'ed about 8 times today. Every single time I attempt to flash recovery, no matter which recovery, it overwrites the system and upon rebooting to recovery through fastboot, it permanently stays in fastboot. I can MSM out of it. I've tried conversion MSM, temporarily booting recovery, flashing firmwares, resetting, wiping. I cannot fix this. I have spent over 11 hours trying to troubleshoot this. Google comes up with useless results. This is the first time I've not been able to recover from a situation with this phone. Please, if you have any ideas, shoot. The model is kb2007.
Click to expand...
Click to collapse
Sorry I'm very bad at this. I was thinking you didn't even boot properly.... just update to the latest using oxygen updater or the systems bultin update... Im a moron and ill be leaving that up there.