Database Users

[HOW-TO]Flash a custom splash screen

With the arrival of S-OFF for the HTC One we also got the possibility to flash a custom splash screen. Many of us used this already on their previous devices and now it's possible for the HTC One too.
Preparing image for flashing:
First you need the image of your choice. Make sure you it has the size 1080x1920 !!!. It must have been already the correct size because the converter doesn't re-size it. The image can be in the format BMP, JPG or PNG.
Grab EZ Splash Screen Flasher and Image Converter and convert your image. Instructions how to convert it are in the original thread.
Take the custom.img in the place-image-here folder and rename it to splash1.nb0.
Download the attached splash.zip and replace the splash1.nb0 inside.
Have a look at the android-info.txt file and check if your CID is present inside. IF not than add it. I have already added a lot of CID's but if there are some missing I will update it from time to time.
Requirements for flashing:
S-OFF
Steps for flashing:
Boot your HTC One into bootloader and enter fastboot mode
adb reboot bootloader
Start RUU Flash mode
fastboot oem rebootRUU
Flash the custom splash screen
fastboot flash zip splash.zip
Make sure that there are no error messages when flashing
Reboot your device
fastboot reboot

If someone is interested this is the actual image in the splash.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you want to go back flash the splash_stock.zip
fastboot flash zip splash_stock.zip

THX for Tutorial, here my splashscreens.

Thanks for the tutorial, now i'm S-Off i can see me turning into a splash flashaholic!

thx for sharing..works fine here..cheers~

