Database Info

[Q] PLEASE HELP - Nexus 5 stuck on Google logo; accidentally deleted OS using TWRP

Hello everyone,
I am stuck in a very frustrating dilemma with my Nexus 5 and need help very badly. I somehow managed to delete my entire OS using TWRP. Now my phone is constantly stuck on the Google logo screen. I am able to get into the bootloader screen, but any further action from there only takes me back to the frozen Google logo screen. I have spent the last several hours researching this issue and found many, many forum posts about solving this same issue, but I either don't understand the things people are suggesting or what I am able to understand, does not work for my phone.
So far I have messed around with the Wugs Toolkit thing but not sure what is right step for me considering almost everything requires me to go into my phone settings to mess with the USB debugging mode....since I cannot even boot my phone I am obviously unable to do this step.
I also have read about pushing a ROM file onto my phone but I'm not quite sure how to do this and how I know it even worked.
Please, can anyone give me any pointers/step-by-step guides? Thank you so much...

arthur94rice said:
Hello everyone,
I am stuck in a very frustrating dilemma with my Nexus 5 and need help very badly. I somehow managed to delete my entire OS using TWRP. Now my phone is constantly stuck on the Google logo screen. I am able to get into the bootloader screen, but any further action from there only takes me back to the frozen Google logo screen. I have spent the last several hours researching this issue and found many, many forum posts about solving this same issue, but I either don't understand the things people are suggesting or what I am able to understand, does not work for my phone.
So far I have messed around with the Wugs Toolkit thing but not sure what is right step for me considering almost everything requires me to go into my phone settings to mess with the USB debugging mode....since I cannot even boot my phone I am obviously unable to do this step.
I also have read about pushing a ROM file onto my phone but I'm not quite sure how to do this and how I know it even worked.
Please, can anyone give me any pointers/step-by-step guides? Thank you so much...
Click to expand...
Click to collapse
1.Don't Panic..keep it cool
2.Flash Google latest Factory Image http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
3. Please don't use any Toolkit !
Cheers :highfive:

Someone else had a similar issue.
http://forum.xda-developers.com/showthread.php?p=52279866
Sent from my Nexus 5 using Tapatalk

1) don't use toolkits
2) USB debugging only works in Android anyway
3) just adb push a ROM to /sdcard and flash it. All you need to know is in my signature
Sent from my Nexus 5 using Tapatalk

Partially Bricked Nexus 5

I never tried flashing a custom kernel before on my phone, but I downloaded Code Blue last night latest (615 I think) and I tried flashing it this morning. I have MultiROM installed with TWRP. When I rebooted my phone, MultiROM came up and I selected my internal 4.4.4 stock ROM. It then went to a black screen and stayed there for about 5 minutes until I rebooted the phone. Now I am currently sitting at a "Google" logo and the phone is completely stuck and won't move. I'm guessing the kernel wiped MultiROM or it wasn't compatible and now it's trying to boot something that is corrupted.
What's weird is, if I go into TWRP and go to MultiROM, it tells me it isn't installed.
Does anyone know how to fix this

I tried downloading MultiROM uninstaller tool and lo and behold, my data wont mount in TWRP on my laptop or desktop to put it on there :'(
Is there anyway to install the uninstaller without it on my internal

snappycg1996 said:
I tried downloading MultiROM uninstaller tool and lo and behold, my data wont mount in TWRP on my laptop or desktop to put it on there :'(
Is there anyway to install the uninstaller without it on my internal
Click to expand...
Click to collapse
Hello,
use wugs nexus toolkit, you can flash back to stock with this tool.
There ist a point named flash stock and unroot, there you must set the point by current status, bricked/bootloop.

Freddy Krüger said:
Hello,
use wugs nexus toolkit, you can flash back to stock with this tool.
There ist a point named flash stock and unroot, there you must set the point by current status, bricked/bootloop.
Click to expand...
Click to collapse
Thank you for the reply just to ensure, this will wipe everything right is there any way to save my data

