When the battery is inserted, my Desire X will automatically boot. The bootlogo will appear for ten seconds, and immediately shut off. Then (to my extreme annoyance) the process will begin all over again. And again. And again. Connecting my device to an outlet has no effect, nor taking the battery out for an extended period of time and reinserting it.
I am able to access hboot, but attempting to select anything (literally anything) on the phone results in the device restarting and thus entering the endless boot cycle. My bootloader is locked (HBOOT-1.25.0002, RADIO-1.15.40.04, eMMC-boot); I haven't bothered messing around with my phone. Neither of my computers (Windows 7 and 8) are able to recognise the device whilst in the bootloader. It appears I am missing some drivers. Updating to the latest version of HTC Sync Manager had no effect.
What I find particularly odd is that even when my phone isn't connected to a power source, the orange LED will still glow if the battery is inserted. I noticed this a few days ago when it was functioning properly (except the LED of course), perhaps there's an unlikely connection?
Any suggestions, methods, or other advice for restoring my phone would be sincerely appreciated. I do apologise if I my inquiry is ignorant or a waste of time, I will admit electronics are not my area of expertise.
ajsiryj said:
When the battery is inserted, my Desire X will automatically boot. The bootlogo will appear for ten seconds, and immediately shut off. Then (to my extreme annoyance) the process will begin all over again. And again. And again. Connecting my device to an outlet has no effect, nor taking the battery out for an extended period of time and reinserting it.
I am able to access hboot, but attempting to select anything (literally anything) on the phone results in the device restarting and thus entering the endless boot cycle. My bootloader is locked (HBOOT-1.25.0002, RADIO-1.15.40.04, eMMC-boot); I haven't bothered messing around with my phone. Neither of my computers (Windows 7 and 8) are able to recognise the device whilst in the bootloader. It appears I am missing some drivers. Updating to the latest version of HTC Sync Manager had no effect.
What I find particularly odd is that even when my phone isn't connected to a power source, the orange LED will still glow if the battery is inserted. I noticed this a few days ago when it was functioning properly (except the LED of course), perhaps there's an unlikely connection?
Any suggestions, methods, or other advice for restoring my phone would be sincerely appreciated. I do apologise if I my inquiry is ignorant or a waste of time, I will admit electronics are not my area of expertise.
Click to expand...
Click to collapse
In hboot try to do reset it will clear all your data in phone but your phone will start as i had also faced same problem but after this my phone start..
ajsiryj said:
When the battery is inserted, my Desire X will automatically boot. The bootlogo will appear for ten seconds, and immediately shut off. Then (to my extreme annoyance) the process will begin all over again. And again. And again. Connecting my device to an outlet has no effect, nor taking the battery out for an extended period of time and reinserting it.
I am able to access hboot, but attempting to select anything (literally anything) on the phone results in the device restarting and thus entering the endless boot cycle. My bootloader is locked (HBOOT-1.25.0002, RADIO-1.15.40.04, eMMC-boot); I haven't bothered messing around with my phone. Neither of my computers (Windows 7 and 8) are able to recognise the device whilst in the bootloader. It appears I am missing some drivers. Updating to the latest version of HTC Sync Manager had no effect.
What I find particularly odd is that even when my phone isn't connected to a power source, the orange LED will still glow if the battery is inserted. I noticed this a few days ago when it was functioning properly (except the LED of course), perhaps there's an unlikely connection?
Any suggestions, methods, or other advice for restoring my phone would be sincerely appreciated. I do apologise if I my inquiry is ignorant or a waste of time, I will admit electronics are not my area of expertise.
Click to expand...
Click to collapse
Did you try charging your battery for a few hours? Then try restarting.
Related
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 apologies if this is addressed elsewhere in the forum, but if it is I couldn't find it...at least, not exactly what I'm dealing with.
Phone: Verizon Samsung Galaxy Nexus (Toro)
I was running an unofficial Cyanogenmod of Android 5 on my phone for about 2 months with no problems. Last week the phone just shut off on it's own, and since then I've been stuck.
Here's what I can do (note, all these things can only be done if the phone is plugged in and has the battery in...no response at all if just on battery):
I can boot into the boot loader, and can toggle through the options (recover mode, start, etc), but every time I try to go int recovery the phone restarts, enters the google splash screen for a few seconds, then it flickers and shuts down, showing only the "battery charged" icon.
Same thing happens if I just try to start the phone normally...google splash screen, flicker, dead.
I've tried flashing a stable version of CM11 via the CM installer, but the phone just shuts down to the batter icon during the install.
My computer won't recognize the phone via usb (it keeps trying and failing, and trying and failing...again and again and again).
I tried accessing the phone via ODIN to flash the stock android 4.2.2 rom back onto it, but with no luck. Same problem as described above (i can also boot into ODIN Mode, but it stays on "downloading" and never gets past it - again, this is only when plugged in).
Before the crash the battery life was fine, and the "battery charged" icon shows it being fully charged whenever plugged in.
I've tried pulling the battery for long periods of time (overnight, all day, etc). Same result.
I feel like I hard bricked the thing...but if I did I wouldn't expect to be able to turn anything on...
Thanks, in advance for any suggestions!
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.
Hey there. I found a bit old phone in my house, Huawei G730-U10 with MTK6582. Here's problem:
Phone won't turn on at all (no reaction) with battery in and USB out.
With battery in and USB in (connected to charger or PC, no matter what), at first it turns on red led that stays still, and after some time it starts vibrating with interval of about 10 seconds and PC sees it for 2 secs (it connects and after 2 secs - disconnects), then everything repeats. I assume it's bootlooping, but there's no anything on screen (it doesn't even turn on, full darkness). This continues even after taking out USB, only way to stop it - take out battery and place it back.
With battery out and USB in, red led starts blinking with very quiet beeping (very very very quiet).
As you could guess - recovery, fastboot and other things aren't working.
I've checked main board, everything is ok, connected and working fine.
I think there's problem in ROM (not firmware ROM, but ROM that's read-only memory). Something's wrong, maybe there's wrong preloader (or there's no preloader at all), maybe boot partition is damaged, I don't know.
Service center tried to fool me on buying new board for 100$ (althrough it costs 40 on aliexpress), I think they didn't even look at it, so I can't trust them.
I don't need suggestions like "try to flash new rom", you think I didn't try? How is this possible if I can't make PC to see phone for more than 2 secs? Flashtool isn't working even without battery mode.
Do you have any ideas?
Thanks for help.
As the title suggests I have an old Z2 tablet that has been an absolute work horse for many years. I was using it one night and the Android OS prompted me that the device hadn't been rebooted in 28 days. So after I was done using it for the night I rebooted it. Only, it didn't reboot it just stayed off. I tinkered with it for a while and got it to show the Sony logo but then it just went dark again. The device is rooted and I have TWRP on it. So when I got it to turn on again I booted it into the TWRP recovery. I proceeded to clear the cache and also attempted to make a current backup. However, the backup would fail after running for several minutes. I decided to try backing up to an external OTG USB drive but the device needed to be rebooted to detect that the OTG USB drive was attached. So from TWRP I selected "reboot recovery".
Unfortunately that was the last time it worked. The screen will not come at all. When I hold volume+ and power it vibrates 3 times but still doesn't boot. I plugged it into the charger even though the battery charge last showed at 85%, but with the cable connected the charge light doesn't even come on. I tried plugging it into my computer but it doesn't detect the device has been connects and adb devices doesn't show anything in the list.
I read on a forum to try drying it out with a hair dryer and while the device hasn't ever gotten wet it has been humid here so I figured what the heck. Unfortunately that also hasn't resolved the issue.
Pretty much everything I've tried hasn't worked. Even the red reset button under the top panel just causes it to vibrate 3 times.
The device has been in this state for a week now. I was hoping maybe the battery would die and then I could recharge it, but since it still vibrates 3 times I'm guessing the battery still has a charge.
One thought I had is that maybe the internal storage is either dead or corrupted.
At this point I'm wondering if the device is a lost cause and I should just let it rest in peace or if there's any other solution. Even if there was a way to factory reset it from it's current state that would be better than having it be a paper weight.
Any suggestions beyond what I've already tried would be greatly appreciated. And, yes, I may look into seeing if I can get it serviced however there's definitely no warranty and I don't really want to poor money into it since it's probably time for an upgrade anyway.
Why is my phone vibrating 3 times and won't turn on? - Sony Xperia Z5
When I try to turn my phone on it just vibrates 3 times and does nothing after that, just wondering what the problem could be?? - Sony Xperia Z5
www.ifixit.com
The device vibrated 3 times, that's good, then it is off.
"Sony writes: This is how you force the device to turn off:
Press and hold the power button and the volume (+) button simultaneously until the device vibrates three times."
Did you try to put the device into flash mode after that? I think only a complete flash will bring the device back to life.