Hi chrisch1974,
I do not own this device myself, but Sneakyghost and I have been playing around a bit, and he confirms that this works for the One. It seemed appropriate to offer it up here in your thread..
For the One-S Ville, I have an online boot splash zip generator. You can upload a picture and it will generate a recovery flashable .zip file. I have now made a version for the One M7 that's identical, except it uses a different resolution and block device. (1080x1920 into P13 instead of 540x960 into P14) For people who don't have a windows box available, this might be an easier option.
http://jobiwan.net:81/bootsplash-one
I don't know whether S-Off is required or not. On the Ville you have to be either S-Off or on a lower hboot version. Again, the .zip files this generates are recovery flashable, not fastboot-RUU flashable, unlike yours.
Enjoy,
-Jobo
(PS: This is my original thread for the One-S Ville: http://forum.xda-developers.com/showthread.php?t=1777223 The online generator is introduced in post#115.)

chrisch1974 said:
With the arrival of S-OFF for the HTC One we also got the possibility to flash a custom splash screen. Many of us used this already on their previous devices and now it's possible for the HTC One too.
Preparing image for flashing:
First you need the image of your choice. Make sure you it has the size 1080x1920 !!!. It must have been already the correct size because the converter doesn't re-size it. The image can be in the format BMP, JPG or PNG.
Grab EZ Splash Screen Flasher and Image Converter and convert your image. Instructions how to convert it are in the original thread.
Take the custom.img in the place-image-here folder and rename it to splash1.nb0.
Download the attached splash.zip and replace the splash1.nb0 inside.
Have a look at the android-info.txt file and check if your CID is present inside. IF not than add it. I have already added a lot of CID's but if there are some missing I will update it from time to time.
Requirements for flashing:
S-OFF
Steps for flashing:
Boot your HTC One into bootloader and enter fastboot mode
adb reboot bootloader
Start RUU Flash mode
fastboot oem rebootRUU
Flash the custom splash screen
fastboot flash zip splash.zip
Make sure that there are no error messages when flashing
Reboot your device
fastboot reboot
Click to expand...
Click to collapse
I attempted to flash with these instructions and received the following:
C:\Users\brandon\Downloads\One_M7_All-In-One_Kit_v1.3\Data>fastboot flash zip sp
lash_stock.zip
sending 'zip' (20 KB)...
OKAY [ 0.233s]
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.666s
I edited the text file to add my CID (BS_US001) but no luck...
I am S-OFF but did not change the CID.
MG

Hey Chrisch!
Nice thread really! I was a bit frustrated first when i found it because i spent all afternoon working out where splash is, how to convert it etc. Now you have been faster!
Well, at least Touch of Jobo can offer his form for recovery flashable zips as a supplement.
I will link your thread to my hboot modification thread so people who edit out the red warning have easy access to custom splash screens (in my eyes these two always go together somehow )
Well done mate! Thanks a lot!

touch of jobo said:
Hi chrisch1974,
I do not own this device myself, but Sneakyghost and I have been playing around a bit, and he confirms that this works for the One. It seemed appropriate to offer it up here in your thread..
For the One-S Ville, I have an online boot splash zip generator. You can upload a picture and it will generate a recovery flashable .zip file. I have now made a version for the One M7 that's identical, except it uses a different resolution and block device. (1080x1920 into P13 instead of 540x960 into P14) For people who don't have a windows box available, this might be an easier option.
http://tibook.jb.b4m.com:81/bootsplash-one
I don't know whether S-Off is required or not. On the Ville you have to be either S-Off or on a lower hboot version. Again, the .zip files this generates are recovery flashable, not fastboot-RUU flashable, unlike yours.
Enjoy,
-Jobo
(PS: This is my original thread for the One-S Ville: http://forum.xda-developers.com/showthread.php?t=1777223 The online generator is introduces in post#115.)
Click to expand...
Click to collapse
It won't flash I n recovery, I tried to open up the zip and it fails
Sent from my HTC One using Tapatalk 4 Beta

superchilpil said:
It won't flash I n recovery, I tried to open up the zip and it fails
Click to expand...
Click to collapse
I've tested it myself and it creates valid .zip files. I can not flash them because I don't have a One. Is the z.ip file you get zero bytes? Can you (zip up and) post the picture you tried to upload?
Edit to add: can 2 or 3 others please report? So as to see whether this is a special case, or it just doesn't work at all..
Edit2: I used the metallica picture you posted, and it generated a 905K .zip file. (attached)

touch of jobo said:
I've tested it myself and it creates valid .zip files. I can not flash them because I don't have a One. Is the z.ip file you get zero bytes? Can you (zip up and) post the picture you tried to upload?
Click to expand...
Click to collapse
The zip I got is about 1.11 kb
Here's the image http://db.tt/rZlKDiBZ
Sent from my HTC One using Tapatalk 4 Beta
---------- Post added at 12:09 PM ---------- Previous post was at 12:02 PM ----------
I figured out my issue, it was my phone. Tried it on a computer and it works just fine
Sorry for the troubles

superchilpil said:
The zip I got is about 1.11 kb
Here's the image http://db.tt/rZlKDiBZ
Sent from my HTC One using Tapatalk 4 Beta
---------- Post added at 12:09 PM ---------- Previous post was at 12:02 PM ----------
I figured out my issue, it was my phone. Tried it on a computer and it works just fine
Sorry for the troubles
Click to expand...
Click to collapse
Your zip is broken. THats not right. Re-Do the process. It worked for me totally ok.
I just tried it again. My zip is 139KB from an image with only 23KB.
[EDIT] lol i just saw you fixed it already. Totally overseen that haha!
---------- Post added at 07:20 PM ---------- Previous post was at 07:14 PM ----------
moregadget said:
I attempted to flash with these instructions and received the following:
C:\Users\brandon\Downloads\One_M7_All-In-One_Kit_v1.3\Data>fastboot flash zip sp
lash_stock.zip
sending 'zip' (20 KB)...
OKAY [ 0.233s]
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.666s
I edited the text file to add my CID (BS_US001) but no luck...
I am S-OFF but did not change the CID
MG
Click to expand...
Click to collapse
It doesn't say FAILED custom id check (CID) but model id check (MID)
I have that on my thread for the hboots as well. I am still trying to find out if there are ONE devices with a different Model ID.
[EDIT]
OK thanks to Mike1986 Website i found the answer already.
There are three MID's
PN0710000
PN0711000
and a third one Mike didn't specify.
You can try to change the MID in your android-info.txt and see if that helps Maybe it flashes then!

Phone would not get past Rootbox bootanimation after successful flashing (the splash showed up fine). fastboot erase cache seems to have fixed it though. Thanks for the how-to!
modelid: PN0712000
cidnum: 11111111

Sneakyghost said:
It doesn't sai FAILED custom id check (CID) but model id check (MID)
I have that on my thread for the hboots as well. I am still trying to find out if there are ONE devices with a different Model ID.
Can you run fastboot getvar all for me to get me your model id? Thank you!
Click to expand...
Click to collapse
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
MG

Thanks, it worked great! I recreated the Nexus splash screen and posted it below if anyone wants it.

just a theoretical scenario, if I were to flash the custom splash screen and then revert to S-ON, would the splash screen stay? and would my phone become a brick?

Stargazer418 said:
Thanks, it worked great! I recreated the Nexus splash screen and posted it below if anyone wants it.
Click to expand...
Click to collapse
I'm guessing you've managed to remove the "this is for development purposes" message?

dh2311 said:
just a theoretical scenario, if I were to flash the custom splash screen and then revert to S-ON, would the splash screen stay? and would my phone become a brick?
Click to expand...
Click to collapse
Only a RUU or maybe an OTA can reset your splash back to stock, so yes, it will stay. The splash image is not signed. Having a modified splash on S-On will not brick you. (Having a modified hboot on S-On will brick you tho!)

Simba501 said:
I'm guessing you've managed to remove the "this is for development purposes" message?
Click to expand...
Click to collapse
There's another thread on how to do that, look for hboot mod
Sent from my HTC One using Tapatalk 4 Beta

Simba501 said:
I'm guessing you've managed to remove the "this is for development purposes" message?
Click to expand...
Click to collapse
No, I didn't. I saw the thread about removing it, but I don't know if it will overwrite the splash I already flashed. It doesn't seem to show up every boot, though, so it's not that bad in my opinion.

[Firmware] HTC ONE M7 | Firmware 5.11.661.8 | No Red Text | Radio 4T.27.3218.14

This is the latest firmware for HTC ONE M7 extracted from official OTA for TELUS, 5.11.661.8
You need unlocked bootloader and S-OFF
I removed Red Warning Text and flashed successfully on my phone.
This build is for
development purposes only
Do not distribute outside of HTC
without HTC's written permission.
Failure to comply may
lead to legal action.
The zip contain:
- firmware 5.11.661.8
- hboot 1.57.0000
- radio 4T.27.3218.14
- the new splash screen "powered by android"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download file and copy to your adb folder:
A - full firmware link removed
MD5 be417a18c76ef0e517f32266e4b5d744
B - hboot only link removed
MD5 4b74f5f8c47bdd6aa2fc20446e5ce743
DON'T REBOOT THE PHONE UNTIL YOU GET A SUCCESS MESSAGE​
1 - Reboot bootloader
Code:
adb reboot-bootloader
2 - Reboot to RUU
Code:
fastboot oem rebootRUU
3 - Flash firmware
Code:
fastboot flash zip firmware_5.11.661.8_noredwarn.zip
Very important!!! One more time
Code:
fastboot flash zip firmware_5.11.661.8_noredwarn.zip
3b - Flash hboot only, if you want
Code:
fastboot flash zip hboot_1.57_no-red-warning.zip
4 - Reboot to bootloader and verify version
Code:
fastboot reboot-bootloader
5 - Reboot to system
Code:
fastboot reboot
6 - Enjoy
WARNING
Flash at your own risk, I can't be held responsible if you brick the phone!!!​

If case you need original firmware for modelid: PN0712000 cidnum: TELUS001
The zip contain:
- firmware 5.11.661.8
- hboot 1.57.0000
- radio 4T.27.3218.14
- the new splash screen "powered by android"
- stock boot
- stock recovery
link removed
MD5 895F3ADD2CCC1DE09F85910DCFE94B99

If flashed successfully please post your modelid and cid here.
Thanks

Flashed succsessfully on PN0710000 with super cid...:good:

I'm looking for the Telus M7 firmware for sense 6 - why were the links removed in this thread?
Sent from my HTC One using Tapatalk

Can you help me? Bricked my phone!
So I did something pretty dumb yesterday. Installed the HTC Sense 6 update on my HTC ONE M7, hated it so decided to root my phone to revert back to Sense 5.0 or 5.5 or potentially try a custom ROM. Downloaded a Tmobile 4.3 JB RUU, downloaded android SDK, HTC sync manager, Fastboot. I unlocked boot loader, installed Wheaton recovery by Koush, installed SU, figured phone was rooted but it wasn't. Now I've somehow succeeded in deleting EVERYTHING. Phone continues booting into recovery. Commands using Fastboot aren't recognized because it cannot find any device. When plugged in via USB, PC recognizes that something is plugged in but that's about it.
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
Open DSP-v32.120.274.0909
OS-5.14.531.1
eMMC-boot 2048MB
May 9 2014, 15:00:26.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Any help will be greatly appreciated

rodenti said:
I'm looking for the Telus M7 firmware for sense 6 - why were the links removed in this thread?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Some issues with corrupted zip files.
Download from here
http://forum.xda-developers.com/showthread.php?t=2485651
bonedatt said:
So I did something pretty dumb yesterday. Installed the HTC Sense 6 update on my HTC ONE M7, hated it so decided to root my phone to revert back to Sense 5.0 or 5.5 or potentially try a custom ROM. Downloaded a Tmobile 4.3 JB RUU, downloaded android SDK, HTC sync manager, Fastboot. I unlocked boot loader, installed Wheaton recovery by Koush, installed SU, figured phone was rooted but it wasn't. Now I've somehow succeeded in deleting EVERYTHING. Phone continues booting into recovery. Commands using Fastboot aren't recognized because it cannot find any device. When plugged in via USB, PC recognizes that something is plugged in but that's about it.
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
Open DSP-v32.120.274.0909
OS-5.14.531.1
eMMC-boot 2048MB
May 9 2014, 15:00:26.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Any help will be greatly appreciated
Click to expand...
Click to collapse
Post questions in Q&A section please

Thread closed at OP's request.

[FIX] Android Lollipop OTA GPE stuck at bootlogo

For those who are stuck at bootlogo, the problem is the same as the one when we tried before downgrading from 4.4.4 to 4.4.2 it is with the partition table, the version in the ota is older that the one we have on our devices, I dunno how the hell is that but it is what happened to most of us, though the easy fix, flash the attached gpt through fastboot command:
fastboot flash partition gpt.bin
Hope this fixed everything ​

Thanks very much for the information!
I recently tried flashing the 4.4.4 GPE firmware onto my XT1032 and I got an error when trying to flash the GPT.bin partition using mfastboot. It said "failed". I got nervous and went back to the retail US firmware just in case. We need more people to confirm that this fix will work.
OP do you know if it's safe to flash your GPT partition before installing the OTA update on the 4.4.4 GPE ROM?

It works!
I cant flash any rom to my phone and everything failed on half proces and with this file i rescued my phone i flashed 4.4.4 gpe and than 5.0.1 ota (by sideload) !
My Moto Gpe was brick!! And now it works again!!!! Thanks!!!!

Yes I can confirm, I faced this issue myself and used this fix for it )​

Yeah!!! this work very well, you save my phone, thanks man

seriusly that was all? i had 2 moto g at home and when the first one got the ota it got hard bricked, but stupid me got back to 4.4.2 and at the 4.4.4 ota the phone hard bricked, i think that the bootloader is corrupted and now i have to wait for the full 5.0 rom to be aviabable. Thanks man i appreciate it (i had another moto g and just got the ota and booted because of this)

can't use that, i've got the 41.18 bootloader so i have to wait a 5.0 original firmware :/
or am i doing something wrong?

Bad news
ssalamon said:
can't use that, i've got the 41.18 bootloader so i have to wait a 5.0 original firmware :/
or am i doing something wrong?
Click to expand...
Click to collapse
We have the same problem fella. We must wait the firmware with the image of new bootloader...Maybe in one month we take a solution...

So, with new bootloader is not possible to apply OTA. I have received 5.0.1 OTA on my 4.4.4 GPE converted XT1032, but this failed to start after latest try to update

sebadomaitis said:
We have the same problem fella. We must wait the firmware with the image of new bootloader...Maybe in one month we take a solution...
Click to expand...
Click to collapse
The original GPE firmware has a bootloader version older than that of the 4.4.4 "again I don't know why" the only fix is by flashing the gpt file included, if you flashed the android lollipop and it didn't work, flash this and give it a shot .
"bear in mind also that this fix is for devices stuck at bootlogo not bootanimation, not a fix for bootloop"

ruphert said:
So, with new bootloader is not possible to apply OTA. I have received 5.0.1 OTA on my 4.4.4 GPE converted XT1032, but this failed to start after latest try to update
Click to expand...
Click to collapse
I faced exactly what you are facing now, flash this and everything will go smooth

Rostomania said:
I faced exactly what you are facing now, flash this and everything will go smooth
Click to expand...
Click to collapse
Thanks for you reply. After sideload 5.0.1 and stucking and google logo should I flash only your gptfix.zip and reboot?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Phone is stucking after reboot.

ruphert said:
Thanks for you reply. After sideload 5.0.1 and stucking and google logo should I flash only your gptfix.zip and reboot?
Phone is stucking after reboot.
Click to expand...
Click to collapse
No man, do the following:
1- Reboot Into bootloader and connect your device via usb.
2- In your adb folder paste the gpt file I included and press right click and shift in any white space in the folder and choose start command prompt.
3- type fastboot flash partition gpt.bin and your problem should be fixed.

Rostomania said:
No man, do the following:
1- Reboot Into bootloader and connect your device via usb.
2- In your adb folder paste the gpt file I included and press right click and shift in any white space in the folder and choose start command prompt.
3- type fastboot flash partition gpt.bin and your problem should be fixed.
Click to expand...
Click to collapse
Thanks a lot, you rocks!
Code:
sudo fastboot flash partition gpt.bin 12:02
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.036s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.320s]
finished. total time: 0.356s
sudo fastboot reboot
Phone is booting now

