M8 stuck at Blue Android after update to CM14 - General Questions and Answers

Hi everyone!
I'm having a problem with my HTC One M8 after updating to cm-14.1-20161130-NIGHTLY-m8.zip. I was waiting for an appointment and playing with my phone when I noticed that an update was available. I really wasn't paying full attention, (e.i I got stupid!), and I applied the update via TWRP. When I installed the update, I got the following error, but it didn't notice it at that time:
##
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Installing zip file '/sdcard/cmupdater/cm-14.1-
20161130-NIGHTLY-m8.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: 1480477704
detected file system ext4 for /dev/block/platform/msm
_sdcc.1/by-name/system
Patching system image unconditionally
E:unknown command [log]
E:unknown command [log]
detected file system ext4 for /dev/block/platform/msm
_sdcc.1/by-name/system
detected file system ext4 for /dev/block/platform/msm
_sdcc.1/by-name/system
script succeeded: result was [1.000000]
Updating partition details...
...done
##
When I rebooted the phone, I was stuck at the blue android. I was able to reboot into developers mode and try to reflash which is when I saw the error warning. I powered off the phone and rebooted again and the phone booted, but it is not detecting the SIM chip or seeing wifi. Many apps are not working and error messages about apps not starting keep popping up, (com.android.phone has stopped, Google Play services keeps stopping, etc.). Some widgets are working, (Bob Clock 3D), but others like Beautiful Weather are not.
I tried to reflash with the previous rom, cm-13.020161010-NIGHTLY-m8, but that one, as well as cm-13.020160301-NIGHTLY-m8, but they just remain at the blue android. I then downloaded cm-14.1-20161201-NIGHTLY-m8 and tried to install that, but I got the same error. I also tried to reinstall Open GApps, both open_gapps-arm-6.0-mini-20160301 for cm-13 and open_gapps-arm-7.1-mini-20161201 for cm-14 with no results. I have also tried wiping the cache and the dalvik.
Does anyone have any suggestions on what I can try next?
Thanks
zog

Related

[Q] Drive errors reported in TWRP and trying to change to F2FS

I just got a used TF700t 64gb US version and I'm trying to flash it to CROMBI-KK. I was able to get it unlocked and TWRP 2.8.3.0 installed (the latest version as of 12/22/2014). However, every time I boot to recovery, it begins with a serious looking error. The output screen always starts off with this:
Updating partition details...
... done
Full SELinux support is present.
E:Failed to get default contexts and file mode for storage files.
MTP Enabled
No other errors are shown at first and I was able to flash the ROM. I tweaked something and it failed to boot so I went back in to reflash it. The error was still there. I have tried several wipes and changed to F2FS but the same error remains. I don't know if it's related to the error or not, but when I try to install while configured for F2FS, it always ends with another error and no OS installed. I didn't get the exact wording, but something about recursion and that something failed (it's quite vague).
Right now it is back to working, but it had to be on regular EXT4 and data journaling to work. Anyone know if there is any way to remove the storage error? Are there any other options I could try to get F2FS working?
You are only changing /data to f2fs, right?
Try to get the recovery log whenever something fails that shouldn't.
In TWRP: Advanced > Copy log
From PC: adb pull /tmp/recovery.log
berndblb said:
You are only changing /data to f2fs, right?
Try to get the recovery log whenever something fails that shouldn't.
In TWRP: Advanced > Copy log
From PC: adb pull /tmp/recovery.log
Click to expand...
Click to collapse
I was trying to do F2FS on all three available locations (/system, /cache, and /data). I didn't realize that I was only supposed to do it on /data, though when I looked at my older device, that's how it was configured as well.
So the F2FS error is figured out, but then there was the issue of the error in TWRP immediately on loading it. I rebooted my older TF700 into recovery and it did not have the error line. However, I noticed that it was running TWRP 2.8.0.1 and my newer one was running TWRP 2.8.3.0. I upgraded the older device to 2.8.3.0 and, lo and behold, the error appeared. So I'm relieved that the error doesn't seem to be an actual problem with my new device, but I'm curious still on what it means and how to resolve it. Is this something that is just inherently funky with TWRP now, or is there something I can do to configure my device so it will register as TWRP is expecting?
techturtle said:
I was trying to do F2FS on all three available locations (/system, /cache, and /data). I didn't realize that I was only supposed to do it on /data, though when I looked at my older device, that's how it was configured as well.
So the F2FS error is figured out, but then there was the issue of the error in TWRP immediately on loading it. I rebooted my older TF700 into recovery and it did not have the error line. However, I noticed that it was running TWRP 2.8.0.1 and my newer one was running TWRP 2.8.3.0. I upgraded the older device to 2.8.3.0 and, lo and behold, the error appeared. So I'm relieved that the error doesn't seem to be an actual problem with my new device, but I'm curious still on what it means and how to resolve it. Is this something that is just inherently funky with TWRP now, or is there something I can do to configure my device so it will register as TWRP is expecting?
Click to expand...
Click to collapse
It seems to be a bug in TWRP 2.8.3. I just flashed that version (was on 2.8.1 before), flashed data2sd.zip an got the E: Failed to get default context.... error. I am dirty flashing ZOMBi now and got the same error although the flash seems to be going fine.
I'll post the logs in the TWRP thread. Let's see what the experts have to say....

