After tying and failing to update my sky im-a650s via online self update I'm now stuck at bootloader. The phone can still be detected by sky's online update page but as soon as the activeX application starts to connect to my phone internet explorer crashes. It can still be detected by computer but i cant access it via fastboot and adb to try to install rom. any help would be greatly apreciated.
things i tried to do:
tried to update using different os/computer
tried different key combinations to invoke recovery and fastboot
tried different drivers
Related
Hey guys,
I tried flashing stock JH7 after disabling lagfix. When I tried to reboot, I ended up in a boot loop and the phone kept getting stuck on the "AT&T World Phone" screen. I can access stock Samsung recovery and Download Mode, but, although I tried numerous methods, Odin3 doesn't recognize my phone in Download Mode. I also don't have any update.zip or backup on my phone that I can flash in stock recovery.
Is there any way I can fix my phone without Odin3? If not, how can I get Odin3 to work on my computer? I'm running Windows 7 HP x64 on my laptop, and I have adb installed, but can't access adb shell for some reason.
I searched numerous threads but couldn't come up with a solution. Please help!
psai said:
Hey guys,
I tried flashing stock JH7 after disabling lagfix. When I tried to reboot, I ended up in a boot loop and the phone kept getting stuck on the "AT&T World Phone" screen. I can access stock Samsung recovery and Download Mode, but, although I tried numerous methods, Odin3 doesn't recognize my phone in Download Mode. I also don't have any update.zip or backup on my phone that I can flash in stock recovery.
Is there any way I can fix my phone without Odin3? If not, how can I get Odin3 to work on my computer? I'm running Windows 7 HP x64 on my laptop, and I have adb installed, but can't access adb shell for some reason.
I searched numerous threads but couldn't come up with a solution. Please help!
Click to expand...
Click to collapse
Have you tried reinstalling your drivers?
My laptop won't recognize my phone anymore for the Android UMS drivers so I've been using my desktop to flash using Odin.
I've tried, but Odin only recognizes my phone in recovery mode and doesn't recognize it in download mode.
Fixed at last!
I finally fixed my phone! I found out that I was using the wrong USB drivers -_-
I installed the correct drivers, and voila, my phone was recognized by Odin3
Sorry for the n00b error
Hi all,
I've had to root my HTC One S for school recently (yes, really), but now I can't install the update that's been released.
When I start the update my phone reboots and enters Clockwork..
I've been trying to unroot my phone, but there's a lot of (different) information out there, and I can't seem to put my finger on it.
For starters, I have no idea what RUU is and I have no idea which stock img I need, since their are more than 20 of them out there..
Can somebody please guide me through?
Thanks!
Tom
Edit: I can't seem to get a Android 1.0 USB driver working.. If I type adb devices it lists no devices.. I've tried like 5 different drivers but none are working.
Edit: My normal USB driver is working. ADB devices returns my device, but when I try to flash the recovery in normal mode, it just says 'waiting for device'.
Hi there,
I've read every kind of threads here and no one works for me. I rooted my Samsung GT-I9000 and all worked well, then the phone started acting crazy, my root was gone and when I boot the phone I come to the usual screen where you enter pincode but after that the popup screens start, multiple popups saying that twlauncher crashed, media, acore etc.. so I cant get to the screen where I can enable usb debugging. I can enter the stock recovery and my PC can contact the phone, but when I press vol down + home + power so I get the download mode the PC cant find the phone, not in win7 or in Linux. I have tried every kind of driver there is for Samsung but no one works that make it possible for the PC to find the phone when it is in download mode, win7 list it under "unknown device" and NO driver at ALL works so win7 can reqonize the phone. I've tried installing Kies how many times I dont know and uninstalling, updated SDK, uninstalled every USB driver and even the hubs and installed them again, updated win7.. what can I do to flash the phone!?!? Because Odin, no matter old from new; cant find the phone in DL mode, same with linux. And in stock recovery, I wiped cache and data but the problem is still there when I enter the OS after enter my pin...
How can I flash my phone without PC finding the phone in DL mode and no USB debugging enabled? Or how to flash CWM so I can flash a ROM from SD? Please help!!
At first try another PC with Winsows or use another USB cable.
About recavery-try to find temperery recovery or cwm,that flash from recovery.
DeMaCr said:
At first try another PC with Winsows or use another USB cable.
About recavery-try to find temperery recovery or cwm,that flash from recovery.
Click to expand...
Click to collapse
As I wrote, my desktop is under Linux and the laptop under Win7 and none can reach the phone, both computers can only detect the phone in Recovery mode, but the laptop under Win7 only detect the phone as offline, Linux on the other hand can reboot phone into recovery from recovery, to download mode and reboot normal. Already tried to use Ubuntu 13 Live and it cant detect the phone in DL mode either. And tried different cables also. And if I find a recovery or CWM, then what? Dont I need to get phone into DL mode to flash something?
But in Linux I've got a small breakthrough, Heimdall can detect the phone know, but fails to flsah anything. Maybe wrong files or something..? But anyhow, if Heimdall now can detect the phone and it couldnt before; know I just need the right files to flash.
Just find a friend who owns Windows desktop/ laptop, download stock from Sammobile, flash stock via Odin. If not, try Odin mobile...
Been searching on these forums for the last 6 hours, trying a number of different solutions, and I haven't found an answer yet. I am going to go back through step-by-step through the night in my next post unless someone else appears with a solution, first, starting with using fastboot to flash the firmware images again.
I had attempted to install CWM 12 on my LG G2 D80020u today. It didn't work, but when I attempted to recover, I hit a wall.
I found a few solutions for my problem, but they assume Windows PC, and I'm running Ubuntu Linux.
Currently:
If I reboot normally with the device unplugged, I get the LG logo with "security error"
I CAN access fastboot and erase/flash various images, but none have solved my issue yet
I CAN get to Download Mode, but my linux computer cannot see the device to transfer files.
I CANNOT use ADP. I could earlier, but now when I type "adp devices", my terminal displays no devices.
If I run ./ioroot.sh, I get "Waiting on ADB detection" and then a stand-still.
Any ideas? Thanks for all of the help.
I was recently trying to update my Acer Iconia A500 and it appears I made a mistake...I had my tablet rooted and I was using the Acer recovery tool to try to use cwm to update. I was running stock OTA ICS. Acer recovery tool warned that my bootloader should be updated to version 1.03 (Acer recovery tool said I had 0.03.12-ICS). I was trying to update the bootloader and initiated a reboot and I haven't been able to boot since. When I try to boot, I see "boot verified failed...". I've tried several fixes from what I've found searching. The hard reset with power/volume/screen lock does not work and I still see the boot verified failed. I tried copying every version of update.zip I could find to a microsd card and booting by holding power+volume down - same result. If I boot by holding power+volume down+screen lock I get a message saying "bootloader: v.03.12-ICS: Starting Fastboot USB download protocol", but nothing happens. If I plug the tablet into my computer in this state, it makes a noise recognizing a connected device, but I cannot view the drives (drivers are current) - also in this same state if I use the list devices command in adb fastboot no device is displayed.
Any feedback or advice would be greatly appreciated. I'm not experienced and I am simply trying to piece together information from various sources. Normal solutions would be hard reset or booting with update.zip, but neither are working.
XDA Visitor said:
I was recently trying to update my Acer Iconia A500 and it appears I made a mistake...I had my tablet rooted and I was using the Acer recovery tool to try to use cwm to update. I was running stock OTA ICS. Acer recovery tool warned that my bootloader should be updated to version 1.03 (Acer recovery tool said I had 0.03.12-ICS). I was trying to update the bootloader and initiated a reboot and I haven't been able to boot since. When I try to boot, I see "boot verified failed...". I've tried several fixes from what I've found searching. The hard reset with power/volume/screen lock does not work and I still see the boot verified failed. I tried copying every version of update.zip I could find to a microsd card and booting by holding power+volume down - same result. If I boot by holding power+volume down+screen lock I get a message saying "bootloader: v.03.12-ICS: Starting Fastboot USB download protocol", but nothing happens. If I plug the tablet into my computer in this state, it makes a noise recognizing a connected device, but I cannot view the drives (drivers are current) - also in this same state if I use the list devices command in adb fastboot no device is displayed.
Any feedback or advice would be greatly appreciated. I'm not experienced and I am simply trying to piece together information from various sources. Normal solutions would be hard reset or booting with update.zip, but neither are working.
Click to expand...
Click to collapse
Hard/factory reset would have been my first answer too.
Is your issue similar to this one: Boot verified failed after update PLEADE HELP?
Maybe you can unbrick it like described here: [GUIDE] How to unbrick Acer Iconia A500.
And if you need further help, please register on xda and ask in the thread directly.
Good luck !
Thread closed. Thank you!