I really don't know much about multitom.. But just use adb to pull your sdcard data then factory reset.
You could return to stock but please don't use toolkit as mentioned above. I'm really not sure why people insist on this being then answer.
2 links in my signature. 1 about why toolkits are not the answer. Another about guides and info threads. You can read about fastboot and adb. There and never think about pesky toolkits again.
Also no such thing as partially bricked. Its either bricked or not. This is not. Just a boot loop

do not use root toolkits. the reason you listed your phone as "partially bricked" is because you dont know better. a phone is either completely bricked or not. you do not learn how to do things using root toolkits. root tooolkits are not meant for noobs. what you want to do is flash the factory img via fastboot while you are in the bootloader.

Your phone isn't bricked at all, it can be easily fixed.
1) Downlaod 4.4.4 stock rom for nexus 5 on the offical site : https://developers.google.com/android/nexus/images
2) Unzip the folder and click the "flash all.bat" file inside the folder. This will install 4.4.4 on your nexus 5. (connect nexus 5 to your computer first)
3) You're done. (During the installation process from flash.all, all your data will be deleted).
So next time you get bricked, you can rely on that flashall bat but in the future, read the general info in the forums about how to use adb and fastboot without flashall.bat so you can unbrick your phone in minutes.
Link for all the general info you need to know : http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
EDIT: Nvm, others have already explained above

rootSU said:
I really don't know much about multitom.. But just use adb to pull your sdcard data then factory reset.
You could return to stock but please don't use toolkit as mentioned above. I'm really not sure why people insist on this being then answer.
2 links in my signature. 1 about why toolkits are not the answer. Another about guides and info threads. You can read about fastboot and adb. There and never think about pesky toolkits again.
Also no such thing as partially bricked. Its either bricked or not. This is not. Just a boot loop
Click to expand...
Click to collapse
How could I go about pulling the sdcard and resetting that would save data
I have no idea at all how to do those things, kind of in the dark without being able to mount anything. I just don't want to lose anything if it's possible, and if I wipe the phone, I have a feeling MultiROM will still be there. I'll check out the links

snappycg1996 said:
How could I go about pulling the sdcard and resetting that would save data
I have no idea at all how to do those things, kind of in the dark without being able to mount anything. I just don't want to lose anything if it's possible, and if I wipe the phone, I have a feeling MultiROM will still be there. I'll check out the links
Click to expand...
Click to collapse
Like I said, there's a guides and info link in my signature. If you click that and then read "adb and fastboot. What is it?" - all your answers are there..

rootSU said:
Like I said, there's a guides and info link in my signature. If you click that and then read "adb and fastboot. What is it?" - all your answers are there..
Click to expand...
Click to collapse
Thank you so much for your help, I really do appreciate it. however I installed abd and I went into TWRP and went to abd sideload and I typed in CMD "abd devices" and it don't show my phone, it shows "adb devices attached" but no serial numbers. Is there something I must do before it will show up
btw, I always typed abd wrong lol and it never showed up. I felt dumb when I realized it's actually adb.
EDIT fastboot works just fine showing serial numbers adb still nothing..

snappycg1996 said:
Thank you so much for your help, I really do appreciate it. however I installed abd and I went into TWRP and went to abd sideload and I typed in CMD "abd devices" and it don't show my phone, it shows "adb devices attached" but no serial numbers. Is there something I must do before it will show up
btw, I always typed abd wrong lol and it never showed up. I felt dumb when I realized it's actually adb.
Click to expand...
Click to collapse
No idea what happens when you enter adb sideload. That's not what you should be doing. Just test adb from the main menu of TWRP. If no devices, driver, USB issue.

rootSU said:
No idea what happens when you enter adb sideload. That's not what you should be doing. Just test adb from the main menu of TWRP. If no devices, driver, USB issue.
Click to expand...
Click to collapse
When I enter recovery on my laptop and desktop, it makes the "usb failed sound" the du du dun. Not sure if that is my problem. Is there anyway to fix the issue I think it isn't possible with fastboot to put stuff on any storage.

