Related
Hi,
So I just purchased a Samsung Galaxy S II, and I've been trying a few different ROM's found on this site. The last thing I did was actually revert back to a stock Samsung Kernel and firmware. This worked fine, but it unrooted my device, which I knew would happen, but now I'm not able to root it again because when I put the device into download mode, ODIN, or better yet, my computer won't detect the device.
I have all the drivers installed, and I also deleted them all, and Kies, and started from scratch again after searching XDA for similar issues.
I don't believe this to be a driver issue, since I was able to root my device, and swap roms before I went back to the official kernel and firmware. I'm with Bell in Canada, so the versions I went back to were not the official Bell versions, since Samsung has not made them available.
I have a Mac, but I've been using Windows 7 and Odin under VMWare. I can connect my device to either OSX, or Windows 7 when the device is not in download mode, and everything works fine, and Odin detects the device (Not that that does any good of course)
When I connect the device under download mode, the Mac detects the device and asks me if I want to connect it to my Mac, or to Windows (As it should) but no matter which one I select, neither OS acknowledges the device after that point, where as when I'm not in Download mode, both OS's detect the device fine.
After all my troubleshooting with my computer based off of what I found online here, The only conclusion I have left is that there is something missing on the device that allows it to be found under download mode, but that aspect of all this is beyond my current skill level.
Anyone have any ideas?
Are you pressing the Volume Up button to continue in Download mode? Besides, Virtual machine isn't recommended I think.
Yes, Once the Custom ROM warning comes up, I press the Volume up button to continue.
That wasn't even necessary on the Stock Bell ROM. The warning didn't come up at all.
VM has been working fine up until now, so I don't think that's the problem, but I have been thinking of trying this on my old laptop that runs on windows if nothing else pans out.
Scott56 said:
Yes, Once the Custom ROM warning comes up, I press the Volume up button to continue.
That wasn't even necessary on the Stock Bell ROM. The warning didn't come up at all.
VM has been working fine up until now, so I don't think that's the problem, but I have been thinking of trying this on my old laptop that runs on windows if nothing else pans out.
Click to expand...
Click to collapse
Have you found anyway to Make Odin recognize to phone in download mode?? Im still struggling with that. my phone is on stock kernel and not rooted yet, ODIN finds it fine when the phone is on and USB Debugging is on, but once I put the phone on download mode it wont recognize it, I dont know why..
Could it be because of the ''SAMSUNG Mobile MTP Device'' driver failed to install correctly??
all other drivers are installed correctly.. I have tried to get the driver mentioned above to install correctly but it fails every time, with USB debugging on and off, i have wiped the phone and installed Kies and the drivers several times, Im clueless right.. anyone have any idea please help??
I myself am also suffering from this problem. However, USB seems to function fine while the phone is booted up or in recovery (For ADB). I'm wondering if necessary files may have become corrupted or deleted in reference to USB drivers (phone side mind you) that are used in download mode.
edit: It's also recognized in recovery mode.
Even if it can't be fixed I'd still like to understand why.
-Simply D
was looking for help on this and saw this thread, same problem too..
Connects to Odin and Kies fine when switched on "normally", can use USB mass storage mode Etc.
comes up with a USB device has malfunctioned message on PC when I connect USB cable when switched on and in download mode
EDIT:- just to add, if I try upgrading firmware via Kies it gets to the point where it switches the phone to download mode to upgrade it and has the same issue even with an official upgrade
Figuring download mode is outside the normal boot procedure, I hoped on an off chance that pulling my battery and sim for a few minutes would reset it. It did indeed. Download mode is now functional again, just to be certain I tested it right before pulling the battery to make sure it was still broken. And multiple flashes and reboots afterwards seem to confirm that it has returned to normal.
Anyone else who solves it with this method, please report back.
-Simply D
SimplyD said:
Figuring download mode is outside the normal boot procedure, I hoped on an off chance that pulling my battery and sim for a few minutes would reset it. It did indeed. Download mode is now functional again, just to be certain I tested it right before pulling the battery to make sure it was still broken. And multiple flashes and reboots afterwards seem to confirm that it has returned to normal.
Anyone else who solves it with this method, please report back.
-Simply D
Click to expand...
Click to collapse
Tried this and it didn't work for me :/ going to give it another try later, thanks for the suggestion either way
I have been posting (and have had some nice people try to help) in the How to Recover Fascinate from any Brick thread for about a week and can't seem to find a solution. I have also searched the internet high and low looking for a solution with no success. Hopefully someone here has had the same issues and can point me in the right direction.
I rooted the Fascinate using a one click method and was able to get a Titanium backup but could not get into the proper recovery to do a system image. Stupidly, I flashed SP Recovery from within ROM Manager. From that moment on I when the phone is turned on it gets to the "Samsung" screen and locks.
I did my research and found out all I needed to do to fix is install ODIN and reflash the stock ROM again. The problem is that ODIN will not recognize the phone. I start ODIN, pull the phone battery, plug the phone into USB cable, push volume down to get the phone into download mode (Yellow Triangle). I keep getting USB Device Not Recognized errors from Win 7 (64-bit).
I tried installing Heimdall to load the correct drivers but it doesn't see the device either. I can connect my Droid or Droid 2 and Heimdall sees immediately so I know it is not a problem with the software or cable.
I have tried to install the correct USB drivers (even the ones listed on this site). I tried installing Kies and it doesn't see the phone either.
Since the phone is looping at the "Samsung" screen I can't change any settings in the phone as some have suggested. I really do not have any more ideas other that to use this phone as a very expensive door stop. Hopefully, someone here can help. Thanks in advance!!!
pscpa said:
I have been posting (and have had some nice people try to help) in the How to Recover Fascinate from any Brick thread for about a week and can't seem to find a solution. I have also searched the internet high and low looking for a solution with no success. Hopefully someone here has had the same issues and can point me in the right direction.
I rooted the Fascinate using a one click method and was able to get a Titanium backup but could not get into the proper recovery to do a system image. Stupidly, I flashed SP Recovery from within ROM Manager. From that moment on I when the phone is turned on it gets to the "Samsung" screen and locks.
I did my research and found out all I needed to do to fix is install ODIN and reflash the stock ROM again. The problem is that ODIN will not recognize the phone. I start ODIN, pull the phone battery, plug the phone into USB cable, push volume down to get the phone into download mode (Yellow Triangle). I keep getting USB Device Not Recognized errors from Win 7 (64-bit).
I tried installing Heimdall to load the correct drivers but it doesn't see the device either. I can connect my Droid or Droid 2 and Heimdall sees immediately so I know it is not a problem with the software or cable.
I have tried to install the correct USB drivers (even the ones listed on this site). I tried installing Kies and it doesn't see the phone either.
Since the phone is looping at the "Samsung" screen I can't change any settings in the phone as some have suggested. I really do not have any more ideas other that to use this phone as a very expensive door stop. Hopefully, someone here can help. Thanks in advance!!!
Click to expand...
Click to collapse
Control Panel/ User Account/ User Account Control settings- set to- Never notify- restart computer.
Should recognize phone. Reset to default when done and restart. Windows crap!
Thanks but this setting has always been set to "Never Notify"......any other ideas...please
I don't know nothing about it but the guy said " reset to default and restart (again)??
Sent from my SCH-I500 using xda premium
Followed the directions exactly. I think the OP wanted me to reset to default after I was done flashing. This is so strange....I figure if the people on XDA can't figure this out the phone is doomed.
Have you tried a different USB plug on the computer? Or a different USB cord? Or a different computer?
Sent from my SCH-I500 using XDA App
schu9120 said:
Have you tried a different USB plug on the computer? Or a different USB cord? Or a different computer?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I had to use a laptop to access my Fascinate because my desktop wouldnt even show it as unrecognized hardware, it was like it didnt even exist... I went in device manager and uninstalled all my usb devices, rebooted with everything but mouse/kb unplugged, installed SDK drivers for Nexus S, rebooted again (probably not needed but better safe than sorry) and I can now Odin into my phone... Hope this helps ya man... sucks bricking a phone
The Heimdall drivers won't work. Kies won't recognize it if it won't boot. There should be an option in Kies to install the driver. Drop down box in the top left corner. Did you try to install your driver that way?
have you installed the driver yet? samsung driver?
So I tried the S off and I failed a couple of times with the wire trick. My timing was more than likely off. I re-ran the program and tried again. After it rebooted to check my alcohol level like it had the time before it could not find the device. It just kept counting to 45 secs over and over and kept asking me to check device drivers and adb and fastboot. And it worked fine before. Before I even started I checked adb devices.
Now the phone boots to the juopunutbear screen and it when I try to run the program it says that the device is not detected. So I rebooted in hboot and tried to run some adb or fastboot commands and the phone is not detected at all. I tried my mac too and no luck. I tried a different usb cable and no luck either.
So no I cant push anything to my phone and its just reboots to the juopunutbear screen. I think I bricked it. I dont know what to do. I cant push files to the phone. Any help?
DeviceSettings said:
So I tried the S off and I failed a couple of times with the wire trick. My timing was more than likely off. I re-ran the program and tried again. After it rebooted to check my alcohol level like it had the time before it could not find the device. It just kept counting to 45 secs over and over and kept asking me to check device drivers and adb and fastboot. And it worked fine before. Before I even started I checked adb devices.
Now the phone boots to the juopunutbear screen and it when I try to run the program it says that the device is not detected. So I rebooted in hboot and tried to run some adb or fastboot commands and the phone is not detected at all. I tried my mac too and no luck. I tried a different usb cable and no luck either.
So no I cant push anything to my phone and its just reboots to the juopunutbear screen. I think I bricked it. I dont know what to do. I cant push files to the phone. Any help?
Click to expand...
Click to collapse
I'm not sure what's happening with your computer not seeing the phone, but if you have a microsd adaptor you could get a stock RUU onto your card and flash back to stock.
Edit: or just your boot.img. If you can get into hboot you're not bricked.
Part fix
As previous poster said, put a PH...IMG with boot on it and you'll be able to boot up again. Yours is third phone reported here with USB problem after failed S-0ff.
I can boot my rom, but no radio or wifi, No charging, and no computer can see it for fastboot. Hoping for cure soon.
Thanks guys. I am downloading an RUU now. Hopefully it works. I hope the usb connection is not fubar'd ...but i took the risk so its on me.
Same thing happened to me. I just finished uninstalling HTC Sync and Android SDk, then reinstalled both. Now the drivers are working properly, and computer sees my phone again. This should help.
***edit: this process helped with my computer finding software drivers to connect phone to computer. Before- "Windows could not find drivers for Android device" (device manager in windows)
I could never get it to work in the first place. Cleanflash finds and flashes to it just fine but the s off just can't see my phone once it reboots.
Sent from my ADR6425LVW using XDA
DeviceSettings said:
Thanks guys. I am downloading an RUU now. Hopefully it works. I hope the usb connection is not fubar'd ...but i took the risk so its on me.
Click to expand...
Click to collapse
If the phone is rebooting to the screen with the arrow when you press power to enter fastboot then try going to recovery, your regular recovery will probably not show up but another stock hboot menu will. Then try selecting fastboot there and see if you can run fastboot commands without rebooting to arrow screen.
Sent from my HTC Vigor
Success getting it to reboot with the boot.img from the rom I was running....But unfortunately the usb is fried. Can not charge the phone or connect to a computer. So I guess that is another potential risk with using this method.
Ouuuuch :/
Sent from my ADR6425LVW using xda premium
Yeah sucks. I'm trying everthing I can, but its looking more and more bleak
DeviceSettings said:
Yeah sucks. I'm trying everthing I can, but its looking more and more bleak
Click to expand...
Click to collapse
Warranty!
(edit: kidding, no need for a ****storm)
Hello,
I have probably bricked my Huawei Vision by rewriting boot image.
However, I can connect* it to PC and it sees my phone as "Huawei Handset" (same with Windows and Linux). But Windows misses its drivers (non-bricked phone worked); Linux seems to work. No OS can connect to it using default (downloaded) ADB, nor Fastboot, nor SoftwareUpdateTool.
Its PCI ID is 12d1:c002.
How could I reflash it? I would prefer the ways without disassembling the phone.
Thanks
----How to boot the phone, so you can connect it to PC:
1. turn off my phone completely (vol up + power for 10 seconds - release power for a seconds and repeat it once again)
2. prepare USB cable, so you can connect it in few seconds
3. hold vol down + power and after ~1s, connect USB cable (still hold vol down)
4. when Huawei logo appears, release both buttons - your phone is connected now
petoxxx said:
Hello,
I have probably bricked my Huawei Vision by rewriting boot image.
However, I can connect* it to PC and it sees my phone as "Huawei Handset" (same with Windows and Linux). But Windows misses its drivers (non-bricked phone worked); Linux seems to work. No OS can connect to it using default (downloaded) ADB, nor Fastboot, nor SoftwareUpdateTool.
Its PCI ID is 12d1:c002.
How could I reflash it? I would prefer the ways without disassembling the phone.
Thanks
----How to boot the phone, so you can connect it to PC:
1. turn off my phone completely (vol up + power for 10 seconds - release power for a seconds and repeat it once again)
2. prepare USB cable, so you can connect it in few seconds
3. hold vol down + power and after ~1s, connect USB cable (still hold vol down)
4. when Huawei logo appears, release both buttons - your phone is connected now
Click to expand...
Click to collapse
mine is not working i think mine is bricked completly
bricked my mobile...Help!!!!
I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
sivakarthick said:
I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
Click to expand...
Click to collapse
The thread called 'Problem with huawei vision' still seems to be active. You may want to try asking your question over there.
Huawei (u8850) unbricked
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
how to turn off huawei u8850 completely
hey,could you please help me.i am stuck on huawei logo.how can i turn off the phone completely.i cant remove the battery obviously.the above trick isnot working.plz.help me
bikeshrt said:
hey,could you please help me.i am stuck on huawei logo.how can i turn off the phone completely.i cant remove the battery obviously.the above trick isnot working.plz.help me
Click to expand...
Click to collapse
it's actually not difficult to remove the battery...
but i read somewhere the 'volume-up + power for five seconds' will hard restart, but re-press power immediately will then turn it off (not tested myself; the back of mine is already off at the moment.)
Anyone here interested in developing a 3.x kernel? seems other phones with msm8255 have successfully got one...
u8850 power off
btsimonh said:
but i read somewhere the 'volume-up + power for five seconds' will hard restart, but re-press power immediately will then turn it off (not tested myself; the back of mine is already off at the moment.)
Click to expand...
Click to collapse
now i have tried it, and no success.
However, what i have found to work - if your non-boot is actually booting the kernel, but failing to initialise the phone, then you can still use adb with it... I ran adb shell, and then used 'poweroff' to power off my phone, which then meant i could boot into CWM recovery....
i HAVE THE SAME PROBLEME? PLEASE CAN U HELP ME TO SOLVE IT BY GIVING ME DETAILS.
it is working, thank you bro
btsimonh said:
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
Click to expand...
Click to collapse
it is working thanks bro
Stock rom download plz.
btsimonh said:
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
Click to expand...
Click to collapse
HOLY GOD! F**K ME!!! I finally did it! THANKS A LOT, BRO! YOU'RE AWESOME!!!
Hi, I was looking everywhere since yesterday but can't find a solution. I had cwm + twpr + lollipop cm12. I've decided to back to stock, so as allways: driver, b2cApp, kdz, v20h and v10a, usb, s/w mode, xml parser, shhtp, etc... Standard offline kdz method. But during flashing I stuck on 15% and get the info that my phone anad pc are not connected by usb cable, I tried changing usb ports at pc, reinstaling everything, but I have still the same error. If that woldn't be much enough I ****ed something up and I think I don't have any recovery right now
I can put my phone in s/w mode but I stuck on 15% with usb not connected error.
I can put my phone in fastboot mode but my pc does not recognize it, its just pluging in and out it from windows.
I can put my phone in stuck on LG logo 'mode'
Any help? How to unbrick it? How to flash stock or at least some custom recovery? Of course unlocked bootloader. Please help me :crying:
Key it ****ed up even more.
When kdz show me to connect my cable i clicked retry, plugen cable out and in, kdz found my device, and go to step 2. In half way I had again the same error, so again clicked retry, plug out, plug in. Again founded my device, when I had downloaded 100%, same situation. founded my device, log that tool is extracting kdz and nothing. Waiting about ~1,5h, nothing happend, so I diconected cable. In that moment kdz go to third step and I get windows force close for not repodnig app kdz. I said a loud **** and started again. Phone has not been found anymore by kdz. After a few tries, booted to fastboot, and connected to computer. It has been found as Google Fasbtoo USB, no way to update driver to fastboot. I disconected phone and decided to try again with s/w but nope. S/W not turning on anymore (with or without battery). Fastboot not turning on any more. Just LG logo, when I'm connecting device to PC it is sometging pluging in and out but nothing showing in device manager
Any ideas? Please!
I have the SAME problem with my (now old) LG... I read more than 20 tutorials for getting back to stock and nothing
Sent from my GT-I9205 using XDA Free mobile app
I triend on clen frsh windows I get OMAP device, fastboot is finding my device but wont start fastboot mode in my phone, when trying to flash cwm I get security error and still no s/w mode So I'm affraid that we have to say goodbay to our L9
What's more:
1. Can't find orginal p760 recovery, tried to flash p769 and I get wird effect, after LG logo screen looks like broekrn, some color stripes and all display going to white, then turn off.
2. Using fastboot and choosing options wit u-boot making my phone turning to LG logo with no security error, still no s/w, fastboot or recovery mode.
3. Using option 1 (1. Fastboot) from the fastboot tool is making my phone turnig black screen and nothin more, no even LG logo.
Please can anyone help us?