boot stuck
Hi, I've stucked on "android logo with unlocked lock icon".
Originally I had xt1033 asian, which was converted to 4.4 GPE one sim. Today I've tried to flash the 5.0.1 lollipop via adb, and as many of you guys, stucked on boot.
I've already tried your fix, and tried to downgrade following this thread http://forum.xda-developers.com/moto-g/general/guide-xt1033-downgrade-lollipop-5-0-to-t2969729
but still phone doesn't boot, just "Google" and lock icon...
can you help me, at least boot it, android version doesn't metter
** UPDATE **
So, I've managed to boot phone thatks to this thread http://forum.xda-developers.com/moto-g/general/guide-restore-softbricked-phone-t2965459
Gonna make a backup and try installing 5.0.1 again

sebadomaitis said:
We have the same problem fella. We must wait the firmware with the image of new bootloader...Maybe in one month we take a solution...
Click to expand...
Click to collapse
Not exactly, my XT1033 had 41.18 bootloader when i applied the 5.0.1 ota, it just worked with the following tutorial. I didn't even use the gpt file here.
http://forum.xda-developers.com/moto-g/general/guide-convert-brazilian-firmware-gpe-5-t2969472

awesome.. this works like wonder.. but now i am not getting the network .. any idea what to do?

ghost9685 said:
awesome.. this works like wonder.. but now i am not getting the network .. any idea what to do?
Click to expand...
Click to collapse
Look at this tread
http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847
1st post
Step 5
Maybe it could work

