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.
Hi,
I have a Sprint 4G LTE rooted with VIPER rom installed. Last night my phone freaked out, so I did the 10 second "battery pull" and it started up again. I plugged it into the charger and I fell asleep without much worry.
I woke up to find my phone stuck at the LTE splash screen of the VIPER rom. I've done the 10 second "battery pull" several times, and it doesn't just shut the phone off, it forces a reboot. Each time it only makes it as far as the LTE splash screen.
My experience with phones and computers is telling me that the OS might have gotten corrupt some how since it is stuck at the splash screen.
I do have access to the bootloader, so I have some paths I can go down, factory reset/recovery, but both those I'd like to avoid so that I do not lost the contents of my storage.
I have had VIPER rom installed for a good half year, so this issue isn't due to a new rom being flashed.
Does anyone have any suggestions?
Thanks,
-billypilgrim
When data gets corrupted, all you can do is wipe and start over. I had to do that once when running Viper as well.
Just a thought in trying to be helpful....
I used that ROM for a while myself and never really had any issues but have had a similar situation.
I pulled my sd card out and backed it all up. Replaced SD card.
Then went into recovery and reflashed the ROM.
Worked solid after that and no explanation as to why it was corrupt/hanging in a loop.
Hope this helps..
billypilgrim said:
Hi,
I have a Sprint 4G LTE rooted with VIPER rom installed. Last night my phone freaked out, so I did the 10 second "battery pull" and it started up again. I plugged it into the charger and I fell asleep without much worry.
I woke up to find my phone stuck at the LTE splash screen of the VIPER rom. I've done the 10 second "battery pull" several times, and it doesn't just shut the phone off, it forces a reboot. Each time it only makes it as far as the LTE splash screen.
My experience with phones and computers is telling me that the OS might have gotten corrupt some how since it is stuck at the splash screen.
I do have access to the bootloader, so I have some paths I can go down, factory reset/recovery, but both those I'd like to avoid so that I do not lost the contents of my storage.
I have had VIPER rom installed for a good half year, so this issue isn't due to a new rom being flashed.
Does anyone have any suggestions?
Thanks,
-billypilgrim
Click to expand...
Click to collapse
I have that happen several times. Nothing obvious that causes it. Cap'n is right need to wipe and re-flash. Here's the small trick since it just keeps rebooting on you, after you hold power for ten seconds and the screen blacks out. Make sure the capacitive buttons go out as well, that split second they go dark let go of the power button and press vol down and power to get it back into bootloader. Then you can get back in recovery to flash.
Hello XDA,
Way to start off my Friday Hope EVERYONE has a GOOD AND SAFE weekend!
PROBLEM:
Out of the blue it started to reboot itself more often, always had issues with candykatt even after few re-install and wipes. Last night, it would reboot with in 1-5 minutes after full boot and load, then the time decreased to 30 seconds. Till finally 1 second, that is if i am lucky to full boot and load. (auto attempt to reboot with multiple vibrations).Tried to load into odin and twrp, and same symptoms first will fully load into those two for 30 seconds and then auto reboot.
ATTEMPTS
Tried various batteries of various charge types percentages, stock samsung battery fully charged another 2500MAH even 5400MAH. Tried taking sim and memory card out and same thing! (debating on opening up and clean, hope just power button even though feels fine)
CANDYKATT:
I love the rom, work well for couple months with minor popular known issues, like camera not working and random but not frequent freezes. And power hungry, was waiting for updates in forum but never happened. Not as tech savy as i used to be (not my first rom, ran every blackstar and everything from GB, JB,KK and just not on this device) still a not a pro or almost out of noob stafe
XDA FAMILY HELP ME PLEASE!
would love to fix issue with out wipe or reflash at the moment to save files (did not have memory card long)
Phone:
AT&T i717
CandyKatt (Non Uber)
TWRP
64gb SD
No Other tweaks or fancy anything
All Buttons seem fine
No Rattles haha
NO WARRANTY
(Charge port messed up, no major accident besides tripped on power cord while plugged in)
Power Button
XDA World,
Attempt Power Button cleaning and pop out with screw driver (not forced). My button worked fine, looked fine and felt fine. After attempting ODIN and TWRP many times, idk what I did but re flashed and loaded into candykatt os set up. My files still there, and so far has been on for a few minutes as I transfer my photos to SD (full battery).
Uh oh random auto reboot!!! dang it
working better
I still do not know what I did, entered odin and twrp so many times (as mentioned old post). After it reflashed due my button mashing between those two, it works better random reboots even vibrating thing. But does the bad vibrations here n there until I hold power button then reboots.
And was able to sync to get photos off.
I am going to try a new rom, sorry candykatt ...promise soon as bugs are fixed I will re-install
Many times the stuck power button issue seems okay it may not be. I always tell folks to flick the phone in the back a few times, even if the button feels the click. Flick it. Some are courageous enough to take a swab and alcohol to the contacts for cleaning. Not me.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
A couple weeks ago, I finally figured out that Cyanogenmod wasn't auto-updating past CM 10.2 on my Evo 4G LTE because I needed to update TWRP to 2.7.1.2 and also get S-OFF and update HBOOT to version 2.10.0000. Although I had a couple stressful moments in updating all of that where I thought I might have accidentally bricked my phone (I'm still pretty new at flashing custom ROMs), I managed to get it all figured out and I updated Cyanogenmod to CM11. I can't remember whether I updated directly to Snapshot M11 or if I updated first to M10 and then M11, but at any rate everything worked out fine and I had no problems with my phone. Then I updated to snapshot M12 through the auto-updater when it came out a week or so after doing all the above, and again everything was working fine with no problems (though I did start having some lag sometimes when I was using the Kii keyboard app I had installed, or sometimes the keyboard would drop my swipe halfway through a word and type two words instead of the one that I wanted, which was happening at an increasing frequency in the days before my phone crashed). At any rate, a few days ago I was reading the news on a news app, then the screen froze, the operating system crashed (the screen just went black and the phone turned off), and ever since then I haven't been able to use the phone at all. It doesn't turn on now.
I have tried booting into recovery a number of times using the power + down volume combo, but I haven't been able to get it to work -- though I'm not sure if there's some trick that I don't know about how long to press down. The phone does not boot up into Cyanogenmod, either. The screen just stays black no matter what I do. Sometimes when I mess around with pressing the power button or holding it for different periods of time and/or pressing and holding the down volume, the phone has made some responses. Sometimes the capacitative buttons will light up for a couple seconds before going black again, and sometimes the phone will vibrate for a half second. (Also, when I have it plugged in, sometimes I can get the battery charging light to turn off or on.) But after that, the screen always just stays black. It seems like I bricked my phone, but I wanted to ask before throwing in the towel. The thing is, sometimes when I was flashing new ROMs, my phone would get into a similar state (I was never quite sure what was going on) and I'd be able to get it into recovery or get it to boot regularly (though I was never quite sure what exactly I did to make it work again -- I always kept trying different combinations and pressing-lengths of the power and volume down buttons like I've been doing recently), so it seems like maybe there's still a possibility I could do something similar now.
Any idea what I should try? Any idea what might have happened to lead to a crash like this, so that I can avoid making the same mistakes or having the same problems in the future? I would appreciate your help so much; I'm overseas right now and was depending on having my phone to stay in touch with people. Thank you!
I started to restore to a back-up I made two days ago in TWRP and I think it got interrupted by my accidentally canceling it. I was on my way out the door and wasn't paying attention and must've touched the screen (phone in hand).
Now it behaves much like cadcamaro's description in his recent post about having tried to install a Z2 ROM. I can get into FastBoot, but all options simply shut down the phone. If I don't choose an option, it shuts down by itself after a a minute or so.
Power + Volume Down gets a short vibration.
When I plug it into the PC, Power + Volume Up Gets me a blue LED that stays lit, but the PC (and Flashtool) doesn't see it.
Power + Volume Down gets an orange, then green LED with vibration that repeats.
The first time I realized it was screwed up, I did get into Recovery. I tried to re-run the back-up (which is saved to external SD), and it shut down.
Thanks, all.
AddictedToGlass said:
I started to restore to a back-up I made two days ago in TWRP and I think it got interrupted by my accidentally canceling it. I was on my way out the door and wasn't paying attention and must've touched the screen (phone in hand).
Now it behaves much like cadcamaro's description in his recent post about having tried to install a Z2 ROM. I can get into FastBoot, but all options simply shut down the phone. If I don't choose an option, it shuts down by itself after a a minute or so.
Power + Volume Down gets a short vibration.
When I plug it into the PC, Power + Volume Up Gets me a blue LED that stays lit, but the PC (and Flashtool) doesn't see it.
Power + Volume Down gets an orange, then green LED with vibration that repeats.
The first time I realized it was screwed up, I did get into Recovery. I tried to re-run the back-up (which is saved to external SD), and it shut down.
Thanks, all.
Click to expand...
Click to collapse
Have you tried pressing and holding the reset button next to the SIM tray? Try holding it down for 2+ minutes and see what happens.
Have you tried pressing and holding the reset button next to the SIM tray? Try holding it down for 2+ minutes and see what happens.
Click to expand...
Click to collapse
Thanks for responding, BladeRunner.
I just tried that in a variety of ways, and got either no response or it simply did what it was doing. I'll explain;
Believing the phone to be OFF, nothing happens for 2 1/2 minutes of pressing the Reset button.
Same goes for a variety of combinations of switches also depressed, such as Volume Up/Down, Power, or any combo therof.
(At this point, I'm uncertain if I even have much of a charge in the phone.)
FastBoot is the menu that has the green Droid with a choice of 4 options, including Power Down, Continue to Power Up, Factory Reset, and something else, correct?
The one time that I did get that to appear during these last few attempts to use the Reset switch, the menu simply shut down after 15 seconds. I continued to press the reset switch, but nothing happened.
Plugged into the PC, the phone continued to cycle Power-On every 8 seconds, with the Orange LED followed by the Green, then Shut-Down. (Apparently, as without the screen on I have no idea what it's really doing....)
Plugged into PC, Power Button in and Volume Up gives me the Blue LED that stays on constantly, but depressing the Reset Switch does nothing.
As I stated earlier, I have no idea how much charge the phone has, so I'm leaving it on the PC in the Blue LED state. It may not be charging, but all it does when I try to charge it any other way is cycle through every 8 seconds with the Orange & Green LED.
Sigh... This would be the first phone I've ever bricked, and I've been messing around since Vivo on the V3m, and always very careful. Sucks since this has been my favorite of them all.
AddictedToGlass said:
Thanks for responding, BladeRunner.
I just tried that in a variety of ways, and got either no response or it simply did what it was doing. I'll explain;
Believing the phone to be OFF, nothing happens for 2 1/2 minutes of pressing the Reset button.
Same goes for a variety of combinations of switches also depressed, such as Volume Up/Down, Power, or any combo therof.
(At this point, I'm uncertain if I even have much of a charge in the phone.)
FastBoot is the menu that has the green Droid with a choice of 4 options, including Power Down, Continue to Power Up, Factory Reset, and something else, correct?
The one time that I did get that to appear during these last few attempts to use the Reset switch, the menu simply shut down after 15 seconds. I continued to press the reset switch, but nothing happened.
Plugged into the PC, the phone continued to cycle Power-On every 8 seconds, with the Orange LED followed by the Green, then Shut-Down. (Apparently, as without the screen on I have no idea what it's really doing....)
Plugged into PC, Power Button in and Volume Up gives me the Blue LED that stays on constantly, but depressing the Reset Switch does nothing.
As I stated earlier, I have no idea how much charge the phone has, so I'm leaving it on the PC in the Blue LED state. It may not be charging, but all it does when I try to charge it any other way is cycle through every 8 seconds with the Orange & Green LED.
Sigh... This would be the first phone I've ever bricked, and I've been messing around since Vivo on the V3m, and always very careful. Sucks since this has been my favorite of them all.
Click to expand...
Click to collapse
I'm not sure what fastboot mode on the z3v looks like honestly, but your description sounds about right. You could try getting into xz dual recovery again and wiping the cache maybe? The instructions to there are in the xzdr thread. If you can get there wiping, a factory reset or flashing something might work but failing that you might want to try letting the battery drain all the way down. If you just let your phone sit that can take a while ( days at least) or you use a rubber band to hold down the poet and volume down button, I believe, to drain the battery. Once its dead completely connect it to your PC and see what happens.
A failed flash on a eeprom can be a hard thing to recover from, sometimes it can ruin the eeprom preminently, depends on the state the eeprom was in in the flash process,usually in erase process it will not be recoverable. . Removing power will not reset the eeprom, eeproms are preminent memory, but it can allow the device to be discovered again hopefully.
You have to get something to erase and flash again, if the eeprom is in a failed state that may be impossible to do.
1linuxfreak said:
A failed flash on a eeprom can be a hard thing to recover from, sometimes it can ruin the eeprom preminently, depends on the state the eeprom was in in the flash process,usually in erase process it will not be recoverable. . Removing power will not reset the eeprom, eeproms are preminent memory, but it can allow the device to be discovered again hopefully.
You have to get something to erase and flash again, if the eeprom is in a failed state that may be impossible to do.
Click to expand...
Click to collapse
So I'm assuming the eeprom is like an order of operations & file allocation index or something really basic upon which everything else is built? This is an old school term for file index, right?
So even if I manage to get everything wiped, I need to start fresh by installing the stock ROM that the phone came with and progress to where I can load the saved Back-Up that's on the External SD?
If the eeprom gets wiped as it's re-written from the Back-Up, and interruption blew this process mid-wipe, will my Back-Up still be useable?
How is it that battery drain will help my device become recognized by the PC?
Thanks for all the help.
AddictedToGlass said:
So I'm assuming the eeprom is like an order of operations & file allocation index or something really basic upon which everything else is built? This is an old school term for file index, right?
So even if I manage to get everything wiped, I need to start fresh by installing the stock ROM that the phone came with and progress to where I can load the saved Back-Up that's on the External SD?
If the eeprom gets wiped as it's re-written from the Back-Up, and interruption blew this process mid-wipe, will my Back-Up still be useable?
How is it that battery drain will help my device become recognized by the PC?
Thanks for all the help.
Click to expand...
Click to collapse
Correct. Your backup is safe as long as you don't mess with sdcard storage. You have to get the eeprom healthy before you can do a recovery.
Back to working on my bricked Z3v...
Plugged into PC with Volume-Up held in yields solid Blue LED. This is the only time that in Windows 8.1 Device Manager that the phone shows up as a connected device. The name of the device is "S1 Boot Fastboot", for which there is no driver installed. When I navigate to Z3-lockeddualrecovery2.8.23-RELEASE.combined / files / adbdrivers and try to install the driver, Windows says "Windows could not find driver software for your device."
However, in the "Events" tab it shows three previous dates that the device was configured. It listed the device as such "Device USB\VID_0FCE&PID_0DDE\BH900JCL1N was configured." on those dates.
Was there something different I had to do for Windows 8? I cannot remember, but this feels familiar.
Driver Name: Google, Inc. (WinUSB)...
Status: Install failed
Meanwhile other drivers do install. What gives?
Well I was hoping for a bit more. Extremely frustrated right now as it took me about 15 minutes just to get here to see that nobody can help.
In the meantime with all the **** I've downloaded trying to fix my phone, I've completely scxrewed my computer. 4 virus scans later and I'm still f'd.
Great.
AddictedToGlass said:
Well I was hoping for a bit more. Extremely frustrated right now as it took me about 15 minutes just to get here to see that nobody can help.
In the meantime with all the **** I've downloaded trying to fix my phone, I've completely scxrewed my computer. 4 virus scans later and I'm still f'd.
Great.
Click to expand...
Click to collapse
Your phone is toast and the only way to get it back is through the Flashtool imo. It wouldn't be common for many to have your circumstances with a bricked phone so you aren't getting much feedback. See if you can follow these instructions with Flashtool that I posted. I've gone from 4.4.4 to 5.02 non-rooted and back to root on 4.4.4 and then forward again so it has worked well for me.
http://forum.xda-developers.com/showpost.php?p=63800685&postcount=8
See if you can download the 4.4.4 firmware after getting flasthool 09.18.6 installed. Granted my instructions are from Windows 10 64 bit but it should work.
Couldn't do any of it. My PC is s screwed up, but even in Safe Mode I was unable to load drivers that would recognize my z3v.
So I'm typing this on my replacement phone that came today via FedEx. I was very nervous about getting a refurb, but this one really is like new. I managed to get the glass protector of the old one, rinse it off, and apply it to the new one.
Now I'm on unrooted kitkat.
If I root and install TWRP, can I simply flash my saved lollipop backup from my SD card and make this phone exactly like the other one was before I borked it?
AddictedToGlass said:
Couldn't do any of it. My PC is s screwed up, but even in Safe Mode I was unable to load drivers that would recognize my z3v.
So I'm typing this on my replacement phone that came today via FedEx. I was very nervous about getting a refurb, but this one really is like new. I managed to get the glass protector of the old one, rinse it off, and apply it to the new one.
Now I'm on unrooted kitkat.
If I root and install TWRP, can I simply flash my saved lollipop backup from my SD card and make this phone exactly like the other one was before I borked it?
Click to expand...
Click to collapse
I wouldn't recommend that. I have used titanium backups before from one device to another and it worked. The whole system from a twrp backup really doesn't sound like a good idea.
OK. Think I'll just be patient and do it from scratch. Have to get the computer cleaned up first.
Really glad to have a clean, new z3v back again, but this ordeal has certainly impacted my confidence doing this stuff.
Thanks for your help, everyone.