So, Lately I've fiddling with my quite old 'spin-off' awkward phone. It's a "GT-i9063T" a different 'version' of the i9082 it's exactly the same, all the same specifications and physical size, screen resolution, everything. BUT (I'm not sure of the next statement since I had only one reference) -- The processor's name are different, even tough both have EXACTLY the same specifications.
And also, most importantly, the main difference between the two, is a useless "TV" function. It can capture (sorry not sure about that verb, I'm not American) average, analogical TV signal, and I never used it.
Since it's SO equal to i9082, i was like, FU*K it, let's use i9082 stuff! And, NOTHING, happened.
My first attempt was to normally odin-mode boot, and then change/flash recovery mode so i could install the ROM through there. The thing is, the TWRP (only recovery that I found who supported i9082) did nothing. I install it normally, no errors pops out, (it's almost instantly) odin even say it were successful, but when I reboot and actually try to enter recovery mode, the stock recovery mode is still there. My guess is: I got this spin-off of mine through a plan (those 6 months contracts and they give you a free cellphone) with Tim (the huge Italian communication conglomerate) And I'm guessing it's bootloader might be locked.
Then what i tried was: Flasihfy, the app crashes when i click to choose archive, then i tried to 'bootloader' mode and i couldn't find how to boot to it (no key combo neither ADB worked) and I think it's not a thing for Samsung devices.
But I know that, the fact that, my phone is a different model and i9082 stuff won't work on it just might be the answer.
So, help on getting a custom recovery on? Anyone? ;-;
PROGRESS! Actually, a verdict I think, I found out that, stock rom's replace the recovery on-boot, i haven't found ANY GUIDE mention that detail. So, knowing that, I tried again the TWRP for i9082, it bricked the recovery. The boot froze when I tried to access recovery mode and the red exclamation of death appeared, I even tried to let it load for a few minutes, try again, but NOUP, nothing. It did brick the recovery mode, then I let it boot normally, it did, replaced, my custom recovery and Voilà. Back to square one. BUT NO! I MUST CONTINUE I CAN'T LET MY DREAMS BE DREAMS, YESTERDAY I SAID TOMO... So I've started looking to see if I could find a recovery specific to i9063T, and I did, found one on a YT video, I flashed it booted into it and it worked!! So i've started the process, by trying to wipe/factory reset, then i found out the partition table of the CWR i found was messed up and it couldn't wipe the data. SO i reboot, let the CWR replace the stock recovery (it asked permission) and booted normally, restarted the phone and tried to boot onto it again, only to find out it had been replaced anyway ):
Veredict: i9082 stuff won't work because the partitions are different named/organized.
Related
So just to state the lead up to the unbootable phone.
Condensed version:
Flashed to Bio360 (ONLY working rom that was running for me thus far)
After a week of use, phone would boot for 5 seconds until screen turned pixelated
reflashed but did nothing
flashed to ICS using download mode again and worked but with limited function as when I first flashed ICS before Bio360
flashed using CWM6 back to Bio360 but still same problem
now will not boot into CWM6 and gets the pixelated screen either way
WILL go into download mode so I tried a few more ROMs to hopefully write over whatever issue there is with the software but nothing
reflashed using ODIN the CWM to 5 and 6 but same problem (will not load to CWM at all now
tried a few more times in the precise order as the first time I ever got the phone working with Bio360 (STILL a messaged up screen)
More detailed account of things:
I originally tried updating to the ICS upgrade a few weeks ago but got stuck on the boot screen and other issues. I finally flashed the CWM6 and updated the rom via that to the Bio360 rom. I finally had a working phone again after countless hours of trying to get it working. I locked my screen after timeout to a pin number but actually found it was a pain in the behind so tried to switch back. However I used the 'settings' feature which was present on the home screen after boot that comes with the Bio360. Then I deleted the icon an could no longer find the one that I was originally using, but found the other newer icon in the applications. So I took the lock feature off. Though it did nothing and the phone still required the pin. I tried changing it etc etc etc and nothing worked.
So, I flashed the Bio360 rom again and tried to start fresh, only to find that most of the settings that I originally were using before the re-flash were still present. This lead me to believe the settings are not completely wiped and flashing through CWM6 does not do a pristine clean update. Then I read that I should have to clear any and all settings by factory reset, clear cache, partition or whatever other clear functions I found within CWM6. So I did that and everything was back in good order again.
That is until I woke up 3 days ago and found my phone 'bricked'. Not literally as I am told it is almost impossible to brick one of these. Upon rebooting the phone I found that it was booting to the Samsung logo and after about 5 seconds, the screen becomes pixelated with red and green colours, sometimes lines all over. The longer I leave it, the more the screen becomes a wash out.
So I tried flashing the rom again using CWM6 hoping this would fix, but the same thing occured. So I tried to use CWM5 hoping that would fix it but still the same. I tried flashing back to gingerbread, then ICS, then Bio360 as I originally did to get the phone working with Bio360 but the only thing that I can do now is boot into download mode. Anything else causes the screen to become pixelated and wil not boot past the messed up screen no matter how long I leave it.
I searched for other threads but only found threads based on a single large pixel or a physically damaged screen. However, the screen is still functional as when I boot to download mode or just before the screen becomes pixelated, everything looks great. Plus there was one time when I flashed to ICS I got into the blank screen with limited functional capacity as when I first flashed ICS and the pixelated screen disappeared. So this leads me to believe this is a software issue.
I believe that there is an issue with files being left behind that are corrupted or something similar but I cannot even boot to CWM in order to clear everything possible.
ANY IDEAS? I have explored every option that my limited understanding of software could.
picture of what it looks like
This is a crappy picture from my old phone of something like what it looks like.
https://plus.google.com/photos/111944628817208100010/albums/5793637254528885841
This is a capture after it was turned off even and I plugged it into my computer, displaying the battery charging animation, though turned pixelated after a few seconds.
My gut says hardware damage, like something inside the Tegra itself is fried, ESPECIALLY since it's happening sometimes while still in the bootloader (charging animation).
Try Kies emergency recovery. If it flashes successfully but still won't boot, or glitches out like this during the flash, you'll have to start the RMA process.
I am unsure if it would be a hardware issue though since the screen is fine during the 'download mode' and did boot into the stock recovery after a flash a while back, then flipped back to not getting past the Samsung logo and pixelating again.
Would I be able to load the download mode portion of the phone if it was a hardware issue?
I ask because my gut says the opposite.
flashing CWM 6 causes my phone to be unbootable and pixelated screen
So, I have tried to update the phone into whatever other ROM that I can possibly get working only to find out that after flashing a ROM that flashes the original recovery program included with Android, voilà! The phone works again and boots into the black screen with pull down menu. Back to square one for me.
Why would CWM6 be causing such a thing?
EaglesIII said:
So, I have tried to update the phone into whatever other ROM that I can possibly get working only to find out that after flashing a ROM that flashes the original recovery program included with Android, voilà! The phone works again and boots into the black screen with pull down menu. Back to square one for me.
Why would CWM6 be causing such a thing?
Click to expand...
Click to collapse
I'm on CWMR6 since the begining without any issue. Did you flash the touch or the non touch version ? Also whcih odin version are you using, maybe that makes a difference. The 1.82 and 1.85 are tested to be working fine with both cwmr 5 and 6. Also by reading your thread is seems you've never been able to flash through ICS one click, if possible try doing that.
ninthsense said:
I'm on CWMR6 since the begining without any issue. Did you flash the touch or the non touch version ? Also whcih odin version are you using, maybe that makes a difference. The 1.82 and 1.85 are tested to be working fine with both cwmr 5 and 6. Also by reading your thread is seems you've never been able to flash through ICS one click, if possible try doing that.
Click to expand...
Click to collapse
I have been using the cwm5/6 touch and non touch. I have tried flashing them both. I have been using the most suggested version of ODIN 1.85 to flash. I do not think that it would make a difference as to which ODIN version I use, but then again I am quite ignorant on software.
The first thing that I did was tried the flashing using the one click method. I could only get to a black screen with the pull down menu containing the turn wifi on/off etc. I read that the problem may be permissions but I have tried that using the CWM when it worked and I was still stuck at the black screen with pull down menu. Without CWM I have no way of doing anything really since everything is in zip form and without CWM you cant use the zips.
EaglesIII said:
I have been using the cwm5/6 touch and non touch. I have tried flashing them both. I have been using the most suggested version of ODIN 1.85 to flash. I do not think that it would make a difference as to which ODIN version I use, but then again I am quite ignorant on software.
The first thing that I did was tried the flashing using the one click method. I could only get to a black screen with the pull down menu containing the turn wifi on/off etc. I read that the problem may be permissions but I have tried that using the CWM when it worked and I was still stuck at the black screen with pull down menu. Without CWM I have no way of doing anything really since everything is in zip form and without CWM you cant use the zips.
Click to expand...
Click to collapse
Well then probably a logcat output to a developer would help understand the problem you're facing. Find some knowledgeable developer who can help you read the logcat and find the issue. Or post it here and maybe somebody would give you a clue.
EaglesIII said:
So just to state the lead up to the unbootable phone.
Condensed version:
Flashed to Bio360 (ONLY working rom that was running for me thus far)
After a week of use, phone would boot for 5 seconds until screen turned pixelated
reflashed but did nothing
flashed to ICS using download mode again and worked but with limited function as when I first flashed ICS before Bio360
flashed using CWM6 back to Bio360 but still same problem
now will not boot into CWM6 and gets the pixelated screen either way
WILL go into download mode so I tried a few more ROMs to hopefully write over whatever issue there is with the software but nothing
reflashed using ODIN the CWM to 5 and 6 but same problem (will not load to CWM at all now
tried a few more times in the precise order as the first time I ever got the phone working with Bio360 (STILL a messaged up screen)
More detailed account of things:
I originally tried updating to the ICS upgrade a few weeks ago but got stuck on the boot screen and other issues. I finally flashed the CWM6 and updated the rom via that to the Bio360 rom. I finally had a working phone again after countless hours of trying to get it working. I locked my screen after timeout to a pin number but actually found it was a pain in the behind so tried to switch back. However I used the 'settings' feature which was present on the home screen after boot that comes with the Bio360. Then I deleted the icon an could no longer find the one that I was originally using, but found the other newer icon in the applications. So I took the lock feature off. Though it did nothing and the phone still required the pin. I tried changing it etc etc etc and nothing worked.
So, I flashed the Bio360 rom again and tried to start fresh, only to find that most of the settings that I originally were using before the re-flash were still present. This lead me to believe the settings are not completely wiped and flashing through CWM6 does not do a pristine clean update. Then I read that I should have to clear any and all settings by factory reset, clear cache, partition or whatever other clear functions I found within CWM6. So I did that and everything was back in good order again.
That is until I woke up 3 days ago and found my phone 'bricked'. Not literally as I am told it is almost impossible to brick one of these. Upon rebooting the phone I found that it was booting to the Samsung logo and after about 5 seconds, the screen becomes pixelated with red and green colours, sometimes lines all over. The longer I leave it, the more the screen becomes a wash out.
So I tried flashing the rom again using CWM6 hoping this would fix, but the same thing occured. So I tried to use CWM5 hoping that would fix it but still the same. I tried flashing back to gingerbread, then ICS, then Bio360 as I originally did to get the phone working with Bio360 but the only thing that I can do now is boot into download mode. Anything else causes the screen to become pixelated and wil not boot past the messed up screen no matter how long I leave it.
I searched for other threads but only found threads based on a single large pixel or a physically damaged screen. However, the screen is still functional as when I boot to download mode or just before the screen becomes pixelated, everything looks great. Plus there was one time when I flashed to ICS I got into the blank screen with limited functional capacity as when I first flashed ICS and the pixelated screen disappeared. So this leads me to believe this is a software issue.
I believe that there is an issue with files being left behind that are corrupted or something similar but I cannot even boot to CWM in order to clear everything possible.
ANY IDEAS? I have explored every option that my limited understanding of software could.
Click to expand...
Click to collapse
I have the same problem, i bought mine in ebay, (i live outside USA so i cant get money back) my problem start when i try to install a apk, then, i try to restore with wipe in cwm (sometimes works, sometimes no) and eventually, only download mode work. I dont know what i do, but in one of my trys, ICS 4.04 works everything, but i was network lock,i try to downgrade to Gingerbread and the problem come back, i dont know what to do, i feel like i waste te money.
PD: I have the roger version
EDIT: I just flashed ICS from ATT And works, but i w ould like to root and i cant, every time that i flash CWM, the problem come back
EDIT 2: I use the one click to install ICS from att and works, its seem the problem is when i use a custom rom or the CWM, dont know why, its seems that is not hardware because ICS works perfect, but Every custom rom or CWM, cause the problem
Maybe is there a way torecreate all the internal partition, i dont know, or something like that, to make a clean install, I am starting to regret for buying this phone, maybe the problem is because is from rogers (a security rule maybe?)
Sorry for my english
EaglesIII : your phone has hardware malfunction.
It is basically trash.
*sorry*
Sent from my SGH-I927 using xda app-developers app
ericpeacock79 said:
EaglesIII : your phone has hardware malfunction.
It is basically trash.
*sorry*
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
I dont Know, its happen similar to me, but if i use ICS from ATT, everything works right
---------- Post added at 03:05 AM ---------- Previous post was at 02:45 AM ----------
Ok, i learned something, when a flash the Gingerbread version, there is a error while booting (the first time that boot lik recovery) , the error is can't access to /system/csc/ATT/system/
When i use the ICS from ATT, that doesnt happen, maybe that is the problem? i dont know, maybe someone can tell us what are these files
There is a working solution, http://forum.xda-developers.com/showthread.php?t=1953672 thanks to Rawr0w0,its works when you flash in that order, my phone is rooted and full working in ICS, i hope that helps you
I have an unlocked and rooted e973 running stock 4.1.2 (E97320e). I have somehow managed to flash both TWRP and CWM as a custom recovery, and now cannot access recovery mode at all. I know this because ROM Manger shows both under the "Recovery Already Installed" section. I can boot normally and access download mode with no issues, but if I am trying to get into recovery mode I always get a black screen that shows the LG logo and says "secure booting error! cause : boot certification verify". If I use ROM Manager or GooManager to reboot to recovery I always get a warning pop-up "unfortunately com.lg.hiddenmenu has stopped" before it reboots to that secure booting error screen.
So I'm really not sure how to fix this, I just want to start trying some different ROMs, but need to get the custom recovery sorted out first. Should I just follow this guide for unbricking? How about doing a factory reset (booting with power and volume down)? Will being rooted/unlocked matter for doing a factory reset? Would it even clean up the mess I have made of the recovery? I guess I am just looking for a way to wipe everything completely clean and start fresh since I have all my important stuff backed up. I should note I got this phone unlocked and discovered a "NOT FOR SALE" engraved into the side after peeling all the stickers off.
Thanks in advance for any advice.
edit: I decided I might try fastboot erase recovery, only to discover I cannot access the bootloader or fastboot mode. adb reboot bootloader just reboots the phone like normal and starting in fastboot mode by holding volume down and power just takes me to the factory reset screen. Any ideas?
edit: Tried to use TeenyBin, but LGNPST doesn't detect my device ("no port connected") even when it is properly connected in download mode.
Not to be that guy, but its been stated several times to use FreeGee to install custom recovery. Mainly because even if you do install it correctly som other way, your bootloader would be locked and if you install something then, you get a soft brick (in a good scenario). Make sure you have root and grab FreeGee from the market and let it install.
Also, why would you keep a phone that says "NOT FOR SALE"? I wouldnt touch it with a stick and send it back wherever you got it from.
wargreymon89 said:
Not to be that guy, but its been stated several times to use FreeGee to install custom recovery. Mainly because even if you do install it correctly som other way, your bootloader would be locked and if you install something then, you get a soft brick (in a good scenario). Make sure you have root and grab FreeGee from the market and let it install.
Also, why would you keep a phone that says "NOT FOR SALE"? I wouldnt touch it with a stick and send it back wherever you got it from.
Click to expand...
Click to collapse
I bought it at cost from a guy on Kijiji (Canada's craigslist equivalent) brand new. He claimed he had a bunch of them because his company was going to use them but then last minute they decided to go with blackberry so he had to sell them. I didn't realize it had the not for sale until i was home and peeled all the stickers off, and since it worked fine with my existing SIM I just kept it.
Anyways, I will give freegee a shot and see if that can fix the problem. I have been looking through many different resources and threads and never saw it mentioned to use freegee to install a custom recovery, but I guess it's worth a shot. Thanks!
edit: It worked! I can now finally get into TWRP 2.5.0. Thanks again for the reply!
xerockz said:
I bought it at cost from a guy on Kijiji (Canada's craigslist equivalent) brand new. He claimed he had a bunch of them because his company was going to use them but then last minute they decided to go with blackberry so he had to sell them. I didn't realize it had the not for sale until i was home and peeled all the stickers off, and since it worked fine with my existing SIM I just kept it.
Anyways, I will give freegee a shot and see if that can fix the problem. I have been looking through many different resources and threads and never saw it mentioned to use freegee to install a custom recovery, but I guess it's worth a shot. Thanks!
edit: It worked! I can now finally get into TWRP 2.5.0. Thanks again for the reply!
Click to expand...
Click to collapse
Good thing it worked. Hope you got it for a very good price or I would go nuts on the seller But as long as you are happy with it. We finally have a few roms to try so good luck finding one that fits you.
I have Cyanogenmod 10.1 (stable) installed; the other day it crashed while I was on Instagram, rebooted itself, and wouldn't go past the spinning circle screen. Tried rebooting it, now it won't go past the screen before that, with the blue Cyanogenmod man and the Samsung logo.
I have TWRP 2.5.0.0 installed with it, which I don't know how is possible being that the file systems are incompatible, so unless I used Odin to install CM10.1, I don't know how I did it without installing Clockworkmod Recovery over TWRP.
I've been trying to fix it for a couple days now (I'm kicking myself for not getting around to posting here sooner). When I go into TWRP it asks me for a password (which I've never set, I assume it's asking me because that's all it knows to do when the file system is incompatible), which I click cancel at every time, and when I try to do just about anything (including installing new ROMs or recoveries from within TWRP) it gets errors when trying to mount any partitions on the device, so I can't change anything on the phone at all.
I've tried re-installing TWRP AND Clockworkmod Recovery with Odin, and they succeed, but when the phone tries to reboot, the screen just turns off and nothing happens, and I have to take the battery out to do anything else.
So right now I'm totally screwed unless I can fix this thing. I'd like to not have to drop 200 on a Nexus 4 after only a year or having this phone I bought brand new, especially with the Nexus 5 already coming out later this year...can somebody help me???
EDIT: I should clarify that I can access recovery and download mode
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
FoxTrotz said:
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
Click to expand...
Click to collapse
I should've clarified that I've tried this with a bunch of roms, and it just shows SBA2 in the status box forever. I left it for a full hour before and it never changed.
According to this page http://www.alliance-rom.com/community/wiki/bricked-android/ reformating your external sd card may help. It also links to something I personally have never heard of but apparently this: http://forum.xda-developers.com/showthread.php?p=15330252 can help unbrick any samsung phone that's flashable with odin.
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
mozphoto said:
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
Click to expand...
Click to collapse
After flashing through odin did you format data?If not try it.
Go into recovery and wipe data.
**SOLVED**
Thanks xXFl4sh, I had tried that.
Solved!
Alright where do I start? How about RTFM Some how I had missed the part about flashing a bootloader and a modem after the ROM. Not recalling having to do that before, I skipped right over it. Once the recovery CWM 6.0.3.1 was finally loaded, getting the flashing the ROM, the bootloader and the modem was easy as usual.
The key was having to use Odin to install a recovery in .tar or .tar.md5 format since I could not access a Recovery Mode on the GS3, as well as a rooted stock image (I used root66_ATT_I747UCDLK3.tar.md5 which is a rooted Android 4.1.1 for AT&T) For the recovery, I couldnt' find a .tar or .tar.md5 for ClockWorkMod (did find a utility to convert it, but didn't want to introduce another variable into the mix) so I used one from Team Win Recovery (v2.6.3.0) and with that I loaded the CWM recovery. Once all of that was in place, I proceed to factory reset, clear data, cache, system and then flash the new ROM, bootloader and modem.
In all of this I learned quite a bit about the whole process and how to narrow down possible resolutions. I still see the "Rom may flash stock recovery on boot" message after flashing either a ROM, bootloader or modem, but just backing out without answering Yes or No seems to work. Also (and this may be related, I don't see the option to restart in recovery from shutdown menu). Don't really know what that's all about for now, and honestly don't want to mess around (at least for a while)
I know the steps are general, but I hope this can help some else if they get their devices in a soft brick situation. As for the i747z v3 ROM with 4.3, I really like it, everything works (Wifi,Blutooth,tethering) and the battery seems good as well.
Thanks!
Hello. I've spent about the past 2 hours trying to figure this out. So, how this started was, a while back when I first got the phone, I wanted 4.4, so I rooted my phone, and tried to flashify a recovery like CWM and TWRP. Both of these failed. I tried many times, and no matter what I tried, flashing always failed. But guess what, my stock recovery was erased in the process. I forgot about it until today, where I found the OTA update to 4.4 was released, and attempted to do it. To my dismay, I forgot I had no recovery mode, and instantly got the "boot certification verify" error screen. Now All I can access is download mode, to my knowledge. So I've been trying to fix this, either by installing stock recovery, or another way to install a custom. All to no avail. When I use the lg flash tool for the stock recovery, it fails at "BIN CRC Check". Every.... Single.... Time. Despite downloading multiple replacement files. I would be perfectly content with installing a customer recovery, but the ways I see require the phone to be on, and use the built in recovery mode. At this point, my phone is bricked, and I am looking for any and all ways to either A) boot back up normally without installing a recovery and fix it later, or B) install a recovery, even if it's the hard way.
Update:
I followed this thread:
http://forum.xda-developers.com/show....php?t=2582142
It looked like it was going to work. I am using a Xubuntu virtual machine. I was copying the files over, and every time it finished copying a file, it unmounted and remounted my phone (I don't know if that was suppose to happen, just worth mentioning if it wasn't suppose to). I was super excited to do it. Hard rebooted my phone. And now it's just a blank screen. I have no logo, no error, and no download mode like I had before. Seriously need some help here.
Update#2:
I have the flash tool correctly working. Awesome! But..... I still have no download mode here.... So I can't use the tool....
Update
I followed the thread:
http://forum.xda-developers.com/showthread.php?t=2582142
It looked like it was going to work. I am using a Xubuntu virtual machine. I was copying the files over, and every time it finished copying a file, it unmounted and remounted my phone (I don't know if that was suppose to happen, just worth mentioning if it wasn't suppose to). I was super excited to do it. Hard rebooted my phone. And now it's just a blank screen. I have no logo, no error, and no download mode like I had before. Seriously need some help here.
I'm decently surprised NO ONE has replied here.