My Own devices is a XT1032, and this fix has nothing to do with the XT1033 converted to GPE .​

I can also confirm that this works. But my phone was already converted to GPE and had 4.4.4 before I did the OTA update.
Giovani's guide works if you're stuck on the bootlogo after updating to 4.4.4 and then lollipop through OTA (on a gpe converted device of course). I used the second method in that thread.

[DISCONTINUED | GUIDE] HTC U11 How-To - Return to Full Stock ROM/Firmware

Hello folks,
as for me such guides were really helpful in the past, and there are alway poeple who are new to a device and modding it, I decided to do one on my own, to show you how to perform a reset of your HTC U11 to Full Stock ROM/Firmware.
In many points I tried carrying together all that has been written down prior to this guide in many others, by many others. Thus I - in some kind - just consolidate the fact, using my own words and a little bit different structure than others. Anyway I'll show you my steps again in this tutorial as I think it is of importance to many that they can read the hole to do in one thread. But I advise everyone.
Please note that I will not accept any responsibility for possible occurring bricks. I can only confirm that this tutorial has been used by me, for my specific unit and all went successful.
Look here for [Collection] HTCU U11 – RUU/Firmware/Recovery/OTA/Backups
Regards
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Restore using a Nandroid Backup
Restore using a RUU
Knowledge of adb/fastboot
htc_fastboot and adb installed
HTC U11
07 RU_CID_FAIL: CID in android-info.txt does not match your phone’s CID
10 RU_MODELID_FAIL: MID in android-info.txt does not match your phone’s MID
12 SIGNATURE FAIL: phone expects an HTC signature and can't find one; or found a wrong one
22 RU_HEADER_ERROR: something wrong with your zip; check md5 of download
23 PARSING IMAGE FAIL: something wrong with the image within the zip
24 ANDROID-INFO FAIL: something wrong with android-info.txt within the zip
32 HEADER ERROR: the zip couldn't be read and unzipped properly; seems same as 22.
33 NOT KNOWN YET: might indicate hardware failure.
35 FAILED (remote: 35 RU_PARTITION_NOT_SUPPORT <PartitionName>): means you can’t flash an image in download mode, as it has to be done in bootloader mode.
41 WRONG MODEL ID: means the RUU is menat for a different device
42 WRONG CUSTOMER ID: means you got to swap CID first
90 PRE-UPDATE FAIL: means it only flashed aboot and you have to run the process again immediately to flash all other partitions. The htc_fastboot.exe now auto-reboots on Error 90!
99 UNKNOWN: usually indicates you are S-ON, but sometimes also recognizes other Security related issues.
130 WRONG MODEL ID: see 41
155 INDICATES DIFFERENT THINGS:
the need to relock bootloader; if S-ON
the RUU cannot be executed, because the software versions of ROM, Firmware and RUU aren't matching
170 CHECK USB: RUU won’t run because ADB isn't working properly
171 USB ERROR: happens all the time when the RUU reboots the phone to download mode. For some reason the device is losing its connection and making a RUU flash virtually impossible . There is an incompatibility between USB 3/3.1 and Fastboot/ADB, as well as an issue with Windows Device Detection on the newer Windows 10 builds.
171 USB ERROR FIX by @Sneakyghost:
How to fix RUU error 171 on Windows 10x64 easily
System: Win 10 Redstone (1607) x64 with Intel based USB3.0 and USB2.0 ports:
Sync Manager from HTC Website
Imported Reg-File from Post #1
Reboot
Click to expand...
Click to collapse
​

