Very long boot time htc one m8

Search This thread

denisdm91

Member
Aug 16, 2014
14
0
Hello to all members of this wonderful forum.
I'm Italian, so my English isn't perfect.

I have a htc one m8, I unlocked it, I installed the TWRP recovery, I installed Android HD Revolution 10.2 and the kernel Elementalx.

I noticed, however, that in addition to the red writing at bootup, the phone takes a long time to turn on, even 3/4 or 5 minutes.

Why?

I can't understand where is the problem, I have already tried to wipe cache and dalvik.

I don't have enabled ART.

Can you help me please?
 

SouthernEvo

Senior Member
Aug 6, 2010
473
55
Jacksonville FL
I would hazard a guess you have older Firmware installed on your phone and that version of Android HD requires the newer firmware of whatever carrier phone you have . Most complaining of long boot times and wifi issues is generally a result of a mismatch of firmware version . Check your firmware version in "About Phone" section of your device then check the thread of the before mentioned rom you are running and see if they are similar firmware versions .
 
  • Like
Reactions: navid0308

denisdm91

Member
Aug 16, 2014
14
0
I would hazard a guess you have older Firmware installed on your phone and that version of Android HD requires the newer firmware of whatever carrier phone you have . Most complaining of long boot times and wifi issues is generally a result of a mismatch of firmware version . Check your firmware version in "About Phone" section of your device then check the thread of the before mentioned rom you are running and see if they are similar firmware versions .

I heard of custom rom, recovery, kernel, unlock, s-off. but never by firmware.

I never had these problems with one m7, galaxy s2/s3 and s4. can I have a guide for the firmware?

however, if I update the firmware, can I lose the data?

I can't see the current firmware version.

to do the firmware update should be s-off?
because a month ago when I tried I couldn't do the s-off. maybe because I had the custom rom. ??
 

5m4r7ph0n36uru

Senior Member
Apr 23, 2014
3,799
3,489
MD5: 91497e1b11f2262d0d8ff0aa7a164f3b
I heard of custom rom, recovery, kernel, unlock, s-off. but never by firmware.

I never had these problems with one m7, galaxy s2/s3 and s4. can I have a guide for the firmware?

however, if I update the firmware, can I lose the data?

I can't see the current firmware version.

to do the firmware update should be s-off?
because a month ago when I tried I couldn't do the s-off. maybe because I had the custom rom. ??

To get your firmware version you also can use the getvar main command in fastboot mode. For more detailed guides just search this forum.

By updating firmware you won't loose any date, but you have to be s-off to do it, yes. Firewater s-off does the job for some of the users, but not all. SunShine does it in most off the cases were firewater doesn't. But it won't work on a custom ROM. You got to have a stock RO.M to perform the S-Off procedure.

Sent from my HTC One_M8 using XDA Free mobile app
 
Last edited:

denisdm91

Member
Aug 16, 2014
14
0
To get your firmware version you also can use the getvar main command in fastboot mode. For more detailed guides just search this forum.

By updating firmware you won't loose any date, but you have to be s-off to do it, yes. Firewater s-off does the job for so be users, but not all. SunShine does it in most off the cases were firewater doesn't. But it won't work on a custom ROM. You got to have a stock RO.M to perform the S-Off procedure.

Sent from my HTC One_M8 using XDA Free mobile app
ùI'm trying to do s-off with sunshine.
but it ask me the stock kernel. where is it?
 

5m4r7ph0n36uru

Senior Member
Apr 23, 2014
3,799
3,489
MD5: 91497e1b11f2262d0d8ff0aa7a164f3b
ok, with the maximushd 5.0 rom sunshine worked.
my device is now s-off.

where can I check if it worked?

now I have to update the firmware to version 2.22.401.5 to install the viperone 2.1.0.

can you send me a guide?

In bootloader you can check if you are S-Off. If SunShine gave a positive you should be by now.

What you have to do is:
1) download firmware 2.22.401.4, ViperOneM8 Full ROM and TWRP.

2) Change CID I if needed to correspond with above named FW.

3) flash firmware

4) flash TWRP

5) got to recovery, enable adb sideload and sideload Viper ROM from adb folder and install.

6) reboot and be happy to use ViperOne ROM

Sent from my HTC One_M8 using XDA Free mobile app
 

denisdm91

Member
Aug 16, 2014
14
0
In bootloader you can check if you are S-Off. If SunShine gave a positive you should be by now.

What you have to do is:
1) download firmware 2.22.401.4, ViperOneM8 Full ROM and TWRP.

2) Change CID I if needed to correspond with above named FW.

3) flash firmware

4) flash TWRP

5) got to recovery, enable adb sideload and sideload Viper ROM from adb folder and install.

6) reboot and be happy to use ViperOne ROM