Unable to install Rom Successfully

I love the liquidsmooth rom but a few months ago I suddenly couldn't install new updates or any other rom.
I'm using Team Win Recovery Project v2.7.0.0. I've been doing this for years exactly as the instructions say .
This is what it says at the end of installing zip:
Patching system image unconditionally...
Flashing SuperSU...
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc. 1/by-name/system at /system: Device or resource busy
script succeeded: result was [/system]
Updated partition details...
So then I reboot and it seems ok until I leave wifi and try to use mobile data, then it freaks out (freezing, image contouring, no phone reception). I found that I have to restart my phone in order to turn on mobile data and even then it only works half the time I do that and when it does work it's only while I keep the screen off. If I turn the screen off and go back to it a minute later it freaks out again...
I've scoured the internet trying to find a solution but everything seems to fail...
This is the last thing I tried:
http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
cmh436 said:
I love the liquidsmooth rom but a few months ago I suddenly couldn't install new updates or any other rom.
I'm using Team Win Recovery Project v2.7.0.0. I've been doing this for years exactly as the instructions say .
This is what it says at the end of installing zip:
Patching system image unconditionally...
Flashing SuperSU...
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc. 1/by-name/system at /system: Device or resource busy
script succeeded: result was [/system]
Updated partition details...
So then I reboot and it seems ok until I leave wifi and try to use mobile data, then it freaks out (freezing, image contouring, no phone reception). I found that I have to restart my phone in order to turn on mobile data and even then it only works half the time I do that and when it does work it's only while I keep the screen off. If I turn the screen off and go back to it a minute later it freaks out again...
I've scoured the internet trying to find a solution but everything seems to fail...
This is the last thing I tried:
http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
Click to expand...
Click to collapse
I would do a reset with stock recovery.
So I would flash RUU boot to ROM, back to hboot do factory reset.
Then flash custom recovery flash ROM see how it goes.
cmh436 said:
I love the liquidsmooth rom but a few months ago I suddenly couldn't install new updates or any other rom.
I'm using Team Win Recovery Project v2.7.0.0. I've been doing this for years exactly as the instructions say .
This is what it says at the end of installing zip:
Patching system image unconditionally...
Flashing SuperSU...
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc. 1/by-name/system at /system: Device or resource busy
script succeeded: result was [/system]
Updated partition details...
So then I reboot and it seems ok until I leave wifi and try to use mobile data, then it freaks out (freezing, image contouring, no phone reception). I found that I have to restart my phone in order to turn on mobile data and even then it only works half the time I do that and when it does work it's only while I keep the screen off. If I turn the screen off and go back to it a minute later it freaks out again...
I've scoured the internet trying to find a solution but everything seems to fail...
This is the last thing I tried:
http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
Click to expand...
Click to collapse
Is your firmware up to date?
Sent from my Nexus 6 using Tapatalk
blah
andybones said:
I would do a reset with stock recovery.
So I would flash RUU boot to ROM, back to hboot do factory reset.
Then flash custom recovery flash ROM see how it goes.
Click to expand...
Click to collapse
\
I've been trying to use these directions to do what you said:
[wouldn't let me post a link but it was using DOTTAT files]
The Option 1 didn't work because somehow the "format" option of my sd card has disappeared and I don't have a card reader on my computer.
The second one, I kept trying to run the program and it would just say that my phone battery was less than 30% even though it wasn't.
Do you have better directions?

Am I doomed? What does '32k crc checked failure' mean?

I happened to get Mate 8 two days ago, and it turned out that it was a Chinese version.
- The phone version is: NXT-TL00C01B596
- Android version was 7(and some decimals, maybe.),
- EMUI version was 5.0.1 or something if I remember correctly.
I wanted to flash an international stock rom, so started with this thread.
- I got the bootloader unlocked,
- installed TWRP following this instruction,
and downloaded some roms from here,
(I downloaded roms starting with 'NXT-L09' since I read they're international version).
I went to TWRP, and wiped and formatted (without a backup, idiot!), and tried to flash the downloaded update.zip file, and got the following message:
Installing zip file '/external_sd/update (1).zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Removing unneeded files...
Patching system files...
Removing empty directorys...
Unpacking new files...
add link type file...
write radio image...
32k crc checked failure
E:unknown comman [errno]
E:unknown comman [errno]
update_huawei_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Installing zip file '/external_sd/update (1).zip'
Updating partition details...
...done
I know not much, but I guess the error started at where it says '32k crc checked failure'.
I searched for what it means and what'd be the solution for it, but it seemed there aren't much information about it.
Then I decided to roll back to original rom to make it work again, so found a rom from 'firmware finder for Huawei' app.
And when I tried to flash it on TWRP, I got this error message:
Installing zip file '/external_sd/update.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Warning: No file_contexts
mountencrypt: failed to mount /data: Success
script succeeded: result was []
write radio image...
check_write_data_to_partition,write data error update_huawei_pkg_from_ota_zip: update package from zip failed
E:unknown command [errno]
Updater process ended with ERROR: 9
Error installing zip file '/external_sd/update.zip'
Updating partition details...
...done
I tried dload method with the original rom for my device(NXT-TL00C01B596), and it gives me an error message "Software install failed" almost instantly.
(i see 5% progress for a moment)
I still have an access to eRecovery, so tried it, and it also got me an instant error message "Download package failed" at 0%.
And I also still have an access to fastboot.
Now I'm so confused in which step I made a mistake.
Did I install a wrong version of TWRP? Or should I not have attempted to flash the roms from different version?
I tried to figure it out by myself by searching, but am getting more confused.
Could anyone help me out from this issue?:crying:
dasidaz said:
I happened to get Mate 8 two days ago, and it turned out that it was a Chinese version.
- The phone version is: NXT-TL00C01B596
- Android version was 7(and some decimals, maybe.),
- EMUI version was 5.0.1 or something if I remember correctly.
I wanted to flash an international stock rom, so started with this thread.
- I got the bootloader unlocked,
- installed TWRP following this instruction,
and downloaded some roms from here,
(I downloaded roms starting with 'NXT-L09' since I read they're international version).
I went to TWRP, and wiped and formatted (without a backup, idiot!), and tried to flash the downloaded update.zip file, and got the following message:
Installing zip file '/external_sd/update (1).zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Removing unneeded files...
Patching system files...
Removing empty directorys...
Unpacking new files...
add link type file...
write radio image...
32k crc checked failure
E:unknown comman [errno]
E:unknown comman [errno]
update_huawei_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Installing zip file '/external_sd/update (1).zip'
Updating partition details...
...done
I know not much, but I guess the error started at where it says '32k crc checked failure'.
I searched for what it means and what'd be the solution for it, but it seemed there aren't much information about it.
Then I decided to roll back to original rom to make it work again, so found a rom from 'firmware finder for Huawei' app.
And when I tried to flash it on TWRP, I got this error message:
Installing zip file '/external_sd/update.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Warning: No file_contexts
mountencrypt: failed to mount /data: Success
script succeeded: result was []
write radio image...
check_write_data_to_partition,write data error update_huawei_pkg_from_ota_zip: update package from zip failed
E:unknown command [errno]
Updater process ended with ERROR: 9
Error installing zip file '/external_sd/update.zip'
Updating partition details...
...done
I tried dload method with the original rom for my device(NXT-TL00C01B596), and it gives me an error message "Software install failed" almost instantly.
(i see 5% progress for a moment)
I still have an access to eRecovery, so tried it, and it also got me an instant error message "Download package failed" at 0%.
And I also still have an access to fastboot.
Now I'm so confused in which step I made a mistake.
Did I install a wrong version of TWRP? Or should I not have attempted to flash the roms from different version?
I tried to figure it out by myself by searching, but am getting more confused.
Could anyone help me out from this issue?:crying:
Click to expand...
Click to collapse
Hi
Try install a Chinese old nougat rom like b562 with twrp.

Not able to flash Stock image with custom Recovery (TWRP 3.1.1.1.)

Hello guys,
Today I wanted to update my Honor 8 (FDR-L09) because it was showing me, that there is a new update ready to install (FRD-L09C432B405) and I was on a very old firmware (something from mid 2017). So it was time for me to update.
I downloaded the latest update (FRD-L09C432B405) and tried to wipe the cache, dalvik, and Data, but for some reason it "couldn't mount /data" and the wipe failed.
After an advanced wipe it worked and I tried to flash the stock image (the update which was shown to me (FRD-L09C432B405) with TWRP (3.1.1.1.)).
Now my hassle starts:
1. The Rom couldn't get flashed because of "Error: 7" --> I fixed it with the common "Error 7 fix --> editing the update-script and removing the assert line. (And yes, I'm 100% sure that it was the right ROM.
2. Now TWRP seemingly starts to flash the rom but inbetween the lines there is "mountencrypt: failed to mount /data: no such file or directory and it ends with "unknown command [[]" and it takes just two seconds, so the flash obviously isn't succsessfull.
I tried the "failed to mount /data" fix, where I change the data system to ext3 and then back to f2fs and change it back, but it won't work.
In my frustration I did another pretty bad thing and made another advanced wipe and wiped the system too, so now I don't have an OS on my system.
Maybe it's also important to note that there was a window showing up for a very short amount of time, with something like "encryption/encrypted" showed up.
What should I do now? Is there a way to fix the "/data couldn't be mounted" problem? Or am I missing a vital step in flashing the stock rom?
Thanks for your kind help!
You can not flash an update with twrp unless you use hurupdater. You essentially bricked your phone. Look for hurupdater here on xda and follow the instructions and you'll be fine

Noob (in Android workings) needs help updating rooted HTC One M8 (Verizon?) 32GB

Hi folks,
I'm a relatively tech-savvy individual of the elder generation. I recently acquired a secondhand HTC One M8 on eBay (well, its one of a number, as gifts) but I'm having trouble with the OTA update from Android 4.4.4 (KitKat?) failing to be updated to 4.21.512.4 via my Virgin Mobile's SIM. To complicate matters, I'm away from home, in Sofia Bulgaria, but I do have a relatively fast Internet connection here and roaming privileges.
When the update is successfully downloaded I get a screen saying:
Install now
Install later
Don't install
If I select Install now, i get the rooted(?) bootloader(?) which announces itself as TeamWin 3.0.0-1 gives me a set of 8 buttons:
Install - Wipe
Backup - Restore
Mount - Settings
Advanced - Reboot
This is unknown to me, but if I just hit the Install button I get failure messages:
<begins>
(in white text)
Updating partition details...
...done
Full SELinux support is present.
Running Recovery Commands
Installing zip file '/data/media/0/Download/OTA_M8_WL_L50_SENSE60_MR_LRA_US_4.21.512.4-3.31.512.2_release_426215.zip'
Installing zip file '/data/media/0/Download/OTA_M8_WL_L50_SENSE60_MR_LRA_US_4.21.512.4-3.31.512.2_release_426215.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
L50QCT.01.001.009
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: File exists
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: File exists
Package expects build fingerprint of htc/lra_us/htc_m8wl:4.4.4/KTU84P/395691.2:user/release-keys or htc/lra_us/htc_m8wl:5.0.1/LRX22C/470008.4:user/release-keys; this device has .
(in red)
Updater process ended with ERROR: 7
Error installing zip file '/data/media/0/Download/OTA_M8_WL_L50_SENSE60_MR_LRA_US_4.21.512.4-3.31.512.2_release_426215.zip'
(in white again)
Done processing script file
MTP Enabled
<ends>
Could someone please explain what I need to do to get the update(s) to Android 6.0 (Marshmallow?) to proceed?
Regards
Tim Clarke
OK, I've realised that the Team Win 3.0.0-1 menu is in fact TWRP (DOH!) and have updated that to the latest release and also installed Titanium Backup Pro,so I am all ready to make an update,but the failure message is still the sticking point. How/where do I get/put this signature (file?)?

Categories

Resources