Restore using a Nandroid
flash TWRP custom recovery
download custom recovery at https://twrp.me
reboot to download mode
Code:
adb reboot download
flash recovery image
Code:
htc_fastboot flash recovery nameoftwrp.zip
Restore your Nandroid. If you got none yourself, it might be possible that you’ll find one here.
unzip the according Nandroid
copy Nandroid to TWRP/Backup/SerialNo/Nameofbackup on your extSD
restore Nandroid by using TWRP > RESTORE and choosing above copied Nandroid
Flash incremental OTA firmware
reboot to download mode
perform
Code:
htc_fastboot getvar all
and note down your original software version
download all incremental OTA firmwares to your PC, starting with the one above your current firmware version, up to the software version number of your above choosen Nandroid Backup (ATTENTION: If you are S-OFF it will suffice to download the latest Incremental OTA as well as the latest Combined Full Wipe firmware according to the above choosen Nandroid Backup)
flash all incremental OTA firmwares – one after another – following the below named steps (ATTENTION: If you are S-OFF you start with the Combined FullWipe, and proceed with the Incremental OTA one, to ensure that you’ll be able to receive upcoming OTA updates)
Code:
htc_fastboot flash zip nameoffirmeware.zip
(ATTENTION: this has to be done twice to comlete, and it will flash full firmware, thus TWRP will be replaced by stock recovery)
As soon as you restored the Nandroid and flashed all incremental firmware file up to the current build number of your Nandroid, that's it. Your are now Full Stock again!