Sent from my HTC One_M8 using XDA Free mobile app
asks me to change the cid.

I tried to give the command fastboot oem writecid VZW_001 but doesn't work
 

denisdm91

Member
Aug 16, 2014
14
0
asks me to change the cid.

I tried to give the command fastboot oem writecid VZW_001 but doesn't work
fastboot oem writecid 11111111

and then:
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,99
INFO[RUU]WP,hboot,100
INFO...... Successful
INFOstart image[sbl1-1] unzipping for pre-update...
INFOstart image[sbl1-1] flushing...
INFOsignature checking...
INFO[RUU]WP,sbl1-1,0
INFO[RUU]WP,sbl1-1,100
INFO...... Successful
INFOstart image[sbl1-2] unzipping for pre-update...
INFOstart image[sbl1-2] flushing...
INFOsignature checking...
INFOverified fail
INFO...... Bypassed
INFOstart image[sbl1-3] unzipping for pre-update...
INFOstart image[sbl1-3] flushing...
INFOsignature checking...
INFOverified fail
INFO...... Bypassed
INFOstart image[rpm] unzipping for pre-update...
INFOstart image[rpm] flushing...
INFO[RUU]WP,rpm,0
INFO[RUU]WP,rpm,100
INFO...... Successful
INFOstart image[tz] unzipping for pre-update...
INFOstart image[tz] flushing...
INFO[RUU]WP,tz,0
INFO[RUU]WP,tz,100
INFO...... Successful
INFOstart image[sdi] unzipping for pre-update...
INFOstart image[sdi] flushing...
INFO[RUU]WP,sdi,0
INFO[RUU]WP,sdi,100
INFO...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
 

denisdm91

Member
Aug 16, 2014
14
0
I repeated the command and it gave me this:
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,99
INFO[RUU]WP,hboot,100
INFO...... Successful
INFOstart image[sbl1-1] unzipping for pre-update...
INFOstart image[sbl1-1] flushing...
INFOsignature checking...
INFO[RUU]WP,sbl1-1,0
INFO[RUU]WP,sbl1-1,100
INFO...... Successful
INFOstart image[sbl1-2] unzipping for pre-update...
INFOstart image[sbl1-2] flushing...
INFOsignature checking...
INFOverified fail
INFO...... Bypassed
INFOstart image[sbl1-3] unzipping for pre-update...
INFOstart image[sbl1-3] flushing...
INFOsignature checking...
INFOverified fail
INFO...... Bypassed
INFOstart image[rpm] unzipping for pre-update...
INFOstart image[rpm] flushing...
INFO[RUU]WP,rpm,0
INFO[RUU]WP,rpm,100
INFO...... Successful
INFOstart image[tz] unzipping for pre-update...
INFOstart image[tz] flushing...
INFO[RUU]WP,tz,0
INFO[RUU]WP,tz,100
INFO...... Successful
INFOstart image[sdi] unzipping for pre-update...
INFOstart image[sdi] flushing...
INFO[RUU]WP,sdi,0
INFO[RUU]WP,sdi,100
INFO...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediat

C:\ Fastboot \adb-windows>fastboot flash zip firmware1.zip
sending 'zip' (99380 KB)... OKAY
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOtotal_image_number=12

INFOstart image[adsp] unzipping & flushing...
INFO[RUU]UZ,adsp,0
INFO[RUU]UZ,adsp,11
INFO[RUU]UZ,adsp,21
INFO[RUU]UZ,adsp,33
INFO[RUU]UZ,adsp,44
INFO[RUU]UZ,adsp,54
INFO[RUU]UZ,adsp,66
INFO[RUU]UZ,adsp,76
INFO[RUU]UZ,adsp,87
INFO[RUU]UZ,adsp,99
INFO[RUU]UZ,adsp,100
INFO[RUU]WP,adsp,0
INFO[RUU]WP,adsp,100
INFO...... Successful
INFOcurrent_image_number=0

INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,14
INFO[RUU]UZ,boot,24
INFO[RUU]UZ,boot,36
INFO[RUU]UZ,boot,47
INFO[RUU]UZ,boot,63
INFO[RUU]UZ,boot,82
INFO[RUU]UZ,boot,96
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,99
INFO[RUU]WP,boot,100
INFO...... Successful
INFOcurrent_image_number=1

