Related
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.
Today i decided to try out the nocturnal rom, but before that i had to make a backup. at the the time the phone was what i would a call luke warm so i paid no mind to it. so a few minutes later i look back at the phone and notice that the screen turned off annd the phone was now averagely hot
so i let it cool down for a bit (i thought that the phone must have shut itself off in order to make sure the internals wouldn't be damaged), then when i try to turn it on the lg logo does show up but never gets to the base roms nexus boot animation, now i'm thinking that TWRP must have drained my battery because when i usually make a backup my battery can go from 94% to 50% in a span of 7 minutes (only during backup). So i leave it to charge for 30 minutes 1 hour and then 5 hours but each time i check it still won't turn on correctly.
Now i have had this happen to me before, when i had the atrix 4g this happened and i had to buy a battery only charger to even get it to work again
but as we all know that won't work for the optimus g because you cannot take out the battery.
so i have to ask, what should i do? is there any way to fix this?
Side note: can't get into recovery (seems to shut off before it loads up, its like an infinite loop of dying and turning on again) the power button still glows while its connected giving the appearance of charging but it still never boots up all the way ( the most i can get it to is the part of recovery before going into TWRP. you know holding vol+ and seeing fastboot mode)
There is thread here someone made of disassembly. You can do a battery pull pretty easily. Never know might help.
Have you tried download mode at all BTW?
Sounds more like something was deleted then a batter problem to me. If download mode works you could try lgnpst back to stock.
The information in THIS thread might be able to help.
I can't vouch for it because I haven't experienced these problems, but the OP there seemed to get his problem fixed.
GL.
Although, looking things over, sounds like you have a different issue.
So you can get to the bootloader?
from the bootloader have you tried hitting the volume down key twice then hitting power?
That should reboot you into recovery, where you can restore something or flash stock.
Edit. Quote from FreeGee post.
To enter bootloader, hold volume UP and power.
Upon entering the bootloader, you will notice that there is no 'menu' to enter fastboot or recovery. Unfortunately, since the stars didn't align properly, we were unable to tell the new bootloader where to load the images that contain the menu from.
In light of that, you'll have to navigate the menu blind. Use the volume keys to change selection, and the power key to select.
The choices are (in order of pressing volume down):
Start - boot the phone normally [already selected]
Restart Bootloader - reboot into the bootloader
Recovery Mode - enter recovery (CWM)
Power Off - powers the phone off
So, to get to Recovery, you would press volume down twice then power.
Click to expand...
Click to collapse
bleached45 said:
The information in THIS thread might be able to help.
I can't vouch for it because I haven't experienced these problems, but the OP there seemed to get his problem fixed.
GL.
Although, looking things over, sounds like you have a different issue.
So you can get to the bootloader?
from the bootloader have you tried hitting the volume down key twice then hitting power?
That should reboot you into recovery, where you can restore something or flash stock.
Edit. Quote from FreeGee post.
Click to expand...
Click to collapse
when i try to get into TWRP it doesnt start up, same as when it trys to turn on, it seems to die before it boots fully or so to say the screen
goes from a backlit black to just black and then it doesn't come on again. (looking at thread and nothing has worked yet i'm now trying last advice in thread since my phone won't even turn on unless its connected to the charger)
also i have no idea what download mode is but since nothing seems to be working i will assume that does not work either
Edit: actually maybe i can lgnpst. all i have to do is be able to get into the bootloader right? going to try in the afternoon.
Kurodo said:
when i try to get into TWRP it doesnt start up, same as when it trys to turn on, it seems to die before it boots fully or so to say the screen
goes from a backlit black to just black and then it doesn't come on again. (looking at thread and nothing has worked yet i'm now trying last advice in thread since my phone won't even turn on unless its connected to the charger)
also i have no idea what download mode is but since nothing seems to be working i will assume that does not work either
Edit: actually maybe i can lgnpst. all i have to do is be able to get into the bootloader right? going to try in the afternoon.
Click to expand...
Click to collapse
Sorry none of that is working.
To enter download mode:
Connect phone to computer, power off, and then power on, holding down the power button and both volume buttons
Click to expand...
Click to collapse
In the FAQ section of THIS thread, it explains how to use LGNPST.
This is god's way of telling you not to mess with flashing roms on your phone. Hopefully you will learn your lesson and keep your dirty hands off your phone, it just wants to be left alone!!!!!!!
sent from my Nexus 4 using xda premium
jamesc760 said:
This is god's way of telling you not to mess with flashing roms on your phone. Hopefully you will learn your lesson and keep your dirty hands off your phone, it just wants to be left alone!!!!!!!
sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I can't tell if you're being serious or not
to that nay sayer
jamesc760 said:
This is god's way of telling you not to mess with flashing roms on your phone. Hopefully you will learn your lesson and keep your dirty hands off your phone, it just wants to be left alone!!!!!!!
sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
There is beauty in god given stock but there is TRUE beauty in the purgatory that is flashing roms and making it all your own!!!!!!:laugh:
last resorts
well the lgnpst did work but the battery still won't charge, so if i can't get a replacement i'll try this http://forum.xda-developers.com/showthread.php?t=2039707 and see if i can charge it.
now a different question...
does anyone know if i can exchange the phone at an att store if i bought it from amazon or would i have to go through amazon?
and exactly how does that work?
Kurodo said:
well the lgnpst did work but the battery still won't charge, so if i can't get a replacement i'll try this http://forum.xda-developers.com/showthread.php?t=2039707 and see if i can charge it.
now a different question...
does anyone know if i can exchange the phone at an att store if i bought it from amazon or would i have to go through amazon?
and exactly how does that work?
Click to expand...
Click to collapse
Amazon is actually VERY easy to deal with, and a HELL of a lot easier than AT&T. They'll ship you out a replacement, you send the old one back once you receive the new one. Done. You MAY have to send the old one first, but if you let them put a hold on a credit card, I believe they'll definitely ship first.
You may be able to fix this by holding down both the volume down and power buttons for at least 45 seconds after you plug in the phone.
so
STEP 1: PLUG IN PHONE
STEP 2: PRESS AND HOLD THE VOLUME DOWN AND POWER KEYS TOGETHER FOR AT LEAST 45 SECONDS
STEP 3: LEAVE PLUGGED IN FOR TEN MINUTES
STEP 4; BOOT INTO RECOVERY MODE, WIPE BATTERY STATS, WIPE CACHE, AND WIPE DALVIK, THEN REBOOT TO SYSTEM FROM WITHIN RECOVERY.
LAST PART IS TO PREVENT IT FROM HAPPENING AGAIN.
I've gone the three of these for various reasons and some times lgnpst pretends to work and you need to do it again. And some times you need to wipe data boot back into download and do it again. This phone is retarded.
My buddies rooted i717 with CM10 4.2 has been running great. Then it started to turn just turn off on it's own. Last time it turned off now it won't turn on.
When you hit the power samsung logo flashes normally then screen goes blank. At this point it keeps making that powering on vibrating sensation repeatedly. Touch power button and this routine repeats.
It will not boot into recovery. After the sammy logo flash continuing to hold down power +/- does not yield recovery mode. It just starts the vibrating loop.
I thought I will just install stock via kies or flash JB via odin. Well odin mode turns on ok but shuts off after barely 2 to 3 seconds. I have tried this with and without battery, plugged in and not plugged in on pc but end up the same way.
I have checked battery, same is super aok. I swapped batteries with my i717 and mine turns on just fine all the way. My buddy doesn't mind any which way the phone comes back to life.
jayinc11 said:
My buddies rooted i717 with CM10 4.2 has been running great. Then it started to turn just turn off on it's own. Last time it turned off now it won't turn on.
When you hit the power samsung logo flashes normally then screen goes blank. At this point it keeps making that powering on vibrating sensation repeatedly. Touch power button and this routine repeats.
It will not boot into recovery. After the sammy logo flash continuing to hold down power +/- does not yield recovery mode. It just starts the vibrating loop.
I thought I will just install stock via kies or flash JB via odin. Well odin mode turns on ok but shuts off after barely 2 to 3 seconds. I have tried this with and without battery, plugged in and not plugged in on pc but end up the same way.
I have checked battery, same is super aok. I swapped batteries with my i717 and mine turns on just fine all the way. My buddy doesn't mind any which way the phone comes back to life.
Click to expand...
Click to collapse
If you read and run any kind of search, you would find similarities to the all common stuck power button.
Flick tye back of the phone a few times.
I know, you can feel it click.......doesnt matter, flick the phone.
If you are brave enough, you can open phone and clean with qtip and alcohol.
I am not.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
I did actually, it didn't work. I thought there's was something that could help before I have to open it up cause of time. I change ports, cameras, etc on these models so it's not a biggie to clean it. Will do this this weekend.
jayinc11 said:
I did actually, it didn't work. I thought there's was something that could help before I have to open it up cause of time. I change ports, cameras, etc on these models so it's not a biggie to clean it. Will do this this weekend.
Click to expand...
Click to collapse
There have been multiple times that I couldn't get into recovery mode, but download mode worked fine.... I just reinstalled CWM and reflashed.
May not help the root cause, but may get you past the no-recovery mode issue.
morgandc said:
There have been multiple times that I couldn't get into recovery mode, but download mode worked fine.... I just reinstalled CWM and reflashed.
May not help the root cause, but may get you past the no-recovery mode issue.
Click to expand...
Click to collapse
Neither works. DL mode turns off after 2-3 seconds; I have even induced it with a DL dongle. Repeats the same. Recovery mode is a no go-phone flashes sammy logo and goes silent. You are right the first issue to fix is the power button. I will update this weekend once I take it apart. Thanx all the same.
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.
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.