Database Info

Possible Corrupted flash?

Hey all,
I need some help. The other day my touch cruise was working fine, but I wasnt able to connect to the network, and I thought it was time to do a soft reset. After soft reset my phone has now stopped working. It is stuck on the screen that says:
POLA100
SPL-3.13.0000
CPLD-2
The screen has 4 color bars on it, in this order:
RED
GREEN
BLUE
WHITE (SERIAL OR USB)
Every time I reset the phone it quickly flashes the screen with a messege that I believe says "No Image Found"
Any ideas on how I can fix this?
Thanks for all your help guys in advance!
Matrixum

A quick update...
I have managed to get back into the phone. I plugged it into the usb, and of course it would not recognise it. However, after it was plugged in I held down the camera button, and the power button and pushed in the reset button, and vola the phone restarted back to normal. I have not lost the operating system or anything. I am not sure what will happen if I turn it off. So I plan on backing it all up and then trying to turn it off and on.
But if you have any answers to this problem please let me know as I am not sure what i have done.
Thanks again guys
Matrixum
Update:
Ok everytime I turn off my phone I go back to the tri color screen. The only way for me to get back into the phone is if I plug it into the USB and hold down the camera button and hit the soft reset. Any ideas?

I guess nobody has had this problem? I must be the first! Seriously.... Well I still have the problem, each time I shut off the phone and turn it back on it goes to the tri color screen. I have to do my combination of camera button and soft reset in order to get the phone to start properly. I dont loose any information, but the phone is now running very slugish at times.
Once again, any help would be great... Unless I am really the first one to run into this problem.
Thx,
Matrixum

Hmmm... I have no idea what could the problem be.
But I have some questions:
1. What OS is/was on your Polaris?
2. Have you managed to backup your data via ActiveSync or other means?
It looks to me like you're stuck somewhere in the upgrade process. But I'm not sure, just guessing.
I'd recommend flashing Polaris with official ROM.
Be aware that you'll lose all your data on device.

[Q] HTC One S bricked-ish

Hi,
long story short: while trying to install CM on my old one s I first flashed the boot.img as described here: h t t p : / / wiki.cyanogenmod.org/w/Install_CM_for_ville. It appears that the firmware overwrote the custom recovery on a reboot, and when I entered recovery to install CM I got a screen saying "entering recovery..." in pink at the top, htc logo in the middle, and "This build is only intended for development, to not leak from HTC" (something like that) in red at the bottom. Nothing happened.
I shut it down and started it back up, and it went to boot with the same htc logo and red message at the bottom -- and froze there. Only 10+ sec power button restarts it, nothing else helps. Weird enough I noticed that if it's on a cable it won't restart but just stay off, and if it's not connected it will restart immediately, no chance to switch it off.
Here's my biggest problem: my volume rocker is brocken. Up works somewhat, but down is 95% dead. I entered the bootloader through adb before, but since I can't boot the phone anymore I can't get in anymore.
It seems to me like the best solution would be to somehow fix the volume rocker. It's not 100% dead, occasionally I could get a keypress through, so I would just suppose the contacts are a little bad and I could just polish it a little? But the phone seems a pain to take apart.
What would you suggest? Is it too easy to break the whole thing while trying to clean the contacts of the rocker?
Thanks for any help / comments!
compul

why not change the volume button, at gsm service.
It's a good phone.

compul said:
Hi,
long story short: while trying to install CM on my old one s I first flashed the boot.img as described here: h t t p : / / wiki.cyanogenmod.org/w/Install_CM_for_ville. It appears that the firmware overwrote the custom recovery on a reboot, and when I entered recovery to install CM I got a screen saying "entering recovery..." in pink at the top, htc logo in the middle, and "This build is only intended for development, to not leak from HTC" (something like that) in red at the bottom. Nothing happened.
I shut it down and started it back up, and it went to boot with the same htc logo and red message at the bottom -- and froze there. Only 10+ sec power button restarts it, nothing else helps. Weird enough I noticed that if it's on a cable it won't restart but just stay off, and if it's not connected it will restart immediately, no chance to switch it off.
Here's my biggest problem: my volume rocker is brocken. Up works somewhat, but down is 95% dead. I entered the bootloader through adb before, but since I can't boot the phone anymore I can't get in anymore.
It seems to me like the best solution would be to somehow fix the volume rocker. It's not 100% dead, occasionally I could get a keypress through, so I would just suppose the contacts are a little bad and I could just polish it a little? But the phone seems a pain to take apart.
What would you suggest? Is it too easy to break the whole thing while trying to clean the contacts of the rocker?
Thanks for any help / comments!
compul
Click to expand...
Click to collapse
Taking it apart is smth you can do. Ik its hard, i tried but if you're confident its your power button then do it. After you reveal the back of our phone, you can access the buttons
CM11 Powered G-Wonder

