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
Related
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
Afternoon all,
Last night I left my Desire charging as normal, having recently installed the Remote Media App. I suspect it used up all my storage with some sort of indexing process, as I returned to the phone this morning to find it perpetually showing the glinting HTC logo.
A reboot failed to clear it, and booting into recovery mode reveals"E:Error in DATA:data/recovery/log, (No space left on device)"
I've tried connecting to it with adb, but I get the following error
- exec '/system/bin/sh' failed: No such file or directory (2) -
Is there any way out of this bind? I had/have ClockWorkMod recovery installed in order to use ROM Manager, but I'm not terribly clued up on what else is out there on offer.
Any advice would be greatly appreciated.
Kyle
Try rebooting the phone into recovery mode and wipe/factory reset and see if this fixes it?
(Although you will loose all your apps/settings/scenes, though)
This should resolve the problem though.
hehe, there is always that option. I was hoping not to lose texts, settings, etc though this time round. Sadly my backup is more than a few days old.
I was mistaken in thinking I had ClockWorkMods recovery image installed, it appears to have gone back to the default image. I've just discovered a modified recovery ROM from JesusFreke here http://forum.xda-developers.com/showthread.php?t=443041 which may be of use.
Having to wipe and start from scratch again is a disgustingly appaling out of space failure mode. >:-/
bin the phone and use a pineapple
That recovery image is for G1! Don't even think about flashing it.
Even if you have stock recovery, you should still be able to clear storage from HBOOT.
Regards,
Dave
One other thing that might be worth trying is booting the device in safe mode.
Whilst the phone is power down, hold down the menu button and then power on - keep menu held down until the phone is fully booted.
I doubt that it will help in this situation, since clearly /data is completely full, but there's always a slim chance it work.
Regards,
Dave
munkehman said:
bin the phone and use a pineapple
Click to expand...
Click to collapse
Thanks for the advice m, I'll be sure to kick you in the nads next time you cross the border
Sadly Safe Mode fails too. The HTC logo appears and glints for a while, and then briefly vanishes just to reappear again. My thumb got sore after 5 minutes of holding the button down
I realised that was a G1 ROM shortly after reading more about it! I see there may be a more suitable recovery ROM at http://forum.xda-developers.com/showthread.php?t=709146 that I can flash. Failing that, then I'll clear storage and consign myself to failure
Wahey! It's sorted! Well, it was sorted a couple of hours ago, but a meeting got in the way
Wrote up some of the details here - http://lodge.glasgownet.com/2010/08/31/recovering-a-htc-desire/ if anyone is interested!
kylegordon said:
Wrote up some of the details here - http://lodge.glasgownet.com/2010/08/31/recovering-a-htc-desire/ if anyone is interested!
Click to expand...
Click to collapse
Sorry to dig up an OLD OLD thread, but your "guide" helped me out last night.
In addition to looking for "big" items in the data partition, I also moved some of the Google updates (5meg Maps.apk anyone ?) from /data/app to /system/app ... renaming to overwrite the original version from my Rom.
Thanks Again.
Hello XDA,
I've searched the forum and couldn't find anything similar to the problem I have though, so here it goes...
This morning I wanted to check my Facebook through the official FB app on my phone. The whole thing hung up - couldn't even turn the screen off with the lock button. I removed the battery, the phone began to restart, then it restarted the process, then again, and again...
I removed the battery, the SD card and the SIM card, no difference. I inserted both cards and since then the phone just goes to the white screen with the "HTC" logo (not the one with the 'quietly brilliant" - the one before that) and then nothing happens.
I googled here and there, eventually got to the recovery screen. After choosing the 'recovery' option the screen goes black, then a green icon appears, after that a red triangle with an exclamation mark appears and the whole process restarts. After about three-four restarts the phone goes to the white screen with the "HTC" logo mentioned above. If I press Vol-Up+Power when the red triangle appears I get these three lines:
Code:
E: can't open /cache/recovery/command
E: can't mount /data/data/recovery/log
E: can't open /data/data/recovery/log
FAKE EDIT: when doing the restart to check the three lines while writing this post, after the third reboot to that red triangle icon the phone loaded the recovery menu with the options to reset to factory defaults, etc. I chose to whipe cache and after rebooting got as far as this "quietly brilliant" screen. After that the screen died, power button not responding. Another battery replacement and the difference is that now, after the screen dies the phone just restarts the "quietly brilliant" screen (and the annoying sound...).
Now, here's the trick that makes my case unique, compared to other people's problems on this forum: I did NOTHING to the phone earlier. It's the official, out of the box Android, updated to the latest version given by HTC (2.3.3 I believe) using the update option within the system, I didn't ever try to root it, mount anything, change ROMs, shorten the loading time. The only thing I did was installing some apps from the Android Market and the K9 mail client from an install file downloaded from their official site.
Can you help, XDA? : (
Cheers!
Alaknár
Could be a bad emmc or curropt partition, either wont matter if rooted or not. Try booting into safe mode (hold down s while powering on) if it boots you have a bad app, if not then one of the above is your problem.
If it doesnt work try a factory reset, if that still wont work then download the latgest ruu directly from htc, if that works your fine and it was just a curropt partition, if not that you most certainly have a bad emmc which unfortuntetly is not so easy to replace.
By not rooting it would be hard to check which chip you have other than opening up the phone and looking, which would void warranty if there even is any left. I find that in most cases rooting an android phone makes issues that arise easier to deal with in the long run but when its harware at fault it never matters
Sent from my HTC MyTouch 4G Slide using xda premium
demkantor said:
Could be a bad emmc or curropt partition, either wont matter if rooted or not. Try booting into safe mode (hold down s while powering on) if it boots you have a bad app, if not then one of the above is your problem.
If it doesnt work try a factory reset, if that still wont work then download the latgest ruu directly from htc, if that works your fine and it was just a curropt partition, if not that you most certainly have a bad emmc which unfortuntetly is not so easy to replace.
By not rooting it would be hard to check which chip you have other than opening up the phone and looking, which would void warranty if there even is any left. I find that in most cases rooting an android phone makes issues that arise easier to deal with in the long run but when its harware at fault it never matters
Sent from my HTC MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Thanks for responding!
I'm afraid I'm a noob in regard to smartphones, so I'll be needing a bit more detailed advice...
So, first of all: what do you mean by "hold down s while powering on"? What's "s"? : ) The "s" key on the QWERTY keyboard? If so, it doesn't work, I get the same greet screen restart loop as earlier.
Second: where do I even start looking for this "ruu"? A simple Google search didn't help me much. I got to a different forum with someone's post containing a dead link... : /
Yes that holding the s key, which being it didn't work it wasn't a malicious app causing your problem. For the ruu go to HTC.com > support > pick phone > go to downloads > find latest firmware/software download
You will need to get fast boot working to do this and I believe there will also be a link for any drivers you may news
Sent from my Nexus 7 using xda premium
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??
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
jerrytaff said:
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
Click to expand...
Click to collapse
Since posting this I have had a partial success. A more complete set of fastboot flashing using the TOS111B fastboot images has got me to a phone that boots. Many of the apps work. However...
a) I get an "unfortunately the process com.android.phone has stopped" appearing almost as fast as I can close the app making it very difficult to get anything off the phone. However, I did manage to set up a google sync to upload the photos.
b) my daughter now tells me that her SMS's are vital.... and the messaging app says " getting message" then closes down
c) I cannot enable developer setting to enable usb debug mode. I can get into the phone status page under settings. Repeated tapping on the android version brings up the nougat splash screen, but the 7 taps (or 700 for that matter) on build number does nothing whatsoever.
Does anyone have any ideas how to recover to a fully working system without doing a factory reset?
I suspect that the sms database would have gone when the cache was cleared. Can anyone confirm that to be the case before I spend any more time trying to recover them?
Hi Jerry ,
Exactly the same problem here. Could you tell me where you've found the TOS111B fastboot images?
Thx!
Have you tried booting into safe mode?
I think you do that by pressing and holding the volume down down button during reboot.
If you can manage that you may be able to dissable the apps that are causing the crash.