INFOstart image[dzdata] unzipping & flushing...
INFO[RUU]UZ,dzdata,0
INFO[RUU]UZ,dzdata,9
INFO[RUU]UZ,dzdata,16
INFO[RUU]UZ,dzdata,23
INFO[RUU]UZ,dzdata,31
INFO[RUU]UZ,dzdata,38
INFO[RUU]UZ,dzdata,46
INFO[RUU]UZ,dzdata,55
INFO[RUU]UZ,dzdata,62
INFO[RUU]UZ,dzdata,67
INFO[RUU]UZ,dzdata,74
INFO[RUU]UZ,dzdata,81
INFO[RUU]UZ,dzdata,86
INFO[RUU]UZ,dzdata,93
INFO[RUU]UZ,dzdata,100
INFO[RUU]WP,dzdata,0
INFO[RUU]WP,dzdata,9
INFO[RUU]WP,dzdata,28
INFO[RUU]WP,dzdata,39
INFO[RUU]WP,dzdata,47
INFO[RUU]WP,dzdata,54
INFO[RUU]WP,dzdata,59
INFO[RUU]WP,dzdata,67
INFO[RUU]WP,dzdata,74
INFO[RUU]WP,dzdata,83
INFO[RUU]WP,dzdata,97
INFO[RUU]WP,dzdata,100
INFO...... Successful
INFOcurrent_image_number=2

INFOstart image[pg2fs_spcustom] unzipping & flushing...
INFO[RUU]UZ,pg2fs_spcustom,0
INFO[RUU]UZ,pg2fs_spcustom,23
INFO[RUU]UZ,pg2fs_spcustom,45
INFO[RUU]UZ,pg2fs_spcustom,67
INFO[RUU]UZ,pg2fs_spcustom,88
INFO[RUU]UZ,pg2fs_spcustom,100
INFO...... Successful
INFOcurrent_image_number=3

INFOstart image[ recovery ] unzipping & flushing...
INFO[RUU]UZ, recovery ,0
INFO[RUU]UZ,recovery,8
INFO[RUU]UZ,recovery,14
INFO[RUU]UZ,recovery,21
INFO[RUU]UZ,recovery,28
INFO[RUU]UZ,recovery,37
INFO[RUU]UZ,recovery,42
INFO[RUU]UZ,recovery,61
INFO[RUU]UZ,recovery,68
INFO[RUU]UZ,recovery,74
INFO[RUU]UZ,recovery,81
INFO[RUU]UZ,recovery,86
INFO[RUU]UZ,recovery,91
INFO[RUU]UZ,recovery,99
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,99
INFO[RUU]WP,recovery,100
INFO...... Successful
INFOcurrent_image_number=4

INFOstart image[sensor_hub] unzipping & flushing...
INFO[RUU]UZ,sensor_hub,0
INFO[RUU]UZ,sensor_hub,100
INFO[RUU]WP,sensor_hub,0
INFO[RUU]WP,sensor_hub,4
INFO[RUU]WP,sensor_hub,8
INFO[RUU]WP,sensor_hub,12
INFO[RUU]WP,sensor_hub,16
INFO[RUU]WP,sensor_hub,20
INFO[RUU]WP,sensor_hub,24
INFO[RUU]WP,sensor_hub,28
INFO[RUU]WP,sensor_hub,32
INFO[RUU]WP,sensor_hub,36
INFO[RUU]WP,sensor_hub,40
INFO[RUU]WP,sensor_hub,44
INFO[RUU]WP,sensor_hub,48
INFO[RUU]WP,sensor_hub,52
INFO[RUU]WP,sensor_hub,56
INFO[RUU]WP,sensor_hub,60
INFO[RUU]WP,sensor_hub,64
INFO[RUU]WP,sensor_hub,68
INFO[RUU]WP,sensor_hub,72
INFO[RUU]WP,sensor_hub,76
INFO[RUU]WP,sensor_hub,80
INFO[RUU]WP,sensor_hub,84
INFO[RUU]WP,sensor_hub,88
INFO[RUU]WP,sensor_hub,92
INFO[RUU]WP,sensor_hub,96
INFO[RUU]WP,sensor_hub,100
INFO...... Successful
INFOcurrent_image_number=5

INFOstart image[sp1] unzipping & flushing...
INFO...... Successful
INFOcurrent_image_number=6

INFOstart image[tp] unzipping & flushing...
INFO..... Bypassed
INFOcurrent_image_number=7

INFOstart image[tp] unzipping & flushing...
INFO..... Bypassed
INFOcurrent_image_number=8

INFOstart image[wcnss] unzipping & flushing...
INFO...... Successful
INFOcurrent_image_number=9

INFOstart image[ radio ] unzipping & flushing...
INFOtrying to rename MBA
INFO...... Successful
INFOcurrent_image_number=10

INFOstart image[rcdata] unzipping & flushing...
INFO...... Successful
INFOcurrent_image_number=11

OKAY


now on the phone is the HTC logo and a progress bar half green and half black.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I would hazard a guess you have older Firmware installed on your phone and that version of Android HD requires the newer firmware of whatever carrier phone you have . Most complaining of long boot times and wifi issues is generally a result of a mismatch of firmware version . Check your firmware version in "About Phone" section of your device then check the thread of the before mentioned rom you are running and see if they are similar firmware versions .