I picked up a used Vibrant last week and it initially worked fine. However, it still had 2.1 installed so I decided to update to 2.2 with Kies Mini. After 4 hours of screwing around and with it and much searching of forums, I finally got it upgraded, but something seems to have happened to the phone in the process.
The phone acts like the USB is permanently on, even if no cable is attached. The USB plugged in notification stays on even when the cable is unplugged. After I charge the phone and unplug it, the battery indicator continues to show that it is charging. The main problem is that the phone gets stuck in some kind of loop when the phone is turned off and never truly turns off. Initially, what would happen was that the little loading circle indicator would appear then the battery charging icon would pop up for a moment. However, since there was no cable plugged in, it would disappear. After several seconds of a black screen, the loading circle would come back up. This loop would simply continue over and over. Pulling the battery and putting it back in did nothing; the loop would just start over again the moment the battery was inserted. The phone would not respond to the power button while this loop was going.
At this point, I was still able to get the phone to boot by plugging in the USB cable, waiting until it started to charge (with the green battery icon) and then hitting the power button. This went on for several days. Today, I decided to take the battery out for several hours to see if anything would reset. However, things only got worse. The loading icon still pops up but now the charging icon doesn't come up, even if the USB is plugged in. I just get a loop where the loading circle pops up, disappears, comes back, and so on. I am now also not able to power on the phone with the power button.
I am still able to get into download mode (but not recovery mode) so I flashed everything back to stock using Odin and the instructions on this forum. This does get the phone booted back up, but as soon as I turn it off again everything starts all over.
So now I have a phone that, if it is ever turned off or loses power, has to be reset, wiping everything in the process. Does anyone have any idea how to fix this? Is it some kind of bootloader issue?
Odin, put 2.1 stock rom back.
Like the post before me mentioned, Odin back to stock 2.1
And personally, I'd much rather install stock froyo with ODIN rather than KIES.
Or just use a Custom ROM altogether.
As I mentioned in the original post, I've already restored the phone with Odin several times and it has absolutely no effect. It allows the phone to boot once but as soon as it is turned off again the loop starts over.
mordrid52 said:
As I mentioned in the original post, I've already restored the phone with Odin several times and it has absolutely no effect. It allows the phone to boot once but as soon as it is turned off again the loop starts over.
Click to expand...
Click to collapse
I have heard of KIES updates screwing phones before! I would contact T-mobile and tell them the situation....letting them know its used and had stock T-mo 2.1 and after using KIES to upgrade to 2.2 it screwed your phone.
Eventhough its used and You didnt buy it from them, they would probably fix it for you for free since their update program caused the issue...If it was a stock phone then they will probably fix it.
edit: in your story to them, leave out the part about you using ODIN...i am sure they will call that a void of the warranty.
Wondering if anybody has experience or suggestions on this issue. I've searched around but I can't find this particular formulation of an Amaze/Ruby boot loop problem.
I unlocked my bootloader a few months back and, after a fair bit of monkeying around, got Speedrom running perfectly smoothly. I had the occasional random reboot, same as on the stock rom, but everything was working well.
A few weeks ago, the reboots got more and more frequent. They only ever occurred when I was interacting with the phone i.e. not when the screen was off. Last week, the phone stopped turning on altogether. I couldn't even boot to recovery. After a day with the battery pulled, I managed to get to recovery and reflash Speedrom. Now a few minutes after every boot, the phone reboots itself and the process loops indefinitely. This happens whether I'm using the phone or not. The strangest part is that as long as I have the phone plugged into the USB drive of my computer (charge only, storage not mounted), it's rock solid with no random reboots. The second I unplug the USB cable, it reboots itself.
I've tried flashing the stock RUU (I'm on Mobilicity), a backup I made while on stock, and multiple other roms. They all work perfectly as long as my Amaze is charging off my computer via USB, and all reset ever minute or so when not plugged in. I'm really at a loss here.
For what it's worth I'm using 4ext and I'm s-on. If anybody has any words of wisdom here you will be my internet hero.
Hello, yesterday I cleared some cache using some app called "App Cache Cleaner - 1 Tap Clean" because my Dad's phone was low on storage, and it cleaned allright and then I umnounted the 2GB SD Card and then rebooted the phone. I don't know if this could be the cause, but ever since I did it the phone always reboots when the phone autolocks (or someone locks it). Sometimes it even reboots and stays black (note when someone calls you don't get a message that the subscriber is offline, it keeps ringing!) and then I have to hold the power button long enough for the phone ro reboot...
I removed the SD Card, tried factory reset, but nothing seems to work. The phone was never rooted or with a different ROM than the officials,. so I honestly have no idea why it keeps rebooting and doing stuff like that. It's on the latest available Android firmware -- 4.1.2.
What can I do to fix it?
Clean battery contacts with isopropyl alcohol, then try replace battery, then replace USB board/port - which is a relatively easy fix to do yourself for around 10 bucks (if you pay someone else to do it, labour could easily take this up to $70/80 or even more depending on labour costs in your country). If you decide to do this, KeithRoss39 has a guide in the General section (search for 'replacing USB charger board') that has all the info you need to get it done.
The other thing you could try before replacing the USB board is to flash stock firmware manually with Odin/in download mode (assuming you haven't already done this/the updates you've done up until now have been via Kies).
If I had to bet money though. I'd be wagering the battery (particularly if it's getting on age-wise) or the USB board (which is a common fault with Samsung phones).
Seriously, that is the only thing to do? I mean, it was okay yesterday and this suddenly hapenned... How can I be sure that it's from the USB Charger Board? And also, the phone won't reboot while I'm using it, but as soon as I lock it and wait a while, it reboots. I just tried wiping the phone again, and it even does that on the setup screen at the beginning... :crying:
Okay, I flashed a stock rom with Odin, as suggested, but it's doing the same thing... Now it's even worse! When I push the lock button when the phone is on, the phone freezes immediately and you can hear the lock sound looping over and over and over again. I have to hold the lock/power button for the phone to reboot... but it does that every time. Even when I don't press the lock/power button, only leave it to lock on its own, it does it again. It charges the battery just fine, I recharged it last night and it has 100% baterry... what could this be?
Hi everyone. I'll try to make a long story short while being thorough. Any help is much appreciated in advance.
TLDR Version: after messing around trying to get a working ROM and finally getting Tachyon 4.3.1 to load (without the SIM Card in), I powered down and the Rezound no longer powers on in any mode nor is it registered by adb. LED lights up while plugged in, that's it.
Complete version:
I spent a few days reading up on rooting & ROMing - but apparently not long enough - then spent an arduous night attempting to get a working ROM on my Rezound. I initially used AmonRa to get RezROM EX 3.4 to load up, but was stymied by constant "com.android.phone has stopped working" messages. After attempting several fixes, I formatted all back to Ext 3, and wiped the phone to factory settings (I know, I know...) in an attempt to start fresh. After that sloppy attempt, the phone wouldn't get past the initial white HTC screen, so I did the following using less than stellar judgment: I removed the Verizon SIM Card, rebooted, and installed Tachyon 4.3.1 (linked at bottom) in AmonRa recovery. Miraculously, I thought, the phone loaded up Tachyon and after one "com.android.phone has stopped working" message, I was able to use the phone, albeit with no network connection. I thought all I had to do was power down, put in the SIM Card, and maybe things would be alright.
Instead, what happened was this: I powered down, took out the battery (which had some charge) and put the SIM Card in. When I pressed the power button back on, the phone did not turn on. Unplugged, not even the LED would light up. I plugged it into my PC, at which point the LED does turn on, but pressing power only causes the buttons on the bottom portion of the phone to light up for a few seconds. That's it. The screen does not do anything. Holding Volume Down + Power does the same thing; it does not vibrate or boot to Recovery. Lastly, adb no longer registers the phone's presence (error: device not found). I plug it in the USB, hear the chime, but commands like adb list, adb reboot, etc. do nothing. The phone appears as an external drive in Explorer, but it cannot be opened. I've now tried two batteries and let the phone charge for a few hours. Still no results.
If I've bricked the phone, I understand. I fortunately have another Rezound I can fall back on. I understand the risk of taking the unresponsive phone to the Verizon store, so I'm asking for help/suggestions here. Thanks!
DentalAppointment said:
Hi everyone. I'll try to make a long story short while being thorough. Any help is much appreciated in advance.
TLDR Version: after messing around trying to get a working ROM and finally getting Tachyon 4.3.1 to load (without the SIM Card in), I powered down and the Rezound no longer powers on in any mode nor is it registered by adb. LED lights up while plugged in, that's it.
Complete version:
I spent a few days reading up on rooting & ROMing - but apparently not long enough - then spent an arduous night attempting to get a working ROM on my Rezound. I initially used AmonRa to get RezROM EX 3.4 to load up, but was stymied by constant "com.android.phone has stopped working" messages. After attempting several fixes, I formatted all back to Ext 3, and wiped the phone to factory settings (I know, I know...) in an attempt to start fresh. After that sloppy attempt, the phone wouldn't get past the initial white HTC screen, so I did the following using less than stellar judgment: I removed the Verizon SIM Card, rebooted, and installed Tachyon 4.3.1 (linked at bottom) in AmonRa recovery. Miraculously, I thought, the phone loaded up Tachyon and after one "com.android.phone has stopped working" message, I was able to use the phone, albeit with no network connection. I thought all I had to do was power down, put in the SIM Card, and maybe things would be alright.
Instead, what happened was this: I powered down, took out the battery (which had some charge) and put the SIM Card in. When I pressed the power button back on, the phone did not turn on. Unplugged, not even the LED would light up. I plugged it into my PC, at which point the LED does turn on, but pressing power only causes the buttons on the bottom portion of the phone to light up for a few seconds. That's it. The screen does not do anything. Holding Volume Down + Power does the same thing; it does not vibrate or boot to Recovery. Lastly, adb no longer registers the phone's presence (error: device not found). I plug it in the USB, hear the chime, but commands like adb list, adb reboot, etc. do nothing. The phone appears as an external drive in Explorer, but it cannot be opened. I've now tried two batteries and let the phone charge for a few hours. Still no results.
If I've bricked the phone, I understand. I fortunately have another Rezound I can fall back on. I understand the risk of taking the unresponsive phone to the Verizon store, so I'm asking for help/suggestions here. Thanks!
Click to expand...
Click to collapse
So, if you disconnect the USB cable, remove and reinsert the battery (also, try another battery), then press and hold POWER+VOL DN for a few seconds are you able to get into HBoot? If not, it is likely borked, but not because of flashing a ROM, it was probably just it's time to go...
got it working
Thanks for the reply.
Just to update this post, I did eventually get the Rezound working again. Clearly it wasn't totally borked, but I guess I had in fact drained the first battery without knowing it - when I inserted the second battery, which I believe did have some power left, for some reason that power wouldn't register with the phone. I left it plugged into USB for a couple more hours and after several on-off and USB plug-unplug attempts, I eventually got it back into HBOOT (not to give myself credit for this), to my relief.
I then switched to Clockwork revival and managed to get Cyanogenmod 10.2 (10.2-20131217-Flyhalf2015-vigor) working on the phone. Without understanding what happened with perfect clarity, I surmise the reason the install wasn't working in the first place was that I was attempting to install a different kernel simultaneously - ie. from recovery mode without a reboot in between. Either I got the order of installation wrong (ROM before kernel or ROM after kernel I don't know) or that kernel was not compatible. Anyway I wiped the phone again and just installed Cyanogen without attempting to install a kernel and it worked - I'm guessing with cyanogen's own kernel.
So now I have Cyanogen working and ROM Manager set up with a backup. While the new features and customizability are cool, the system overall is somewhat glitchy. Don't know if that's due to the version of cyanogen, the kernel, my installation technique, or the phone hardware. It's certainly not unusable and I'm going to leave it as-is for a bit after this ordeal, but the following glitches happen occasionally:
-not all lock screen features appear, or lock screen background won't appear
-phone screen will suddenly fill up with random 'glitchy' patterns of colored pixels
-screen will remain black after tapping power switch to go from idle state to using. backlit keys will light up but will have to remove battery and restart device to work again
-battery life is still poor if not a bit worse (probably not a glitch, just rezound's stock battery)
But it's now an old piece of hardware and I'm still happy I carried the process through to the end. Given that I couldn't stand certain aesthetic features of the stock OS, I am content with the results for now.
Fin
DentalAppointment said:
Thanks for the reply.
Just to update this post, I did eventually get the Rezound working again. Clearly it wasn't totally borked, but I guess I had in fact drained the first battery without knowing it - when I inserted the second battery, which I believe did have some power left, for some reason that power wouldn't register with the phone. I left it plugged into USB for a couple more hours and after several on-off and USB plug-unplug attempts, I eventually got it back into HBOOT (not to give myself credit for this), to my relief.
I then switched to Clockwork revival and managed to get Cyanogenmod 10.2 (10.2-20131217-Flyhalf2015-vigor) working on the phone. Without understanding what happened with perfect clarity, I surmise the reason the install wasn't working in the first place was that I was attempting to install a different kernel simultaneously - ie. from recovery mode without a reboot in between. Either I got the order of installation wrong (ROM before kernel or ROM after kernel I don't know) or that kernel was not compatible. Anyway I wiped the phone again and just installed Cyanogen without attempting to install a kernel and it worked - I'm guessing with cyanogen's own kernel.
So now I have Cyanogen working and ROM Manager set up with a backup. While the new features and customizability are cool, the system overall is somewhat glitchy. Don't know if that's due to the version of cyanogen, the kernel, my installation technique, or the phone hardware. It's certainly not unusable and I'm going to leave it as-is for a bit after this ordeal, but the following glitches happen occasionally:
-not all lock screen features appear, or lock screen background won't appear
-phone screen will suddenly fill up with random 'glitchy' patterns of colored pixels
-screen will remain black after tapping power switch to go from idle state to using. backlit keys will light up but will have to remove battery and restart device to work again
-battery life is still poor if not a bit worse (probably not a glitch, just rezound's stock battery)
But it's now an old piece of hardware and I'm still happy I carried the process through to the end. Given that I couldn't stand certain aesthetic features of the stock OS, I am content with the results for now.
Fin
Click to expand...
Click to collapse
I had some unfortunate nastiness happen to my Rezound a while back which prompted me to go out and get an M8, but I did eventually get the Rezound 99% functional again.
First off, cell phones in general rely on something called NAND memory for all mass storage. It's decently quick stuff, but not the most reliable storage medium in the known universe. Basically, it slowly dies with use. NAND only has so many read/erase/write cycles before it begins to degrade. This can lead to very quirky corruptions in the partitions, and that's kind of what it sounds like has happened to your Rezound. The fix that got mine back to working order was a complete stock RUU restoration followed by a "factory reset" through Hboot. That will wipe and rewrite all of your partitions. Then flash your custom recovery, ROM, and kernel.
As for flashing ROM's and kernels in the right order, you want to flash the ROM and then the kernel. A lot of devs recommend flashing the ROM, then booting it up, then flashing a custom kernel, however, if you know you've got a working combination of ROM and kernel, there is no reason you can't just flash the ROM and kernel (in that order) at the same time in recovery.
My S9+ was acting quite weird this morning. Some apps continuously crashed or wouldn't start.
So i rebooted my phone (just from the normal power button menu) and then it went completely black.
It doesn't charge (or at least, it doesn't show it charging), it doesn't respond to forced resets and the screen is completely black.
The only thing it does, is briefly show a USB device when connecting it to a PC.
I've connected it to a Linux dev computer i have laying around and i see the following device connected briefly:
VID: 0x04e8
PID: 0x1234
It stays connecting longer if i hold the power button (about 8 seconds before power cycling).
The only things i could find online were some very old threads about Samsung's DNW mode, but nothing from this decade.
I think my Flash chip might be cooked, but i hope i'm wrong.
Anyone got any experience with this?
Update
I've sent it back to Samsung for repair under warranty.
The flash chip was gone. It started corrupting writes and finally it was so far gone that it couldn't load the bootloader.
They've replaced the main board and battery (probably because they tested it and saw it was going bad), that fixed it.