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?
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 .
SouthernEvo said:
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 .
Click to expand...
Click to collapse
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. ??
denisdm91 said:
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. ??
Click to expand...
Click to collapse
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
HTCNerdYoda said:
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
Click to expand...
Click to collapse
ùI'm trying to do s-off with sunshine.
but it ask me the stock kernel. where is it?
denisdm91 said:
ùI'm trying to do s-off with sunshine.
but it ask me the stock kernel. where is it?
Click to expand...
Click to collapse
As I wrote you've got to be on a stock ROM, not on a custom ROM.
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
As I wrote you've got to be on a stock ROM, not on a custom ROM.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
can I use this?
http://forum.xda-developers.com/showthread.php?t=2694994
odexed
denisdm91 said:
can I use this?
http://forum.xda-developers.com/showthread.php?t=2694994
odexed
Click to expand...
Click to collapse
and, how can I return one m8 to 100 % stock?
my CID is: T-MOB101
denisdm91 said:
and, how can I return one m8 to 100 % stock?
Click to expand...
Click to collapse
On the arhd downloads site they have a stock odexed ROM that I used for sunshine. Worked perfectly.
Heisenberg420 said:
On the arhd downloads site they have a stock odexed ROM that I used for sunshine. Worked perfectly.
Click to expand...
Click to collapse
where?
can you send me the link please?
I just have to flash the rom, right?
denisdm91 said:
where?
can you send me the link please?
I just have to flash the rom, right?
Click to expand...
Click to collapse
I read that MaximusHD 5 is compatible with sunshine.
I feel that at this point
denisdm91 said:
I read that MaximusHD 5 is compatible with sunshine.
I feel that at this point
Click to expand...
Click to collapse
Read that too, but never tested it.
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
Read that too, but never tested it.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
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?
denisdm91 said:
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?
Click to expand...
Click to collapse
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
HTCNerdYoda said:
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
Click to expand...
Click to collapse
asks me to change the cid.
I tried to give the command fastboot oem writecid VZW_001 but doesn't work
denisdm91 said:
asks me to change the cid.
I tried to give the command fastboot oem writecid VZW_001 but doesn't work
Click to expand...
Click to collapse
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)
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.
Reflash again immediately. Most times you need to flash firmware twice
stathis95194 said:
Reflash again immediately. Most times you need to flash firmware twice
Click to expand...
Click to collapse
I turned off the phone in bootloader and leave and re-gives me this:
M8_UL PVT SHIP S-OFF
CID-T-MOB101
HBOOT-3.18.0.0000
radio-1.19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS-2.22.401.5
Related
hi
Im not getting past step2 on this guide
Im getting device not found error....see below (NB. i have htc sync installed and working correctly
(might also be worth noting that i noticed this line come up whist doing step 1 "FAILED (remote: 42 custom id check fail)"
(is this the cause of the problem below?)
Rebooting to bootloader...
rebooting into bootloader... OKAY
Step 1 complete - now use the bootloader menu to enter recovery mode.
To do this, press the power button, wait a few seconds, then use the volume keys
and power button to select the RECOVERY option.
C:\Users\Chris\Desktop\HTC STUFF\Unzipped R5\r5-desire-root>step2-windows.bat
Desire Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
error: device not found
C:\Users\Chris\Desktop\HTC STUFF\Unzipped R5\r5-desire-root>
InspectorFrost said:
hi
Im not getting past step2 on this guide
Im getting device not found error....see below (NB. i have htc sync installed and working correctly
(might also be worth noting that i noticed this line come up whist doing step 1 "FAILED (remote: 42 custom id check fail)"
(is this the cause of the problem below?)
Rebooting to bootloader...
rebooting into bootloader... OKAY
Step 1 complete - now use the bootloader menu to enter recovery mode.
To do this, press the power button, wait a few seconds, then use the volume keys
and power button to select the RECOVERY option.
C:\Users\Chris\Desktop\HTC STUFF\Unzipped R5\r5-desire-root>step2-windows.bat
Desire Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
error: device not found
C:\Users\Chris\Desktop\HTC STUFF\Unzipped R5\r5-desire-root>
Click to expand...
Click to collapse
Try set your device to HTC Sync, and do the ./... again
disconnect then reconnect your device and try again
Error 42, isn't that related to a goldcard?
Do you have a branded Desire?
I had the same problem. Started out rooting on my Win7 x64. Got past step 1 - failed with device not found on step 2.
Finally I started all over using a Tiny Core Linux guide (sorry - for some reason I'm not allowed to post outside links - yet?). Google "easy desire Linux rooting guide".
I know it's Linux but it's really not that hard. Only thing I missed in the guide was the fact that when selecting something from the recovery menu you have to actually press the optical trackball.
Good luck
Rudolfje said:
Error 42, isn't that related to a goldcard?
Do you have a branded Desire?
Click to expand...
Click to collapse
I would also recommend the Goldcard method here. Although my Desire is supposedly unbranded, I got the same error which was solved by using a Goldcard.
I previously hit 42 error as well.
Its related to the Goldcard in Step1... try to use another SD card. I used Sandisk 1GB and it works.
Device seems Bricked? PLS HELP URGENTLY!
InspectorFrost said:
hi
Im not getting past step2 on this guide
Im getting device not found error....see below (NB. i have htc sync installed and working correctly
(might also be worth noting that i noticed this line come up whist doing step 1 "FAILED (remote: 42 custom id check fail)"
(is this the cause of the problem below?)
Rebooting to bootloader...
rebooting into bootloader... OKAY
Step 1 complete - now use the bootloader menu to enter recovery mode.
To do this, press the power button, wait a few seconds, then use the volume keys
and power button to select the RECOVERY option.
C:\Users\Chris\Desktop\HTC STUFF\Unzipped R5\r5-desire-root>step2-windows.bat
Desire Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
error: device not found
C:\Users\Chris\Desktop\HTC STUFF\Unzipped R5\r5-desire-root>
Click to expand...
Click to collapse
I attach the log here of what happen (not a 42 error but a 51 error... during step 1)
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,40
INFO[RUU]UZ,boot,85
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,45
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,8
INFO[RUU]UZ,radio,16
INFO[RUU]UZ,radio,24
INFO[RUU]UZ,radio,33
INFO[RUU]UZ,radio,41
INFO[RUU]UZ,radio,49
INFO[RUU]UZ,radio,57
INFO[RUU]UZ,radio,65
INFO[RUU]UZ,radio,73
INFO[RUU]UZ,radio,78
INFO[RUU]UZ,radio,86
INFO[RUU]UZ,radio,94
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,6
INFO[RUU]WP,radio,14
INFO[RUU]WP,radio,19
INFO[RUU]WP,radio,27
INFO[RUU]WP,radio,36
INFO[RUU]WP,radio,44
INFO[RUU]WP,radio,51
INFO[RUU]WP,radio,59
INFO[RUU]WP,radio,100
INFOstart image[rcdata] unzipping & flushing...
INFO[RUU]UZ,rcdata,0
INFO[RUU]WP,rcdata,0
INFO[RUU]WP,rcdata,100
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,24
INFO[RUU]UZ,recovery,44
INFO[RUU]UZ,recovery,65
INFO[RUU]UZ,recovery,93
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,22
INFO[RUU]WP,recovery,44
INFO[RUU]WP,recovery,67
INFOstart image[sp1] unzipping & flushing...
INFO[RUU]UZ,sp1,0
INFO[RUU]UZ,sp1,100
INFO[RUU]WP,sp1,0
INFO[RUU]WP,sp1,100
INFOstart image[system] unzipping & flushing...
INFO[RUU]UZ,system,0
INFO[RUU]UZ,system,3
INFO[RUU]UZ,system,7
INFO[RUU]UZ,system,12
INFO[RUU]UZ,system,16
INFO[RUU]UZ,system,20
INFO[RUU]UZ,system,25
INFO[RUU]UZ,system,29
INFO[RUU]UZ,system,33
INFO[RUU]UZ,system,37
INFO[RUU]UZ,system,41
INFO[RUU]UZ,system,45
INFO[RUU]UZ,system,50
INFO[RUU]UZ,system,54
INFO[RUU]UZ,system,58
INFO[RUU]UZ,system,62
INFO[RUU]UZ,system,66
INFO[RUU]WP,system,0
INFO[RUU]WP,system,66
INFO[RUU]UZ,system,66
INFO[RUU]UZ,system,68
INFO[RUU]UZ,system,70
INFO[RUU]UZ,system,72
INFO[RUU]UZ,system,74
INFO[RUU]UZ,system,76
INFO[RUU]UZ,system,78
INFO[RUU]UZ,system,80
INFO[RUU]UZ,system,83
INFO[RUU]UZ,system,85
INFO[RUU]UZ,system,87
INFO[RUU]UZ,system,89
INFO[RUU]UZ,system,91
INFO[RUU]UZ,system,93
INFO[RUU]UZ,system,96
INFO[RUU]UZ,system,98
INFO[RUU]UZ,system,100
INFO[RUU]WP,system,66
INFOstart image[userdata] unzipping & flushing...
INFO[RUU]UZ,userdata,0
INFO[RUU]UZ,userdata,100
INFO[RUU]WP,userdata,0
INFO[RUU]WP,userdata,100
FAILED (remote: 51 partition update fail)
sending 'zip' (137446 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,40
INFO[RUU]UZ,boot,85
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,45
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,8
INFO[RUU]UZ,radio,16
INFO[RUU]UZ,radio,24
INFO[RUU]UZ,radio,33
INFO[RUU]UZ,radio,41
INFO[RUU]UZ,radio,49
INFO[RUU]UZ,radio,57
INFO[RUU]UZ,radio,65
INFO[RUU]UZ,radio,73
INFO[RUU]UZ,radio,78
INFO[RUU]UZ,radio,86
INFO[RUU]UZ,radio,94
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,6
INFO[RUU]WP,radio,14
INFO[RUU]WP,radio,19
INFO[RUU]WP,radio,27
INFO[RUU]WP,radio,36
INFO[RUU]WP,radio,44
INFO[RUU]WP,radio,100
INFOstart image[rcdata] unzipping & flushing...
INFO[RUU]UZ,rcdata,0
INFO[RUU]WP,rcdata,0
INFO[RUU]WP,rcdata,100
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,24
INFO[RUU]UZ,recovery,44
INFO[RUU]UZ,recovery,65
INFO[RUU]UZ,recovery,93
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,22
INFO[RUU]WP,recovery,44
INFO[RUU]WP,recovery,67
INFOstart image[sp1] unzipping & flushing...
INFO[RUU]UZ,sp1,0
INFO[RUU]UZ,sp1,100
INFO[RUU]WP,sp1,0
INFO[RUU]WP,sp1,100
INFOstart image[system] unzipping & flushing...
INFO[RUU]UZ,system,0
INFO[RUU]UZ,system,3
INFO[RUU]UZ,system,7
INFO[RUU]UZ,system,12
INFO[RUU]UZ,system,16
INFO[RUU]UZ,system,20
INFO[RUU]UZ,system,25
INFO[RUU]UZ,system,29
INFO[RUU]UZ,system,33
INFO[RUU]UZ,system,37
INFO[RUU]UZ,system,41
INFO[RUU]UZ,system,45
INFO[RUU]UZ,system,50
INFO[RUU]UZ,system,54
INFO[RUU]UZ,system,58
INFO[RUU]UZ,system,62
INFO[RUU]UZ,system,66
INFO[RUU]WP,system,0
INFO[RUU]WP,system,66
INFO[RUU]UZ,system,66
INFO[RUU]UZ,system,68
INFO[RUU]UZ,system,70
INFO[RUU]UZ,system,72
INFO[RUU]UZ,system,74
INFO[RUU]UZ,system,76
INFO[RUU]UZ,system,78
INFO[RUU]UZ,system,80
INFO[RUU]UZ,system,83
INFO[RUU]UZ,system,85
INFO[RUU]UZ,system,87
INFO[RUU]UZ,system,89
INFO[RUU]UZ,system,91
INFO[RUU]UZ,system,93
INFO[RUU]UZ,system,96
INFO[RUU]UZ,system,98
INFO[RUU]UZ,system,100
INFO[RUU]WP,system,66
INFOstart image[userdata] unzipping & flushing...
INFO[RUU]UZ,userdata,0
INFO[RUU]UZ,userdata,100
INFO[RUU]WP,userdata,0
INFO[RUU]WP,userdata,100
FAILED (remote: 51 partition update fail)
Rebooting to bootloader...
rebooting into bootloader... OKAY
Step 1 complete - now use the bootloader menu to enter recovery mode.
To do this, press the power button, wait a few seconds, then use the volume keys
and power button to select the RECOVERY option.
C:\Users\admin\Desktop\HTC Root\r5-desire-root>step2-windows.bat
Desire Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
error: device not found
C:\Users\admin\Desktop\HTC Root\r5-desire-root>step2-windows.bat
Desire Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
error: device not found
C:\Users\admin\Desktop\HTC Root\r5-desire-root>step2-windows.bat
Desire Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
error: device not found
I should note it is an unbranded HTC Desire. After Step 1, phone went off with 2 vibrations. Never went back into bootloader mode (as described in the step 1 bat file). Also the USB connection to the computer (win 7) died. Should note I have already installed HTC Sync v.33. Can not get the phone to enter boot loader mode. Only activity is when battery & usb cable is reinserted, I can see the charging led/green led go on. Pressing the on/off, makes charging/green led go off.
Hope you can help....
FAILED (remote: 51 partition update fail)
Click to expand...
Click to collapse
There's your error..
Thanks for all the responses .
I started over using a slightly different guide ( the one on the Nimbu site....still one of Pauls i think)
anyway, still had trouble getting the step2 going....
All fixed now, it seems my command prompt went a little weird on my laptop.
everytime i clicked the .bat file (when phone was in recovery, red triangle) the command prompt window would open for about half a second then dissappear and nothing would happen on the Phone.
Fix was just to reboot the laptop, worked like a charm afterward
then flashed Pays Bravesoul 2......now thats a speedy little rom !!!
using Launcher pro too
I love being able to mix things up
thanks again
I've been trying to install CyanogenMod for my endeavoru by the instructions in their wiki. These are the steps I took in the very beginning:
Unlock via HTC Dev
Flashed CWM
Entered CWM
Ran the CWM backup function
Wipe data/factory reset
Transferred over the .zip file
Attempted to flash from sdcard
The installation aborted because I apparently have an insufficient version of HBOOT (1.12.0000). The page on endeavoru itself had a note on this, but the install page doesn't, so like a fool I thought there would be instructions relating to that when it became relevant. Thinking what to do, I figured maybe upgrading HBOOT is the same as flashing boot.img (which IS mentioned in the install guide), so I did that as well, but the HBOOT version stayed the same.
I was uncomfortable with not feeling in control of events, so I thought I'd get back to the stock OS as a way to reassure myself and make an external (nandroid?) backup. I thought using CWM's backup/restore function would make that possible, but when I did a restore and rebooted it just went into a bootloop. (There was a FAQ item on this, but it assumed I had a zip file to get the boot.img out of, which I don't -- this was a recovery).
Easier than finding a stock rom would seem to be just to upgrade HBOOT. I found this guide on the topic, but the link to firmware doesn't work. I've found others using Search, but they don't work either. (I have HTC__Y13.) One site that has files is here, but I'm being cautious because the phone isn't cheap and I'm trying hard not to brick it. First, the site is in German (I speak a little, but I can't bee 100% sure what these things are saying); second, the link didn't come from xda-developers, so I'm wary of trusting it out of hand.
Would you suggest going on a search for another ROM (2.17.401.2), or flashing HBOOT (with a file from the German site or from somewhere else), or some other thing? The main thing I'm concerned about for the moment is having a functional phone in the next few days.
Also, can I generally expect the battery to not run out while plugged in by USB?
Thanks in advance.
Grab the firmware.zip from the german site, it seems good.
You can get the boot.img for your nandroid backup by selecting mounts and storage > mount usb storage > /sdcard/clockworkmod/backup/
Your device will charge, provided that you are booted in recovery and the version is 5.8.4.0.
Sent from my One X using xda premium
Also, you shouldn't be concerned when flashing a HBOOT, because the package will have to be signed by HTC.
And before flashing anything you will have to flash original recovery, and relock bootloader. This basically means you will be unbrickable!
Unless something goes wrong in the process ofcourse (unlikely)
hallydamaster said:
Also, you shouldn't be concerned when flashing a HBOOT, because the package will have to be signed by HTC.
And before flashing anything you will have to flash original recovery, and relock bootloader. This basically means you will be unbrickable!
Unless something goes wrong in the process ofcourse (unlikely)
Click to expand...
Click to collapse
To flash the hboot you don't need to flash back the stock recovery first ...... Just relock, flash the firmware, unlock, flash a custom recovery again and install a new rom
Thanks. It looks like I got the lock and flash done fine, but it hangs on unlock:
Code:
[~/endeavory] fastboot oem lock
...
OKAY [ 0.000s]
finished. total time: 0.001s
[~/endeavory] fastboot oem rebootRUU [13:14]
...
(bootloader) Save data from original MSC...
(bootloader) Save data from SIF...
(bootloader) Update partition data to SIF partition
(bootloader) Update partition data from original MSC...
(bootloader) [MSG] OKAY
OKAY [ 0.190s]finished. total time: 0.190s
[~/endeavory] fastboot flash zip firmware.zip [13:15]
sending 'zip' (12876 KB)...
OKAY [ 1.757s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 5.116s
[~/endeavory] fastboot flash zip firmware.zip [13:15]
< waiting for device >
sending 'zip' (12876 KB)...
OKAY [ 1.661s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[boot] unzipping & flushing...
(bootloader) Format partition LNX done
(bootloader) [RUU]WP,boot,100
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) Format partition SOS done
(bootloader) [RUU]WP,recovery,100
(bootloader) ERASE backup cid
OKAY [ 3.176s]
finished. total time: 4.837s
[~/endeavory] fastboot flash unlocktoken
Unlock_code.bin [13:16]
sending 'unlocktoken' (0 KB)...
OKAY [ 0.021s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
What I'm seeing right now is a black screen with a htc logo and a full green status bar. It's been this way for a while.
What should I do? Is it safe to terminate the unlock command?
Yeah press ctrl+c and reboot phone.
Sent from my One X using xda premium
All right, I'm happily using HBOOT 1.39 now with a CyanogenMod nightly running, and ready to explore this supermarket of excitement and possibility.
I terminated the process and rebooted, which worked fine, and flashed boot.img and CWM and then CM from recovery.
Thanks again to all of you.
Hello i hope someone can help me out i am trying to reflash the stock ICS rom for my htc one v but i keep getting an error halfway through the flashing saying an unknown error has occured and something about flashing the correct rom. To my knowledge i am flashing the correct stock rom which i have downloaded from http://www.androidfiles.org/ruu/?developer=Primo. Their are 2 roms for H3g ics and i have tried both with the same error. Iff someone could point me in the right direction i would much appeciate it thankyou in advance. Atm i am stuck in fastboot everytime i reboot the phone as i have relocked the bootloader also as suggested in the instructions on how to reflash.
I don't know if its why or not. But you also have to flash the stock kernel and recovery before re locking. You can get these files by first running the RUU. Without doing anything go into your temp folder and you'll see a folder with all the flash images.
The RUU also has to be for your HBOOT/RADIO as far as I know.
sam0056 said:
Hello i hope someone can help me out i am trying to reflash the stock ICS rom for my htc one v but i keep getting an error halfway through the flashing saying an unknown error has occured and something about flashing the correct rom. To my knowledge i am flashing the correct stock rom which i have downloaded from http://www.androidfiles.org/ruu/?developer=Primo. Their are 2 roms for H3g ics and i have tried both with the same error. Iff someone could point me in the right direction i would much appeciate it thankyou in advance. Atm i am stuck in fastboot everytime i reboot the phone as i have relocked the bootloader also as suggested in the instructions on how to reflash.
Click to expand...
Click to collapse
ain't this funny..
i am trying the exact same thing.. and i am getting stuck 2..
Code:
C:\htc\Fastboot>fastboot erase cache
erasing 'cache'... OKAY
C:\htc\Fastboot>fastboot oem lock
... INFODevice was already locked!
OKAY
C:\htc\Fastboot>fastboot oem rebootRUU
... OKAY
C:\htc\Fastboot>fastboot flash zip "rom.zip"
sending 'zip' (321386 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
INFOstart image[radio] unzipping for pre-update...
INFOstart image[radio] flushing...
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,6
INFO[RUU]WP,radio,14
INFO[RUU]WP,radio,22
INFO[RUU]WP,radio,30
INFO[RUU]WP,radio,38
INFO[RUU]WP,radio,48
INFO[RUU]WP,radio,53
INFO[RUU]WP,radio,61
INFO[RUU]WP,radio,69
INFO[RUU]WP,radio,77
INFO[RUU]WP,radio,85
INFO[RUU]WP,radio,91
INFO[RUU]WP,radio,100
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
C:\htc\Fastboot>
:laugh:
---------- Post added at 10:22 AM ---------- Previous post was at 09:52 AM ----------
oNNoZeLe said:
ain't this funny..
i am trying the exact same thing.. and i am getting stuck 2..
Code:
C:\htc\Fastboot>fastboot erase cache
erasing 'cache'... OKAY
C:\htc\Fastboot>fastboot oem lock
... INFODevice was already locked!
OKAY
C:\htc\Fastboot>fastboot oem rebootRUU
... OKAY
C:\htc\Fastboot>fastboot flash zip "rom.zip"
sending 'zip' (321386 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
INFOstart image[radio] unzipping for pre-update...
INFOstart image[radio] flushing...
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,6
INFO[RUU]WP,radio,14
INFO[RUU]WP,radio,22
INFO[RUU]WP,radio,30
INFO[RUU]WP,radio,38
INFO[RUU]WP,radio,48
INFO[RUU]WP,radio,53
INFO[RUU]WP,radio,61
INFO[RUU]WP,radio,69
INFO[RUU]WP,radio,77
INFO[RUU]WP,radio,85
INFO[RUU]WP,radio,91
INFO[RUU]WP,radio,100
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
C:\htc\Fastboot>
:laugh:
Click to expand...
Click to collapse
i locked the device b4 upping the signed boot.img and signed recovery.img..
i am gonna try a stock rooted lite rom
oNNoZeLe said:
ain't this funny..
i locked the device b4 upping the signed boot.img and signed recovery.img..
i am gonna try a stock rooted lite rom
Click to expand...
Click to collapse
If you locked it you cant flash a kernel. It has to be unlocked to do that.
bandit97 said:
If you locked it you cant flash a kernel. It has to be unlocked to do that.
Click to expand...
Click to collapse
true..
i found this thread an after unlocking and a redo i got my V back to stock..
slimbean
oNNoZeLe said:
true..
i found this thread an after unlocking and a redo i got my V back to stock..
Click to expand...
Click to collapse
I gave up in the end and i installed the HOV slimbean rom and have found it to be brilliant i think ill stick with it.
sam0056 said:
I gave up in the end and i installed the HOV slimbean rom and have found it to be brilliant i think ill stick with it.
Click to expand...
Click to collapse
i installed
http://forum.xda-developers.com/showthread.php?t=1647052
this one..
and seems to be working fine so far..
what is the HOV?
H=HTC
O=one
V=v
htc ics lite
mrcorey said:
H=HTC
O=one
V=v
Click to expand...
Click to collapse
their is also a lite verision of ICS around somewhere which i also tried for a few weeks and it was also very good but the only problem was it wasnt a rooted rom so thats why i went to slimbean. That other rom is here http://forum.xda-developers.com/showthread.php?t=2121780
I've spent a couple of hours searching the forum, but haven't found the exact answer I'm after.
I recently purchased a rooted, s-off, unlocked bootloader blue HTC one on Swappa. It's currently got TWRP 2.7.0.1 recovery. I wanted to try the NuSense Six ROM, but in order to do that, I need to update the firmware according to the ROM's post. This phone currently has 1.10.605.8 CL221778 release-keys.
I found a link for the firmware updates here: http://forum.xda-developers.com/showpost.php?p=46506621&postcount=2 Says it won't affect root, s-off, or bootloader unlock... but, being somewhat inexperienced with rooting (I've done my Nexus 7 and a few older HTC phones, but they had nice little programs that I pushed buttons on), if I flash the new firmware according to that post, will it affect my TWRP recovery? Or, can I just flash the firmware, then flash the NuSense 6 ROM?
Thanks.
The firmware won't affect your recovery. The firmware consists of the hboot, baseband, prl and modem data, and a boot img if you're flashing the version with that still apart of the zip.
Sent from my HTC6525LVW using Tapatalk
disconnecktie said:
The firmware won't affect your recovery. The firmware consists of the hboot, baseband, prl and modem data, and a boot img if you're flashing the version with that still apart of the zip.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Thanks. Appreciate it! I'll add that to my notes. :fingers-crossed:
Now I'm stuck in a boot loop...
So, the flash of the Firmware went well. I followed the directions to the letter. But, now I'm stuck in a bootloop. I was able to boot into recovery and use TWRP to do a wipe, thinking that might be the problem, but it's not. Still stuck in a boot loop. I get as far as the HTC logo screen, then it goes blank, and then it'll reboot in 15 - 20 seconds. I may have forgotten to turn off fastboot in the stock Sense menu before I got rebooted into the boot menu... could that be the problem?
Or is this because the updated firmware won't work with stock 4.2.2? If not, how do I get the NuSenseSIX ROM onto the phone so I can install it with TWRP?
You probably flashed the firmware that has the boot.img from kitkat. Flashing a Rom in recovery with a full wipe will fix the problem. Doing this will not wipe the firmware. You only have to do that once unless you're changing firmware. Newer firmware typically works okay with older roms while old firmware often times won't work with newer roms.
Sent from my HTC6525LVW using Tapatalk
disconnecktie said:
You probably flashed the firmware that has the boot.img from kitkat. Flashing a Rom in recovery with a full wipe will fix the problem. Doing this will not wipe the firmware. You only have to do that once unless you're changing firmware. Newer firmware typically works okay with older roms while old firmware often times won't work with newer roms.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Yeah, I did flash the firmware that had the boot.img. I didn't know it'd be a problem.
Can you point me to a link here that can give me the steps of what exactly I need to do? The ROM is on my computer, not on the phone, unfortunately, so I can't just install with TWRP. I don't know how to get it on the phone via Fastboot.
Do I do the full wipe in TWRP before or after I flash? Because I've already done the full wipe once in TWRP trying to get this to work.
Thanks again.
EDIT: Found some instructions for adb push. Going to give it a try and see what happens.
If you have adb setup on your pc then you should be able to use the adb sideload command in twrp to flash the Rom. If not then you shouldn't have any problem using a usb cable to transfer the file from your pc to the sd card in recovery. Once the file is on your sd card, do a full wipe (everything except the internal storage) and then install the Rom.
Sent from my HTC6525LVW using Tapatalk
Well, it rebooted, updated Android, rebooted again, and I got to setup. It's now restoring my settings (from my other One) from my Google account.
THANK YOU for your patience and kind instruction. I learned something today!
PS: The NuSenseSIX updates are coming pretty often. Can I just download them to my phone, reboot into TWRP, flash them, and be done without losing current settings, apps, contacts, etc?
Souldrifter said:
Well, it rebooted, updated Android, rebooted again, and I got to setup. It's now restoring my settings (from my other One) from my Google account.
THANK YOU for your patience and kind instruction. I learned something today!
PS: The NuSenseSIX updates are coming pretty often. Can I just download them to my phone, reboot into TWRP, flash them, and be done without losing current settings, apps, contacts, etc?
Click to expand...
Click to collapse
The Rom is in early development so it would probably be best to wipe completely between flashes. Titanium backup will allow you to backup user app and data. I don't recommend backing up system app data.
Sent from my HTC6525LVW using Tapatalk
disconnecktie said:
The Rom is in early development so it would probably be best to wipe completely between flashes. Titanium backup will allow you to backup user app and data. I don't recommend backing up system app data.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So, I'm troubleshooting the lack of 4G on this phone. Icon lights, but no data. I go to settings and it says connecting, connecting, then disconnected and I cannot get it to connect no matter what I do.
I figured I'd go back to the point I got the phone and try it that way. I made a backup in TWRP, but if I restore that, that will only restore the stock rooted ROM I had on it, right? What if it's the firmware flash? I did update the firmware (successfully, by all looks) before I installed the new ROM.
Can you revert firmware?
Backup your sd card, flash the stock Rom, fastboot flash the stock recovery and do a factory reset. Then flash a new recovery and the Rom that is giving you trouble and see if it works. If it doesn't then maybe try getting a new sim from Verizon.
Sent from my HTC6525LVW using Tapatalk
disconnecktie said:
Backup your sd card, flash the stock Rom, fastboot flash the stock recovery and do a factory reset. Then flash a new recovery and the Rom that is giving you trouble and see if it works. If it doesn't then maybe try getting a new sim from Verizon.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Alright, I'll do that. And, I figure it can't be the SIM because it works in my current One just fine. It's only this other one I bought where it doesn't work.
Souldrifter said:
Alright, I'll do that. And, I figure it can't be the SIM because it works in my current One just fine. It's only this other one I bought where it doesn't work.
Click to expand...
Click to collapse
Ah ok. Yeah sometimes a bad sim will have a similar effect.
Sent from my HTC6525LVW using Tapatalk
disconnecktie said:
Ah ok. Yeah sometimes a bad sim will have a similar effect.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Before I decided to go back fully stock and do as you recommended, I wanted to try something. I already didn't have any 4g data connectivity, so what could possibly go wrong?
I went into recovery, wiped, restored a pre custom rom backup that I took (I received it 4.2.2 rooted stock), then flashed the stock 1.10.605.10 firmware from Santod's post. Rebooted. Took the SIM out of my current One and put it in this Blue One. Turned off wifi. Oh, look, I have Data.
So, any ideas WTF I did wrong with the custom rom install? Was it the fact that I didn't use the no boot image firmware?
I doubt that was the cause. Maybe try flashing the new firmware again and a kitkat Rom to see if it works now.
Sent from my HTC6525LVW using Tapatalk
disconnecktie said:
I doubt that was the cause. Maybe try flashing the new firmware again and a kitkat Rom to see if it works now.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Sounds like a good idea. I think I'll try the NuSense 5.5 one. Thanks!
Check out this log of the firmware flash, please. Is that Bypassed line ok?
C:\adb>fastboot flash zip firmware.zip
sending 'zip' (24034 KB)...
OKAY [ 1.928s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 3.713s
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (24034 KB)...
OKAY [ 1.976s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,12
(bootloader) [RUU]UZ,adsp,23
(bootloader) [RUU]UZ,adsp,34
(bootloader) [RUU]UZ,adsp,45
(bootloader) [RUU]UZ,adsp,56
(bootloader) [RUU]UZ,adsp,67
(bootloader) [RUU]UZ,adsp,79
(bootloader) [RUU]UZ,adsp,90
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl2,0
(bootloader) [RUU]UZ,sbl2,100
(bootloader) [RUU]WP,sbl2,0
(bootloader) [RUU]WP,sbl2,100
(bootloader) ...... Successful
(bootloader) start image[tp] unzipping & flushing...
(bootloader) [RUU]UZ,tp,0
(bootloader) [RUU]UZ,tp,100
(bootloader) ..... Bypassed
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,8
(bootloader) [RUU]UZ,radio,17
(bootloader) [RUU]UZ,radio,25
(bootloader) [RUU]UZ,radio,34
(bootloader) [RUU]UZ,radio,42
(bootloader) [RUU]UZ,radio,47
(bootloader) [RUU]UZ,radio,55
(bootloader) [RUU]UZ,radio,64
(bootloader) [RUU]UZ,radio,72
(bootloader) [RUU]UZ,radio,77
(bootloader) [RUU]UZ,radio,85
(bootloader) [RUU]UZ,radio,90
(bootloader) [RUU]UZ,radio,98
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,34
(bootloader) [RUU]WP,radio,68
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,100
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,100
(bootloader) ...... Successful
OKAY [ 13.256s]
finished. total time: 15.233s
C:\adb>
It probably didn't flash it because you are already using that hboot.
Sent from my HTC6525LVW using Tapatalk
disconnecktie said:
It probably didn't flash it because you are already using that hboot.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
NuSenseONE 1.4 works like a charm. I miss the Sense 6.0 bells and whistles, but I figure we should have a debloated, rooted build of the official M7 release for that this summer.
Maybe now that it works for sense 5.5 it should work fire sense 6.
Sent from my HTC6525LVW using Tapatalk
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I want to get the latest android available for my HTC M8 (AT&T). I'm currently on Android 4.4.2. I have an mdnsd battery drain bug, and the bluetooth has a bug that causes it to break whenever I get around too many bluetooth devices.
I've tried flashing to TWRP, flashing back to the factory recovery, multiple RUU files, and a SkyDragon ROM. All either don't update or cause a boot loop, and I end up doing a nandroid restore to my old ROM.
I get the impression that I need the correct version of the boot loader, which is included in the right firmware.zip file. I've tried to find the right file, but when I go to the mike1986 page to download the firmware, I'm not sure which version to try. What is the latest official firmware that will work for my phone, and what is the latest official version of Android I can update to?
Any help is greatly appreciated!
Read this - https://forum.xda-developers.com/showthread.php?t=2751432
and this - https://forum.xda-developers.com/att-htc-one-m8/general/marshmellow-update-t3379303
everything that you need is there.
The latest version is Marshmallow 6.20.502.5
ckpv5 said:
Read this - https://forum.xda-developers.com/showthread.php?t=2751432
and this - https://forum.xda-developers.com/att-htc-one-m8/general/marshmellow-update-t3379303
everything that you need is there.
The latest version is Marshmallow 6.20.502.5
Click to expand...
Click to collapse
Thanks! I notice that the firmware isn't flashing, either hanging indefinitely or giving an error message:
C:\adb>fastboot flash zip fw_6.20.502.5.zip
target reported max download size of 1772113920 bytes
sending 'zip' (57092 KB)...
OKAY [ 2.585s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.924s
Do I have to have S-off? I was trying to get around paying $25 for the software.
kentuckythrash said:
Thanks! I notice that the firmware isn't flashing, either hanging indefinitely or giving an error message:
C:\adb>fastboot flash zip fw_6.20.502.5.zip
target reported max download size of 1772113920 bytes
sending 'zip' (57092 KB)...
OKAY [ 2.585s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.924s
Do I have to have S-off? I was trying to get around paying $25 for the software.
Click to expand...
Click to collapse
repeat the flashing command immediately after you see this error
no need for s-off to flash signed firmware only relocked/locked bootloader
ahmed.ismael said:
repeat the flashing command immediately after you see this error
no need for s-off to flash signed firmware only relocked/locked bootloader
Click to expand...
Click to collapse
Thanks! I ended up getting the " FAILED (remote: 90 hboot pre-update! please flush image again immediately)" multiple times, apparently going 7/8s of the way through. I ended up trying the RUU, and it got much further and right now has been on "Updating...(1/1) Sending...." for about 20 minutes. The same window has "Remember, the operation will take about 10 minutes." Should I keep waiting or try the RUU again? I don't know if it's hung or not, and there's no real progress meter.
kentuckythrash said:
Thanks! I ended up getting the " FAILED (remote: 90 hboot pre-update! please flush image again immediately)" multiple times, apparently going 7/8s of the way through. I ended up trying the RUU, and it got much further and right now has been on "Updating...(1/1) Sending...." for about 20 minutes. The same window has "Remember, the operation will take about 10 minutes." Should I keep waiting or try the RUU again? I don't know if it's hung or not, and there's no real progress meter.
Click to expand...
Click to collapse
actually in my first respond i was mistaken about the error 99
i was talking about error 90 sorry about that
now wait for the RUU to complete the process or return with an error
if something changed please post it here
ahmed.ismael said:
actually in my first respond i was mistaken about the error 99
i was talking about error 90 sorry about that
now wait for the RUU to complete the process or return with an error
if something changed please post it here
Click to expand...
Click to collapse
It's been an hour and no change... should I let it continue? Seems like it should have finished by now.
kentuckythrash said:
It's been an hour and no change... should I let it continue? Seems like it should have finished by now.
Click to expand...
Click to collapse
what is the current status for the phone ?
If the flashing didn't start then try to flash the firmware again
Another question : did you relocked the bootloader ?
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
what is the current status for the phone ?
If the flashing didn't start then try to flash the firmware again
Another question : did you relocked the bootloader ?
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
The phone screen has the htc gradient logo. The bootloader is relocked.
I've attached an image of the ROM update window.
kentuckythrash said:
The phone screen has the htc gradient logo. The bootloader is relocked.
I've attached an image of the ROM update window.
Click to expand...
Click to collapse
Ok open cmd window and type
fastboot reboot-bootloader
Then flash the firmware
From where you got the firmware ?
and try with another USB 2 port don't use USB 3 type
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
Ok open cmd window and type
fastboot reboot-bootloader
Then flash the firmware
From where you got the firmware ?
and try with another USB 2 port don't use USB 3 type
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
I got the firmware from:
https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU
I tried the 'fastboot reboot-bootloader' command and see:
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
and it won't go past that point.
kentuckythrash said:
I got the firmware from:
https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU
I tried the 'fastboot reboot-bootloader' command and see:
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
and it won't go past that point.
Click to expand...
Click to collapse
Close the RUU setup wizard if it still didn't flash anything or hanging on the same screen
And restart your pc then try to flash the firmware again on the device ( as it's on RUU mode )
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
Close the RUU setup wizard if it still didn't flash anything or hanging on the same screen
And restart your pc then try to flash the firmware again on the device ( as it's on RUU mode )
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
Thanks for your prompt responses! I managed to successfully update the firmware, seeing a completed message in the command prompt, and green bar on the HTC screen. However, now I'm still stuck on "
Updating...(1/1) Sending.......
Updating the ROM image on your Android phone...
"
I've rebooted my workstation and the phone multiple times. Not sure where to go from here.
kentuckythrash said:
Thanks for your prompt responses! I managed to successfully update the firmware, seeing a completed message in the command prompt, and green bar on the HTC screen. However, now I'm still stuck on "
Updating...(1/1) Sending.......
Updating the ROM image on your Android phone...
"
I've rebooted my workstation and the phone multiple times. Not sure where to go from here.
Click to expand...
Click to collapse
another solution you can extract the rom.zip from the RUU.exe
By start it and goto %temp% folder and you will find rom.zip
Here what you need to do
press ctrl+r and type %temp% it will open a folder,delete everything in this folder
start the RUU.exe again,once it starting and hang goto %temp% folder again you will find a folder and the rom.zip inside it copy it and flash using fastboot or
rename it to 0P6BIMG.zip and put it in your sd card ( formatted as fat32 ) then reboot into bootloader the update process should start automatically
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
another solution you can extract the rom.zip from the RUU.exe
By start it and goto %temp% folder and you will find rom.zip
Here what you need to do
press ctrl+r and type %temp% it will open a folder,delete everything in this folder
start the RUU.exe again,once it starting and hang goto %temp% folder again you will find a folder and the rom.zip inside it copy it and flash using fastboot or
rename it to 0P6BIMG.zip and put it in your sd card ( formatted as fat32 ) then reboot into bootloader the update process should start automatically
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
OK. There were 2 .zip files, rom_01.zip and rom_02.zip. Here's what happened when I tried to flash each:
--------------------------------------------------------------------------------
C:\adb>fastboot flash zip rom_01.zip
target reported max download size of 1826418688 bytes
sending 'zip' (493 KB)...
OKAY [ 0.218s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) total_image_number=1
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,50
(bootloader) [RUU]UZ,hboot,100
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
OKAY [ 2.260s]
finished. total time: 2.480s
C:\adb>fastboot flash zip rom_02.zip
target reported max download size of 1825775616 bytes
sending 'zip' (1584998 KB)...
OKAY [ 48.647s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 106.973s
C:\adb>
--------------------------------------------------------------------------------
So I guess the problem is the FAILED "remote:12 signature verify fail"
kentuckythrash said:
OK. There were 2 .zip files, rom_01.zip and rom_02.zip. Here's what happened when I tried to flash each:
--------------------------------------------------------------------------------
C:\adb>fastboot flash zip rom_01.zip
target reported max download size of 1826418688 bytes
sending 'zip' (493 KB)...
OKAY [ 0.218s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) total_image_number=1
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,50
(bootloader) [RUU]UZ,hboot,100
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
OKAY [ 2.260s]
finished. total time: 2.480s
C:\adb>fastboot flash zip rom_02.zip
target reported max download size of 1825775616 bytes
sending 'zip' (1584998 KB)...
OKAY [ 48.647s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 106.973s
C:\adb>
--------------------------------------------------------------------------------
So I guess the problem is the FAILED "remote:12 signature verify fail"
Click to expand...
Click to collapse
rom_02 rename it to 0P6BIMG.zip and put it in your sd card and reboot to bootloader,have you tried to do that ?
rom_01 is hboot as shown in the output
rom_02 supposed to be the RUU
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
rom_02 rename it to 0P6BIMG.zip and put it in your sd card and reboot to bootloader,have you tried to do that ?
rom_01 is hboot as shown in the output
rom_02 supposed to be the RUU
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
That worked! Thank you very much for your help. These M8s are really hard to update!
kentuckythrash said:
That worked! Thank you very much for your help. These M8s are really hard to update!
Click to expand...
Click to collapse
Not hard but tricky
Glad i helped
Sent from my HTC M8 using XDA Labs