Related
ok i need help please , i had gbread on it and installed superoneclick to get root then tried to flash cwm with vipermod. message said out of storage space or something (dont have ext mem only internal)and now phone will not turn on.
have followed this guide http://forum.xda-developers.com/showthread.php?t=1244490 and phone was recognised by omapp but couldnt change the port in device manager and couldnt find a bin to download so i tried to flash a kdz v21a
clicked start on lgflasher but nothing happened so after about 5 mins i cancelled it thinking without the port change it was a waste of time.
now i cant even get omapp to flash up when i connect phone . device manager refreshes but i cant see anything change .
hope thats enough info for some kind person to help.
many thanks in advance
marty
Try this start on step 3 its in the thrill forum but they are the same phone http://forum.xda-developers.com/showthread.php?t=1491870
sent from my acidhazard thrill
marty41 said:
...then tried to flash cwm with vipermod...
marty
Click to expand...
Click to collapse
Where did you get vipermod from? The Transformer Prime forums? That's meant for the TFP and would not have worked with the O3D since it flashes to mmcblk0p4 rather than mmcblk0p. You should have used the flasher here.
Download this, this and this. Extract smartflash.zip, install both driver packages. Then, run Windows Enabler, in the notifications bar, click it and make sure it is set to 'on'.
Now remove your phone's battery and sim card, press volume up and connect your phone to the computer. Hold volume up until it is detected by the computer. It should take no longer than 20 seconds.
Now run B_SmartFlashTool_Extern.exe, go to rom copy d/l, select LGP920_CP.fls for CP bin and LGP920_AP.bin for AP bin. Make sure under communications setup that your phone is connected (verify the com port in device manager) and then click start. If all goes well, you'll have a stock v21D phone again
Thanks for the help guys but i'm not getting a com port when i connect the phone so i don't think i can use any of those methods . or can i
i want to go back to the beginning and see if omapp will detect phone and install drivers but i can uninstall the installer but dont think that will remove the drivers , does anyone know how to do that.(cos i think i messed that bit up )
thanks again
marty
vipermod , i think i followed a link somewhere in the o3d forum where someone said u could use it to flash cwm
so , i uninstalled all lg drivers uninstalled omap installer searched registry for for any mention of omap and deleted (some wouldnt delete ) .
restarted computer (xp by the way )
then installed omap installer and lg drivers and connected phone holding vol up
and................. NOTHING whereas yesterday i had a little icon in the task bar and the opportunity to install omap drivers.
conclusion , phone is dead , i had an oppurtunity to fix it yesterday and i blew it
hope someone tells me i'm wrong but its not looking good
marty
take off battery and just put your usb cable and tell us if it shows omap in your device manager
dont press keys
if i connect phone without battery device manager just refreshes a couple of times but nothing changes with regards to ports doesn't matter if i have vol+ button in power button in or nothing
thanks anyway
marty
am i getting somewhere
update : ok so i'm on a clean install of xp and i connected the phone with vol+ and it wants to install omap4430 drivers. is that good news?
i installed omapinstaller , then the 2 lg drivers ca and ma , then reconnected the phone and went thro omap driver install but still don't have any ports in device manager
is there no way i can force it to flash without it having to think it is connected cause if its recognising it as omap4430 there must be something there
don't want to give up on it too easy , if only i put this much effort into it whilst it was working lol
marty
evening all . new update
tonight i've installed the lg support tool and drivers and found that if i leave my phone connected i occasionally get "TI sample boards" popping up in device manager for a couple of seconds without having to press buttons , unfortunately it doesn't stay on for any longer with buttons pressed.
i was wondering how to force install the "LG CDMA composite usb device " drivers cos its never asking for them as it should according to the tutorial
hope someone can help cos i've seen a few threads with same problem as me
marty
Howdy folks!
I am working my way through a minor (?) technical difficulty.
Would appeciate any suggestions you folks can off this newbie along the way.
Earlier today, I made an absent-minded mistake. Tried to go to my stock Froyo kernel without undoing my voodoo/lagfix/ext/watchamacallit setup. Whoops. Bootloop. No recovery mode available.
So, I attempted to use the procedure described in [ROM] [2.3.6] Heimdall One-click Back-To-Stock UCLB3 here:
http://forum.xda-developers.com/showthread.php?t=1524081
I’m in Windows 7.
I right-clicked on the Heimdall one-click program (Stock_SGH_I997_UCLB3_Repartition-One-Click), but there was no option to run as administrator. So I just double clicked it and it opened it (deviated from instructions on the first step...oh oh).
With the Heimdall one-click program now open, I put my phone in download mode and it indicated connected (perhaps in retrospect I connected too early)
I followed instruction on the PC program to install drivers, which it did (I already had Samsung drivers installed that I used successfully for SOC root program and for EFS Pro, I’m not sure what it was installing).
The pc program told me it needed to reboot. The phone screen said something about “dont’t shut off...”. I wasn’t sure what to do at that point, so I granted the pc permission to reboot.
PC rebooted, phone remains attached the whole time
Upon reboot, the Heimdall one-click program did not start up again.
So I double-clicked it and started it again.
The phone remained attached, but was not recognized as connected by the pc one-click program.
So I pushed 3 buttons on the phone to get it to turn off, then removed the batteries.
.
Then started pc Heimdal one-click program again. Then put my phone in download mode which it did successfully.
Then ran the flash and go the message “The FACTORYFS upload failed!”
(This occurred run without the checkbox about bootloaders)
At that point I checked the checkbox about bootloaders, and it came up with some scarey warning so I didn’t flash (probably should have).
I once again deenergized the phone (three-buttons, remove battery during the brief period it’s deenergized). Shut down pc heimdall one-click program.
Then started pc heimdall program.
Tried to put phone into download mode and received the following inauspicous message:
“Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again”
Deenergized phone again. Shutdown pc program. Powered PC off. Restarted pc. Restarted Heimdall one click.
Tried to put the phone in download mode again and got the same error message.
I don’t know anything about selcting recover mode, not sure how to follow that instruction (any ideas?).
What I did next was search for the error message. It apparently has not been reported in the Infuse section, but I found two threads with this message discussed in the Galaxy S2 section.
“help” is the title of the first
http://forum.xda-developers.com/showthread.php?t=1189473
“Firmare upgrade encountered an issue - Am i done for?” is the title of the 2nd:
http://forum.xda-developers.com/showthread.php?t=1386232
There may be some more out there...
What I gathered was that I needed to remove my drivers.
I did remove the Sansung USG drivers in my control panel. I think these are the one’s I already had installed prior to me SOC root.
Rebooted.
Reinstalled drivers (filename SGH-i997_Infuse4G_USB_Drivers_5_2_0_2)
Restarted Heimdall one-click.
Put phone in download mode.
The same error message indicating that my phone has “issues”
Uninstalled my Samsung USB driver again.
Went back and looked at my control panel, there is another program. Keis. Uninstalled that. Rebooted.
Reinstalled SGH-i997_Infuse4G_USB_Drivers_5_2_0_2 driver
Reinstalled Kies_Mini_For_Captivate_11011_4.exe
Rebooted
Started the Heimdall one-click program.
Put phone in download.
Get the same error message on the phone (firmware upgraded encountered an issue...).
PC at this time thinks the phone is “connected”. So I clicked flash.
It proceeds to the next screen for driver installation.
I selected options / all / Samsung usb / Replace
PC Error message: Driver installation failed.
From those other threads, I’m pretty sure if I get my drivers straightened out I’ll be all right.
I don't know what I did wrong with the drivers... if anyone has a link with concise instructions for uninstalling/reinstalling the required drivers, maybe that would help me see if I've done something wrong.
Any other suggestions?
My java version is Version 6 Update 25
I have made a couple of change to this, a post I did for someone else today. You have done an excellent job of trying to resolve this- I hope this will be helpful.
There are a couple of things to point out:
Get Kies off your computer - it is a source of problems. Also means delete from recycle bin if there.
Download the Infuse drivers from bigjoe's ISET here: http://d-h.st/sKF
Thanks to bigjoe for an amazing page of resources !!
Be sure you have the latest version of Java here: http://www.java.com/en/download/index.jsp
Follow qkster's instructions he provides here:http://forum.xda-developers.com/showthread.php?t=1524081
Post 1 gets you back to stock- Post 2 gets root back.
Big thanks to qkster for doing this - saved many phones for countless number of users !! Me alone over a million times and counting
A video- no academy award nomination, but can be helpful : http://www.youtube.com/watch?v=sHyY7WHx4zc
Video is returning to Gingerbread.
You are willing to learn - therefore there will be many who are willing to help.
Take your time- do it right once and it will be easy next time !!
Heimdall uses it's own driver.
Once you install heimdall on one USB port of your pc, reserve that 1 port for going back. Also good to use that same USB cord.
The first part where it failed was because of bad connection. You just needed to change USB cord or change the port.
Read the heimdall thread and the how to thread a few times...
You could also use the froyo heimdall i put together for ucke3..see my sig link
Thanks very much for the replies.
Updated java.
Uninstalled Kies and Samsung driver (SGH-i997_Infuse4G_USB_Drivers_5_2_0_2)
Rebooted.
Reinstalled Samsung driver from bigjoe's link (same file).
I think it asked me to reboot.
Started the PC Heimdall program.
Attempted to put phone in download mode, it says "Firmware upgrade encountered an issue....".
So phone is not recognizing PC.
But PC recognizes the phone as connected.
Press flash. It goes to next page... I list all drivers, there is nothing Samsung in there.
Disconnected phone. Shut down program. Removed drivers/rebooted / reinstalled Samsung driver
Started Heimdall.
Attempted download mode, same error message "Firmware upgrade encountered an issue..."
Tried flash anyway, the next screen list of devices still has no Samsung.
Oddly when I go back to the first pc screen and try plug/unplug the phone, the PC recognizes phone as connected/disconnected. But it doesn't recognize it on the 2nd page where it tries to install the driver. And the phone has never successfully entered download mode since the first one or two tries...I get this "Firmware upgrade encountered an issue with yellow triangle screen every time since.
All above was on a single USB. I then tried on two other USB's same result. I may try another PC tomorrow night after work.
And will review the qkster's thread again as well as the video link posted by Pony Express.
Will report those results...
For now my head hurts . Time to call it a day.
Thanks for all your help.
I definitely appreciate it.
post deleted by op
meaning of this error message?
deleted
I see there is one other current thread in this forum on similar issue
"stuck on screen with (phone)---!----(Computer) "
http://forum.xda-developers.com/show...rch+this+forum
I noticed one thing we had in common is we both had Kies installed at some time early in our process (now removed).
I have some questions about the meaning of this screen that appears on my phone when I attempt to get to download mode:
"Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again"
The screen has a yellow warning triangle on it
Is that a common screen to see on your phone during this process ?
Does it represent download mode? (I don't think so, since I saw a different screen on my phone the first time I connected... but maybe that had something to do with Kies?)
Is there any point in even trying to flash/download drivers when I see that message?
If the opportunity presents itself, is it advisable to attempt flash with "download bootloaders checked" when this error message is present?
(* If these questions are answered by the video, then I apologize in advance. I don't have the opportunity to watch that video here from my work computer, but I am eager to get a head start so I can hit the ground running when I get home after work tonight).
electricpete1 said:
I see there is one other current thread in this forum on similar issue
"stuck on screen with (phone)---!----(Computer) "
http://forum.xda-developers.com/show...rch+this+forum
I noticed one thing we had in common is we both had Kies installed at some time early in our process (now removed).
I have some questions about the meaning of this screen that appears on my phone when I attempt to get to download mode:
"Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again"
The screen has a yellow warning triangle on it
Is that a common screen to see on your phone during this process ?
Does it represent download mode? (I don't think so, since I saw a different screen on my phone the first time I connected... but maybe that had something to do with Kies?)
Is there any point in even trying to flash/download drivers when I see that message?
If the opportunity presents itself, is it advisable to attempt flash with "download bootloaders checked" when this error message is present?
(* If these questions are answered by the video, then I apologize in advance. I don't have the opportunity to watch that video here from my work computer, but I am eager to get a head start so I can hit the ground running when I get home after work tonight).
Click to expand...
Click to collapse
For the moment don't check the bootloaders. You will only need them for ICS and JB to get rid of rainbows in the recovery. A bootloader flash is practically the only thing that can brick our phone.
Is that "firmware upgrade.." screen the one with the pc!phone? It has been a long time since I soft bricked so I don't recall if it said that somewhere.
If heimdall is giving you issues, try Odin and see how it goes there.
Sent from my sweet & buttery Infuse
electricpete1 said:
I see there is one other current thread in this forum on similar issue
"stuck on screen with (phone)---!----(Computer) "
http://forum.xda-developers.com/show...rch+this+forum
I noticed one thing we had in common is we both had Kies installed at some time early in our process (now removed).
I have some questions about the meaning of this screen that appears on my phone when I attempt to get to download mode:
"Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again"
The screen has a yellow warning triangle on it
Is that a common screen to see on your phone during this process ?
Does it represent download mode? (I don't think so, since I saw a different screen on my phone the first time I connected... but maybe that had something to do with Kies?)
Is there any point in even trying to flash/download drivers when I see that message?
If the opportunity presents itself, is it advisable to attempt flash with "download bootloaders checked" when this error message is present?
(* If these questions are answered by the video, then I apologize in advance. I don't have the opportunity to watch that video here from my work computer, but I am eager to get a head start so I can hit the ground running when I get home after work tonight).
Click to expand...
Click to collapse
Yes...that's represents download mode...just another form...heimdall should still work
Sent from my SGH-I997 using Tapatalk 2
Thanks to everyone. That is very helpful.
I have some more questions. I'm not trying to be nit-picky, but just want to make sure I understand exactly what is being said.
qkster wrote:
Heimdall uses it's own driver.
Click to expand...
Click to collapse
Does that mean we don't need the Samsung driver SGH-i997_Infuse4G_USB_Drivers_5_2_0_2 driver ?
Any guess whether it works better with or without it? I will definitely try without it, but if anyone knows a preferred configuration, that would be helpful so I can focus on changing other things.
qkster's how to:
2. If you have not used Heimdall, you will need to set up the driver for device recognition
Click to expand...
Click to collapse
As a clarification. I'm not sure precisely what that means. All I'm doing is starting the program, letting it load drivers on first screen, connecting the phone in download mode (with error screen), pushing flash which will hopefully get me to the 2nd screen where I select options/all/Samsung/Replace to set up the driver. Is this statement intended to say anything different?
qkster's how to:
6. If it did not work, you will have to put it back into DOWNLOAD mode and reflash a second time, with the FLASH BOOTLOADER box checked.
Click to expand...
Click to collapse
I take it that in my situation (with error message and no evidence of success in previous flashing, and going to GB) this is really only a last resort after all other options exhausted as per andros' suggestion above?
By the way, I'm going to keep trying to install the UCLB3 GB (vs Froyo), as long as the chance of success is the same on both.
qkster's how to
4. Click on the FLASH button. (In my opinion: I recommend that you do this in a safe environment. Do not disturb your phone will flashing this firmware. Turn off Antivirus. Do not run any other programs, upload/download/youtube/burning DVD etc)
Click to expand...
Click to collapse
I'm a little nervous about turning off my security program (a/v, firewall etc) since I haven't done that in years.
Have there been problems attributed to doing this with security enabled, or is it just a general suggestion to avoid interruptions from unexpected scans or pop-ups etc? (my security runs peacefully in background and never interrupts me unless I ask it)
If it's really necessary to disable security program, I'd feel better about keeping my internet disconnected for the duration that the anti-virus is off. Is there any problem created if the internet connection remains disconnected for the duration of this process?
electricpete1 said:
Thanks to everyone. That is very helpful.
I have some more questions. I'm not trying to be nit-picky, but just want to make sure I understand exactly what is being said.
Does that mean we don't need the Samsung driver SGH-i997_Infuse4G_USB_Drivers_5_2_0_2 driver ?
Any guess whether it works better with or without it? I will definitely try without it, but if anyone knows a preferred configuration, that would be helpful so I can focus on changing other things.
As a clarification. I'm not sure precisely what that means. All I'm doing is starting the program, letting it load drivers on first screen, connecting the phone in download mode (with error screen), pushing flash which will hopefully get me to the 2nd screen where I select options/all/Samsung/Replace to set up the driver. Is this statement intended to say anything different?
I take it that in my situation (with error message and no evidence of success in previous flashing, and going to GB) this is really only a last resort after all other options exhausted as per andros' suggestion above?
By the way, I'm going to keep trying to install the UCLB3 GB (vs Froyo), as long as the chance of success is the same on both.
Click to expand...
Click to collapse
Drivers: when you launch heimdall it will install its own custom drivers for whatever usb port its pluged into...so if you plug it into one of your ports in the front and run heimdal only the port the phone is currently plugged into will be effected by the new driver. the driver is only used when in download mode...so dont uninstall your current drivers
selecting device: i think you got it (if my memory is correct...) just launch and run heimdall with device connected in dl mode...when you get to installing drivers just go to options and choose list all...i cant remember the exact name the infuse shows up as though
Bootloaders: just flash the first time without it checked...if it doesnt go through then check it and flash again
Antivirus: i have never turned off my anti virus when using heimdall on any of my computers (one computer uses norton 360 premier, the other one uses avast free) i never had it conflict with the process...so just leave it on for now...and only turn it off if you are having problems...if your worried about viruses then disconnect from the internet when you turn off your anti virus -i dont think the heimdall relies on internet at all...well maybe for the drivers...so just dont turn anything off until after you get the drivers
EDIT: i have a frseh install of windows 7 on my dev computer that i havent used heimdal on yet...so ill run it and clarify the driver section...i dual boot both linux and windows...currently im near the end of a repo sync so as soon as that finishes ill boot into windows and run heimdal...in less then a half hour hopefully...
Thanks mg2195.
Very good info.
I have tried my Windows 7 PC and another windows Vista PC.
On both pc's I tried with drivers pre-installed on the pc and without. Reboots in between.
I also used two different cables and tried all usb ports that were available.
In all cases but one, the anti-virus/firewall was on and pc connected to internet
In one case I tried with anti-virus off and pc diconnected from internet.
In all cases (except for the first one or two at the beginning of this thread), here's what happens:
I start Heimdall, it takes me to the first Heimdall screen, which shows "device status" red/disconnected as expected.
I try to put phone in download. Get the error message screen on the phone (see subject line). The "device status" shown on the pc changes from red/disconnected to green/connected (as expected).
I Click flash.
It asks to run the program, I say ok, it takes me to the second Heimdall screen, where I select Options/List-all.
There is no samsung driver choice.
I close the selection window (click x in upper right hand corner), it takes me back to the first Heimdall screen.
Device status still shows green/connected on the first Heimdall screen.
If I press flash again, the experience at the second screen repeats without showing Samsung driver.
Before I go to the next configuration (next usb port or cord or whatever), I remove the phone and close out the Heimdall program.
The bootloader option is available to be checked in the first Heimdall screen, but I have not done it
I’m not sure if I explained before that I have not had a successful driver installation in that second Heimdall screen (since the first one or two attempts). Does this change fact change your suggestion about checking the flash bootloaders box?
electricpete1 said:
Thanks mg2195.
Very good info.
I have tried my Windows 7 PC and another windows Vista PC.
On both pc's I tried with drivers pre-installed on the pc and without. Reboots in between.
I also used two different cables and tried all usb ports that were available.
In all cases (except for the first one or two at the beginning of this thread), here's what happens:
I start Heimdall.
Try to put phone in download. Get the error message screen.
Click flash in the first Heimdall screen.
It asks to run the program, I say ok, it takes me to the second Heimdall screen, where I select Options/List-all.
There is no samsung driver choice.
I close the selection window (click x in upper right hand corner), it takes me back to the first Heimdall screen.
The bootloader option is available to be checked in the first Heimdall screen, but I have not done it.
I’m not sure if I explained before that I have not had a successful driver installation in that second Heimdall screen (since the first one or two attempts). In this circumstance, do you still think it’s ok to check bootloaders?
Click to expand...
Click to collapse
you should probably wait until you get the heimdal drivers installed...im still wating for my reposync to finish...for some reason the download slowed down to 200kb/s,,,so it could take a while...
but for the drivers do this
1) On the menu bar (Device,Options,Help) Click Options --> List All Devices
2) Under USB Device select “Samsung USB Composite Device”
if its not locating it then try differnt ports/cables...if still no then run as admin...rightclick or shift+rightclick...if still not showing up...maybe bad usb port on the phone?
Quick response... thanks again!
Bad usb on phone is certainly possible, but I've never had a problem with it before.
I can believe the pc usb port might be finicky. Because historically on my Windows 7 PC, every once in awhile when I insert a flash drive memory stick, it does not get recognized. I will see if I can try a 3rd computer.
Regarding "run as administator":
When I right-click on the file, I don't see any option for "run as administrator" in either my Windows 7 pc or my Windows Vista pc.
So I have just been double-clicking the file. I think the Windows Vista asked me if I trusted the program and I said yes. Windows 7 just launches it.
Maybe there's some setting I need to change somewhere in order to get this "run as administator" ....I will google that... tomorrow. Right now, my pillow awaits.
electricpete1 said:
Quick response... thanks again!
Bad usb on phone is certainly possible, but I've never had a problem with it before.
I can believe the pc usb port might be finicky. Because historically on my Windows 7 PC, every once in awhile when I insert a flash drive memory stick, it does not get recognized. I will see if I can try a 3rd computer.
Regarding "run as administator":
When I right-click on the file, I don't see any option for "run as administrator" in either my Windows 7 pc or my Windows Vista pc.
So I have just been double-clicking the file. I think the Windows Vista asked me if I trusted the program and I said yes. Windows 7 just launches it.
Maybe there's some setting I need to change somewhere in order to get this "run as administator" ....I will google that when I get a chance.
Click to expand...
Click to collapse
Did you try holding shift while right clicking?
Sent from my SGH-I997 using Tapatalk 2
electricpete1 said:
I take it that in my situation (with error message and no evidence of success in previous flashing, and going to GB) this is really only a last resort after all other options exhausted as per andros' suggestion above?
Click to expand...
Click to collapse
Thanks for pointing out the imprecise grammar, Pete.
I corrected the op.
Recheck step 6 and 7.
To get heimdall to install its drivers, Zadig, you need the initial Samsung Android drivers. so when you pull down the zadig menu, Samsung Adroid device should show up.
Then reboot the PC.
Then try connect in dl mode again.
You had it at some point...
Thanks all.
That is now very clear qkster. (Actually it was reasonably clear before and I was pretty sure I knew what you meant, but just wanted to double check in case I was misunderstanding something)
I've had some trouble running as administrator, apparenlty others don't
Here's my difficulties and how I resolved it (I think):
DIFFICULTIES IN RUN-AS-ADMINISTRATOR.
If I right-click on an executable file (anything.exe), I get option to run as administrator. Great.
If I right click on a jar file (like the one I'm trying to run), no such option. Sad.
Same thing with short-cuts.
If I right-click on shortcut to exe, I can choose compatibility tab and select run as administrator. Great.
If I right-click on shortcut to jar, there is no compatibility tab. Sad.
HOW I RESOLVED RUN-AS-ADMINISTRATOR (I think)
I found some instructions for specifically for running jar as administrator here:
http://stackoverflow.com/questions/...r-with-administrators-privileges-on-windows-7
Specifically, click start, type cmd in the window just above start, right-click on the cmd result, and click "run as administrator.
That takes you to an elevated command prompt with the word administrator in the window heading.
Navigate to the directory and type
java -jar myfile.jar
where myfile is your file name (I renamed it to shorter name to make it easier).
RESULT:
I was able to launch Heimdal from the elevated command prompt.
Unfortunately, results have been the same thus far when using Heimdall launched from elevated command prompt as the previously reported results.
QUESTION: is there any way to check the program truly has admin priveleges?... it didn't ask any permission when launching Heimdall from the elevated command prompt.. the only permission asked was when launched cmd from the windows start menu screen.
I will repeat a few of yesterdays trials.
If those are unsuccessful, I think next step is trying GTG's package with ODIN.
QUESTION: Is there any way to clear any settings loaded into the USB ports by the Heimdall so they don't interfere with ODIN?
For Odin, just install the drivers you see at the iset page or kies drivers.
If you had a pc, one user when you log on, it is auto assume admin.
You can also go to control panel, users, look at privileges
Solved,
if your story sounds similar to mine(Go to TL;DR) Refer to post 4
ok, where to begin
my N5 was A-OK just 3 days ago running the Dev Preview of Lollipop. by A-OK i mean that it worked but with a few
bugs
(its the dev preview i know, its got bugs) like when i stayed on an app, e.g spotify, and exited to the home screen it
would take like 15 sec for all the apps on the home screen (like 6) to appear. There is not where the problem lies.
Again 3 days ago. i poked around both ROM sections to find a Lollipop based on that was to my liking, found one and
directly downloaded it to my phone (in hindsite it would of been better to do it on my comp) and being no stranger
to flashing ROMs i went on auto-pilot adn begun the wiping of cache and factory resetting, setting up for the move to
more stable ROM. When it was time to flash the ROM I completely downloaded was no where to be found, a bit
panicked i went to a backup i had on the device, it did its thing and i booted it up but it went back to Clockworkmod
recovery screen That's problem No. 1 . I rebooted it still the same thing. Scouring through
the web for help on setting ADB to sideload the ROM. The thing is that when i hooked up my phone to my desktop
it didn't recognize the device, The correct drivers are installed but it doesn't recognize the device its labeled as
unknown USB device. That's problem No. 2
*update i plugged in my N5 and the comp read it as a N5 but when i selected the option to sideload it it doesn't
recognize it anymore
and problem No. 3 is USB debugging might be turned off
TL;DR? 1. Boots into Clockworkmod
2. my computers don't recognize the device
3. USB debugging might be off
-Q: Can USB Debugging be enabled some other way.
Any help is appreciated
why is it double spaced? i find it a bit eye-straining reading that much all bunched together
Setup fastboot on your computer. Once done open a command prompt and type fastboot devices. If it doesnt display a long line of numbers and letters the computer isnt recognizing the device. At this point try a different usb port, and try a different cord, until it recognizes. The fastboot flash the images for 5.0. 1. =profit.
Lokke9191 said:
Setup fastboot on your computer. Once done open a command prompt and type fastboot devices. If it doesnt display a long line of numbers and letters the computer isnt recognizing the device. At this point try a different usb port, and try a different cord, until it recognizes. The fastboot flash the images for 5.0. 1. =profit.
Click to expand...
Click to collapse
ok, used a different cable and it now recognizes it.
tried fastboot devices and nothing
tried ADB devices and numbers appeared and what state the device is in, recovery.
thank you thank you thank you sooo much
all is good
My Nexus 5 is alive,
i tried to upgrade to 5.0 directly and kept getting errors e.g archive does not have boot.sig/ system.sig. That lead me to look up Boot.sig/System.sig, that lead me to a blog saying i could fix the problem if i added something to the directory, forgot how to get to environmental variables, i went and watched the vid that helped my set up adb/sdk and thats when it clicked..
What if i tried flash-all with KitKat and voila it started running the process of flashing. Since it was basically a new phone unrooted and everything it had the system update to lollipop.
Hi Guys,
Im new to the forums so i hope this is the right place for this post
I have a hardbricked oneplus one 64GB.
I have read and followed mutiple guides here and on youtube on how ot unbrick it.
But in every guide i followed mine "failed" at the same step.
When i start the "oneplus one recovery tool" or Msm8974DownloadTool this happens; (cant seem to use a link so ill try to explain it).
It starts with one green bar, when that is finished it stops an i hear the disconnected device sound.
I am currently on Win 10 but i also tried it on WinXP since mutiple posts suggested hat it would work better, but that also didnt help.
I also tried diffrent drivers (oneplus driver from the color zip), google multi driver, qualcomm driver etc.
Hope someone can help
Tiic said:
Hi Guys,
Im new to the forums so i hope this is the right place for this post
I have a hardbricked oneplus one 64GB.
I have read and followed mutiple guides here and on youtube on how ot unbrick it.
But in every guide i followed mine "failed" at the same step.
When i start the "oneplus one recovery tool" or Msm8974DownloadTool this happens; (cant seem to use a link so ill try to explain it).
It starts with one green bar, when that is finished it stops an i hear the disconnected device sound.
I am currently on Win 10 but i also tried it on WinXP since mutiple posts suggested hat it would work better, but that also didnt help.
I also tried diffrent drivers (oneplus driver from the color zip), google multi driver, qualcomm driver etc.
Hope someone can help
Click to expand...
Click to collapse
How your device got bricked?
Which recovery tool you tried?
Mr.Ak said:
How your device got bricked?
Which recovery tool you tried?
Click to expand...
Click to collapse
I don't have all the info since i got the phone from a "friend" who was about to throw it out, but ill do my best to provide accurate info
According to the privious owner the flashing of a custom rom or recovery went wrong and it ended up in it's current state.
The recovery tools i tried are;
- Oneplus one recovery tool by; Zyxxeil
- Oneplus one toolkit 1.5 by Manudroid19
- Msm8974DownloadTool
Tiic said:
I don't have all the info since i got the phone from a "friend" who was about to throw it out, but ill do my best to provide accurate info
According to the privious owner the flashing of a custom rom or recovery went wrong and it ended up in it's current state.
The recovery tools i tried are;
- Oneplus one recovery tool by; Zyxxeil
- Oneplus one toolkit 1.5 by Manudroid19
- Msm8974DownloadTool
Click to expand...
Click to collapse
Use the one with cm11s by Zyxxeil.Use Xp and use Qualcomm drivers,as this tool doesn't use fast boot/adb drivers and instead uses USB debugging port.
It need a few tries before device getting detected.
Make sure the device is getting recognized as "Qhs_bulk" or "Qualcomm diagnostics 9006" or some thing like that then install drivers manually.Also try different ports and refresh the toolkit. Open the toolkit with administrator rights.
Hope this helps
Mr.Ak said:
Use the one with cm11s by Zyxxeil.Use Xp and use Qualcomm drivers,as this tool doesn't use fast boot/adb drivers and instead uses USB debugging port.
It need a few tries before device getting detected.
Make sure the device is getting recognized as "Qhs_bulk" or "Qualcomm diagnostics 9006" or some thing like that then install drivers manually.Also try different ports and refresh the toolkit. Open the toolkit with administrator rights.
Hope this helps
Click to expand...
Click to collapse
I'm on windows xp now.
Made a clean install to be sure.
Phone is connected as Qualcomm HS-USB QDLoader 9008
The Zyxxeil tool recognizes it as a com port.
When i press start, it starts flashing 8974_msimage.mbn
When it finishes it just does the same. It looks like it's stuck on a loop at flashing 8974_msimage.mbn
I would post some pictures but i can't since im a new user
Edit; It is the same as this guy; youtube (dot) com/watch?v=TOw3-yX57jM
Flashing 8974_msimage.mbn nin a loop.... you're not the only one with this problem. I couldn't find a solution to this problem so far. Have tried fresh installs of Windows XP and Windows 7 and drivers installed in Test Mode without success. Please report back once you could figure out what's wrong.
Tiic said:
I'm on windows xp now.
Made a clean install to be sure.
Phone is connected as Qualcomm HS-USB QDLoader 9008
The Zyxxeil tool recognizes it as a com port.
When i press start, it starts flashing 8974_msimage.mbn
When it finishes it just does the same. It looks like it's stuck on a loop at flashing 8974_msimage.mbn
I would post some pictures but i can't since im a new user
Edit; It is the same as this guy; youtube (dot) com/watch?v=TOw3-yX57jM
Click to expand...
Click to collapse
Got it,it's because of a bad download or corrupt zip perhaps.Redownload the toolkit and also try with Color Os toolkit too.
If your device is recognized then there's no way you can't bring it back to life.
Mr.Ak said:
Got it,it's because of a bad download or corrupt zip perhaps.Redownload the toolkit and also try with Color Os toolkit too.
If your device is recognized then there's no way you can't bring it back to life.
Click to expand...
Click to collapse
Just redownloaded the tools and tried again.
Still the same issue, i also tried the color os toolkit like you suggested.
I have the same issue too, keep installing 8974_msimage.mbn again and again.
I'm still open for sugestions since the issue is still there
Right click msm tool, and RUN AS ADMINISTRATOR.
Problem solved.
kthejoker20 said:
Right click msm tool, and RUN AS ADMINISTRATOR.
Problem solved.
Click to expand...
Click to collapse
Although it is correct that you must run it as admin, this isn't the issue at all. There are phones that appear to be broken beyond the point where you can fix it with software.
MrBrainstorm said:
Although it is correct that you must run it as admin, this isn't the issue at all..
Click to expand...
Click to collapse
Yep, i always run tools like this as admin, the issue is something else in this case, but i wouldn't know what exactly
I may have found a solution/work-around to the problem described (in case anyone's still trying to unbrick a OPO after all this time). I must warn, however, that I really have no idea what I'm doing as I'm new to all of this, and have blundered through with no real understanding of what's going on, so pay heed at your own risk. It uses Qualcomm's QFIL program and Zyxxeil's OPO unbricking tool. I want give detail in describing the steps involved, so this will be fairly long.
***background***
My 64GB OPO has for the past couple of months almost always failed to get past the first 6-7 seconds of booting, and powered off before reaching the Cyanogen animation. It did the same when booting into fastboot and recovery, and at some point it stopped being able to access recovery at all. Very rarely it would boot, but pressing the power button while it was on would cause it to crash a few seconds later. I discovered that it would consistently boot properly if volume up were tapped while holding down the power button before it vibrates and the OnePlus logo appears, but this fix simply stopped working recently, and so it became impossible to turn the OPO on. Before giving up on it, I decided it would be worth trying the hard unbricking tool based on the ColorOS installer by Zyxxeil. However, I had the problem where the tool continually repeats the step of flashing 8974_msimage.mbn without progressing any further, to which nobody ever seemed to find a solution. I may have found a way to get around the problem, however.
Even though the procedure seems to have worked, the phone still shuts down after a few seconds as it did before (so I suspect my device has a hardware problem, possibly with the power button, and there's nothing that can be done for it). This means that I can't confirm that the fix actually works, but only that it appears to have worked. What it did was:
1) unbricked the phone - it probably wasn't even bricked before, but it definitely was after the installer hung on 8974_msimage.mbn ; it wouldn't respond to the power button at all afterwards. Applying the workaround allowed it to show signs of life again.
2) installed the COS11 fastboot. I'm not sure and can't tell whether the rest of the OS is there or intact, but the fastboot logo has changed from the newer small one to the bigger one from older versions.
***the problem***
The standard method for dealing with a hard-bricked OPO is to use the ColorOS tool as described in the "[GUIDE] [UNBRICK] Unbrick Oneplus One" thread and then flash Cyanogen, or to use Zyxxeil's tool which goes straight there. A common issue in both is that after pressing start, the tools repeat the step of flashing 8974_msimage.mbn , seemingly disconnecting the phone each time, and never progressing beyond that. This happened to me as well. This will happen if the tool is not run as an administrator, but for some people the same problem is seen even if it's run as an administrator. To the best of my knowledge, nobody has posted a solution to this problem, but some have suggested using alternative methods such as using QFIL (which I have gotten to work) or MiFlash.
***potential solution***
From what I understand, QFIL does the same thing as the unbricking tool, only not automatically. I directed it to use the files provided by Zyxxeil's tool, and it was then able to do something that unbricked the device as described above. This is what I did: (all on Windows 10, *not* using the original cable)
Required files:
1) Obtain the Qualcomm QDLoader driver. I used the the Qualcomm HS-USB QDLoader 9008 2.1.0.5 x64 driver from Zyxxeil's tool's thread (page 5, #48).
2) Download Zyxxeil's tool. I used the 64GB version. Extract DRIVER.iso and run setup.exe as described. I'm not sure whether this actually did anything and presume manually installing the driver in 1) overrides this, but I'm including this for completeness.
3) Download QFIL version 1.0.0.2 . I originally used 2.0.0.5 , but this did not work (it produced the error "unable to read packet header. only read 0 bytes", to which the recommended solution was to use an older version). This can be run from the extracted folder. Open it once, and then close it again - it seems not to behave properly the first time it is run.
Preparation:
4) Create a new folder, for instance on the desktop, and give it a short name. Copy and paste (or just move) the contents of the "OnePlusRestoreTool" folder from Zyxxeil's tool into here. This step is because QFIL supposedly doesn't like long folder names or locations (I'm not sure whether this is true or not but there's no harm in making sure).
5) Install the QDloader driver: (the PC may need to be disconnected from the internet for this stage, I think Windows may try to automatically download and install incorrect drivers)
>Open device manager, then plug the OPO into the computer. It should come up after a few seconds under "Ports (COM & LPT)" as something like QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Mine originally showed up as "Quectel QDLoader 9008". If it comes up as a malfunctioned device ("Unknown USB Device") under "Universal Serial Bus controllers", try holding the power button on the OPO down for a few seconds, or holding it down for a few seconds at the same time as volume up. If it's still not recognised, try rebooting the PC and repeating this step.
>Right click on the device as it appears in device manager, select "Uninstall device", tick the box saying "Delete the driver software for this device", and click on "Uninstall".
>The OPO will disappear from device manager. Unplug and then replug it into the PC, and after a few seconds it should be recognised again, perhaps as "Unknown USB Device" again, requiring the same procedure as above. It should now show up as QHSUSB_BULK under "Ports (COM & LPT)"
>Right click on the device and select "Update driver", then "Browse my computer for driver software". Paste in the file path for the folder containing the driver as downloaded above, which will be called "20561190_ed08f7139a2028da454a6668162f44ac311facc0" if using the driver specified above. Ensure "Include subfolders" is ticked, and click on Next. This should install the driver, and because it's signed, it shouldn't present problems often encountered in this stage. Your device should now be called "Qualcomm HS-USB QDLoader 9008", with (COM#) after it.
Fix:
6) Restart the PC, leaving the phone plugged in. Open device manager again. At this point, if it is detected as a malfunctioned "Unknown USB Device", do not try to remedy it as described above - leave it as it is. This is exactly what happened in my case.
7) Run QFIL.exe as an administrator. I don't know whether this is actually necessary to run as an administrator, but seeing as problems arise in the normal methods from not doing so, it seems sensible. If the device is listed as "Unknown USB Device", then QFIL should say "No Port Available".
8) In QFIL, click on "Browse" in the "select programmer" section. Navigate to the folder where the contents of Zyxxeil's tool were copied/moved to, and open "prog_emmc_firehose_8979.mbn". Lower down, click on "Load XML", which should give you three files to choose from. As I couldn't fully boot my OPO afterwards I don't know which one is most appropriate, but I have tried the procedure with each and it worked for all of them. Perhaps start with rawprogram_unsparse.xml and if that doesn't work try the other two. Click Open, then select patch0.xml , then click Open again.
9) Paying attention to the QFIL window, hold down power+volume up until the text changes from "No Port Available" to "Qualcomm HS-USB QDLoader 9008 (COM#). Incidentally, this will also cause the device to change from "Unrecognised USB Device" to "Qualcomm HS-USB QDLoader 9008 (COM#)" in device manager. I believe that this step starts "Qualcomm's debugging mode" as explained in Zyxxeil's thread, and this is necessary for the process to work.
10) Click on "Download" (below "Load XML"). QFIL should do its thing, and if nothing has gone wrong the phone might be unbricked at the end of the process. Disconnect from the PC and see if it works.
In my experience, where this step did not work it gave one of two errors:
"unable to read packet header. only read 0 bytes" - this happens on the newer version of QFIL, which is why I used the older one.
"unable to download flash programmer using sahara protocol" - this was the troublesome one. I believe it means that the phone is not in Qualcomm's debugging mode. This would probably be the case if, for whatever reason, the PC recognised the phone immediately as Qualcomm HS-USB QDLoader 9008, and so it wasn't necessary to hold power+volume up for the PC to recognise it properly. In my case the program ran properly the first time but was interrupted because I hadn't transferred all of the right files to the target folder. After I had done this and tried again, it gave this error. I fixed this by holding down power+volume up, while the device was recognised, until the PC made a sound indicating something had been plugged in. The next attempt to download was successful.
If the procedure doesn't work properly, it might also be worth using one of the other two XML files mentioned in step 9.
*** ***
Anyway, after hours of searching and trial and error, this unbricked the phone, with it becoming responsive once more to button presses, despite still having the original problem of powering down during boot. It seems to have the CM11 fastboot as expected, and I was able to have my PC recognise it in the short time it stays on using fastboot devices. Other than that, I'm afraid I don't know how successful this was, or how successful it would be for other people. I hope this is useful nonetheless!
hi follow this guide https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
lg optimus 3d won't turn on after baseband v20c flash and reboot, using the power button or power button, volume down and 3d key.
If I keep power and volume down while it's connected to the pc, then click power/volume down not sure the exact sequence, it starts making 3 short usb sounds, pause, 1 usb sound, then repeats forever
If I keep device manager open, in other devices with exclamation mark "OMAP4430" appears and device manager refreshes each time the sounds repeat, but it won't do anything else. If I pull the USB cable "OMAP4430" dissapears and sound loop stops
How can I fix this?
service sais I overwritten the bootloader. Baseband zip that I picked around here didn't say anything about bootloader... so far it made my phone inoperable. I'm trying to get this to work: https://forum.xda-developers.com/showpost.php?p=33650068&postcount=46
I unbricked it following this tutorial: https://forum.xda-developers.com/showthread.php?t=2246001
I'm pasting my post while I had some trouble with it:
Got P920 and I think I deleted my bootloader with a baseband zip: https://forum.xda-developers.com/op...ont-baseband-v20c-flash-t3654606#post73445561
I get stuck at step 7, can't find "LG port", basically what I get is fastloader mode, not downloader mode and LG port
then I get stuck at step 11, can't see "LG Cosmo"
If I pick step 13 and try to load gb bootloader it sais "waiting on device" forever, same as on fastloader trying to replace boots
What am I doing wrong?
EDIT1: Decided to do this on laptop (xp) not pc (windows 7). Now I see in ports section (which in windows 7 I don't at all) "LGE Bluetooth TransPort (COM15), not as in the tutorial but at least it's something... I set that to COM41 as instructed. Will edit here if I get any further
EDIT2: if I keep vol+ pressed it won't enter fastboot with os hacking tool. After it did, it found another hardware which I pointed to the only driver it finds in os hacking tool package, that is omap4430 which I already have installed, but this new one gives a code 10 this device will not work message, so I believe I'm stuck at step 11 again because I see no LG Cosmo in device manager.
EDIT3: I looked inside Device Manager > Android Device > OMAP4430 FastBoot USB Device, and is described in "Location:" as Location 0 (LG COSMO) ... which dissapears in a minute like while typing this Have no idea if this is what I'm suppose to get at step 11
EDIT4: seems that's LG COSMO after all because at step 13 after rebooting OS HACKING it did flash the GB BootLoaders (wrote a few lines of text)
...aaand ... drumroll ... it rebooted in my last rom (king's)
WOOOT! THANK YOU! THANK YOU! THANK YOU!
phone unbricked!
Now back to the problem of getting a proper rom that doesn't consume my battery idly in a day like 4.x unlike froyo (2.2.2) which can keep idle for a week, and that also gets a signal... tried them all except back to froyo (2.2.2) :-/
Click to expand...
Click to collapse