Related
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.
Disclaimer: You are performing this modification at your own risk. I take absolutely no responsibility for any damages that may occur to your phone as a result of this modification. You are solely responsible for any changes you make to your phone.
Please read this post before flashing your new splash screen! Also, if you plan to revert to a locked bootloader, or revert to S-On, please flash a stock bootloader for your variant. If you neglect to do this, you could end up with a brick during the revert process! This also means that you should revert to a stock splash screen!
Please remember that by changing your splash screen you will no longer have your stock splash screen. I believe one is posted somewhere in the general M8 forums. Please search there for it.
Please choose the splash screen for your variant. I tried to make sure that all the main versions (read as OS version) in the android-info.txt file match the main version for each respective variants. Since, as of August 30, 2014, it seems that Verizon has not yet released their official 4.4.3 update, I have the main version set to the international variant's main version (2.22.401.4). As stated above, remember to flash back to your official bootloader before reverting to a locked state, or to S-On!
Below is important information about what the main version is and why it is important to revert. I was very worried that this would effect flashing splash screens to all the variants, so I asked @santod040 for clarification on the subject. @santod040 is the person that has given S-Off users the awesome ability to remove the red text on the splash screens by changing the HBOOT (link provided in Thanks section).
Below is the portion of the pm that pertains to the android-info.txt file.
santod040 said:
Essentially, that usually reads the devices current OS version.
When taking an OTA or a signed RUU, it will check many things before it will proceed.
One of those things, is the main version info.
If what you have is newer then what you try to flash while s-on, it will fail, as you cannot downgrade while s-on.
Essentially, if it does not match the expected version when flashing anything signed while s-on, it will fail.
It will essentially have zero effect for anyone who is s-off, so long as they remain s-off.
The main thing is making sure that folks know not to turn s back to ON while they have any modified hboots or even firmware info, such as the main version.
As they will then be stuck not being able to flash just about anything after that unless they can re-unlock/s-off.
So, you can do it with a one size fits all zip and force everyone's to read the same version info in hboot, but it would be better if you could avoid it.
I realize that would mean more work in packing it up for different variants and software revisions, so probably not the way you wanna do it either.
What it comes down to really, is you can do it the easier way, and make sure to let the users know that they should revert to stock firmware before ever trying to relock or go back to s-on.
Click to expand...
Click to collapse
TLDR: You absolutely need to revert to official bootloader before reverting to a locked bootloader state, or reverting to S-On. This is now the third time this has been mentioned. If you forget to do this, any fault absolutely lies with you. The main versions included in the zips will change the OS version listed in the bootloader. A different OS version there from your installed OS version will not effect the functionality of your phone in any way. It only effects locking bootloaders, or reverting to S-On.
If you use TWRP you may not see the OS version listed. This is due to an error in TWRP that does not display the OS version, not from a failed splash screen flash. There is a version of TWRP that does not have this limitation (at least for GSM variants). Can't remember where this is posted, but it does exist.
All this being said, I have included versions of the splash screens with main versions matching the variants. Please flash the splash screen for your variant.
This mod is persistent through ROM flashes and nandroid restore. Flashing an RUU may change the splash screen.
These have been updated to Android version 4.4.3. I have zipped all the 4.4.2 splash screens and uploaded them and the previews here if anyone is still on 4.4.2. Anyone that posted new Model IDs and Custom IDs, the info.txt file has been updated with them for 4.4.3.
Remember to check below to see your if your MID and CID are included in the zips. If not, you can just open the zip and open the android-info.txt file and add your MID and CID by following the syntax of the others. Notepad++ or similar is best suited for editing the txt file.
Requirements:
S-Off
Android SDK (adb and fastboot)
USB Debugging turned on
HTC M8 Drivers
Useful Commands:
Code:
adb devices
(when your phone is connected to the computer, this will tell you if your phone is detected)
expected output:
C:\sdk\platform-tools>adb devices
List of devices attached
FAXXXXXXXXXX device
Code:
fastboot devices
(when your phone is connected and booted to the bootloader, this will tell you if your phone is detected)
expected output:
C:\sdk\platform-tools>fastboot devices
List of devices attached
FAXXXXXXXXXX fastboot
You must use an adb shell, or a terminal emulator app to use the commands below.
Code:
getprop ro.cid
(displays your phone's Custom ID (cid))
expected output:
[email protected]/# getprop ro.cid
getprop ro.cid
T-MOB010
Code:
getprop ro.mid
(dispays your phone's Model ID)
expected output:
[email protected]/# getprop ro.mid
getprop ro.mid
0P6B13000
Instructions:
1. Place the zip in the same folder as adb and fastboot.
2. Open a command window and navigate to your adb and fastboot folder. Window button + R and type "cmd"
Alternative: Hold Shift and right-click inside the folder or on the folder's icon and select "Open command window here"
3. Use this command:
Code:
adb reboot bootloader
4. After it boots into fastboot use these commands:
Code:
fastboot devices
fastboot oem rebootRUU
expected output:
C:\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.025s]
finished. total time: 0.025s
The first command confirms the connection to the computer, the second command reboots your phone into an RUU flash mode. The screen will be black with a silver and black HTC logo.
5. Next use the command:
Code:
fastboot devices
fastboot flash zip splash.zip
expected output:
C:\sdk\platform-tools>fastboot flash zip splash-t-mo.zip
sending 'zip' (156 KB)...
OKAY [ 0.191s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) total_image_number=1
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) [RUU]UZ,sp1,0
(bootloader) [RUU]UZ,sp1,23
(bootloader) [RUU]UZ,sp1,45
(bootloader) [RUU]UZ,sp1,67
(bootloader) [RUU]UZ,sp1,89
(bootloader) [RUU]UZ,sp1,100
(bootloader) [RUU]WP,sp1,0
(bootloader) [RUU]WP,sp1,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
OKAY [ 2.188s]
finished. total time: 2.379s
I always perform the devices check before flashing.
6. Then reboot using:
Code:
fastboot reboot-bootloader
expected output:
C:\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.015s
This allows you to make sure that the flash was successful. If it was not, from here you could start the process over and flash a splash screen you know works.
4.4.3 Downloads
AT&T
mainver: 2.23.502.3
AT&T
Download
MD5: 98e73d321ec32ecb9eaf2675a4a45b80
AT&T-No Carrier
Download
MD5: c8ba2aa9e07412e90db1669c690c973b
AT&T-Unlocked
Download
MD5: 7909b5739356dd2875a60bca961f860e
Developer
mainver: 2.22.1540.4
Dev-No Carrier
Download
MD5: 19f0c68a61b0149234981a234f32ddbc
Dev-Unlocked
Download
MD5: a7112e62b9da72f8d3979945d513b76b
International
mainver: 2.22.401.4
International-No Carrier
Download
MD5: 4fde99126b8ec8e988602bd3413f5484
International-Unlocked
Download
MD5: a71cf6bde5cab9978a558605f7c7d442
Sprint
mainver: 2.16.654.4
Sprint
Download
MD5: c93b4fc4ccc4bbe5a2406ca16192c57a
Sprint-No Carrier
Download
MD5: 40f258362582c8a60c8502779aa8f5b4
Sprint-Unlocked
Download
MD5: 1b118dbf8c358fe3bff998dae206f3e7
T-Mobile
mainver: 2.22.531.5
T-Mobile
Download
MD5: 2cdec4a58a9f6f31d76ef4b5ed4e2d4a
T-Mo-No Carrier
Download
MD5: aa7a9cbddb66c5f175d7eb1a770e0519
T-Mo-Unlocked
Download
MD5: 255b62e6e18a9b9ddb0524423c4dd2bb
Verizon
mainver: 2.22.401.4
Verizon
Download
MD5:49d40286e79a6bc8ff2dba2bcc189288
Verizon-No Carrier
Download
MD5: 4fde99126b8ec8e988602bd3413f5484
Verizon-Unlocked
Download
MD5: a71cf6bde5cab9978a558605f7c7d442
Check your Custom ID and Model ID here:
Contents of the android-info.txt file in each 4.4.3 zip:
Code:
modelid: 0P6B13000
modelid: 0P6B12000
modelid: 0P6B20000
modelid: 0P6B10000
modelid: 0P6B70000
modelid: 0P6B11000
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: GOOGL001
cidnum: VZW__001
cidnum: SPCS_001
cidnum: HTC__621
mainver: ***Varies - Listed with the variants***
btype:1
aareport:1
hbootpreupdate:12
MD5 Sums:
4.4.3 MD5 sums are listed with the variants
4.4.2
AT&T
EC9694FB1E0E1045018D47F014C3880A
No-Carrier
1E4466590F99EF431E752D35C1662514
Sprint
312AB76943BA54B9406EB21A627C3C58
T-Mobile
508F020E3A30552A1B4C79A80209DCB4
Unlocked
EF40CCF59D9D64B3BC628F18937A206C
Verizon
926DC41ACB0AF03C8F99F6CAB0EB2F42
Thanks:
@santod040 - For taking all the time to write up a detailed explanation of what the main version is and its function. Also, for modifying the HBoots of our devices to not show that hideous red text! Modified HBoot thread found here: http://forum.xda-developers.com/showthread.php?t=2710503
@starbase64 - For the splash screen creator for the M8 found here: http://forum.xda-developers.com/showthread.php?t=2713947
@dgtiii - For the fastboot flash instructions.
@ordg7341 - For android-info.txt base.
@JaY iZz BaKk - For testing the splash screen on the T-Mobile variant.
VolcanicSkunk said:
Disclaimer: You are performing this modification at your own risk. I take absolutely no responsibility for any damages that may occur to your phone as a result of this modification.
This mod should work on all versions of the M8. I included all the Model IDs and Custom IDs I could find, so hopefully it should be compatible with all variants of this device. The android-info.txt file that is used is shown later in this post so you can check your IDs before you flash.
If you find that your Model ID or Custom ID is not included in the file, you can check the Useful Commands section for how to find your IDs, then just add them to your zip before flashing. Also, please post your IDs here so I can update the android-info.txt to include your variant.
Please remember that by changing your splash screen you will no longer have your stock splash screen. I believe one is posted somewhere in the general M8 forums. Please search there for it.
This mod is persistent through ROM flashes and nandroid restore. Flashing an RUU may change the splash screen.
Requirements:
S-Off
Android SDK (adb and fastboot)
USB Debugging turned on
HTC M8 Drivers
Useful Commands:
Code:
adb devices
(when your phone is connected to the computer, this will tell you if your phone is detected)
expected output:
C:\sdk\platform-tools>adb devices
List of devices attached
FAXXXXXXXXXX device
Code:
fastboot devices
(when your phone is connected and booted to the bootloader, this will tell you if your phone is detected)
expected output:
C:\sdk\platform-tools>fastboot devices
List of devices attached
FAXXXXXXXXXX fastboot
You must use an adb shell, or a terminal emulator app to use the commands below.
Code:
getprop ro.cid
(displays your phone's Custom ID (cid))
expected output:
[email protected]/# getprop ro.cid
getprop ro.cid
T-MOB010
Code:
getprop ro.mid
(dispays your phone's Model ID)
expected output:
[email protected]/# getprop ro.mid
getprop ro.mid
0P6B13000
Instructions:
1. Place the zip in the same folder as adb and fastboot.
2. Open a command window and navigate to your adb and fastboot folder. Window button + R and type "cmd"
Alternative: Hold Shift and right-click inside the folder or on the folder's icon and select "Open command window here"
3. Use this command:
Code:
adb reboot bootloader
4. After it boots into fastboot use these commands:
Code:
fastboot devices
fastboot oem rebootRUU
expected output:
C:\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.025s]
finished. total time: 0.025s
The first command confirms the connection to the computer, the second command reboots your phone into an RUU flash mode. The screen will be black with a silver and black HTC logo.
5. Next use the command:
Code:
fastboot devices
fastboot flash zip splash.zip
expected output:
C:\sdk\platform-tools>fastboot flash zip splash-t-mo.zip
sending 'zip' (156 KB)...
OKAY [ 0.191s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) total_image_number=1
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) [RUU]UZ,sp1,0
(bootloader) [RUU]UZ,sp1,23
(bootloader) [RUU]UZ,sp1,45
(bootloader) [RUU]UZ,sp1,67
(bootloader) [RUU]UZ,sp1,89
(bootloader) [RUU]UZ,sp1,100
(bootloader) [RUU]WP,sp1,0
(bootloader) [RUU]WP,sp1,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
OKAY [ 2.188s]
finished. total time: 2.379s
I always perform the devices check before flashing.
6. Then reboot using:
Code:
fastboot reboot
expected output:
C:\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.017s
Check your Custom ID and Model ID here:
Contents of the android-info.txt file in each zip:
Code:
modelid: 0P6B13000
modelid: 0P6B12000
modelid: 0P6B20000
modelid: 0P6B10000
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: GOOGL001
cidnum: VZW__001
mainver: 1.54.401.5
btype:1
aareport:1
hbootpreupdate:12
MD5 Sums:
AT&T
EC9694FB1E0E1045018D47F014C3880A
No-Carrier
1E4466590F99EF431E752D35C1662514
Sprint
312AB76943BA54B9406EB21A627C3C58
T-Mobile
508F020E3A30552A1B4C79A80209DCB4
Unlocked
EF40CCF59D9D64B3BC628F18937A206C
Verizon
926DC41ACB0AF03C8F99F6CAB0EB2F42
Thanks:
@starbase64 - for the splash screen creator for the M8 found here: http://forum.xda-developers.com/showthread.php?t=2713947
@dgtiii - fastboot flash instructions
@ordg7341 - for android-info.txt base
@JaY iZz BaKk - for testing the splash screen on the T-Mobile variant
Click to expand...
Click to collapse
love this! I would suggest posting it in the international htc one m8 section
JaY iZz BaKk said:
love this! I would suggest posting it in the international htc one m8 section
Click to expand...
Click to collapse
I think I'll do that right now actually.
When i try to flash the tmobile variant on my tmobile m8 running viper rom i get a failed error
Gs0230 said:
When i try to flash the tmobile variant on my tmobile m8 running viper rom i get a failed error
Click to expand...
Click to collapse
Can you confirm MD5? If so, please run the following commands in a terminal emulator or adb shell:
Code:
getprop ro.cid
getprop ro.mid
Then post the results from each command. I can then update the android-info.txt to include your cid and mid.
Flashed the no carrier version on my Dev edition phone, looks great! Good job mate, and thanks for the mention in your OP,
dgtiii said:
Flashed the no carrier version on my Dev edition phone, looks great! Good job mate, and thanks for the mention in your OP,
Click to expand...
Click to collapse
Glad you like it! And I have to give credit where due.
Sent from my HTC One M8
Call me a noob but... When does the splash animation happen? Is it the first one you see when you power the device on? Like the white background with green HTC Logo before the actual boot animation?
nicholi2789 said:
Call me a noob but... When does the splash animation happen? Is it the first one you see when you power the device on? Like the white background with green HTC Logo before the actual boot animation?
Click to expand...
Click to collapse
Yep. The splash is the image that appears before the boot animation begins.
Sent from my HTC One M8
It doesn't display any real info though, am I right?
Shebee said:
It doesn't display any real info though, am I right?
Click to expand...
Click to collapse
No, it doesn't detect anything on your device. The information should correspond with your variant though.
Splash screens are just a converted png image.
Sent from my HTC One M8
Please excuse the dumb question, but I am also trying to get rid of the tmo boot animation after the splash screen, I have tried to remove it manually but with no luck. Any direction you can give me?
cdfosburg said:
Please excuse the dumb question, but I am also trying to get rid of the tmo boot animation after the splash screen, I have tried to remove it manually but with no luck. Any direction you can give me?
Click to expand...
Click to collapse
You need to have r/w permissions. I think there is a thread in the international M8 development forums. I'm not sure if you need to be S-Off to use it. Or flash a custom kernel. I think ElementalX kernel has it built in. Or most custom roms have it built in.
Sent from my HTC One M8
VolcanicSkunk said:
You need to have r/w permissions. I think there is a thread in the international M8 development forums. I'm not sure if you need to be S-Off to use it. Or flash a custom kernel. I think ElementalX kernel has it built in. Or most custom roms have it built in.
Sent from my HTC One M8
Click to expand...
Click to collapse
I am starting to think that the rom / kernel i have is what the issue is, it isn't the worst thing, just a pain lol.
Ran into this error?
I downloaded the adb sdk, extracted the file to my desktop, moved the splash.zip file to the platform-tools folder, then held shift and rich clicked to open the command prompt and followed directions.. Any idea what I may have done incorrectly..
Thanks for the help guys!
C:\Users\alex.pahler\Desktop\adt-bundle-windows-x86-20140321\sdk\platform-tools>
fastboot flash zip splash.zip
target reported max download size of 1829171200 bytes
sending 'zip' (1375 KB)...
OKAY [ 0.291s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.884s
pahlerc1 said:
I downloaded the adb sdk, extracted the file to my desktop, moved the splash.zip file to the platform-tools folder, then held shift and rich clicked to open the command prompt and followed directions.. Any idea what I may have done incorrectly..
Thanks for the help guys!
C:\Users\alex.pahler\Desktop\adt-bundle-windows-x86-20140321\sdk\platform-tools>
fastboot flash zip splash.zip
target reported max download size of 1829171200 bytes
sending 'zip' (1375 KB)...
OKAY [ 0.291s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.884s
Click to expand...
Click to collapse
Run the command to check your model id and post the result. Then I can update the zip with your model id.
Sent from my HTC One M8
VolcanicSkunk said:
Run the command to check your model id and post the result. Then I can update the zip with your model id.
Sent from my HTC One M8
Click to expand...
Click to collapse
I fixed it.. For your thread the information was MID: 0P6B20000
I edited the android text file to that and everything works fine now.. Also have removed the red text which is amazing! It awesome having a custom splash screen, boot animation, and down animation!!
cdfosburg said:
Please excuse the dumb question, but I am also trying to get rid of the tmo boot animation after the splash screen, I have tried to remove it manually but with no luck. Any direction you can give me?
Click to expand...
Click to collapse
This is what I did....Disclaimer: it's a pretty ghetto way of doing it, but it worked for me. Use at your own risk though. And always back up your original files first.
The files you're looking for are located in /system/customize/resource
The annoying sound is: T-Jingle.wav and T-Jingle.ogg
I replaced those with blank ones and changed permissions to rw-r-r
No more annoying sound
The startup Bootanim is TMOUS_bootanimation.zip
Near as I can tell your new one needs to have the same format as this to replace it with a new animation.
When I replaced it with a custom that had a unique desc.txt, the classic part0/part1 folders, etc. it did not work.
What it did do(the part you're interested in)is make the boot anim not play anymore.
So, you could do that to make it not play anymore. Or you could just replace the images in its folders with new ones and have a new boot animation. That's what I ended up settling with.
Once again set permissions on the file to rw-r-r. Also when you make the zip you need to set compression to Store for it to work I think.
Anyways, hope that helps. Thanks again to OP for the info on the splash screen-worked like a charm.
gokun said:
The files you're looking for are located in /system/configuration/resource
Click to expand...
Click to collapse
I found mine in /system/customize/resource.
I was able to rename T-Jingle.wav and T-Jingle.ogg to Z-Jingle.wav and Z-Jingle.ogg using root explorer and the sound is finally gone. Thanks for pointing me in the right direction!
Has anyone gotten this error message?
error: cannot open 'splash.zip'
I can't seem to find anything on how to fix this.
This is an ATT version phone I rooted this phone a couple of days ago with TWRP. However, I had to use adb to enter fastboot as it would not go to fastboot using power/volume keys. Actually, it never shows a fastboot screen, even in adb, so it may have been going into fastboot all along and I just could not see it.
So, instead of leaving well enough alone, I RUU'ed (newest ATT version from HTC site) it to try to get fastboot to work normally (it still works, I just can't see it on screen). Now, I can't get rooted again. FWIW, I did make a backup with TWRP before RUU'ed. Regardless, there is nothing on this phone I need to keep, I just want to root it before I start using it.
Any help is greatly appreciated...
Here is my unlock sequence. Note what happens if I try to flash TWRP immediately after unlock. I have to CTRL C and Reboot phone.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash unlockt
oken unlock_code.bin
target reported max download size of 1826414592 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.110s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.012s]
finished. total time: 0.125s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
twrp30m8.img
^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
Now when I try to flash TWRP, I get :
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
twrp30m8.img
target reported max download size of 1826414592 bytes
sending 'recover' (20022 KB)...
OKAY [ 1.884s]
writing 'recover'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.611s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.28.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(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: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
HT445####### fastboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.013s
Fastboot flash recover is wrong, it should be :
Fastboot flash recovery < see the Y there.
Mr Hofs said:
Fastboot flash recover is wrong, it should be :
Fastboot flash recovery < see the Y there.
Click to expand...
Click to collapse
Same Results:
C:\s>fastboot flash recovery twrpm8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (14818 KB)...
OKAY [ 1.438s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.976s
C:\s>
C:\s>fastboot flash recovery twrp30m8
error: cannot load 'twrp30m8'
C:\s>fastboot flash recovery twrp30m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.889s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.616s
C:\s>
Bad download then, see how the sizes of the file are different when you flash it again. At least the command is correct now. Re-download the recovery file and try again.
Mr Hofs said:
Bad download then, see how the sizes of the file are different when you flash it again. At least the command is correct now. Re-download the recovery file and try again.
Click to expand...
Click to collapse
Already tried that, but tried again. First below is my result before I downloaded new twrp and the second one is my result after I re-downloaded image
C:\s>fastboot flash recovery twrp.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.896s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.625s
C:\s>fastboot flash recovery twrp.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.899s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.625s
C:\s>
Try the HTC_fastboot adb package. It's posted several times here on xda.
Mr Hofs said:
Try the HTC_fastboot adb package. It's posted several times here on xda.
Click to expand...
Click to collapse
Still no luck, same error (see below). This worked flawless before I flashed the latest ATT RUU.
Is it possible phone is still not unlocked or would I be getting that far if it was still locked?
Question. This phone is AT&T (more details in getvar above) but at the end of the contract, AT&T sent me code to unlock the SIM. Now, the SIM I am using is on a T-Mobile MVNO (TING). Since they SIM unlocked the phone, would I be able to and would there be any advantage/risk to trying to flash the Stock RUU for HTC unlocked/developer. It is a higher software version than the ATT version I flashed (twice).
C:\FB>htc_fastboot flash recovery twrp.img
sending 'recovery' (20022 KB)... OKAY
writing 'recovery'... (bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Execution time is 3(s)
Any other ideas? I can't see bootloader screen, but it appears I can access and do all bootloader functions in adb.
I would really like to be able to eliminate locked bootloader as the issue, is there anything else I can flash or try that might let me know if bootloader is still locked. I can get results from getvar and fastboot devices.
I also have an image of the phone saved from TWRP before I flashed the RUU, but seems no way to get that image back. I am not opposed to purchasing S-off if that will for sure help me.
Try to flash a lower version of TWRP and see if that helps: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img.html
joikep said:
Try to flash a lower version of TWRP and see if that helps: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img.html
Click to expand...
Click to collapse
Already tried two previous versions
rockfordpi said:
Already tried two previous versions
Click to expand...
Click to collapse
OK, lets try this a different way. IF one were to try to flash TWRP to M8 AND the bootloader was NOT UNLOCKED, what error message would one get?
Would there still be a response from adb getvar and fastboot devices IF the bootloader were locked?
Trying to eliminate potential issues one at a time
Is there a more appropriate forum for me to post the question?
rockfordpi said:
OK, lets try this a different way. IF one were to try to flash TWRP to M8 AND the bootloader was NOT UNLOCKED, what error message would one get?
Would there still be a response from adb getvar and fastboot devices IF the bootloader were locked?
Trying to eliminate potential issues one at a time
Is there a more appropriate forum for me to post the question?
Click to expand...
Click to collapse
OK, we can close this one out. I did want to post my solution, just in case anyone else had a similar error.
Long Story a little bit shorter, on my HTC one M8, the error:
sending 'recovery' (11976 KB)... OKAY
writing 'recovery'... (bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Was due to a locked bootloader. Because, for some reason I can't see the bootloader on my phone, I could not see the lock status, so I was having to do EVERYTHING via ADB. The problem was, when unlocking the bootloader there is screen on the phone that asks you to confirm yes or no if you want to unlock it. I could not see that screen and the instructions I was reading left that out (It was a good assumption that if one was trying to unlock one would know to say YES. LOL). So, I was missing that step. When I found that step, even though I could not see it on screen, I just blindly pushed volume down and then power to select. At that point it unlocked and allowed me to flash twrp 3.0.
Still do not know WHY I can't see the bootloader screen. I wonder if for some reason the colors are off in my bootloader screen and all the words are the same color as the background or it is trying to redirect that output somewhere else.
but at this point I am going to live with it as trying to fix it is what got me in here in the first place.
Hi,
I have the same problem phne always reboot in fastboot menu.
The status is also RELOCKED after fashing stock ROM RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
But I'm not able to user adb : device not found.
Fastboot seems working but not adb
Someone have an idea to help me ?
Many thanks
foosee said:
Hi,
I have the same problem phne always reboot in fastboot menu.
Click to expand...
Click to collapse
The top post is in regards to getting signature verify fail message when flashing custom recovery. So I don't see how it's the "same problem".
Be careful about saying "same problem" without giving any specific information about your actual problem, or device details. From my experience, I've seen many dozens of times where folks say they have the "same problem" and when prompted for more info, we find there are many many differences.
foosee said:
Hi,
I have the same problem phne always reboot in fastboot menu.
The status is also RELOCKED after fashing stock ROM
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
Click to expand...
Click to collapse
Did the RUU flash successfully, or were there any error messages?
Also, please do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the phone.
foosee said:
But I'm not able to user adb : device not found.
Fastboot seems working but not adb
Click to expand...
Click to collapse
This is normal and expected. You can't use adb when in bootloader. And you can't use fastboot and adb simultaneously. Meaning, when one works, the other will not work, by definition.
Fastboot = only works in bootloader fastboot mode
adb = only works within OS, or alternately will work in custom recovery TWRP
If you issue the command fastboot devices, you should find that it works.
It is also not clear what you are trying to use adb to do (what commands?).
(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
I am suffering from a bootloop in my phone, lineage suddenly decided to crash trebuchet, and phone turned off. Bootloader works, download mode works, recovery absolutely DOES NOT, It gives me the black HTC logo and turns off and on when I put the "fastboot oem lock" option, and just redirects back to the bootloop when I don't. I can use fastboot to flash files to it, I flashed TWRP old and new, but nonetheless, it bootloops when picking recovery once more. I have S-ON, with the bootloader unlocked. I'd love to buy the sunny license and turn S-OFF, but have no way of accessing my OS anymore.
Here are my details.
(bootloader) kernel: lk
(bootloader) product: htc_himawhl
(bootloader) version: 1.0
(bootloader) version-main: 3.41.651.4
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA20000
(bootloader) cid: SPCS_001
Here is my recovery flashing log
target reported max download size of 800000000 bytes
sending 'recovery' (20084 KB)...
OKAY [ 2.097s]
writing 'recovery'...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 1.838s]
finished. total time: 3.939s
I've tried flashing a signed stock ROM, but I know I need to re-lock the bootloader, the "fastboot oem lock" option doesn't work too well either, it just resets without actually locking anything. It can't hold a flash it seems.
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp (bootloader) [KillSwitch] Last Byte is 0X01, enable unlock (bootloader) RELOCK device
I've tried the "0PJAIMG.zip" method in download mode, but it just gives me these errors as well.
22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 RU_HEADER_ERROR
If my phone gets a file that matches up, it freezes for a bit, THEN goes back to another bootloop. It's frustrating.
9 RU_SECURITY_FAIL is also another error I get when trying to flash the .zip by fastboot, they're so annoying.
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2136250206 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2136250206 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2136250206 is not a multiple of the block size 4096
OKAY [ 1.028s]
writing 'zip' 1/1...
(bootloader) HOSD CL#695981
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.053s
Then after that, I tried flashing "0PJAIMG_HIMA_WHL_L50_SENSE70_SPCS_Sprint_WWE_1.32.651.17_Radio_1.10.C1144022_50312.5_NV_SPCS_0.23_003_release_425355_signed_RYDAH805.zip" via download mode with the SD card, and it gave me a FAIL19 RU_MAIN_VER_FAIL error that I don't understand that well, but I did find a reddit thread on it. I may have messed up my partitions.
https://www.reddit.com/r/AndroidQuestions/comments/69i53h/help_with_htc_m9_fail19_ru_main_ver_fail/
HOSD is also yet another method that ends up in failure
sending 'hosd' (38148 KB)... OKAY
writing 'hosd'... (bootloader) HOSD CL#695981
FAIL35 RU_PARTITION_NOT_SUPPORT hosd
FAILED (remote: 35 RU_PARTITION_NOT_SUPPORT hosd)
Execution time is 4(s)
Here are a list of things that DIDN'T work
-Firmware Flashing
-Boot/TWRP Flashing
-fastboot oem unlock
-the "Power then Volume up" trick, it just redirects me to a white HTC splash screeen
-Recovery from bootloader option
-signed .img files
https://androidforums.com/threads/htc-one-m8-brick-stuck-on-boot.927336/
After finding the thread above, I'm starting to think it might be a hardware error, it now gives me a "Failed to boot to recovery mode" error,. The eMMc may be messed up, ughhhhhhhh
Any way to recover my files, at least? If anyone here has any clues on getting my phone to working condition, I'd appreciate it a ton, hell, I might even pay you for helping me, better than losing all my data!
Will add as much info as possible and update my current status if asked.
Stop before you break it.
Find the official stock signed firmware ruu in .zip format that matches your current firmware. Ie 3.41.651.x (x can be any number but the other 3 octets MUST MATCH). Rename it to 0PJAIMG.ZIP and copy to the external sdcard.
DO NOT relock/lock the bootloader and DO NOT s-on.
Boot to download mode (Black screen red writing) and at the bottom, in yellow text, you should see "press vol up to flash"..
shivadow said:
Stop before you break it.
DO NOT relock/lock the bootloader and DO NOT s-on.
Boot to download mode (Black screen red writing) and at the bottom, in yellow text, you should see "press vol up to flash"..
Click to expand...
Click to collapse
That's unfortunately the issue, I AM S-On, never turned it off, which has pretty much sealed this poor phones fate I assume. If not, I'm betting I would have already flashed a no wipe .zip successfully. It's a shame, since this could have been prevented if I knew this phone was prevalent to system corruption, now the only thing I can depend on is obtaining a compatible recovery, since mine isn't working, download/fastboot is the only thing I have now.
It also seems I cannot find the "RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.4.zip" over the web, would an .exe work if I rename the extension as .zip?
S-on or s-off doesn't matter. What i meant is if you go s-off there is no need to ever s-on again. Same for bootloader. If it's unlocked then you don't ever need to lock/relock it.
Exe or zip but sometimes exe fails. Exe must be run on a pc and have the phone connected via USB. Zip must be run from external sdcard. It MUST be that version regardless.
Your only way without buggering it further is to flash the stock firmware. It will replace the recovery etc itself and will be safer than messing around with it, if it flashes OK.
shivadow said:
S-on or s-off doesn't matter. What i meant is if you go s-off there is no need to ever s-on again. Same for bootloader. If it's unlocked then you don't ever need to lock/relock it.
.
Click to expand...
Click to collapse
Then I'm assuming the correct fw "0PJAIMG.zip" would flash successfully even with an unlocked bootloader?
RebeccaSugar said:
Then I'm assuming the correct fw "0PJAIMG.zip" would flash successfully even with an unlocked bootloader?
Click to expand...
Click to collapse
Correct.
If you prefer the *.zip over the *.exe then take a look at the "further reading" section of the ReadMe thread. There's a link to a decryption tool. Download the correct version for your computer. If you use windows, you can drag and drop the *.exe onto the decryption tool and it will extract the *.zip for you. On Linux and Mac you'll probably need to use some commands.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Correct.
If you prefer the *.zip over the *.exe then take a look at the "further reading" section of the ReadMe thread. There's a link to a decryption tool. Download the correct version for your computer. If you use windows, you can drag and drop the *.exe onto the decryption tool and it will extract the *.zip for you. On Linux and Mac you'll probably need to use some commands.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Done, though, after doing the "0PJAIMG.zip" method once more, it interrupts the flash with a very fast error(?) message highlighted in white then quickly reverts to bootlooping the recovery splash screen (Black Background with Silver HTC Logo)
I decided to flash the boot.img and system.img
target reported max download size of 800000000 bytes
sending 'recovery' (20084 KB)...
OKAY [ 2.097s]
writing 'recovery'...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 1.838s]
finished. total time: 3.939s
(bootloader) kernel: lk
(bootloader) product: htc_himawhl
(bootloader) version: 1.0
(bootloader) imei: 990005027515833
(bootloader) version-main: 3.41.651.4
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA20000
(bootloader) cid: SPCS_001
C:\Users\Infinity>Documents\Pack\fastboot.exe flash system C:\Users\Infinity\Documents\James\HTC\OUT_0PJA_3.41.651.21\system\system.img
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.232s]
sending sparse 'system' 1/6 (743090 KB)...
OKAY [ 40.331s]
writing 'system' 1/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 28.653s]
sending sparse 'system' 2/6 (725823 KB)...
OKAY [ 39.600s]
writing 'system' 2/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 27.937s]
sending sparse 'system' 3/6 (776453 KB)...
OKAY [ 42.390s]
writing 'system' 3/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 30.090s]
sending sparse 'system' 4/6 (764994 KB)...
OKAY [ 41.446s]
writing 'system' 4/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 30.371s]
sending sparse 'system' 5/6 (775925 KB)...
OKAY [ 42.348s]
writing 'system' 5/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 29.562s]
sending sparse 'system' 6/6 (546809 KB)...
OKAY [ 31.210s]
writing 'system' 6/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 21.738s]
finished. total time: 405.943s
They were successful, apparently, but I've seen no changes. When booting, it just hangs on the white splash screen with the green htc logo and the "This build is for development, etc" warning.
If only I had a way to boot a working recovery, the more I do this, the more it seems like it is without a shadow of a doubt, a hardware problem.
Here are some logs, the fw seems to match up with my phone just fine, nonetheles...
View attachment RUU_Decrypt_LOG-0PJA20000_3.41.651.21_2018-04-01_025319.txt
View attachment android-info.txt
View attachment android-info2.txt
View attachment backup_android-info.txt
I noticed that you used fastboot. Be aware that flashing RUUs isn't possible with the generic fastboot files. You'll need htc_fastboot. A download link can be found in the RUU section of the ReadMe thread.
Are you sure that the SD card isn't broken? (Never use old cards for flashing RUUs. They can corrupt the files.) Did you try another one? Normally the extracted *.zip should flash just fine via an SD card.
I'd try a different SD card and flashing the RUU via htc_fastboot. (Flashing only the system and the boot.img might not be sufficient.) If both methods fail then the phone's hardware is most probably damaged and there's nothing you could do.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
I noticed that you used fastboot. Be aware that flashing RUUs isn't possible with the generic fastboot files. You'll need htc_fastboot. A download link can be found in the RUU section of the ReadMe thread.
Are you sure that the SD card isn't broken? (Never use old cards for flashing RUUs. They can corrupt the files.) Did you try another one? Normally the extracted *.zip should flash just fine via an SD card.
I'd try a different SD card and flashing the RUU via htc_fastboot. (Flashing only the system and the boot.img might not be sufficient.) If both methods fail then the phone's hardware is most probably damaged and there's nothing you could do.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I used a different SD card, formatted it to fat32 then exFAT, and nothing happened, it just gave me another error and rebooted. Though, after the reboot I manually booted the download mode and the same happened. Except this time, it gave me a list of all the .img files at 0% inside the "0PJAIMG.zip" before abruptly shutting off.
I took your advice on using the manual htc_fastboot to flash the "0PJAIMG.zip", even with the powershell, and it still fails.
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 3.41.651.21
found large-zip header, file count: 8
processing file 1/8...
sending 'zip' (88845 KB)...
OKAY [ 5.992s]
writing 'zip'...
(bootloader) HOSD CL#695981
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 7.195s
htc_fastboot finished. total time: 8.782s
I did a bit of spelunking and came across this users post, that had the same issue as I.
repl1ca said:
Ok...so hopefully I didn't foobar something. I went to go back to stock since I'm returning my phone soon (1 year lease), so I relocked my bootloader before trying to flash the RUU (I'm S-ON by the way). Relock went fine, but the phone immediately returned to the bootloader with a "*** Security Warning***" message and now the phone won't boot into the ROM or recovery. I tried booting into download mode and flashing the RUU zip, but I am getting the following message:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip d:\downloads\0PJAIMG.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2330284468 is not a multiple of the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 2330284468 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2330284468 is not a multiple of the block size 4096
OKAY [ 1.015s]
writing 'zip'...
(bootloader) HOSD CL#695981
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.017s
I also tried running the RUU exe in download mode, but that didn't work either.
Hopefully I am doing something wrong and didn't mess the phone up! I will be forever in debt to whoever can help me.
P.S. - I also tried unlocking the bootloader again but that is failing as well!! (Even though it says successful...)
_____________________________________________________________________________
EDIT: Ok, so I gave my Windows account full access to the platform-tools folder (which includes fastboot and the unlock token) and tried unlocking again, and it worked?! ROM is booting now, but how do I avoid having this happen again and return to stock? TIA
Click to expand...
Click to collapse
What did he mean by "Full Access to the platform-tools folder"? That may be my meal ticket to getting my phone working or nothing else.
You have to go into Windows Explorer on your computer and find the platform-tools folder. Once you find it, right click on it and go to Properties, then the Security tab. On that tab, add your Windows username in there and make sure the Full Access box is checked. Hit Apply, then OK.
My post is really old, so I'm having a hard time remembering what the actual issue was [emoji23]
Sent from my SM-G965U using Tapatalk
Security fail means the ruu is corrupt. Remote:9 I think is unsigned ruu. You need to be flashing a signed ruu.zip.
shivadow said:
Security fail means the ruu is corrupt. Remote:9 I think is unsigned ruu. You need to be flashing a signed ruu.zip.
Click to expand...
Click to collapse
That's what bothers me the most, the ruu I have IS signed, you sure I don't need S-OFF, or to lock the bootloader?
Security or bootloader make no odds. If you had s-off life would probably be easier..
Exactly which file are you flashing? Have you checked the md5 hash?
shivadow said:
Security or bootloader make no odds. If you had s-off life would probably be easier..
Exactly which file are you flashing? Have you checked the md5 hash?
Click to expand...
Click to collapse
I'll probably buy the XTC 2 Clip chip thing needed to manually turn S-OFF, I don't care about paying a little extra, as long as I can recover all my files in the phone.
I am flashing a "3.41.651.21" .zip from extracted from "RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.21.exe"
The MD5 hash for it is "f41f1b941eb3f9f9ecaebcbf235e87af"
Which looking up the hash reveals to be the version for my exact same hardware, kernel and software version
https://androidfilehost.com/?fid=312978532265363975
I'm more than confident S-OFF is the only way to fix it. Unless there are cases of android bricking, even with a working fastboot. Something, a type of security, is preventing files from being read/flashed, unless It's an eMMc error. Two verdicts now.
You most probably won't be able to recover any files at this point. Flashing a RUU will delete everything that's stored on your phone. Even S-OFF won't change that. S-OFF will only enable downgrading with older RUUs. Converting the phone isn't recommended unless you're willing to risk getting a paperweight since it's a CDMA device.
I haven't seen error 9 before I read about it in this thread. Since you already tried different methods and the md5 checksum of your manually extracted RUU seems to match the one of the AFH RUU, chances are high that the phone's hardware is broken.
Sorry for the bad news.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
You most probably won't be able to recover any files at this point. Flashing a RUU will delete everything that's stored on your phone. Even S-OFF won't change that. S-OFF will only enable downgrading with older RUUs. Converting the phone isn't recommended unless you're willing to risk getting a paperweight since it's a CDMA device.
Click to expand...
Click to collapse
At this point, it's already a paperweight, what's an extra $100 invested on the XTC 2 Clip going to do? Haha! If I can't recover the files, I'll just make an attempt at salvaging this phone and giving it away to someone else.
Flippy498 said:
I haven't seen error 9 before I read about it in this thread. Since you already tried different methods and the md5 checksum of your manually extracted RUU seems to match the one of the AFH RUU, chances are high that the phone's hardware is broken..
Click to expand...
Click to collapse
That IS a fear, especially about hearing about the "horrors" of the Hynix eMMc from people in the the thread I linked in the OP, and others in gsmhosting, this device might have just been another victim of faulty circuitry, which actually has me steamed.
http://forum.gsmhosting.com/vbb/f961/htc-one-m9-bootloop-2214236/#3
This is going to be my brave (read: foolish) attempt.
The biggest problem of the M9 is the Snapdragon 810 processor. Although later firmware revisions fixed the overheating (more or less) the heat damages that emerged from to the usage of older firmware versions aren't fixable.
Most phones that got sold with this processor suffer from similar issues, sooner or later. If you check the xda forums from other 2015 flagship devices with the SD810 you'll see that they all have some kind of sudden bootloop death problem.
And as said before, getting S-OFF won't change your situation. If you really want to try a method that has a slightly chance of being successful you should search for a jtag device like e.g. a riff-box. The thing is I personally don't have any experiences with jtagging. I only know that it can still help in situations in which there already seems to be no hope, anymore. Check sneakyghost's firmware thread in the development section. If I remember correctly, post #5 contains info or at least a link with further info about the topic. Be aware that these devices can be quite expensive.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
The biggest problem of the M9 is the Snapdragon 810 processor. Although later firmware revisions fixed the overheating (more or less) the heat damages that emerged from to the usage of older firmware versions aren't fixable.
Most phones that got sold with this processor suffer from similar issues, sooner or later. If you check the xda forums from other 2015 flagship devices with the SD810 you'll see that they all have some kind of sudden bootloop death problem.
Click to expand...
Click to collapse
I've heard things like that before! It shorts out the board or something above those lines, if heating is an issue, then it certainly did that to mine, which may be the fault of the missing recovery and bootloop, along with one crash I remember! Yes, I remembered I had one crash, the screen had all sorts of garbled colorful static on it and the phone made a beeping noise, why didn't I remember that!? I'm an idiot. That should have been a clear warning to back up everything, I should have reminded myself of the issues with the 810 Processor. Whether the crash months earlier had anything to do with what might have either been a sign of decay, or just a coincidence is beyond me, but knowing my current position with this phone, I'll go with the former.
Flippy498 said:
And as said before, getting S-OFF won't change your situation. If you really want to try a method that has a slightly chance of being successful you should search for a jtag device like e.g. a riff-box. The thing is I personally don't have any experiences with jtagging. I only know that it can still help in situations in which there already seems to be no hope, anymore. Check sneakyghost's firmware thread in the development section. If I remember correctly, post #5 contains info or at least a link with further info about the topic. Be aware that these devices can be quite expensive.
Click to expand...
Click to collapse
Lucky for you (and me) I do! I've successfully soldered about 5 things in the past, so this phone should be familiar territory! I just cancelled the XTC 2 Clip order, and instead ordered myself a Riff Box, I saw that it supports my HTC 9, and I thank you for telling me this! I work much better under hardware than software (Thanks ADHD), I'll check out. I immensely appreciate your help, and you taking time out of your day to give me sources, it truly, honestly means a lot. The device is around $120, not horribly expensive, my wallet can take it, I'll update you on my progress later in the thread! Thanks again!
Woah, apparently I don't NEED to solder? Well, this just makes it easier I'd say! BUT, I don't trust myself enough to risk destroying the sensitive data inside my device, so I will e-mail Tecardo and offer him a price for helping me instead. Can't trust myself enough not to screw up!
Oh, only 120 bucks? Don't ask me why but I had a higher price in mind. Either my mind betrayed me or the riff box got cheaper...
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Oh, only 120 bucks? Don't ask me why but I had a higher price in mind. Either my mind betrayed me or the riff box got cheaper...
Click to expand...
Click to collapse
Well, in your defense, there ARE bundles that are priced ridiculously high (In the $500's for some damned reason) even though you can get the same bundles separately, for less than half of what they ask.