snappycg1996 said:
When I enter recovery on my laptop and desktop, it makes the "usb failed sound" the du du dun. Not sure if that is my problem. Is there anyway to fix the issue I think it isn't possible with fastboot to put stuff on any storage.
Click to expand...
Click to collapse
Fix the drivers

rootSU said:
Fix the drivers
Click to expand...
Click to collapse
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.

snappycg1996 said:
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
Click to expand...
Click to collapse
Its all in my "adb and fastboot" thread. I thought you were reading it?

snappycg1996 said:
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
Click to expand...
Click to collapse
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2

jmtjr278 said:
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
The universal naked driver is already linked in my thread that he was supposed to be reading

jmtjr278 said:
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
LOL. They're directly linked in rootSU's thread.
EDIT: rootSU beats me to it again. One day my friend, one day, I'll learn to type faster.

rootSU said:
Its all in my "adb and fastboot" thread. I thought you were reading it?
Click to expand...
Click to collapse
Maybe my phone is just done for. I download that driver and another one from a different thread and everytime I try to update it is says "nothing is found for your Nexus 5". If I'm in the bootloader it shows "Android Composite Device" with no yellow exclamation mark, however when I try to update there is just says everything is up to date. So I know the drivers work, but what I don't get is why it won't update.

theesotericone said:
LOL. They're directly linked in rootSU's thread.
EDIT: rootSU beats me to it again. One day my friend, one day, I'll learn to type faster.
Click to expand...
Click to collapse
Maybe one day you'll have as little to do on a Sunday as me and you'll beat me tonight

[Android Lollipop.Nexus 5] New discovered problem.Urgent!!! Need help!!

I have bought a nexus 5 two months ago. Everything was fine unlocked boot loader and rooted with custom recovery twrp and have updated to Android 5.0 by flashing with adb, then I rooted installed twrp, chainfire supersu and twrp. Until today was opening my nexus 5 and it didn't turn on, I followed these steps:
1- charged the phone 2 hours, nothing happens.
2- Charged whilst pressing power and every single key combinations.
3- Tried accessing the second bootloader, nothing happens.
4- Tried all suggested steps on google's website for this particular problem, nothing happens.
5- Connecting it to the computer, "qhsusb_bulk" appears in device manager, adb and fastboot won't work.
6- Connecting to the pc and trying every key combination, nothing happens.
7- tearing down the nexus 5 and removing the battery connectors then reconnecting them, nothing happens.
8- Download Qualcom's drivers and installing Them to the nexus 5, then using QPSt to flash boot image or kernel or phone image but won't work, it needs some sort of .bin files.
I hope that someone has some useful info, don't come saying I need to send it back to Google or RMA because that is not possible, or saying that I need a replacement board.
Thanks in advance if someone can figure this out.

Hi,
If you don't have fastboot access that don't sound good...
I had the same issue with Nexus 7, the only solution was to use the warranty.

The problem is that I don't have a warranty. And if I am going to send to LG electronics it will cost me 180$ at least.

Have you tried wug's nexus root toolkit? I used to have similar problems when i couldn't even assess fastboot, but the toolkit worked.

Yes I tried it but it didn't work. What steps did you follow in wug's toolkit to solve your problem?

@bitdomo, this is the brick you want to try to fix?

rootSU said:
@bitdomo, this is the brick you want to try to fix?
Click to expand...
Click to collapse
Yep. There was another one about a week ago. I pointed that guy in @bitdomo direction as well. Maybe he's on vacation or just busy.
OP: Your bricked. Try and PM the OP of this thread:
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stucked-qualcomm-hs-usb-t2935283
He's your only chance other than LG at this point.

theesotericone said:
Yep. There was another one about a week ago. I pointed that guy in @bitdomo direction as well. Maybe he's on vacation or just busy.
OP: Your bricked. Try and PM the OP of this thread:
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stucked-qualcomm-hs-usb-t2935283
He's your only chance other than LG at this point.
Click to expand...
Click to collapse
Ah yeah I saw that thread and noted he hadn't responded.

