Well hello guys. I tried to flash cwm5 using the stock recovery on my gio running 2.2.1 and it seems to have failed the flash and whenever i try to enter recovery its just stuck on the initial samsung logo. For a few times i could have booted normally but after trying to enter recovery via rom manager im stuck on the samsung logo permanently. The only thing i can do is enter download mode but im running win8.1 and it seems this particular phone drivers dont like win8.1 so it errors out with device enumeration failed. I tried everything removing battery for up to 20 minutes, leaving it on for a while, reconnecting download mode repeatedly. Can anyone share some insight on this.
Edit: i managed to flash via odin on xp, fixed it.
Funny, I had the same exact problem and I tried to find a solution for a week. I accidentally flashed CWM6 for ace to my Gio and it got stuck to the Samsung logo. I got the error too on Windows 8.1. The problem is, well, Windows 8.1. It has something to do with how Windows 8.1 handles device validation. I would sen a link, but I don't have enough posts to do that. What I did was, I installed Windows 7 to a VHD-image with VirtualBox, copied the image to C:\ root and added it to the boot menu with EasyBCD. (Boot menu editor) I tried to connect the USB and it worked! So, try to flash a new recovery with a computer running Windows Vista/7/8, not 8.1.
Related
Guys,
I need any help possible although I fear I may be beyond recovery. Basically my Galaxy Nexus is bricked, I had been running 4.0.4 (IMM76D) on it. The phone is rooted and unlocked.
When switching the phone on, all I get is Google and the unlocked keypad. Will not progress further. I can boot into fastboot mode, and sometimes into recovery however although I have files showing on the SD, when I choose them I get a message declaring the path empty.
My main issue is that the handset is not recognised by my computer (running windows 7 and also since yesterday a dual boot of Ubuntu). This results in my Nexus toolkit and the AdamOutler tool being of no use as they do not recognize the device.
Any help/advice will be greatly appreciated as I'm at my wits end.
p.s. I have looked through other threads and even posted this message on one of the threads but recived no replies, hence the new post
Google splash screen = not bricked.
Power+DownVol from a power-off state...does this boot you into odin?
If so...flash an odin file.
You'll lose all of your data/sd contents =/ but at least it'll boot.
But the fact that you can boot into "fastboot" but not access it is bothersome to me.
Have you used fastboot before? (not a toolkit?)
It really SHOULD recognize...
In ODIN mode in shows the droid with a 'downloading...do not turn off target' message however i've left it in this state for hours and nothing happens, I cannot access it from my laptop either to push files to flash etc.
Data appears to be completely wiped from the handset
install the adb drivers http://pdanet.co/bin/PdaNetA302.exe (32bit win 7) or http://pdanet.co/bin/PdaNetA302x64.exe (64bit win 7)
and try fastboot devices after it has been installed.
I can't get into the device to activate USB debugging though?!
try this then.
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Wait...
Are you just leaving it in odin mode?
You have to plug the phone in and use the program "ODIN" to flash a stock image.
Just making sure!
Hi guys,
Just got my new note 2 (international-n7100). I first updated to jb 4.1.2.
Then rooted the phone after several tries to detect drivers (install/uninstall etc).
After that installed rom manager and ROM toolkit pro.
I never achieved to boot in cmw through ROM manager or by using the 3 keys combination, I keep getting the default android boot.
Tried everything to reflash cmw with adb or Odin but now my PC says drivers are not recognized because of a "corrupted attempt to connect the device before" (use win 7, changed usb ports, tried different pc).
I uninstalled every drivers, kies and reinstall either directly from Samsung or using toolkit for note 2.
Nothing...
Please help, I need to get my phone conected to the PC so that I can boot in cmw and backup my ROM.
Thanks
hi,
i have an crashed b5510, but it doesn't boot anymore.
i do have acces to download/recovery mode, but it doesn't stay connected to usb (i hear the connect sound of windows but it immediatly disconnects) so i downloaded gingerbread autoroot file en transferred it tothe external sd, however when i try to update the zip file in recovery modethe phone reboots itself without updating. but when it stands stable not touched it remains in recovery mode. is there anyone who has experience or knowledge of this issue?
i've installed:
Samsung kies
additional samsung driver
odin 3.7
but nothing seems to work
thanks in advance
Greettz Kevin
Hey there guys!
Recently I wanted to get some custom ROM on my brother's Gio. It had stock Samsung software on it, did a factory wipe in recovery, worked perfectly, then I installed CWM in the orignal recovery from the SD card - didn't root before. Since then I can't boot into Recovery, however Android booted up. I tried to use some apps in software to get rid of this problem, but ROM Manager said the device is not supported, then I tried another one called Rashr, which had a question relating to recovery I guess instantly on the app's startup, I hit "Reboot" since then the phone is bricked. If I turn it on with just the power button, it shows the Samsung logo, stuck in a bootloop. I can't access recovery, only dumpram, and Download Modes. I tried fixing this with reinstalling the stock stuff through Odin, but the software doesn't detect the phone. Tried installing Kies, standalone USB drivers, multiple Odin versions, different cables, ports, different computer, nothing worked. When I connect the phone to my PC it plays the "device connected sound" but I got a message, that it's an unidentified device. Went into Device manager, where it recognizes it as a Samsung USB device, with the yellow triangle. Tried updating the driver manually from the manufacturer's list, uninstalling then reinstalling the drivers with no luck. Also I tried cleaning the USB port of the phone, still nothing.
The computers I've tried are running Windows 8.1.
Please help me, I think I've tried everything still the device is bricked.
I have same problem.
did you fix it ?
weLL ,sad to say it but ,its neither worth the effort,time or my typing these letters up here to remind you ,that it's neither the end of days or expensive to buy something this side of the stone aGe ! have fun but not with that one ;(
https://forum.xda-developers.com/galaxy-gio/orig-development
search here, download mode should be enough
Greetings every one ..
I have a half dead Oneplus 3 Unlocked + Rooted
here is my problem
there is no OS in it and i flash TWRP many times via ADB and wont boot to it
and i tried to flash the stock recovery V2.0 and done successfully
the sideload mode Recognize my OP3 but when i try to flash the Oxygen Rom it Gives me cannot read
also i tried the Unbrick Tool when the device is connect it showing me Qualcomm hs-usb qdloader 9008
but when i power up the tool as administrator it showing me (no device)
see here : https://www.youtube.com/watch?v=BIbagVAXJJk
Thanks .
on the unbrick guide try method 2 but completley power off the device and count to 10 when holding the vol up button THEN plug the device in. i had that issue also. if you get errors or for some reason it dosnt show up again try on a diffrent pc it will work
Try method 2. BTW "cannot read" error has to do with faulty ADB drivers, get the platform ones
I did instal the right ADB drivers in fact
still no luck
The ones from platform tools? Since that "cannot read" error has nothing to do with your device. Have you tried renaming it? Rebooting your PC? Last one did wonders for me for some stupid reason.
Hi,
I also had this message of "can not read" in sideload mode, this problem often happens with Windows 10, so I used Windows 7 on another pc and it was OK.
I tried Windows 10 & 8.1 & 7 & XP
still The same problem
What if you flash Twrp and boot into it? Then u can adb push the filemm
I tried via fastboot and its done right
but when i reboot into the new TWRP recovery its stuck in the boot oneplus as same like the Video shown up
book an appointment with oneplus live chat so a service tec can fix it and if they ask if it was rooted say no
Hi,
If you access TWRP, install the Official Oneplus Recovery 4.0.2
In TWRP click "intaller" then choose "install image" and select the file you will have to copy to the phone in recovery mode.
Then restart in recovery mode, choose english, then "adb sideload mode"
From there you should be able to flash your phone with an official Nougat zip.
Do the under windows 7.
It is necessary to install the Oneplus USB drivers and ADB tool on your PC before any manipulation.
Finally I solved the problem
like i said B4 my phone wont boot into TWRP by any chance
i traid all the Officials TWRP one and they stuck on the boot image or power the phone off
i flashed a modified twrp (blu_spark 3.0.3-x) thanks for this beautiful smart man eng.stk if im not wrong
and thank you all for the help
i had similar issue...with several phones.. download Malwarebytes trial version and run it...i had a few stealth root tool kit viruses.causing my system to have a hiccup....