Hello,
I'm new to the Android scene and already I have a problem.
I successfully upgraded my HTC Magic with Cyanogenmod.
I did it exactly like it said in the instructions on cyanogenmod wiki.
Installed Android SDK R05 for Windows and used:
bc-4.2.15.1-ebi1-signed
recovery-RA-sapphire-v1.6.2H.img
update-cm-4.2.15.1-signed
DRC83_base_defanged
HTC_ADP_1.6_DRC83_rooted_base
So i did the magic on Magic and the CyanogenMod worked, at least until recently.
My co-worker asked me to lend him my sdcard so i opened the magic and took out the sdcard from my htc that was on while i did that.
Than the trouble came forth...After a reboot the phone started booting for a long time...than it showed an error that the sdcard wasn't unmounted properly, and it didn't go away even when i inserted the sdcard back in, even after a hundred or so reboots. Than it started to crash the processes (acore and such)
Than after a milionth reboot the screen and the accelerometer stoped working, soon after that the keys followed the screen and the acc. I was thinking maybe the screen and the keys stoped working permanently and wanted to throw the phone away. But after another optimistic restart the keys worked for some time than the ball when pressed stoped responding...so i could highlight an icon on the home screen but couldn't start it. Than i accidentaly pressed it on the screen and it worked, but shortly after that everything was dead again. Than the phone started rebooting on a low battery. When rebooting to bootloader (with the battery fully charged) the screen flashes and nothing responds. But it still shows in a flash those three androids on the skates. And i can't seem to adb push the recovery.img to the sdcard...states some Read only problem. Sdcard seems alright through the card reader. So that is about it of all the problems.
So i was hoping some experts on here could give me some feedback on the device. Is it finished or can I rescue it. I really fell in love with this phone so I would much rather here the second option. I'm attaching the log from adb logcat if it is for any use to any of you...
Thanks in advance
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
flyingsherpa said:
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
Click to expand...
Click to collapse
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
noahvt said:
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
Click to expand...
Click to collapse
I have to confess my ignorance here... I'm brand new to flashing android like this so I don't know the answer to your question. If part of tutorial I followed blanks out the bootloader (and doesn't write something in?)... then you're probably right. I shall look into this more tonight when I'm at home with the nexus. Thanks for at least giving me something to look into, that's exactly what I was hoping for!
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Asus_USA said:
a7medmo7eb - We're very sorry to hear of this. Kindly email us at [email protected] with this copied problem description along with the serial number of your tablet and we will do our best to provide you with troubleshooting and servicing options.
If you have any further questions, comments or concerns please do not hesitate to let us know. We will be more than happy to assist you. Once again, thank you for choosing ASUS products and services.
Thank you.
-In Search of Incredible-
Technical Support Department
http://www.asus.com :: http://service.asus.com/
Click to expand...
Click to collapse
nhizzat said:
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Click to expand...
Click to collapse
Thanks, you're probably right. I did read up to understand all this stuff a bit more, so I know it's not lack of a bootloader or anything. All img files install just fine, so my pc can talk to the nexus, just the screen is all wonky no matter what i do.
Unfortunately I bought this 1.5 years ago so I don't think it's under warranty anymore. Everything was fine until I updated to Lollipop! Seems a big coincidence that I had a hardware failure at the same time as that update... I feel like Google ruined my tablet...
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Masterchief87 said:
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Click to expand...
Click to collapse
Hmm, thanks for the idea, but fastboot wouldn't do "format data", giving me the error: Formatting is not supported for filesystem with type ' '
Googling that makes it not look good. Weird, thing is, it still technically boots up, just the screen is so wonky you can't see where you are or interact with it properly. Not sure what else to try (opening it up and re-seating touchscreen cables?).
I think my phone may have had a catastrophic hardware failure but I am hoping not and maybe some of you clever people can help me resurrect it.
I have been running KK ParanoidAndroid without any problems for a few months. Yesterday I tried to boot it up and after showing the Google screen the screen went black then a single horizontal white line appeared 3/4 way down the screen. It stalled there forever so I pulled the battery and booted into TWRP recovery. It seemed to take a lot longer than normal but did boot into TWRP OK.
Once there however TWRP reported no backups, no OS and no storage space (0 MB). I couldn't mount any partitions,. I tried factory reset but it appeared to fail and just made the phone vibrate for a while. The log shows:
Unable to mount - /system, /cache, /data etc and something about no valid partition for MTP
Then the screen greyed out, faded to black and the phone powered off. Now it seems pretty much non responsive.
Any thoughts, other than bin it and get a new phone?
EDIT: It seems it hadn't powered off, just gone blank whilst attempting to wipe. I am now back in TWRP but the factory reset has failed. So. It seems I still have a functional recovery but not much else. Any help much appreciated.
In the absence of any responses I've searched a bit more and decided in the end to try to install a factory image using fastboot. I was holding out to see if there was any way I could save any user data but in the end that seems unlikely anyway.
So, I followed this guide: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
It all seemed to go smoothly until the final commend - after flashing the zip containing the system, boot and recovery images I got the error message "FAILED (remote: Write Fail)"
Hmmm...
Regardless I tried to finish off with fastboot reboot. As I hit enter the device screen faded slowly to a kind of washed out grey and the horizontal white line appeared on the display again (as before - see my first post). No further progress, and the device became unresponsive. I pulled the battery and tried to boot, and it bootlooped once to the Google screen before the screen faded to a washed out grey again and it became once more unresponsive.
After pulling the battery once more I can still get to fastboot, and I can now get to stock recovery, but otherwise I can't seem to get any further.
Is it toast??
Phone Details:
HTC ONE M8x
Stock Rom (Rooted)
Kit Kat (can't remember the exact version)
Unlocked BootLoader
S-ON
Ok so I'm having a bit of trouble with my phone which all started after a sudden reboot.
Heres the full story so the pros might be able to understand what happened:
While I was browsing the internet, my phone started lagging really badly. After a few more seconds of lag, the screen suddenly froze. When I tried to reboot the phone, the screen just offed and wouldn't turn on anymore though I could still feel the haptic feedback from touching the screen. Holding the power button still brought up the power menu so I decided to reboot and hope for the best. After the reboot the phone was still laggy but not as bad as before however a new problem appeared. I noticed that opening the File Manager App took longer than average and that moving/copying files from internal to external storage would freeze the app for a while but still finish the command.
After getting irritated of the sudden hiccups I decided to boot into the Recovery Menu (mine is TWRP) and try something to see if it works.
I cleared 'Dalvik Cache' and 'Cache' first then rebooted. The phone started like normal but when it got the part of Updating Apps, it stopped at Starting Apps. So I decided to reboot into Recovery again, after clearing the Dalvik Cache and Cache again I went to 'Reboot', but... (HERE'S WHERE THE BIG PROBLEM HAPPENED) instead of choosing 'Power Off', I clicked 'System' and the phone froze. After a while, the phone rebooted but this time it didn't want go past the point where it shows the ONE logo. Panicking, I went to the recovery mode again and went straight to 'Reboot', when I clicked 'Power Off', the notice at the top said:
No OS Installed!
Which led me to believe the phone wouldn't boot because of the lack of an OS... (OBVIOUSLY):crying:
Questions:
1) Is this problem considered as Soft-Brick or Hard-Brick?
2) How can I fix my phone?!
3) Can I install a stock ROM to fix it?
Moderator Information,
Thread has been closed, as you already have a thread open for this issue.
Many thanks,
Stephen
This happened just a little bit ago, but when I woke up this morning my phone was on a screen that said "Your device is corrupt. It can't be trusted and may not work properly." Then it gave me a link which just lead to the google help page for android, as well as a message at the bottom saying "to continue press the power button", though pressing the power button did nothing. After looking things up I loaded the bootloader and tried to activate recovery mode, but trying to do that just lead back to the screen. And I couldn't boot in safe mode since I can't even get to the loading animation. Is there anything I can do short of sending it to the manufacturer to flash the phone?
To my knowledge I've not downloaded any files recently beyond a few pictures, but those are all from trusted sources, and I've never tampered with the software, so I have no ****ing idea what could be causing the corruption.
Did you unlock the bootloader? If you did, you can flash the last official Google image for the device from their pages and restore your device to working order. Keep in mind however that anything on the phone will likely be lost if you didn't back it up, especially if you had set a pin or password for the device.