First off, I would like to say sorry if this is the wrong section to post this. I'm a total noob
Secondly, I don't have a Vibrant, I have a Samsung Galaxy S 4g. I couldn't find a specific thread for my phone but I was guessing I should post it here because I thought that they were pretty close? The Vibrant being sgh-T959 and S4g is sgh-T959V, so I'm hoping I can get some help here.
I've literally spent about 16 hours or more trying to fix my phone (2 days).
Here's what happened:
I flashed my phone with Heimdall following instructions here at this forum: http://forum.xda-developers.com/showthread.php?t=1358498. At the very bottom of the first post is the download section and I downloaded the 2nd choice which I believe is "Download KJ1 Kernel Stock Rom with Bootloaders". I only flashed my phone because it was having problems.
I went and flashed my phone and it worked! It was working fine until I went to RootExplorer changing permissions on a txt file and my phone froze (I don't think changing permissions on the txt file was the problem). So I reseted my phone by holding the power button down until it boots up and then I got stuck in some kind of boot loop (where the phone keeps rebooting after samsung galaxy logo). So I thought the only way to get passed this is to reflash the phone with the same procedure I did earlier.
I put the phone in download mode and went on with the flashing. For some reason it got stuck and it wouldn't finish. On the Command Prompt, it got stuck at this:
[C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\heimdall-win32\heimda
ll.exe, flash, --pit, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\
Sgs4g.pit, --6, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\zImage
, --7, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\zImage-1, --22,
C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\factoryfs.rfs, --23,
C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\data.rfs, --24, C:\DOC
UME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\cache.rfs, --11, C:\DOCUME~1
\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\modem.bin]
And on the other window (Heimdall's window) it got stuck and shows this:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
KERNEL upload failed!
Ending session...
So what I did was close both windows and tried again. This time my computer couldn't recognize my computer. Then I turned my phone off and tried to go back to "Download Mode" but instead, it showed a "Phone with dotted lines through this yellow triangle and into a computer". So I turned the phone off again and tried and tried and kept trying to put it into download mode but couldn't get it to work. It kept showing the phone, triangle, and computer. Although I did realize that my computer can still recognize my phone at this state.
I tried using ODIN but odin couldn't recognize my phone. Went back on Heimdall and that still recognizes my phone! I was feeling hopeful but whenever I kept trying to reflash my phone, it keeps getting stuck at the same spots that I mentioned above.
Can someone, anyone, please help me with my situation? I'm way to broke to buy a new android. This phone is incredible and I really would want to get it up and running again. Is there a way I can get passed this?
I know this is a lot of time reading this but I would highly appreciate anyone that can help! Please and Thanks you!
Here is the Galaxy 4g threads
http://forum.xda-developers.com/forumdisplay.php?f=1065
Also, (Odin speaking), does this look familiar?
This is for our version of the Vibrant, but you get the idea. You'll need to get the Pit/Tar files from your forum.
http://forum.xda-developers.com/showthread.php?t=1307637
"SOFT" BRICKED WHILE USING ODIN?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are getting a "Phone.. ! ..Computer" image (seen above) when booting phone, yes, you are bricked but it is reversible! Just follow these steps...
Make sure you have ODIN OPEN with admin privileges!
1.) Take off your back cover, remove your sim & mirco sd card.
2.) Remove your battery.
Make sure you have the USB plugged into your PC but NOT your phone!
3.) Hold the volume buttons.
4.) Put the battery in.
5.) Put the USB in.
You don't necessarily need the download mode image to be present. As long as you are getting the COM ID to light up yellow in ODIN, just flash back to stock like normal.
Click to expand...
Click to collapse
Woodrube said:
Here is the Galaxy 4g threads
http://forum.xda-developers.com/forumdisplay.php?f=1065
Also, (Odin speaking), does this look familiar?
This is for our version of the Vibrant, but you get the idea. You'll need to get the Pit/Tar files from your forum.
http://forum.xda-developers.com/showthread.php?t=1307637
Click to expand...
Click to collapse
Thanks for the Galaxy 4g threads! and yeah that does look very familiar its just that I did everything I can to get into download mode but I can't get it to work. Thanks again for the threads!
I remember when I was a noob(no pun) the same thing happened and couldn't get it to do anything for like 4 hours. I think I opened odin took battery out, installed usb to computer, hooked usb to phone, pressed volume up and down simultaneously and installed battery without letting go of the volume buttons (I'm not sure if youll see dl mode on phone),pick your .pit/.tar files and flash away even without the COM showing
On the post above mine I think step 4 and 5 should be reversed
Related
i was fixing my brick vibrant using odin. i loaded up the files called 512.pit, and T959UVJI6, and i started the odin with my download moded vibrant pluged into computer and also with the re-partition checked. i know that i shouldn't have checked re-partition but i didn't know
here is what went so wrong. hysterically, my vibrant was unpluged somehow while the odin was processing something even it said 'DO NOT REMOVE TARGET'.
now i got a new brick vibrant. (look at the picture attached)
computer no longer be able to read my device and the phone won't goto download mode.
(power bottom + voulme up and down is not working, and also taking off battery+SIMcard+SDcard and pressing up/down volume and re-insert batter not working)
help me~
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Go to the sticky it has some detailed info on how to fix,
Basically you will need to go into recovery by using the hold down the volume/on buttons with the battery removed and then plug the usb into the computer with Odin already up, this should get you back into recovery then:
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. While in download mode load the files.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'JFD file
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine!
good luck...............
Been there dude. Just keep trying to get Odin to recognize it, maybe restart your PC. I may have also tried rebooting into Download mode (3 buttons) to get the issue resolved. Just keep at it in Odin.
Try these steps if you havent already:
1. Remove USB from phone, take the battery out and put it back in (to make sure its off)
2. Open Odin and plug USB into PC
3.Hold both Vol buttons while connecting USB to phone
4. Phone should go into download.
If not then you need a JIG
thank you
i finally go into the download mode. i followed all each of you guys' suggestions.
thank you all very much~~~~~~~ good night!
simple solution
Go to this addy: http://forum.xda-developers.com/showthread.php?t=954509
It is Baywolf's AIO Toolbox 2.5 do all the steps I describe below and it will restore it back
To Eclair 2.1.1
First though keep you sim and SD card in, pull the battery, open up the program, connect your USB cable to the phone, then put the battery back in! Baywolfs program will detect it, you'll see a port yellow color appear, you now can do a restore, click the flash to stock button, and click pit, use his drop-down list, its already provided, then hit the PDA button, use the tar file he again provided, now its ready, hit the start button, and It will re-flash it back to Eclair 2.1.1 with 0 defects, its an awesome program, and this was the only program, that got me up and running, ODIN and Heimdall's wouldn't respond, but this one saved my ass! trust me, I was in the same scenario, your in! I now have axura 2.3.1.0 up and back running, and I got into that delimna by trying to downgrade a modem, and ODIN totally hosed me up!
Good Luck
Hey there.
First post. I used Odin 3.1 to flash Froyo 2.2 on my Vibrant that was running Eclair 2.1, and Odin showed a successful completion. The phone then turned off and instead of re-booting, has become totally, utterly unresponsive.
I have tried a number of ways to get it to work, or at least get in to Download or Recovery mode, including the "remove everything, then re-insert battery while holding down volume up/down keys" and any number of key combinations. I've trowled the forum and haven't found a single solution for a completely unresponsive Vibrant. even the USB jig seems to be for those phones that at least show the Vibrant Logo or the "S" at start-up, while mine doesn't do anything.
The only encouraging thing has been posts by people who claim to have lefft their unresponsive Vibrants plugged in for several hours only to have them miraculously revive, but that seems like a long shot to me.
Have I managed to do the impossible and brick an unbrickable phone? I'd really appreciate help as I just got the phone last week and don't want to declare it a dead loss so soon.
Cheers!
Utterly, haha
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thinking.. above was a joke...
What ODIN files did you flash? Link to them?
What version of ODIN, the latest?
When you say nothing... you mean you can't see anything on the phone, regardless of the action?
rofl OMG is that chick half naked hahaha seriously is she in her undies milking a cow WTF! LMFAO!
- so the phone won't turn on huh?...... no power at all?....... how about plug in the cord, do you see the batt charge?
haha utterly.. when you say put in the battery while holding the volume keys, did you put in the battery or plug in the USB??
I had to replace mine. Been good ever since.
Sent from my GT-I9000 using XDA Premium App
Here's the long story. My phone was getting the 'device unrecognized' error in Kies and Kies Mini, so I used Odin 3.0 to flash it, using the "T959UVKA6_REV05_home_low_CL860813.tar.md5" file.
After flashing, my phone wouldgo into recovery mode and the following error.
"E:Cant mount /dev/block/st110
(invalid argument)
E:copy_dbdata_media:cant mount DBDATA:
copy default media content failed."
Next I followed the steps detailed in this post . When I flashed my phone according to the 'Gauranteed Solution', my phone turned off at the end of the flash and has stayed off ever since.
And when I say nothing, I mean nothing. No battery symbol, no sound, no Samsung Vibrant logo, nothing. Just a blank screen.
I tried plugging in the phone and then putting in the battery with the volume keys pressed and I also tried it without plugging in the USB. Either way, nothing happens.
As you can probably guess, I'm a n00b of the first order and I fear I might have killed my phone.
If you do manage to revive your phone back.. You better flash roms via cmw. Not that odin isn't great but cmw never caused any problems(to me).
Make a jig to force download mode then reflash stock os and install rom manager to flash roms. P.m for more Info.
Sent from my SGH-T959 using XDA Premium App
Thats funny, the last post in the link you referenced is someone having the same problem as you........ why would you try to do that? and the .tar is some I9000 file being that the (fix) was in the I9000 forum. Neither of these probably have anything to do with your problem now i just thought it was funny. I mean why wouldn't you just use the T959UVJFD.tar in ODIN?
It seems that the "E:cant mount" error is a fairly common issue and from what i am seeing alot of the people having this issue after using samsung kies are getting replacements fairly easily although it is a last resort for many. I would not think its an issue with your drivers or anything like that, probably just ODIN being weird. Don't give up on ODIN i would assume that it will recognize the phone eventually as most "DEAD" vibrants do after time. I'll keep looking into it for you. Hope you find a fix soon. Good luck!
You can also restart the computer and f8 and turn off driver signing and see if that helps. Once again I don't mind helping on a more personal basis. P.m me.
Sent from my SGH-T959 using XDA Premium App
have you ever actually tried a usb jig ?
http://cgi.ebay.com/ws/eBayISAPI.dl...83134&ssPageName=STRK:MESELX:IT#ht_723wt_1139
So i was using my vibrant running DocMasters ics v5 when suddenly my phone rebooted only to be greeted with this "Encryption Unsuccessful" screen that i've never before seen in my life. Not knowing what to do i clicked on "Reset phone". 1 minute later this "Encryption Unsuccessful" screen appeared again so i went into CWM...factory reset..clear cache...and flashed DocMasters ics v5...again the screen appeared. Finally I decided to start from scratch and entered "Download Mode" and flashed back to stock 2.1...Now my phone goes into a bootloop...and i am unable to enter CWM...dont have access to my internal memory/nor sd card. I've tried everthing I think...but know luck at all. So my point is guys. I officially have the first Soft Bricked Vibrant. Those who said this phone was unbrickable...well i managed to do it...of course unintentionally.
RIP Vibrant: 11/20/2010 to 3/25/2012
Oh here is a screen shot i found of the "Encryption Unsuccessful" screen. I can still enter Download Mode so i guess there maybe hope after all. But i dont know where to start. Any help or advice would be greatly appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is EXACTLY what happened to my phone too! I made a thread about it... no one was able to find a solution... .
I'm pretty sure its completely bricked, I've tried EVERYTHING. Luckily, I can upgrade in about a week...
Try flashing Eugene's froyo that does not brick.
@lolrus101...Yeah i have tried everthing from flashing back to stock 2.1 to executing adb commands to try and unbrick this phone. I think at this point it is impossible to fix unless Samsung gets a hold of it...wich is not an option since it is out of warranty. Anyways there no need to worry anymore since i just bought a Galaxy Nexus (GSM).
@djquick...Is Eugenes Froyo flashable through odin or heimdall? I cant access CWM only download mode. If not well i give up. I'll just wait till my GNEX arrives.
Thanks for replying guys.
Eugenes that does not brick is odin flashable, just search it.
Cool it is odin flashable. I guess i'll give it one more try. Lets see if this thing really is unbrickable.
I just flashed Euguene's Froyo rom and there are some good signs and bad ones. Well the good news is there is no more boot loop at the first boot screen (Vibrant Samsung logo)...The bad news is there is what appears to be another boot loop at a different boot screen (Galaxy S Animation). After the animation the screen turns completely off and the led buttons stay lit. I let it sit for about 10 mins and nothing happened. I followed every step in Eugene's guide inlcuding the adb command "adb reboot".
I'll reflash it and wait a little longer lets see if it works.
If you got past that stupid message, just reflash to a regular stock rom 2.1.
Here's a link to help: http://forum.xda-developers.com/showthread.php?t=848737
Follow the directions to a T. Usually works like a charm everytime
I give up
After flashing Euguene's rom nothing happened. Then I flashed T959UVJFD.tar
stock 2.1 and i get the same results. Well i guess this is it then. This phone is officially "soft-bricked". I think i've tried almost everything now. I can wait till my new Galaxy Nexus arrives. This phone i will not root i don't want to brick it like my vibrant.
Even though i wasn't able to fix my phone i truly appreciate the help guys.
Thank you.
I actually just picked up a T-Mobile Nexus S GT-I9020T also and I rooted it as soon as I took it out of the box
Ha that's one thing i probably won't do this time. The only reason i decided to root my phone in the first place was to get an AOSP android build and to get rid of all that Samsung and Tmobile bloatware. Of course rooting my phone won't be necessary this time since my new Galaxy Nexus GT-i9250 will come preinstalled with the latest google build in ICS. Along with that it will not have any bloatware from any carriers since it is unlocked
OP, I kow you already got your GNex but when you got this error, OP, what ROM were you running? Also what kernel?
Since you are not the only one this happened to, I would like to know the above and see if it correlates to the others that this happened to in the Vibrant section. I'll post the same in their threads too.
See here for possible work-around
I was runing 4.2 with MKD build number, tried to update via ODIN to 4.3.3 with his flash image
http://forum.xda-developers.com/showthread.php?p=47011336
Odin gets me this error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that, i got this message on my phone screen
"firmware upgrade encountered error
please select recovery mode in kies and try again"
I cant get into Download or Recovery mod... or power on the phone!
When i conect it to my pc it reads it like "QHUSB DLOAD"
I instaled the QHUSB DLOAD drivers and the pc recognize it like Qualcom HS-USB QDLoader 9008(COM5)
Odin reads it also (COM5) but i cant reflash it because i cant get into Download mode
H E L P !
ANYONE ? Cmon please.... any ides, tips help ?
AnajaDroid said:
ANYONE ? Cmon please.... any ides, tips help ?
Click to expand...
Click to collapse
If you can't boot it into recovery, it's pretty much bricked. Look around for people offering to JTAG it to recover.
Before I consider helping you, why on earth would you attempt flashing this? Why not instead flash a 4.3 rom? I have to know you were intentionally trying to lock your bootloader before I try to help....it just feels so wrong giving instructions for locking a bootloader
---------- Post added at 06:44 PM ---------- Previous post was at 06:39 PM ----------
k1mu said:
If you can't boot it into recovery, it's pretty much bricked. Look around for people offering to JTAG it to recover.
Click to expand...
Click to collapse
I bet it would still get into download mode since aboot wasnt flashed, well I guess it depends on whether or not the phone even attempts to boot or not though. I've gotten my S4 out of qhusb by keep the charger plugged in and constantly removing and inserting the battery.
Surge1223 said:
I bet it would still get into download mode since aboot wasnt flashed, well I guess it depends on whether or not the phone even attempts to boot or not though. I've gotten my S4 out of qhusb by keep the charger plugged in and constantly removing and inserting the battery.
Click to expand...
Click to collapse
Very likely. It's pretty hard to brick this phone into a state where it can't be recovered.
However, I've seen people do amazing things like flashing GS3 ROMs and wondering why they didn't work. Or less crazy, flashing AT&T ROMs on a VZ phone. People that stupid are why Verizon is so anal about locking down their phones.
I was just trying to update it to 4.3 since OTA didnt work I taught this was stock odin flashable image...
AnajaDroid said:
I was just trying to update it to 4.3 since OTA didnt work I taught this was stock odin flashable image...
Click to expand...
Click to collapse
Stock mean locked boot loader!!
What USB cable did you use and what port on the computer? While it's a bit of a stupid question I had a problem like that when doing an ODIN restore and tried all kinds of fixes including a totally different computer and it turns out the USB cable I was using was crap even though it'd transfer files over fine, ODIN didn't like it.
If you can't get it out of QHUSB DLOAD with button pressing, you can try this tool http://forum.legija.net/showthread....g-galaxy-S4-(i9505-and-similar)-via-USB-Cable.
LemonSlice said:
What USB cable did you use and what port on the computer? While it's a bit of a stupid question I had a problem like that when doing an ODIN restore and tried all kinds of fixes including a totally different computer and it turns out the USB cable I was using was crap even though it'd transfer files over fine, ODIN didn't like it.
If you can't get it out of QHUSB DLOAD with button pressing, you can try this tool http://forum.legija.net/showthread....g-galaxy-S4-(i9505-and-similar)-via-USB-Cable.
Click to expand...
Click to collapse
It was COM3 port, and it was OEM samsung usb cable...
I Tried everything i can but there is no way to get into download/recovery mod...
I had a similar problem the other day, don't worry. Depending on whatever build you were on before you bricked it, download that baseband and odin it on there. It did wonders for me and should work for you.
Solved... The device was hardbricked.... JTAG did the trick, cost me about 35$
Hello,
My LG-D280N is bricked... i think... every time it boots it goes on a purple screen called Demigod crash handler, it also does the same thing when i try to factory reset it
So i had no choice but to flash a new room to hopefully fix it, THANKFULLY it does go to download mode without crashes and it does show up on my device manager as "Android bootloader interface" but even so the flashtool says port(USB or Serial) not found, here is what the phone says
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As i was writing all that, it actually booted to android!!!! but there are infinite " app stopped" messages, it's impossible to go to settings and try to hard reset or rather it's impossible to go anywhere, looks to me like re-flashing a brand new stock rom is the only choice
i should say that i put this phone in my closet two months ago and it was fine! when i tried to use it today it was like that but anyway, is there anything i can do? I really need to fix that phone
Thanks alot, i really appreciate any help
An update... the phone responds to fastboot commands from ADB tools, it doesn't show up on "adb devices" list though
Wonder if there is a way to use to use fastboot commands to flash a kdz file?
More updates... i used a tool to extract everything from the KDZ file and reflashed the following files like this:
fastboot flash boot boot.bin
fastboot flash factory factory_475136.bin
fastboot flash factory recovery.bin
fastboot flash aboot aboot_144384.bin
fastboot flash aboot abootb_150528.bin
Now i could of have done something either right or extremely stupid BUT ever since i did that factory reset mode actually worked! no more demigod crash handlers and i also stopped seeing those small "boot verification errors" in the corner and the phone actually booted and saw the initial welcome screen, so it actually factory reseted! BUT even though it did I STILL saw the sea of "*instert app here* has stopped" which makes it impossible to navigate the phone
But for whatever reason, it's now stuck on the startup logo after a reset, well even if i screwed up badly, download mode still works like before sooo it's not much different, at the very least i got rid of the stupid demigod crash handler
I've been working on that phone for hours now... been researching on google with little to no information about this at all, most solutions involve the flash tool WHICH doesn't work so i had to come up with my own ideas... and to make matters worse nobody here has gave me clues on how to fix it which is why i give these updates, maybe all this information will help you come up with a solution
Another update... i was wondering why it wouldn't be detected by my flashtool... until it hit me... the download mode itself has problems, thankfully fastboot still worked and i was able to reflash it using one of the files i extracted from the KDZ file
After this, my download mode now works correctly, it displays everything right and is now recognized by the flashtool! finally some real freaking progress, working on this thing is such a pain but finally im getting somewhere, but it's not over yet, right now im waiting for the device to reach 40% of charge before i flash the rom, hopefully no errors will occur as it has already been a HUGE pain and time consuming
Final update... i have successfully flashed the stock rom, after a whole day of trial and error i did it, let me summarize
My problem was mostly that the download mode itself needed to be reflashed, for whatever reason it was broken or not properly configured but whatever the case, it needed to be reflashed using fastboot in order to work correctly and be recognized by the LG Flashtool, after i reflashed it, it was fine and the LG Flashtool FINALLY recognized my device, but the LG Flashtool would CRASH whenever i clicked the "Read Phone Information" button, not sure why but i tried 4 times until it finally worked, not sure what happened there but who cares, it worked out, then it finally started flashing until it said "error connecting to the server", took me sometime and research to realize that it's SUPPOSED to do that and that i should ignore the message and NOT close it because if i do the whole flashtool stops, after this i let it sit in the background and do all the flashing, it was fine until 77%, it gave me an error message and said that i should try to reset my device back into download mode, then it retried doing the whole process all over again AND THANKFULLY this time it successfully did it, the phone now boots to Android as normal, the sea of "app stopped" message is also gone thankfully and so that's pretty much it...
My absolute stupid mistakes and problems with this could help other people avoid those same mistakes and problems so i won't delete the post since as i said, it can prove to be useful to others