I just got and m8 from Cl, it was cheap and I was told the phone had a software issues so I took the plunge.
The phone seems normal, its pack o apps and you can play with it, then I decided to do a factory restore, but it failed (after the reboot it goes to a error screen showing a phone with and exclamation mark)
I tried the same from hboot, same result..
Tried to unlock bootloader, it appears to work but after boot the phone I still the same (loked and with all the user info intact )
Tried to erase the user accounts, it works, I can do a new setup of the Google account, but after restart the phone goes back to the initial state (user accounts are back)
I am not sure what's going on, but it looks like if the memory was protected and after every reboot it goes back to the original state.
Any suggestions of what to do? I am starting to see of there is any way to get warranty thru htc,
Thanks in advance.
The phone is in 4.4.2, can't take updated (it reboots itself on the process)
The phone with the exclamation point indicates the stock Android system recovery is installed. You could try and install TWRP recovery, at which time you could install a custom ROM. My only other thought is to run the RUU for the latest system update. If that doesn't straighten out your issues, something else is going on. Hit the link below and follow the instructions for the manual system update. This is the non-HK RUU. If you need the RUU for the HK version I can post it, also.
http://www.htc.com/us/support/htc-one-m8-sprint/news/
Thanks, I tried to install twrp but it fails, the bootloader is still locked and won't unlock, is there a way to install twrp without unlocking bootloader?
Will give it a try with the RUU, when tried to update thru fastboot it fails, it starts to do all the file checks and it just send you to the "press the power button message" , but no update was perform.
You might give this a try to get your bootloader unlocked and TWRP installed. There is no way around it. You have to unlock the bootloader first before you install TWRP.
http://forum.xda-developers.com/showthread.php?t=2727900
Thanks a lot for the help, nothing has work so far, the phone keeps having random reboots and every time it comes back its like it load an old backup, havent been able to do a firmwware upgrade (from android over wifi, fastboot, or windowsPC).
Is there an utility to test hardware? (possibly memory)
thanks
At the end I contacted HTC support and after some test I was told my phone was still under warranty and I got and RMA (great service)....
Thanks a lot for the help...
Hi everyone,
I seem to have nothing but trouble when it comes to installing OTA updates for my Gear Live, and am wondering if anyone can help me.
It all started when the Android 5.1.1 update notification arrived on my Gear Live some time ago. I eagerly installed it, and expected it to install without any problems. Unfortunately, the update reached around 30%, before displaying the Android mascot with a red exclamation mark. I managed to restart the watch, and re-downloaded and installed the update. The same thing happened, except, it was stuck in a boot loop :crying:
I contacted Samsung Australia who took the watch in for repairs (it took them 4 weeks). I was pretty happy to see the watch working again, and running the 5.1.1 update.
Just yesterday, I received a notification that an update is ready to be installed. I swiped and hit install. The watch rebooted, and began the installation. Again, reaching 30% before failing and displaying the Android mascot with the red exclamation mark. I am yet again stuck in a boot loop. I managed to tap the Android mascot, which brought up the Android System Recovery. It said
"Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!"
I have cleared the cache, and have wiped the data through recovery. This seems to allow the watch to boot up, however, the process repeats itself when I try to update it again.
Does anyone know why the update would be failing, especially after it has already been repaired by Samsung, and how I can fix it myself (I don't really want to be without a watch again for 4 weeks)?
Thanks,
Tim
Did you try the live restore tool? (read the whole thread)
Brendo said:
Did you try the live restore tool? (read the whole thread)
Click to expand...
Click to collapse
I attempted to use it, however, it was unable to detect my device.
Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
Verifying current system...
"/system/priv-app/ClockworkHomeGoogle/ClockworkHomeGoogle.apk" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!
Click to expand...
Click to collapse
tims1710 said:
I attempted to use it, however, it was unable to detect my device.
Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
Click to expand...
Click to collapse
Try a different usb cable? (ie official, not a cheap one)
My watch always took a few goes to get detected by adb
tims1710 said:
I attempted to use it, however, it was unable to detect my device.
Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
Click to expand...
Click to collapse
I had that exact error yesterday when I was trying to install new OTA update. I flashed back to KMV78Y(from live restore tool v2) Don't use v3 it has corrupted file and breaks bluetooth.
Try to manually flash using fastboot. I wouldn't recommend trying to flash recovery partition from live restore tool since you can end up with a broken OTA and broken adb sideload. Also, don't try to flash TWRP into recovery partition. Loading it into ram memory is fine though.
Anyways, to manually flash using fastboot, you need to open console and go to directory of Gear live restore tool. Make sure your watch is in bootloader mode, not recovery. Type fastboot flash boot 78Yboot.img and then fastboot flash system 78Ysystem.img Do factory reset just in-case and upgrade your way up to latest firmware.
All right, my firmware was C636B168 the au version,
I was new to android, I thought there is only one type of the EVA-L09. So I upgraded it with the Android NOUGAT 7.0 EMUI 5.0 (EVA-L09C432B322), using the 3key update.
Now each time I tried to restart the phone it says: Your device has failed verification and may not work properly. But I can still contine boot it by press power key.
My ui don't even have camrea app on it, I am missing some of the deafult apps.
In about phone, my build numer is not eva-l09c432b322, it's NRD90M test-keys.
I've tried few ways to go back the B168,
1st I tried the rollback pack from the offical site, but then I found another problem, everytime when I tried to factory reset, it will fail, and says reset failed. So when I tried do the rollback, I can see it shows update install success, but then it goes reset failed, then reboot the phone,(still shows failed verification) the build number and version not changed.
Then I tried to do with TWRP, but when I flash the twrp.img, it says failed remote: command not allowed.
So guys, and suggestion? I can still use the phone, I can do most of the normal staffs, but, with out the camera app and some other missing apps, I don't think I should stay in this version, is their anyway to go back? Or go to a correct emui5?
the rollback is a 2 step procedure. first you flash de update.app in the rollback, and then you have your C636B168 and flash that.
EVA-L09C636B168:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1079/g104/v55680/f1/full/changelog.xml
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1079/g104/v55680/f1/full/update.zip
dracushor87 said:
the rollback is a 2 step procedure. first you flash de update.app in the rollback, and then you have to find your C636B168 and flash that.
Click to expand...
Click to collapse
Yes I understand, but when I flash the first update.app, it should make the system to C900B300,
but in my case, I can't even finish this step, when I update the package, It shows update success, but then shows reset failed, I don't know if this is the reason makes the update failed.
by the way I tried to install the b168 after this, but it shows wrong version, so I think the 1st step is not done.
i think you need a memory card, because the instructions say you shouldn't load it to the internal memory. and after the first flash, don't reset it. just flash directly
On the intermediate flash (1st update.app), check if build changed, because mine also said reset failed but it changed to C900
dracushor87 said:
i think you need a memory card, because the instructions say you shouldn't load it to the internal memory. and after the first flash, don't reset it. just flash directly
Click to expand...
Click to collapse
The thing is, I am using the sd card, and I didn't manually reset it, after update it did it itself, and tells me its failed, let me record a video, so u guys can see whats going on.
jamorimpt said:
On the intermediate flash (1st update.app), check if build changed, because mine also said reset failed but it changed to C900
Click to expand...
Click to collapse
Thanks for reply, but its not change, sadly.
dino333 said:
The thing is, I am using the sd card, and I didn't manually reset it, after update it did it itself, and tells me its failed, let me record a video, so u guys can see whats going on.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=Cqbosc3_w2Y
this is the video link, this time don't know why it didn't show the reset failed, but I tried few times when I upload this video, the reset failed shows again, and I found it says " user reset" then " reset failed"
dino333 said:
https://www.youtube.com/watch?v=Cqbosc3_w2Y
this is the video link, this time don't know why it didn't show the reset failed, but I tried few times when I upload this video, the reset failed shows again, and I found it says " user reset" then " reset failed"
Click to expand...
Click to collapse
I think the main problem now is I can't do anything if it need factory reset.
Do not give up on this version to do a reset.
Do as you are doing colleagues giving a link to the instructions.
I did it without any problem
Does anyone know how to fix failed verification or failed reset?
Hi, i have the same problem now, any one can help?
Any one can help me? I'm going to die t-t i want to go back to mm
I had the exact same problem. I flashed the intermediate update file but the reset failed and my customer did not change. In spite of this, I flashed the newest firmware for my device anyways and it rolled back fine.
This worked for me, but I can't guarantee it will work for you. I'm L09C636
I have tried to flash from recovery, 3 buttons, but it only stuck at 5%. Please help me i'm going to cry t-t
Try rebooting to the huawei eRecovery (idk how, but look it up). Download the correct version through there and install it. (have stock recovery, or it will always fail).
To those having issues, my experience may help below. I installed this (unofficial I believe) beta, which is rubbish, so tried to roll-back.
Important Note: I installed the beta update from this post: , which isn't the official beta that everyone is registering for. Don't assume this will work if you are trying to roll-back from official beta.
I didn't use the rollback package for official beta, I used a stock ROM, B166 in my case. I added the update file to a Dload folder on my SD card and tried the 3 button method. Didn't work, 5% and stuck each time.
So used the dialler to input *#*#2846579#*#*, then select "Software Upgrade" - "SDCard Upgrade
This worked first time!
Hope it helps someone
RidgeBoyGenius said:
I had the exact same problem. I flashed the intermediate update file but the reset failed and my customer did not change. In spite of this, I flashed the newest firmware for my device anyways and it rolled back fine.
This worked for me, but I can't guarantee it will work for you. I'm L09C636
Click to expand...
Click to collapse
Hi,thanks for the help, can u tell me which firmware did u use?
FedoraMan said:
Try rebooting to the huawei eRecovery (idk how, but look it up). Download the correct version through there and install it. (have stock recovery, or it will always fail).
Click to expand...
Click to collapse
the erecovery failed getting info
Newkeebrown said:
To those having issues, my experience may help below. I installed this (unofficial I believe) beta, which is rubbish, so tried to roll-back.
Important Note: I installed the beta update from this post: , which isn't the official beta that everyone is registering for. Don't assume this will work if you are trying to roll-back from official beta.
I didn't use the rollback package for official beta, I used a stock ROM, B166 in my case. I added the update file to a Dload folder on my SD card and tried the 3 button method. Didn't work, 5% and stuck each time.
So used the dialler to input *#*#2846579#*#*, then select "Software Upgrade" - "SDCard Upgrade
This worked first time!
Hope it helps someone
Click to expand...
Click to collapse
Thanks for the help. My 3 button doesn't work, the funny thing is, My *#*#2846579#*#* doesn't work either, I type this code but I dont get the page we usually have, sad...
i'm in desperate need for guide please,
so i first off i had some questions (excuse my stupidity but i really couldn't find any answers around)
1) can an never-rooted android device's build number change or is it always the same? like with stock/official updates only?
2) my recovery mode (stock/system recovery) aborts every single installation file (official rom from the Asus website) without even opening the package, it's like i press 'install update from sd card' then as i press the zip file, it immediately says 'installation aborted' without even typing any other significations/steps, and the same happened for the kernals zip files too. so does that mean my recovery mode is corrupted or something is wrong with it?
3) i noticed some slight changes in my recovery since the last bootloop i had and had to use it back then, for example the dead android screen appearing after choosing the recovery mode, at first it used to say 'no command' under the dead android, but this time it doesn't say anything, just the dead android image only until i press power button and volume up to get the recovery options. so does that mean my firmware version changes since last time or my recovery is corrupted or it just means nothing?
4) is there aNYWAY to know my build number of a phone in bootloop (not rooted but bootloader unlocked)
so my initial problem is; i had my asus zenfone go zc500tg on march 2016. it was working so fine actually (using it like a default user not actually knowing anything about roms/flashing/recovery etc) until july of 2017 when i noticed my phone was a bit slow (out of the ordinary) and it used to get SO hot while using it normally and battery drained pretty faster than before, but i didn't know what to do tbh so i just kind of ignored something was off. but not long after these symptoms, the booting of my phone got slower and slower, until it reached its max by staying more than three hours just doing the 'optimizing apps' on the booting screen until it booted, so i thought it was a virus that would go away after a factory reset, and after the reset, it got worse, until it stopped booting and got into a bootloop. I panicked then because i didn't have the slightest idea what was happening until some internet searching guided me into the world of bootloops and custom roms and recovery. so i eventually managed to fix the bootloop and it worked fine for several months until it started to lag again and boot slowly and got the second bootloop, and that i fixed like the first one by installing the rom from the asus website then putting it on the sd card sand flashing it through recovery,
the third bootloop was quite the same, except that i did something additional in recovery mode, i pressed "backup user data" and that did a nandroid backup then i restored it smoothly after flashing the rom.
the fourth bootloop was a bit different, i as always downloaded the same firmware as the times before and flashed it and backed up user data too, but the odd thing that happened was me getting a message box that won't go away that said "unfortunately, the process com.android.phone has stopped" the phone worked but the sim cards weren't recognized and the message box was coming and going every second, so i noticed that the message box went away (nearly) when i got my sd card out, but still the phone app and the sim cards were corrupted,i thought the issue was from my sd card at first but i eventually, (coincidentally tbh) managed to fix it by doing the OTA update that was due, (that bootloop was fixed on the date of January 13th 2018)
then my phone was working so fine and everything was alright.
then shortly after (january 20th 2018) i was on whatsapp normally then suddenly ALL the things on my phone came crashing in front of me : TONS of endless message boxes saying things like "unfortunately, the process com.(any app on my phone) has stopped"
that i literally panicked and tears welled up in my eyes, so i rebooted the phone and while rebooting it did a (relatively quick) "optimizing apps" but as it booted everything was the dreaded same, all the apps crashing, then with the second rebooting was the current bootloop. i thought it was the same as before and just downloaded the usual zip file i use everytime but while flashing it (it did the same as mentioned in question 2 above) but it aborted instantly so i went and downloaded every rom there but it was the same so i went and tried the kernal zips too but always the same (i can't read my build number through the system recovery because it is like not fitting well in the screen si half the number isn't there that's why i asked question number 4)
so can anyone help me please? i'm in desperate need for help, i'm literally crying while typing this because i can't afford another phone and i'm so scared.
also is there a way to install custom recovery to not rooted device while in bootloop?
or if the system recovery was actually corrupted what do i do? :crying:
Dearest forum,
I'm a little desperate:
My P10 randomly crashed yesterday evening without any obvious reason and got stuck in a boot loop for a few rounds. After 10 mins or so, it got its **** together and worked normally throughout today. Unfortunately, in the evening the same problem happened again. This time, I tried the "Download latest version and recovery" in the eRecovery menu but sadly, after installation it got stuck again during reboot (loop) and probably couldn't finish the recovery process completely.
So when I try to do the same thing again now over wifi, it displays the error message "Getting package info failed". The other two options "Emergency backup" (thankfully I used today to create some backups) and "Wipe data/factory reset" are greyed out and not selectable.
I haven't tried a factory reset yet, as I am hoping to still find a solution without losing my data. Is there a possibilty to do what eRecovery is supposed to do via fastboot? The HiSuite unfortunately just says, that my device is not supported for recovery...
Strange thing is, my phone is neither rooted nor unlocked. These times are way in the past for me, so I lost all my knowledge about all that stuff.
I first suspected the battery to have caused the initial problem, since that's the only thing I have changed over the years (Polarcell), but it didn't display any strange behaviour and all cable connections were in place, too. But now, after the unsuccessful recovery attempt, I suspect a soft brick?
Would appreciate any help!
Try to unlock it via potatoNv
(PotatoNV is free)
And then flash any firmware you like
Have a nice day