Restore using a RUU
reboot to download mode
perform
Code:
htc_fastboot getvar all
and note down your original software version
download the latest Stock RUU for your device over here.
flash your RUU to revert to stock
rename RUU to 2PZCIMG.zip
copy 2PZCIMG.zip to root directory of SD card
reboot to download mode
press Volume Up button to confirm flash of RUU
As soon as your RUU has been flashed sucessfully, that's it. Your are now Full Stock again!

Reserved just in case

Thanks you for this Always needed thread

Is it possible to install a non-branded RUU on a branded device, but otherwise keep things completely stock?

Zico 10 said:
Is it possible to install a non-branded RUU on a branded device, but otherwise keep things completely stock?
Click to expand...
Click to collapse
Not possible for as long as S-OFF isn't available. Will do a de-branding thread as soon as it becomes available.
Sent from my htc_ocnuhl using XDA Labs

deleted

Will this wipe my data?

5m4r7ph0n36uru said:
Not possible for as long as S-OFF isn't available. Will do a de-branding thread as soon as it becomes available.
Click to expand...
Click to collapse
Dying to unbranded my HTC U11 as well...

Will the bootloader say "Relocked" or "Locked" if i use this method and restore it to stock?
Sorry for the basic question.. Its been a long time used a HTC phone.

rkrishnamurthy said:
Will the bootloader say "Relocked" or "Locked" if i use this method and restore it to stock?
Sorry for the basic question.. Its been a long time used a HTC phone.
Click to expand...
Click to collapse
It will say relocked. A real locked state might be possible if S-OFF hits, but no way to do it until then.
Sent from my htc_pmeuhl using XDA Labs

Nice info when in the future want to go back to stock.
Sent from my HTC U11 using XDA Developers 2016 Premium

Hi,
I'm new to android. I was advised to root my HTC U 11 but after doing so and exploring options I decided I'd rather just remove root and return to stock. However, I'm a noob and didn't do a backup before flashing the recovery and rooting. I found this thread and it seems to have what I need but I'm hesitant to take the next step as I don't want to brick my new phone. Can someone explain what I need to do to return to stock in as simple/dumbed down way as possible?
It's a single sim variant, carrier is Optus (Australia) and the original software version was 1.03.710.7

There's only this step by step guide. Couldn't be more precise at what to do. If you don't understand such a detailed guide I'm a little bit irritated at why you rooted in the first part, if you don't know what happens by doing so and how to revert back properly
Sent from my htc_pmeuhl using XDA Labs

