Hey,
since two days i experience some serious problems with my Galaxy W, dont know if its bricked or not.
I have flashed CM 10.1 and the newest Clockworkmod recovery, after that i was able to charge my device and connect the device as mass storage with my laptop. But this was just possible for ONE time.
Since then, i havent been able to charge it nor to connect it with my laptop. Funny thing is that my brother wasnt able to charge the battery in his Galaxy W, but i was able to charge and connect with his battery, but again just for ONE time (too bad that i disconnected before flashing the stock rom). When i try to connect my device with the charger, it just starts CM but wont show the charging symbol nor would charge once loaded CM.
Do you guys have any idea what has happened to my device?
So is there any chance to get the stock recovery and Rom back on my phone if i cant use odin or adb? I dont think that i can send it in for warranty under these conditions.
A solution might be buying a new battery so that i can connect it for one time to odin to flash the stock recovery...
sdfee said:
Hey,
since two days i experience some serious problems with my Galaxy W, dont know if its bricked or not.
I have flashed CM 10.1 and the newest Clockworkmod recovery, after that i was able to charge my device and connect the device as mass storage with my laptop. But this was just possible for ONE time.
Since then, i havent been able to charge it nor to connect it with my laptop. Funny thing is that my brother wasnt able to charge the battery in his Galaxy W, but i was able to charge and connect with his battery, but again just for ONE time (too bad that i disconnected before flashing the stock rom). When i try to connect my device with the charger, it just starts CM but wont show the charging symbol nor would charge once loaded CM.
Do you guys have any idea what has happened to my device?
So is there any chance to get the stock recovery and Rom back on my phone if i cant use odin or adb? I dont think that i can send it in for warranty under these conditions.
A solution might be buying a new battery so that i can connect it for one time to odin to flash the stock recovery...
Click to expand...
Click to collapse
Your usb driver migh got corrupted.
This happened to a friend with his S2 after ubgrading his rom via OTA. He also coudn´t connect via USB nor charge his phone. Funny thing was I could charge his phone at my usb connection, but not with my charger. Lucky him it was Samsung stock rom, so Samsungs Service Center reflashed his rom and so fixed this issue. They also told him his usb drivers got corrupted during the ubdate via OTA.
What you can try is for example to download CM9, put in on your SDCard and flash it from there. If that doesn´t help try reflashing CWM.
Related
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Sorry to hear that. This is something I learned (second hand, thank god) when I had my Galaxy S1. Odin can simultaneously be the best and worst tool you use.
Sent from my Galaxy Nexus
ericaraj said:
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Click to expand...
Click to collapse
There is a chance it's not totally bricked, that happened to me on an other samsung device while i was flashing with odin. U pulled the battery too early.i also had that black screen with the yellow pc and exclamation mark, try another usb port in ur pc and try to flash again with odin, if not, take the battery out and keep it out for a while (i don't know, 30min for example) then try odin again... u should be able to enter download mode somehow despite the screen u got now.
Sent from my Galaxy Nexus using xda premium
ericaraj said:
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Click to expand...
Click to collapse
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
rayiskon said:
There is a chance it's not totally bricked, that happened to me on an other samsung device while i was flashing with odin. U pulled the battery too early.i also had that black screen with the yellow pc and exclamation mark, try another usb port in ur pc and try to flash again with odin, if not, take the battery out and keep it out for a while (i don't know, 30min for example) then try odin again... u should be able to enter download mode somehow despite the screen u got now.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
iCaptivate said:
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
Click to expand...
Click to collapse
I had a feeling that it wasn't truly bricked, but since my phone's USB driver (or whatever aspect of USB data transfer) was malfunctioning I couldn't do anything about it. I think of it this way: if in that state my phone had a 5% chance of being recognized by Odin, and if my phone already had less than a 20% chance of being recognized before the soft-brick, then I had a 1% chance or less that it would even show up in Odin and even lower odds at a successful flash. Regardless, Verizon agreed to send me a warranty replacement.
iCaptivate said:
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
Click to expand...
Click to collapse
Same here with the vibrant. IIRC there was a special way to get your phone to recognize Odin when it happened. Something like plugging in the phone to the computer and then pulling the battery. Odin even worked when I borked a flash and the screen wouldn't even turn on. I would think the nexus could be brought back similarly.
But if the USB port is on the fritz I'm not sure I would want to bring it back.
As far as I'm concerned Odin is the worst thing you can hook up to your devce. No single program has bricked more devices than Odin.
______________
Just Flash It !!!
on my old SGS1 there was chance get back bricked device by method called "JIG"..(its hardware way get back download mode) but i dont study it more...
I don't think its bricked, I once restore my phone from a black screen that Odin still recognized as download mode. The drivers can get iffy, do you have a third comp that you can install fresh drivers on. Also is your USB jack on the Nexus loose? Sometimes it really is due to your PC's USB connection. I also had issues with cheap blackberry cables and had to use higher quality ones.
Did you try going into download mode by connecting it to the PC while with battery removed and hold (whatever buttons to boot it into download mode), then insert the batteries. Or try entering using a jig.
Also a bit lazy of me (on phone), but can someone point me to where to get Odin images for the Nexus?
try to use another cable to connect ur phone to pc
just flash stock via odin, it's not bricked.
My s2 sometimes has that problem when i flash stock
eksasol said:
I don't think its bricked, I once restore my phone from a black screen that Odin still recognized as download mode. The drivers can get iffy, do you have a third comp that you can install fresh drivers on. Also is your USB jack on the Nexus loose? Sometimes it really is due to your PC's USB connection. I also had issues with cheap blackberry cables and had to use higher quality ones.
Did you try going into download mode by connecting it to the PC while with battery removed and hold (whatever buttons to boot it into download mode), then insert the batteries. Or try entering using a jig.
Also a bit lazy of me (on phone), but can someone point me to where to get Odin images for the Nexus?
Click to expand...
Click to collapse
I appreciate the advice but I no longer have that phone. My replacement should come today.
With regards to the drivers, I was referring to the drivers on the phone not on the computer. I honestly don't know if there are USB drivers on the phone (I would think there are) or even if those drivers were causing the malfunction.
The first thing I'm doing this afternoon is plugging my replacement phone into my computer. If the new one doesn't work right then I'll have to make a trip to the Apple store because the problem will almost certainly be my laptop. I'll also owe a big apology to Verizon.
Hello everybody.
First I want to say is that I'm sorry for my english. It's not my native language.
And now lets go to my problem:
It started like few days ago when I updated my phone to the newest franco.kernel. After flashing that, my phone began to behave strangely and it didn't want to go tho nexus logo. It just always crashed.
So I decided to plug my phone to PC for flashing stock kernel or older version and what happened.. PC didn't recognize that phone is connected. I tried use Universal Naked Driver, OMAPflash (its just saying "waiting for device") and it still didnt want to work. I tried to plug it in notebook and it didnt work too. Well so I could still go to recovery mode, because I'm using TWRP. I did factory reset and my phone worked again even plug in to PC still hasn't worked.
And today I decided to try flash stock kernel with boot.img via TWRP. Of course it didnt work, so I did a stupid thing and flashed older version of franco.kernel (I don't know why I did that.. Maybe I was thinking it will fix my problem with USB, because it started with flashing the newest version..eh) and then my phone can't go tho Google Logo. Well so I did factory reset again + system reset (really clever) via TWRP well then it didnt work of course (because of no ROM, system), so I remembered that I did nandroid backup before my first factory reset. So I did a restore of backup, but it still stuck at Google Logo and everything I can do now is:
Go to recovery mode (TWRP) or Odin mode (which is just saying "Downloading...")
So I can't flash my phone tho PC, cause it doesn't recognize it is plugged in and I really don't know, what can I do now. I also though that USB cable should be "bad", because I didn't use it too much (like few months ago) so I would buy new one, but I don't think it is that problem, because it worked last time when I rooted my phone with PC etc.(but as I said.. few months ago)
Well.. I hope there will be solution for that.
Thanks in advance for reply.
You can read this. The entire first post. And maybe a couple more.
http://forum.xda-developers.com/showthread.php?t=1626895
Sent from my Nexus
The problem is that my PC doesn't recognize it is connected (when I install drivers, there is "yellow triangle"). It is charging while its connected to PC, but its not working as USB device. If I could see my phone on PC, it could fix my problem and I could return to stock.
Phone is working, it can be charged, it works in recovery-mode (with TWRP) and odin mode, but it cant go tho google logo and PC doesn't recognize it is connected. That's the current status.
+ It's rooted and unlocked....So the warranty is breached and If I will send it back to shop for repair, I will pay a lot of money :-/
Tordiato said:
The problem is that my PC doesn't recognize it is connected (when I install drivers, there is "yellow triangle"). It is charging while its connected to PC, but its not working as USB device. If I could see my phone on PC, it could fix my problem and I could return to stock.
Phone is working, it can be charged, it works in recovery-mode (with TWRP) and odin mode, but it cant go tho google logo and PC doesn't recognize it is connected. That's the current status.
+ It's rooted and unlocked....So the warranty is breached and If I will send it back to shop for repair, I will pay a lot of money :-/
Click to expand...
Click to collapse
Dude, just read the thread. Uninstall all drivers and reboot before doing anything else.
Sent from my Nexus
Tordiato said:
I also though that USB cable should be "bad", because I didn't use it too much (like few months ago) so I would buy new one, but I don't think it is that problem, because it worked last time when I rooted my phone with PC etc.(but as I said.. few months ago)
Click to expand...
Click to collapse
I bought a new USB cable today (Samsung APCBU10) and it works now! So I can flash it back to stock Problem solved.
//Thanks for the help anyway bk201doesntexist
so yesterday I rooted my S3 and installed custom rom
http://forum.xda-developers.com/showthread.php?t=2476970
D2att version!
It was working fine but due some errors on theme, phone contacts and messages i decided to try I9300 international version of rom and then it went off for reboot and didnt started since...
now I cannot turn it on AT ALL! no download mode or recovery mode...
I tried taking battery out for couple of minutes and plug it back in but didnt work ..
when i connect it to computer usb port i can hear computer sound alert you get when connect USB but nothing happens
-no charging logo on phone
-no usb detect on pc
but i can hear usb connection and disconnection sound alert.
anyone knows how to resolve ?
NOTE: pic i attached is prior to all this root and rom install
The international version uses a different processor. It's never a good idea to flash roms for other devices. If you can get into download mode you may be able to flash back to stock. If not, you may be hard bricked and will need a JTAG service.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Aamir_G said:
so yesterday I rooted my S3 and installed custom rom
http://forum.xda-developers.com/showthread.php?t=2476970
D2att version!
It was working fine but due some errors on theme, phone contacts and messages i decided to try I9300 international version of rom and then it went off for reboot and didnt started since...
now I cannot turn it on AT ALL! no download mode or recovery mode...
I tried taking battery out for couple of minutes and plug it back in but didnt work ..
when i connect it to computer usb port i can hear computer sound alert you get when connect USB but nothing happens
-no charging logo on phone
-no usb detect on pc
but i can hear usb connection and disconnection sound alert.
anyone knows how to resolve ?
NOTE: pic i attached is prior to all this root and rom install
Click to expand...
Click to collapse
Take a look at http://forum.xda-developers.com/showthread.php?t=2345860
I was able to go from a completely unresponsive phone back to normal by reading that thread and several like it. From what I can gather flashing the wrong version is a really bad idea. Not what I did but same end result. if this doesn't work for you google JTAG phone repair.
take a look at http://forum.xda-developers.com/showthread.php?t=23458
Aamir_G said:
so yesterday I rooted my S3 and installed custom rom
http://forum.xda-developers.com/showthread.php?t=2476970
D2att version!
It was working fine but due some errors on theme, phone contacts and messages i decided to try I9300 international version of rom and then it went off for reboot and didnt started since...
now I cannot turn it on AT ALL! no download mode or recovery mode...
I tried taking battery out for couple of minutes and plug it back in but didnt work ..
when i connect it to computer usb port i can hear computer sound alert you get when connect USB but nothing happens
-no charging logo on phone
-no usb detect on pc
but i can hear usb connection and disconnection sound alert.
anyone knows how to resolve ?
NOTE: pic i attached is prior to all this root and rom install
Click to expand...
Click to collapse
Jeez, it sounds like this could be a hard brick For the future NEVER flash a rom made for anything other than your specific device! More than likely, you will need a JTAG service to revive your phone and get it back to normal...
Aamir_G said:
so yesterday I rooted my S3 and installed custom rom
http://forum.xda-developers.com/showthread.php?t=2476970
D2att version!
It was working fine but due some errors on theme, phone contacts and messages i decided to try I9300 international version of rom and then it went off for reboot and didnt started since...
now I cannot turn it on AT ALL! no download mode or recovery mode...
I tried taking battery out for couple of minutes and plug it back in but didnt work ..
when i connect it to computer usb port i can hear computer sound alert you get when connect USB but nothing happens
-no charging logo on phone
-no usb detect on pc
but i can hear usb connection and disconnection sound alert.
anyone knows how to resolve ?
NOTE: pic i attached is prior to all this root and rom install
Click to expand...
Click to collapse
MOBILETECHVIDEOS.com is there for you for any bricks or other problems plus i agree with everyone else, NEVER FLASH A ROM that is not made for your device
So my GS3 is about a year old and the charging port gave out while trying to return to a stock touchwiz rom (4.3 to be exact). So i got worried and went to a local phone shop where they fix phones and told them to replace my charging port. As asked they did replace the port with a new one and it works for charging, but it doesn't fully connect to my laptop. I've tried replacing the drivers at least 10 times, I tried going into download mode to see if odin would detect it and as thought it did not appear in the dialog box, and I've tried over 5 different data cables including the original one that came with it, and I tried restoring to stock with Samsung kies both versions and the phone never came up either. Anyway my question was is it something they did or is my phone not going to work anymore. I'll provide some pictures with the things I've tried. Please reply quick this is starting to worry me a lot (I wasn't this worried when i fell off my atv). i forgot to add that when i connect it the phone turns on but doesn't connect to the laptop is it something i did or was it the repair
Hello all
I've a S4 mini rooted twrp installed. running touchwiz based custom rom from a long time.
day b4 yesterday i found it s.off when i turned it on. it stucked on SAMSUNG LOGO.
then i boot into recovery mode its twrp installed, there i saw internal memory 0MB. and in the mean time it was not taking charging.
and now.. it doesn't turn on, charge, or anything. If i plug it into a pc I get a sound from Windows 10 saying the USB device has been connected but nothing from the S4 mini itself.
any help?
inder23 said:
Hello all
I've a S4 mini rooted twrp installed. running touchwiz based custom rom from a long time.
day b4 yesterday i found it s.off when i turned it on. it stucked on SAMSUNG LOGO.
then i boot into recovery mode its twrp installed, there i saw internal memory 0MB. and in the mean time it was not taking charging.
and now.. it doesn't turn on, charge, or anything. If i plug it into a pc I get a sound from Windows 10 saying the USB device has been connected but nothing from the S4 mini itself.
any help?
Click to expand...
Click to collapse
i m getting sound of connecting my s4 mini to pc thats all.... plz any dev look in to this matter
inder23 said:
i m getting sound of connecting my s4 mini to pc thats all.... plz any dev look in to this matter
Click to expand...
Click to collapse
I think 0Mb suggests it was originally a corrupted partition as you were able to use TWRP to see 0Mb. Which flashing stock might have fixed.
But now it won't charge or boot might suggest something worse like failed hardware or hard brick.
But perhaps, as windows is seeing it (I forget now if Windows will detect usb on bricked phone, as luckily I've never had this), it may just be that you have run the battery down too low so now it won't recharge.
IronRoo said:
I think 0Mb suggests it was originally a corrupted partition as you were able to use TWRP to see 0Mb. Which flashing stock might have fixed.
But now it won't charge or boot might suggest something worse like failed hardware or hard brick.
But perhaps, as windows is seeing it (I forget now if Windows will detect usb on bricked phone, as luckily I've never had this), it may just be that you have run the battery down too low so now it won't recharge.
Click to expand...
Click to collapse
i hv tried a [plug n charge] charger to charge my battery,after all this my phone wont boot or nothing happens but just to b very sure, for now i need to arrange fully charged battery, then i ll update the same...
thank u very much 4 replying...