So i keep trying to flash validus.everything flashes fine it starts to optimize the apps then freezes.upon reboot it boots straight into rom.all is good for about 2-3mins then freezes.any ideas or suggestions?
Related
So I started to download the Angry Birds Beta(One of my fav iPhone games), when my Evo decided it would be a great time to do a random reboot.
After phone reboots, I go back to the market. Start the download over, it completes. Then starts to install, when it then notifies me of a Unsuccessful Installation. Now I have tried this several times, rebooted the device a few times, even got the .apk and tried manually installing. With no dice.
Does anyone have any suggestions, or know how I can rectify this situation?
Thanks!
Running gingerbones with the latest kernel edited in atools
So basically what happens is on starting my phone it's really slow sometimes it crashes out sometimes it boots, so when it does boot i run task killer and find that near enough all of my apps have launched on boot
i kill them and the phone is fine again why is this happening?
Hey! I wanted to follow this Tutorial -> klick.
After i finished it, some of the Apps on my SD card didn't work anymore. I wanted to do a factory reset. The Problem is, i deleted some of the system apps, i even deleted the home.apk. I couldn't to anything without the home launcher, so i flashed a zip with launcher pro throu recovery. I downloaded root explorer and wanted to copy my backuped /system/app over to my phone, but i think this wasn't a good idea. The system crashed and just many many force closes came up. I closed everything, but the system still wanted to close, so i removed the battery...another bad idea. Now, if i want to turn on my Phone, the boot animation stops and the phone reboots and is doing the same.
I really hope anybody here can help me
It's called a bootloop, and from what you described caused it, it may be unfixable without flashing a fresh rom with flashtool.
Sent from my R800i using Tapatalk
Fine, but how can i do this? I've read that i habe to hold power when plugging it in while Flashtool is looking for an device, but the phone is just trying to boot normally
EDIT:
Ok, i have to push the back button... but if i want to Flash, i get this:
10/040/2012 06:40:20 - ERROR - Error flashing. Aborted
10/040/2012 06:40:20 - INFO - Now unplug the device and power it on
10/040/2012 06:40:20 - INFO - Then go to application settings
10/040/2012 06:40:20 - INFO - turn on Unknown Sources and Debugging
but i cant do this.
Found a solution! I installed the newest Firmware again with SEUS and everything is working. Thanks, XDA!
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
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.