5m4r7ph0n36uru said:
There's only this step by step guide. Couldn't be more precise at what to do. If you don't understand such a detailed guide I'm a little bit irritated at why you rooted in the first part, if you don't know what happens by doing so and how to revert back properly
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
i've did all the steps and still my bootloader will not relock with the RUU method.

Stock RUU flash not working, her is fail message. Any ideas?
Error code 19 RU_MAIN_VER_FAIL os-version in android-info missing or i

mr573162 said:
i've did all the steps and still my bootloader will not relock with the RUU method.
Click to expand...
Click to collapse
RUU any method does not relock bootloader, you have to manually do it in fastboot. Download mode, CMD type fastboot oem lock
---------- Post added at 08:31 AM ---------- Previous post was at 08:27 AM ----------
andybg40 said:
Stock RUU flash not working, her is fail message. Any ideas?
Error code 19 RU_MAIN_VER_FAIL os-version in android-info missing or i
Click to expand...
Click to collapse
Are you flashing the correct RUU?

schmeggy929 said:
RUU any method does not relock bootloader, you have to manually do it in fastboot. Download mode, CMD type fastboot oem lock
---------- Post added at 08:31 AM ---------- Previous post was at 08:27 AM ----------
Are you flashing the correct RUU?
Click to expand...
Click to collapse
Yes I have tried the command of fastboot oem lock and it tells me failed unknown command.
C:\adb>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.004s

mr573162 said:
Yes I have tried the command of fastboot oem lock and it tells me failed unknown command.
C:\adb>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.004s
Click to expand...
Click to collapse
You really doing it in download mode, or are you in bootloader?!
Sent from my htc_pmeuhl using XDA Labs

Can't access GSM phone after a return to stock

Dear All,
I was on Validus rom 8.10 r4, then i decided to sell the phone and go back to stock and relock bootloader.
I use the toolkit of Motorola Moto G5+ Toolkit.
I flashed and everything went good. Restarted and I can't access to my network.
I have the Amazon version Italian.
Xt1685 Retail...
please help me

tufoz said:
Dear All,
I was on Validus rom 8.10 r4, then i decided to sell the phone and go back to stock and relock bootloader.
I use the toolkit of Motorola Moto G5+ Toolkit.
I flashed and everything went good. Restarted and I can't access to my network.
I have the Amazon version Italian.
Xt1685 Retail...
please help me
Click to expand...
Click to collapse
You have an XT1685 Retail Italian version... Or a Amazon ad supported version? It can't be both, the fact you may have purchased it from Amazon it not relevant.
That aside... 99% chance the radio firmware did not flash correctly. Reflash the ROM manually and watch each step for a failure, if any piece fails, repeat it up to 3 times before continuing (radio firmware often requires 2 or sometimes 3 attempts to flash properly).

acejavelin said:
You have an XT1685 Retail Italian version... Or a Amazon ad supported version? It can't be both, the fact you may have purchased it from Amazon it not relevant.
That aside... 99% chance the radio firmware did not flash correctly. Reflash the ROM manually and watch each step for a failure, if any piece fails, repeat it up to 3 times before continuing (radio firmware often requires 2 or sometimes 3 attempts to flash properly).
Click to expand...
Click to collapse
https://s17.postimg.org/l8pargixr/P1040621.jpg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

so what firmware do you suggest?
I used this procedure and one step fails.. i will do it again...
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot

tufoz said:
so what firmware do you suggest?
Click to expand...
Click to collapse
Retail Italian, whatever is current... Your missing the point though, you need to flash it manually because the most likely case is the radio firmware (NON-HLOS and fsg.mbn) didn't take correctly.

acejavelin said:
Retail Italian, whatever is current... Your missing the point though, you need to flash it manually because the most likely case is the radio firmware (NON-HLOS and fsg.mbn) didn't take correctly.
Click to expand...
Click to collapse
Thanks sir...
I will do it...
So I will pick this one: "POTTER_RETAIL_7.0_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" Agreed ?

tufoz said:
Thanks sir...
I will do it...
So I will pick this one: "POTTER_RETAIL_7.0_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" Agreed ?
Click to expand...
Click to collapse
That firmware appears to be for US devices, which firmware did you lock your device with?
As far as I know, retail EU (software channel retEU) device firmware is up to NPNS25.137-33-11 . I do not know if the npn25.137-92 firmware is suitable for EU devices.