null0seven said:
why not change the volume button, at gsm service.
It's a good phone.
Click to expand...
Click to collapse
While that is my last resort, I'd like to avoid it. I do have a working Nexus 5 after all.
TiTAN-O-One said:
Taking it apart is smth you can do. Ik its hard, i tried but if you're confident its your power button then do it. After you reveal the back of our phone, you can access the buttons
CM11 Powered G-Wonder
Click to expand...
Click to collapse
It's the volume rocker, not the power button; and it's been broken for a long time. I'm a little afraid I might rip things apart, but this makes it look outright easy: youtube.com/watch?v=6j25jajIq3g. I'll give it a try.

Black screen & no recovery!!!!

Hi all !!! Sorry for my English but I need your help
I commented what is happening with my phone N5 (which for good and evil is always stock without root or anything, with corresponding OTA updates.)
1- Yesterday afternoon at lunchtime while reading a book in playbooks, I notice that suddenly disappears one line and then appeared intermittently. I close the app and noticed the same thing happening on the screen menu. I shut down the cell and turn on again and I thought it must be an application be kidding. But still does.
2 Also yesterday I happened to change the security on the phone screen. After a while of normal operation, try to turn it on the screen with the button, nothing, the screen goes "black", with light and retrolight turned on but no picture no nothing .
Called the cell to see if it works or is turned off and the phone rings but the screen nothing. Try turning it off and on again by holding the on / off / lock button and the phone restarts, but the screen nothing. In one such attempt to do the above it is seen that managed to turn it off. And I get it on and do a normal boot, except that the picture of my screen is changed to the original. Change the lock screen which was previously using (slip). And it seemed that out or some conflict with the lock. In one of those again pressed the ON / OFF / lock as would normally and it starts all over again.
After I magically back to life, I want to make a full wipe as I think it should be an app that is doing some conflict or something. BUT ....
3I turn off the phone and then press the keys VOLUME UP / DOWN and ON / OFF is normally off, squeezed the first screen with the options but options RECOVERY / BOOTLOADER appears in red I choose RECOVERY give the ok with the key and .... andriod robot appears with the legend below that says something (I do not remember well) without or without controls options appears. So its seems thatI dont have recovery.
After that keep pressing the key ON / OFF and the phone turns off and / or reboot normally. All this I did it again to see if the error reappears and looks that I do not have recovery.
The failure of the screen is increasing. I dont know if they are separate problems or is it all the same problem.
Sorry if I was too long but I need the help of you.
UPDATE Now it seems that the screen died, since I do not achieve to turn it on as before, the light and the retrolight its ok. The phone receives calls and notifications but the screen stills black.
Thanks all.
Matias M 73

the android laying on its back IS the atock recovery.

simms22 said:
the android laying on its back IS the atock recovery.
Click to expand...
Click to collapse
thank you simms22 but I need to fix or understand what happend with the screen first.
:good::good:

Matias M 73 said:
thank you simms22 but I need to fix or understand what happend with the screen first.
:good::good:
Click to expand...
Click to collapse
sometimes things just "derp". itll happen more often if you dont reboot your phone often. also, your phone will be a little bit more responsive if it gets reboot once a day or two.

RMA or fastboot it back to stock, if the screen doesnt turn on afterwards then it looks like a hardware issue, open device and reconnect the display.

republicano said:
RMA or fastboot it back to stock, if the screen doesnt turn on afterwards then it looks like a hardware issue, open device and reconnect the display.
Click to expand...
Click to collapse
Thank you Republicano!!
I think too that its a hardware issue. I already see on you tube problems like mine.
Thanks again!!

Replaced screen, not booting

Hey guys,
just replaced my screen by myself and it isn't working. It boots and the screen lights up for a few seconds but thats it. So it seems like I ****ed up somewhere. :/
Now I've got some questions for you guys.
1. What could cause this error? Since it's already not working I don't mind taking it apart some more and trying to fix it.
2. Do you think if I send it to the support from OnePlus they will take a look at it?
3. The whole reason I did this was to get my data back. Is there any way to access the data on the phone without the touchscreen? I encrypted it using CynogenMod. USB-Debugging is enabled.
Thank you so much guys, I'd really appreciate some help. This **** is really tearing me down since it was a lot of work.

I did this on my own phone but Idk about OPO. If you use the power+voldown method to boot into recovery (yes ik nothing on screen) then connect a usb and see what happens
If you power it on, wait 5 mins then call it and if the phone rings you should be able to rule out the display and speakers and storage, obvs if the display is still not on at this point it is probably the display.
you can also adb from recovery and or fastboot so you should be able to see it in there if it is still working (make sure you change the phone for a decent amount of hours before you do any of these) If the display is dead its likely its been on for the last day and dead

Sorry for the late answer, really appreciate your help!
So if I connect the phone to the PC (tried it in recovery and in normal mode) windows detects the phone under "Devices" but sadly if I type in "adb devices" in cmd it doesn't detect the device.
But still, windows is detecting the phone so it seems to still function. I booted into recovery and I could use the touscreen and the lower buttons. I couldn't see anything but it was vibrating whenever I was using the touscreen. So it seems like only the display part is broken.
Can't call the phone since it's fully encrypted so I need to type in a password before booting anything (recovery, normal mode, ...)
I'll try to contact the vendor of the display and see what he has to say.
If anyone got any more tips I'd appreciate them. I'm a pretty big noob so I even appreciate "common sense" tips.