Possible Solution
I came to this point before. My solution was to hold all buttons for 15seconds den release down volume button. actually i cant remember the key combination.

[Q] Nexus 5 stuck on boot loop

Hello everyone:
This is the first time I ask for help on the Nexus 5. I read the couple of post about boot loop, but they could not help me. What happened was that I was checking some link on the browser and all of the sudden the phone restarted, I saw the google logo then the four color dots and it stayed there for ever. I check for info on how to deal with the problem and tried the power button plus the volume down (-) to get into the loader. After I was on the loader I tried unsuccessfully all the different menus that come with it, i.e., Start, Reboot, Restore, Power off. The only one that produces any result is the power off with which I can just turn the device off. I have had the phone since November 2013 and it is untouched, original google phone. It updated to os 5 a few months ago and there was no problem with it. I wanted to restore it to factory settings but as mentioned before the phone will not let me in. Is there any other way I could try to access it to restore? Thanks for your help.

Do a search for nexus factory images. You'll have to unlock your boot loader and then follow the instructions on that page.
Sent from my Nexus 5 using Tapatalk

Thanks but...
ldubs said:
Do a search for nexus factory images. You'll have to unlock your boot loader and then follow the instructions on that page.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you Idubs for the help, I am still reading and got stuck on the following:
I got an HP Envy 17 with windows 8.1 and I am trying to follow this instructions to get the Universal Naked Drivers install put can get this to appear:
To Install on Windows 8, you must additionally disable driver enforcement
- From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the - -- pop-out bar to appear, then click the Gear icon).
- Click ‘More PC Settings’.
- Click ‘General’.
- Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
- Wait a bit.
- Click ‘Troubleshoot’.
- Click ‘Advanced Options’
- Click ‘Windows Startup Settings’
- Click Restart.
All that is on bold can't be access. The closest I get is to Restart and the laptop restarts, which makes me loose everything and no driver can get installed.
Any suggestions?

Using Win 7 computer
After hours of no go with Win 8.1, I finally tried my old Win 7 pc. I got android sdk installed per instructions on this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
I can get to the point where I type fastboot oem unlock, and the phone shows it's unlocked, then I am supposed to type fastboot reboot. The phone reboots and stays on the permanent boot loop. I waited 30 minutes and nothing. Is it something I am doing wrong or the phone is toasted? I will like to know before I send it to Google for repairs as it is not in warranty any more and they will probably charge me what the phone was worth in the begining. Any ideas?

Put it back in fastboot mode and flash the factory images using the instructions from the page where you downloaded them.
Sent from my Nexus 5 using Tapatalk

@abyss1957 what happens when you flash a kitkat rom?

Frustrated
Hi:
I did a flash-all per instructions and the phone will not accept it. I unlock the phone, at least it says so on the display, when I give it the command the first thing it does is it reboots the loader and gets locked again. From there on the whole operation fails because it says it can not write to a lock device. I am using the adb program with the windows 7 command line. I think I will let google play with it if is not to costly, anyway I have to call them tomorrow to find out what happened with the shipping labels and instructions they were going to send.

abyss1957 said:
Hi:
I did a flash-all per instructions and the phone will not accept it. I unlock the phone, at least it says so on the display, when I give it the command the first thing it does is it reboots the loader and gets locked again. From there on the whole operation fails because it says it can not write to a lock device. I am using the adb program with the windows 7 command line. I think I will let google play with it if is not to costly, anyway I have to call them tomorrow to find out what happened with the shipping labels and instructions they were going to send.
Click to expand...
Click to collapse
If the bootloader is re-locking itself it's a classic sign of an emmc failure. Sorry man you've done all you can. See if Google will still warranty it. Keep asking to talk to a higher level of costumer service if they say no. Sometimes they can be really generous about out of warranty phones.

Thanks all
I tried today to revive the phone again by doing it per bitdomo thread:
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
After it got to about 6% is failed and the message was: userdata erase failed, and from there nothing happened. I guess it is really toasted. Thanks anyway for all the help all I can say is that I know today more than I did yesterday thanks to the great site. You all have a nice day. :laugh:

abyss1957 said:
I tried today to revive the phone again by doing it per bitdomo thread:
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
After it got to about 6% is failed and the message was: userdata erase failed, and from there nothing happened. I guess it is really toasted. Thanks anyway for all the help all I can say is that I know today more than I did yesterday thanks to the great site. You all have a nice day. :laugh:
Click to expand...
Click to collapse
Don't give up yet..... Look at my post http://forum.xda-developers.com/goo...p-lollipop-t3098632/post60491129#post60491129
I was in a similar situation and managed to fix my phone. Give it a try :good:

Thanks a lot eross
Thanks for the post, unfortunately I tried to flash it a couple of times after I posted my last and nothing happened. Always stuck at 6%, so I finally send it to LG for repairs. It should be back next week. Mine never allowed me to write anything to it, maybe a component bad. They send me an email with the charges for the repair but never said what was really bad with it, except that it was on a start up loop (like I didn't knew that). Anyways thanks to all for the help it was a real learning experience. :good:

Don't give up yet read a post above
LG is a waste of money

Retard in need of Help. Weird problem with recovery of my OPO

Alright have read the first 30 pages of comments on http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 and I starting to feel like I'm dumber then a brick.
Okay here is my problem: Just bought a used OPO with the classic boot logo loop error. I have tried to just simply Factory reset it (both Full and wipe cache) and it gives me E: failed to mount /cache (invalid argument) error. Then I googled it and most of the results said that I need to simply reinstall the software with adb. Okay got adb up and running and installed my phones drivers and booted into fastboot.
Then when I try to install it gave me "device not unlocked" error... Fine googled it tried "fastboot oem unlock" and it was still not unlocked.
Googled that and read the posts about tampered bits and after running the "fastboot oem device-info" It gives me "Device tampering: true" "Device unlocked: false" so damn.
Then I read the posts and tried to sideload OnePlusOne-BootUnlocker.zip (used the "apply update" in cyanogen recovery to get the ADB sideload) but it comes up with E: failed to mount /cache (invalid argument) and fails all the other things.
Have tried "fastboot boot recovery recovery.img" but that have the have a unlocked bootloader.
I'm abit lost ATM because I discovered that wile I can get fastboot and Sideload (from update) to show my device the normal adb can't see it when just being in the menu.
So if one of you could point me in the right way or if you got time guide me then I would be greatfull.
Regards Magnus/Mjallo
PS. Please don't burn me for asking

Can post pictures of the screen if it is needed

@Mjallo google "Bacon Toolkit."
Does literally all the things you are trying to do in a matter of a few clicks. Walks you through everything step by step.

h11wiscan said:
@Mjallo google "Bacon Toolkit."
Does literally all the things you are trying to do in a matter of a few clicks. Walks you through everything step by step.
Click to expand...
Click to collapse
Okay have played around with the program abit more and all it does is that same as me doing it in CMD.
I still have the problem with Device tampering and device unlock state. Where is the tools for fixing that?
Have tried to fix the cache but it still make the invalid argument.

might could fastboot flash official images to get the phone back to normal. you dont have to have bootloader unlocked to flash official boot images. you can go here https://cyngn.com/support and download the cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip (scroll down to opo section) and/or go to http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and get the download and follow directions in that post to flash phone

Mjallo said:
Okay have played around with the program abit more and all it does is that same as me doing it in CMD.
I still have the problem with Device tampering and device unlock state. Where is the tools for fixing that?
Have tried to fix the cache but it still make the invalid argument.
Click to expand...
Click to collapse
Yeah idk then. Need more screenshots or info to help. Could be a million things.
-Are you using OEM USB cable?
-Did you install ALL drivers properly?
-Have you rebooted since installing ALL drivers?
-Have you tried using bacon toolkit on another computer? Sometimes simply switching computers can help.
-Did you try resetting phone to factory state using ABD/Bacon Toolkit?
-In Bacon Toolkit did you select the proper firmware and software version before attempting to use the program?
A few questions to ask yourself before we go further.

kenboyles72 said:
might could fastboot flash official images to get the phone back to normal. you dont have to have bootloader unlocked to flash official boot images. you can go here https://cyngn.com/support and download the cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip (scroll down to opo section) and/or go to http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and get the download and follow directions in that post to flash phone
Click to expand...
Click to collapse
Have tried with both Normal Cyanogen and CyanogenMOD (that is what the bootlogo says on this phone) and both of them give the Device not unlocked error both on screen and in CMD

h11wiscan said:
Yeah idk then. Need more screenshots or info to help. Could be a million things.
-Are you using OEM USB cable?
-Did you install ALL drivers properly?
-Have you rebooted since installing ALL drivers?
-Have you tried using bacon toolkit on another computer? Sometimes simply switching computers can help.
-Did you try resetting phone to factory state using ABD/Bacon Toolkit?
-In Bacon Toolkit did you select the proper firmware and software version before attempting to use the program?
A few questions to ask yourself before we go further.
Click to expand...
Click to collapse
Okay I'm using the OEM cable (have tried both the one I got with this phone and the one I got with my Orginal OPO)
Have gone through the steps checking my drivers and they should be working and A OKAY, reboot and all.
Don't have access to another pc ATM but will look after the option.
Have tried all the option in Bacon toolkit to reset the phone to factory setting and non is working, tried to then use the recovery option to maybe get it to work that way but no dice. Have also tried sideloading both with Toolkit and with CMD and no luck their either. Took a picture of the screen when the sideload tries to work.
http://imgur.com/6L74N6J
The Firmware question is up in the air because I have never got it booted so I have no clue what firmware it has only hint that the boot screen is Cyanogen MOD READY and not just Cyanogen like on my other OPO
Hope it helps finding the problem

I super hard bricked my phone a while back, even lost a partition. I was finally able to get it back by flashing colorOS. took a few tries to get the program to recognize my phone, but finally got it flashed. The phone never booted all the way up with colorOs, but it fixed what needed fixed and I was then able to fastboot flash CM13, unlock bootloader and go from there. don't have that thread bookmarked, but it's here in the forums.
Edit: found thread http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

kenboyles72 said:
I super hard bricked my phone a while back, even lost a partition. I was finally able to get it back by flashing colorOS. took a few tries to get the program to recognize my phone, but finally got it flashed. The phone never booted all the way up with colorOs, but it fixed what needed fixed and I was then able to fastboot flash CM13, unlock bootloader and go from there. don't have that thread bookmarked, but it's here in the forums.
Edit: found thread http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
It sadly did not fix the problem it gives this problem and just stops working (need to close it in taskmanger) http://imgur.com/w1zOQFU.
Well the quest goes on

Mjallo said:
It sadly did not fix the problem it gives this problem and just stops working (need to close it in taskmanger) http://imgur.com/w1zOQFU.
Well the quest goes on
Click to expand...
Click to collapse
when you run the program, one of the columns should have a few random characters and "com" in it. if you dont see com in any of the columns, then the program is not seeing you phone. if you do see com, the click on that row and press start and it will show files being written in green showing progress. if phone is not being seen, follow that guide to the letter, specially if this is on a win7/8 machine. i will get my lappy out in a bit and give a few screenies on what it should look like, i wont actually flash my phone though.

kenboyles72 said:
when you run the program, one of the columns should have a few random characters and "com" in it. if you dont see com in any of the columns, then the program is not seeing you phone. if you do see com, the click on that row and press start and it will show files being written in green showing progress. if phone is not being seen, follow that guide to the letter, specially if this is on a win7/8 machine. i will get my lappy out in a bit and give a few screenies on what it should look like, i wont actually flash my phone though.
Click to expand...
Click to collapse
It sees it (you can see it in COM5 in the picture) and when the progress bar shows it just make a little green tip then just stops showing

are you running the program as administrator? right click on exe and select run as administrator? other than that, don't see why it's not flashing and I'm out of ideas, sorry.