echo92 said:
That firmware appears to be for US devices, which firmware did you lock your device with?
As far as I know, retail EU (software channel retEU) device firmware is up to NPNS25.137-33-11 . I do not know if the npn25.137-92 firmware is suitable for EU devices.
Click to expand...
Click to collapse
edit..
everything went good but still no netw access..
i can see the list of the network but if i try to log in .. it fails..

tufoz said:
edit..
everything went good but still no netw access..
i can see the list of the network but if i try to log in .. it fails..
Click to expand...
Click to collapse
Hmm, is the the Wi-Fi network or the SIM/telephone network you're trying to access?
If the SIM/telephone network, check your mobile APNs are set correctly, and check if the SIM is working in another device (to verify it's not the SIM at fault).

echo92 said:
Hmm, is the the Wi-Fi network or the SIM/telephone network you're trying to access?
If the SIM/telephone network, check your mobile APNs are set correctly, and check if the SIM is working in another device (to verify it's not the SIM at fault).
Click to expand...
Click to collapse
mobile career network...
I done this: returned to stock and the carrier doens't work
Flashed Validus and it doesn't work
But If i Flash omnirom it starts to work.. and then i can flash validus over omnirom to let it work.... very strange!
so what does Ominrom has in order to let it work? Omni rom is the turning point..

tufoz said:
mobile career network...
I done this: returned to stock and the carrier doens't work
Flashed Validus and it doesn't work
But If i Flash omnirom it starts to work.. and then i can flash validus over omnirom to let it work.... very strange!
so what does Ominrom has in order to let it work? Omni rom is the turning point..
Click to expand...
Click to collapse
is 4g working ?

tufoz said:
mobile career network...
I done this: returned to stock and the carrier doens't work
Flashed Validus and it doesn't work
But If i Flash omnirom it starts to work.. and then i can flash validus over omnirom to let it work.... very strange!
so what does Ominrom has in order to let it work? Omni rom is the turning point..
Click to expand...
Click to collapse
The fact that some ROMs work and others don't means your radio firmware did not flash correctly, it is incorrect (US firmware on EU model). I know you said it flashed it correctly, but the symptoms dictate otherwise.
Some ROMs support Marshmallow firmware and others Nougat... But stock requires kernel and firmware match.

I have the same problem, now my imei is on "0" the two imei the same, and i have "without service", so i cant call anyone, i cant use mobile network.

acejavelin said:
The fact that some ROMs work and others don't means your radio firmware did not flash correctly, it is incorrect (US firmware on EU model). I know you said it flashed it correctly, but the symptoms dictate otherwise.
Some ROMs support Marshmallow firmware and others Nougat... But stock requires kernel and firmware match.
Click to expand...
Click to collapse
Can be that i chose the wrong stock file image? now on "pixelEperience" i have GSM signal but only in 3g
rakesh95 said:
is 4g working ?
Click to expand...
Click to collapse
It seems no..

tufoz said:
Can be that i chose the wrong stock file image? now on "pixelEperience" i have GSM signal but only in 3g
It seems no..
Click to expand...
Click to collapse
I have the same problem, the same the same, i want my 4G+ again :crying:

I have the same problem. I manually flashed the stock firmware (NPN25.137-92) many times but I still get no service. Both NON-HLOS and fsg.mbn seem to have flashed without any errors. The only parts that fail are the following:
fastboot erase customize (permission denied)
fastboot erase clogo (permission denied)
When I flash PixelExperience or crDroid only 3g works. I tried changing APN settings but no luck.

Yoga K. said:
I have the same problem. I manually flashed the stock firmware (NPN25.137-92) many times but I still get no service. Both NON-HLOS and fsg.mbn seem to have flashed without any errors. The only parts that fail are the following:
fastboot erase customize (permission denied)
fastboot erase clogo (permission denied)
When I flash PixelExperience or crDroid only 3g works. I tried changing APN settings but no luck.
Click to expand...
Click to collapse
so it's a common situation.... where are you from?

tufoz said:
so it's a common situation.... where are you from?
Click to expand...
Click to collapse
XT1687 retail US

tufoz said:
so it's a common situation.... where are you from?
Click to expand...
Click to collapse
I have one also XT-1681 NPN25.137-92 no imei's showing.

Yoga K. said:
XT1687 retail US
Click to expand...
Click to collapse
Hmm, to the best of my knowledge, NPN25.137-92 is not a firmware designed for retus devices - I think the latest for US devices is NPN25.137-83.
I don't know if you can safely downgrade to NPN25.137-83 now you've flashed NPN25.137-92 onto your device. You may have to wait for a newer retus firmware or if you do downgrade, avoid using OTA updates.