I know this may be a "common sense" thing to say, but double check your connections. Sometimes the connectors aren't made properly and a pin could be covered so you can try connecting and disconnecting several times to see if it clears up.
Since the touch screen was registering and vibrating, then it could be the backlight that's broken. Try holding a flashlight at an angle and see if you can make out anything on screen. If it's the backlight, then you can probably back up your data in case your phone does end up breaking.

reconnected everything multiple times and also tried the flashlight trick. sadly with both no luck
but something good:
adb recognizes my phone in "recovery"
bad news: no commands work, most likely because the phone is encrypted. if I enter a command nothing happens, it looks like its loading forever.
any ideas?

Hey!
I also had the same problem after I replaced OPO's screen about one year ago. The replacement screen was from ebay.
I could see the Cyanogen logo but after a few seconds the screen became black. Booting into recovery mode worked well.
On the video also ROM boots well but the screen stays black.
https://www.youtube.com/watch?v=VcWDCJIkPKQ
Eventually, the screen was defective and I returned it and bought new one.

I will try to answer all the problems of XZ2 :)

Hi , i have working with more than 100 xz2 phones , i got many problems and fix it (google and xda) , so I think I can help you to fix your problem with xz2 asap if u ask me in this post
My exp :
Flash
Unlock
Root
and some small problems...

[deleted]

sinommo said:
Hi , i have working with more than 100 xz2 phones , i got many problems and fix it (google and xda) , so I think I can help you to fix your problem with xz2 asap if u ask me in this post
My exp :
Flash
Unlock
Root
and some small problems...
Click to expand...
Click to collapse
Hello,
My wife's Sony Xperia XZ2 Compact with model number H8324 has an issue with booting or maybe the launcher getting stuck in a loop after getting to the lock screen for a split second.
The phone seems to boot like normal and gets to the lock screen, we are even able to punch in one or two digits of the 4 digit pass code. Then it goes into a loop of the notification bar and back button flickering. From then on the phone is not responding except for the power button which brings up the normal "Turn off, Reboot, and Lockdown" menu. The issue just started out of nowhere yesterday morning and we haven't been able to fix it yet. We haven't done any rooting or custom rom flashing, it's running the official Sony software but it's out of warranty.
Here's a video showing the issue. The video shows the whole boot process but the link takes you to the last part after the logos.
We would love to get some files off it so if there is a way anyone can help us with that we'd prefer it over a hard reset.
Things we've already tried
Turning the phone off and on again
Unlocking the phone in the split second the lock screen works, this is just too short to swipe up and then put in four digits.
Rebooting the phone
Booting while charging
Booting into safe mode (this has the same issue)
Connecting the phone with USB to a pc, the phone is recognized by Windows, but it doesn't share it's filesystem with Windows.
Connecting the ADB to it, alas usb debugging is not yet enabled on the phone
Trying to get into recovery mode, we haven't been able to get into the recovery menu. Googling seems to indicate it might be holding volume up + power button when the phone is off but then it doesn't seem to do anything at all.
We're currently trying to run out the battery of the phone to see if that will resolve the issue on it's own.
If anyone has any idea, we would love to hear it.

mohhom said:
Hello,
My wife's Sony Xperia XZ2 Compact with model number H8324 has an issue with booting or maybe the launcher getting stuck in a loop after getting to the lock screen for a split second.
The phone seems to boot like normal and gets to the lock screen, we are even able to punch in one or two digits of the 4 digit pass code. Then it goes into a loop of the notification bar and back button flickering. From then on the phone is not responding except for the power button which brings up the normal "Turn off, Reboot, and Lockdown" menu. The issue just started out of nowhere yesterday morning and we haven't been able to fix it yet. We haven't done any rooting or custom rom flashing, it's running the official Sony software but it's out of warranty.
Here's a video showing the issue. The video shows the whole boot process but the link takes you to the last part after the logos.
We would love to get some files off it so if there is a way anyone can help us with that we'd prefer it over a hard reset.
Things we've already tried
Turning the phone off and on again
Unlocking the phone in the split second the lock screen works, this is just too short to swipe up and then put in four digits.
Rebooting the phone
Booting while charging
Booting into safe mode (this has the same issue)
Connecting the phone with USB to a pc, the phone is recognized by Windows, but it doesn't share it's filesystem with Windows.
Connecting the ADB to it, alas usb debugging is not yet enabled on the phone
Trying to get into recovery mode, we haven't been able to get into the recovery menu. Googling seems to indicate it might be holding volume up + power button when the phone is off but then it doesn't seem to do anything at all.
We're currently trying to run out the battery of the phone to see if that will resolve the issue on it's own.
If anyone has any idea, we would love to hear it.
Click to expand...
Click to collapse
I think u just need to reinstall rom file with newflasher and stock rom , did u tried it ? with newflasher newest version , u still can keep the personal files and flash stock rom for the phone , then i think this phone will run normal again
If u dont know how to do that , reply comment here , but u should turn off the phone to keep battery well , if u can't turn off the phone , try to press and hold volume up button + power button within 5 sec , phone will vibrate 3 times and totally off

Is there a way to get a stock recovery if somehow the recovery has been deleted?