This is a Moto Z Play XT1635-01 on Verizon in the US.
Can someone point me in the right direction to try to fix this? I've been digging in the forum for a few days and see there are many options to try to do various things, but from what I can see it looks like the only solution will be burning some useful image onto an sdcard?
Without the charger, the phone is entirely dead. Although it is not charging, and will not start.
On the charger I can get the Pwr/VolDn boot screen, however there is no reaction from any selection here:
The initial screen shows various info, one of which is a green "Battery OK".
"Start" - it will show blue Moto screen for 1 second and then shut off.
"Restart bootloader" - same
"Recovery mode" - same
"Factory mode" - same
"BP mode" - same
"Power off" - well it does shut off successfully!
The barcode screen does show apparently useful data.
On this Win10 pc I installed adb, and the Motorola Device Manager, but the phone will not do anything, I get about a 1 second blinking white light on the phone, butit will not respond to Pwr/VolDn boot.
Honestly I just don't know where to find the info.
Any help is appreciated, thank you.
The story goes like this, my wife stuffed the phone in her waistband getting on the roller coaster ride(her pockets were too small and she was worried it might fly out, which has happened before once at Universal Studios). So I asked if the battery was low, she said no, it was fine. But she does run gps, wifi, and bluetooth so I assumed that maybe with us walking around under many of these metal roofs and standing in lines for a couple of hours maybe the battery was lower than she realized. So I have to question the possibility of it being a battery issue.
But the battery is not charging without the system being there.
It seems to me like the operating system is blank. (what is this, second stage bootloader stuff?)
Maybe the phone was that scared on the ride? lol :silly:
I wondered if the metal expansion contacts were all touching her skin and maybe there was static or something that caused a situation.
The most obvious thing seems to be with the phone stuffed in the waistband and the coaster harness pressing down on it and very likely any or all buttons, I can easily see it going into any mode and doing anything, although I guess there's not a boot option for "just erase everything".
You said you as, did you download fastboot as well or just adb , in that bootlaloader menu you should be able to use fastboot commands. But I think you may need to REFLASH the whole phone.
Related
Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.
You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.
Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin
Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.
Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.
Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.
I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.
"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.
Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.
15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.
Edit: Read second post for possible fix.
"Ugh, look at this idiot/noob posting another SDS thread! SPAMZ! " Now hold on there Mr./Mrs. forum person! Give me a chance, if you will, please! Let's start off with phone specs and all of that jazz.
Phone Specs (hopefully all-inclusive, sorry for unknown info)
Phone: Samsung Galaxy S III SPH-L710
Carrier: Sprint
Mobo: It's 16GB, so probably the one that's known to experience the SDS
ROM: FreeGS3 v3.0.0
Kernel: Ktoonsez (couldn't tell you the version, whatever the ROM came with when selecting "ktoonsezz" as my kernel during installation)
If you need more info, ask for it and I will try to supply it.
The Issue
So, I was sitting here using my phone as a wireless hotspot for my laptop, when I went to check on my phone because a webpage was not loading, when I turned on the screen it showed what I believe was the "critically low battery" pop-up, then the phone turned off in less than a second. First I tried to power the phone on: nothing happened. So, naturally, I grabbed my charger and plugged in my phone. Hopefully others know the screen that pops up when you plug in your GS3 while it is off, that little battery with the spinning circle in it? Well that pops up incredibly briefly, then my screen goes blank and the phone is completely unresponsive. I have tried battery pulls, multiple batteries, getting into download mode, anything and everything (as far as I know).
What to Do?
Do I have the SDS? :crying: Is the only option to take my phone in to a Samsung center and get them to repair it? (I think Samsung is building a GIANT building 5 minutes from my house.) Is there some simple thing I can do I am unaware of?
Thanks in advance //Slit
Miraculous Miracle! (9 steps)
Well I'll be darned (moments after post, of course)! I have a solution that may work for anyone with an identical issue:
1. Let phone sit plugged in to wall for some time (hour or so, 30 minutes is probably fine)
2. Keep phone plugged into wall
3. Have any case you may have and the back removed
4. Pull the battery
5. Have fingers ready on the download mode buttons
6. As soon as the battery is slipped in, press and hold download mode buttons
7. Miracle! (download mode starts)
8. Press down and reboot phone
9. Return to normal, clam, non-panicking state
Is Your Issue Semi-Identical to Mine?
If your phone will show that battery with spinning circle in it or light up the LED very briefly when you plug your phone into the wall, then this fix should work for you if done properly.
Hope this helps someone! //Slit
SlitWeaver said:
Well I'll be darned (moments after post, of course)! I have a solution that may work for anyone with an identical issue:
1. Let phone sit plugged in to wall for some time (hour or so, 30 minutes is probably fine)
2. Keep phone plugged into wall
3. Have any case you may have and the back removed
4. Pull the battery
5. Have fingers ready on the download mode buttons
6. As soon as the battery is slipped in, press and hold download mode buttons
7. Miracle! (download mode starts)
8. Press down and reboot phone
9. Return to normal, clam, non-panicking state
Is Your Issue Semi-Identical to Mine?
If your phone will show that battery with spinning circle in it or light up the LED very briefly when you plug your phone into the wall, then this fix should work for you if done properly.
Hope this helps someone! //Slit
Click to expand...
Click to collapse
I have a very similar situation. Was playing around on the phone, and then it just froze, went black and I haven't been able to turn it on since. When plugged in there is no light, unless I don't use a battery then I get a red light for a short while (short while at least on a PC, I haven't tried for an extended period of time when plugged into the wall). PC recognizes it kind of. It recognizes that something is connected, but that is about it. I'm going to give this method a shot, hopefully it works. Just in case though, any other ideas?
Unfortunately I left the phone on in its waterproof/dustproof cover, inside my fully-packed bag with no breathing space and in the car with windows rolled up under the hot sun for several hours.
Once I retrieved my phone it was already boot-looping.
It was very hot. I opened it up to see if there was anything burnt inside (motherboard, camera, SIM, etc.) but didn't see anything out of the ordinary (I'm no expert either).
It gets very warm quickly when I charge it.
I tried to get into the boot recovery mode to see if I could fix the loop by deleting cache or formatting or whatever tips I came across. It would boot, show the Note 4 Samsung Logo with the blue-lettered "recovery boot" in the top left-hand corner, vibrate, then restart and rinse and repeat.
The only hope I have is that it can get into download mode and I have not rooted the phone yet (and I have tried unsuccessfully so far). Is there anything that can be done to fix this? Thanks in advance to anyone who can help.
*shrugs*
Oh well, I'm a bit disappointed there hasn't been any reply to this
I've given up and replaced the motherboard and it's working again.
If any mod would be kind enough to delete this thread which didn't amount to anything, I'd be grateful.
Wondering if someone can help. My boys nexus 7, screen is unresponsive and is stuck on the lockscreen.... It seems the problem happened after a system update downloaded(shown in the image)
Anybody any idea how to fix this
Photo
Try resetting the device by holding the power button.
You could also try to safe mode, by holding the volume down button while booting (safe mode text should appear upon bootup in the bottom left corner).
memphisuklf said:
Wondering if someone can help. My boys nexus 7, screen is unresponsive and is stuck on the lockscreen.... It seems the problem happened after a system update downloaded(shown in the image)
Anybody any idea how to fix this
Click to expand...
Click to collapse
There are at least 3 possibilities.
1. On some, the touch responsiveness decreases with the battery being drained. In other words, the lower the battery percentage, the more unresponsive the touch becomes. Reaching a certain low level of battery would kill touch completely. But this usually occurs with a tab that has had responsiveness issue all along. If it's something new that takes place only at the downloading of the update, then it might not be. Just to make sure, turn it off completely, charge it fully, then turn it on again.
2. The touch problem just occurs out of the blue. You want to make sure the hardware is not at fault. The only way to do this is to remove the back cover and reseat the two-pronged amber cable from the digitizer, and the white/silver cable connecting the daughter card to the main board. If there's a problem of this kind, no amount of software workaround will cure it.
3. The update is the culprit. If this is the case, the only thing to do would be to flash another rom (preferably a custom one that has more or less been sanitized by a known dev.
If you have a lot of data you're not willing to part with, then you can try an OTG USB mouse to navigate and allow the update to install to see if the tab would return to normal after. I wouldn't advise this route since I've heard and read a lot about people bricking the tab from taking automatic updates. Stay away from anything official if you can help it.
So I've searched here AND the entire net for a fix for this but I cannot find it anywhere. I'm decently experienced in the area of androids, flashing, and rooting and currently own a rooted Moto G Play running a debloated stock rom with Xposed installed as my main device (besides the point but just so you know my level of experience.)
I was recently given a HTC Desire 526 and was told by the giver that she couldn't turn it on. So obviously my first thought was to try to enter bootloader mode. I charged the device and held the volume up and power keys to enter bootloader, and it was successful, but still no image on the screen, mind you there is zero visible damage on the phone screen or water damage on the inside so I'm guessing it can't be that the screen is broken physically. I confirmed that it was in bootloader by running fastboot and it is listed under devices when I run "fastboot devices." Vibration works and it occasionally outputs sound so I know the phone turns on (at least). I'm completely new to HTC devices and when i try to do almost anything involving flashing with fastboot I get the s-on error. Adb isn't available as I know that developer options, and furthermore, usb debugging has not been enabled on this device at all in the past.
Can I hard reset with just hardware keys (vol up, vol down, and power)? Everything online says yes and then the instructions go on to explain how to reset via the on screen bootloader menu navigation, that of which I can't see nor navigate with a black screen (I know these "solutions" to this problem make no sense considering I asked about a device with a screen that won't turn on, very frustrating haha.) If not, does anyone have any suggestions on what I could do to get the screen to work? Not sure if this matters but it is a verizon phone. Any info is appreciated as I'm coming to my last leg trying to get this going. So annoying feeling it vibrate and hearing sounds because I feel like it is definitely fixable without replacing the screen but I'm not 100% sure. Thanks.
Edit: My only solution is to see if someone who owns this device (currently I know no one with this device) can direct me on what to push, when, to reset without my screen, so I can navigate through that phone or through pictures of it.
This post can be deleted. Still don't know the cause but it turned on and all is well now. Now I'm just searching for a proper root method!