Database Develop

[HBOOT] HOWTO Install an ENG hboot on your INC S

Brought to you by touchpro247 and I. (touchpro247 put his phone on the line testing this)
First off, I take no blame for anything that happens due to this. This can potentially brick your phone. If this bricks your phone, makes it unstable, kills your cat.. YOUR FAULT not mine.
Please, don't make typos in the commands.
Eng Hboots allow you to flash unsigned images, and opens up more fastboot commands. Most people do not need this. This will not [provide perm root, or un-writeprotecte the emmc chip. In fact, if you don't have s-off it won't work for you.
Requirements:
Root
radio (ship) s-off
Busybox properly installed
adb working
If you do not have busybox, you can use this app to install it https://market.android.com/details?id=stericson.busybox
Download the ENGHboot for Vivo here:
http://cunninglogic.com/android/vivo/vivo_enghboot.img
put the file on your sdcard
Follow these commands
Code:
adb shell
If you have havea $ prompt and not a # prompt, run su
Code:
su
You should now have a # prompt and can continue
Code:
busybox md5sum /sdcard/vivo_enghboot.img
If the output is NOT b1829cfb7cf5d462660a58aa5449d27c , STOP redownload the file and try again. Anything else could cause a brick. If it matches, continue.
Code:
dd if=/sdcard/vivo_enghboot.img of=/dev/block/mmcblk0p18
reboot bootloader
You should now see this, and are done.
{
"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"
}
Enjoy

Very nice.!

Note: This is case sensitive and the file should be placed on the root of your sdcard.
Please just use the "THANKS" feature.
We all need to help keep the Dev threads clean.
Sent from my HTC Incredible S using XDA Premium App

very good!!

look forward to s on～～～

Hi, Man, thank you so much, thanks for your hard working, god bless you.

very nice! good how to

need root ,s-on!!XXXXXXXX

it is soon~!

If a way to unlock the emmc write protection is found (it is not kernel based, and wpthis will not work), then this hboot can be used to set the phone s-off.

i think unlock s-on is not so far

jcase said:
If a way to unlock the emmc write protection is found (it is not kernel based, and wpthis will not work), then this hboot can be used to set the phone s-off.
Click to expand...
Click to collapse
to oil, s-on people wait for you, thx~~~

i think unlock s-on is not so far～～～

dump of vivo hboot after xtc-clip
Hi,
Thank you for this post.
Before trying to flash your hboot, i've made a dump of the one i've obtained after unlocking my phone with an xtc-clip.
It seems that this is the same as yours but a little bit more recent.
Version 1.09.0000.
I've uploaded it here : http://www.multiupload.com/QPS8W9RH0M
If someone is interested.

max-k said:
Hi,
Thank you for this post.
Before trying to flash your hboot, i've made a dump of the one i've obtained after unlocking my phone with an xtc-clip.
It seems that this is the same as yours but a little bit more recent.
Version 1.09.0000.
I've uploaded it here : http://www.multiupload.com/QPS8W9RH0M
If someone is interested.
Click to expand...
Click to collapse
Thanks for this. Couple of questions.
How did you dump the hboot image? I actually had no idea this was possible... Also, did the hboot version actually change after you used the xtc clip? I'm not 100% sure how the clip works internally, but was under the impression that it sets the flags at the radio level, and doesn't specifically modify the bootloader.

deficitism said:
Thanks for this. Couple of questions.
How did you dump the hboot image?
I actually had no idea this was possible...
Click to expand...
Click to collapse
I've dumped the image using your process :
dd if=/dev/block/mmcblk0p18 of=/sdcard/vivo_hboot.img
Also, perhaps it doesn't works. I don't try to reflash it yet.
deficitism said:
Also, did the hboot version actually change after you used the xtc clip? I'm not 100% sure how the clip works internally, but was under the impression that it sets the flags at the radio level, and doesn't specifically modify the bootloader.
Click to expand...
Click to collapse
I'm not sure too.
Perhaps you're right.
But, if you're right, i don't know if there are any differences between my old hboot and yours.
Options in "fastboot" and "bootloader" are the same.

max-k said:
I've dumped the image using your process :
dd if=/dev/block/mmcblk0p18 of=/sdcard/vivo_hboot.img
Also, perhaps it doesn't works. I don't try to reflash it yet.
I'm not sure too.
Perhaps you're right.
But, if you're right, i don't know if there are any differences between my old hboot and yours.
Options in "fastboot" and "bootloader" are the same.
Click to expand...
Click to collapse
The ENG (engineering) is on top. The hboot you dumped is on bottom of the picture, it is a SHIP hboot. Meaning, unless the radio says other wise, you are s-on. It also has limited fastboot commands, and checks for signatures before flashing.
XTC clip sets s-off in the radio config, and does not modify hboot in any way.
I do not know how you determined it to be the same. Most of the time ENG hboots are older, as they are not used in production, but in testing.

jcase said:
The ENG (engineering) is on top. The hboot you dumped is on bottom of the picture, it is a SHIP hboot. Meaning, unless the radio says other wise, you are s-on. It also has limited fastboot commands, and checks for signatures before flashing.
XTC clip sets s-off in the radio config, and does not modify hboot in any way.
I do not know how you determined it to be the same. Most of the time ENG hboots are older, as they are not used in production, but in testing.
Click to expand...
Click to collapse
Yep. Although, he should now be able to flash the engineering bootloader.
From the looks of it, it appears we should be able to talk to the bootloader through a USB cable with some sort of console access. I recall unrevoked's toolset doing so to temporarily disable the NAND protection long enough to flash a custom recovery. Unfortunately, these devices seem to only be booting factory signed hboot and recovery images.
We need either:
(1) As jcase said, an old ass radio image.
(2) A signed engineering bootloader
(3) A methodology for simulating the ports/diag commands that the sim unlock clip is using. And a way to send the config flags over USB.
(4) A brand spanking new vulnerability
Just thinking aloud.

I think best bet will be a new exploit to remove wp and allowed us to flash the eng hboot or set the radio s-off
Sent from my LG Revolution

jcase said:
The ENG (engineering) is on top. The hboot you dumped is on bottom of the picture, it is a SHIP hboot. Meaning, unless the radio says other wise, you are s-on. It also has limited fastboot commands, and checks for signatures before flashing.
XTC clip sets s-off in the radio config, and does not modify hboot in any way.
I do not know how you determined it to be the same. Most of the time ENG hboots are older, as they are not used in production, but in testing.
Click to expand...
Click to collapse
Thank-you for this explanations.

[Q]Get rid of "This is test device... Tell HTC can not be turned off" ?

Hey XDAers
In Settings-Tell HTC- at the bottom there is a warning that says
This is a test device. Accordingly, to collect critical information about the device, Tell HTC is enabled and cannot be turned off regardless of device settings
I have read this is due to S-OFF or due to custom hboot. Is there any way we can save some battery by disabling this? Can we freeze/uninstall Tell HTC? Any ideas?
{
"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"
}

kazprotos said:
Hey XDAers
In Settings-Tell HTC- at the bottom there is a warning that says
This is a test device. Accordingly, to collect critical information about the device, Tell HTC is enabled and cannot be turned off regardless of device settings
I have read this is due to S-OFF or due to custom hboot. Is there any way we can save some battery by disabling this? Can we freeze/uninstall Tell HTC? Any ideas?
Click to expand...
Click to collapse
search the dev forums, a methods been posted already

Been searching for a day now can't find a clear answer any link/help appreciated thanks

There is a HBOOT modification hack that will remove that red text, but it's dangerous if you forgot you did it. With the modified HBOOT, taking an OTA that installs a new HBOOT will automatically perma brick your device. You have to go back to stock HBOOT before updating any OTA's if you're on stock ROM.

kazprotos said:
Been searching for a day now can't find a clear answer any link/help appreciated thanks
Click to expand...
Click to collapse
it took me less than a minuite...
here you go: http://forum.xda-developers.com/showthread.php?t=2316726

Whist this has gotten rid of the red warning when entering fastboot, I was asking about the red text in the settings->about->Tell HTC and error reporting. Screenshot added.

i read somewhere that the sign is due to s-off and also if u get your device s-on again , the the red writing will go..
i didn't try that

ahmed83 said:
i read somewhere that the sign is due to s-off and also if u get your device s-on again , the the red writing will go..
i didn't try that
Click to expand...
Click to collapse
Correct it's due to s off... I think and I could be very wrong but...devices with s off are seen as engineering devices and such

a box of kittens said:
Correct it's due to s off... I think and I could be very wrong but...devices with s off are seen as engineering devices and such
Click to expand...
Click to collapse
I can confirm that going s-on makes the message go away.

And we can't go S-OFF again on 2.24 base
Dliemna

Problem solved
http://forum.xda-developers.com/showpost.php?p=43397722&postcount=72

kazprotos said:
Problem solved
http://forum.xda-developers.com/showpost.php?p=43397722&postcount=72
Click to expand...
Click to collapse
except that now if you go and press tell htc settings force closes ...

Mine just disappeared, no more Tell HTC button

samflorin said:
I can confirm that going s-on makes the message go away.
Click to expand...
Click to collapse
I'm almost at the last part of reverting. When I type "fastboot oem writesecureflag3" it says not found. Any idea what i'm doing wrong?

You're missing the spacebar
----------------------o('_')o----------------------
Sent from an HTC One using xda app and Bulletproof TrickDroid ROM 8.0

I have the exact same problem - what are the steps to resolve this? Status = locked and S-off.... someone please help!

dark_polok said:
I'm almost at the last part of reverting. When I type "fastboot oem writesecureflag3" it says not found. Any idea what i'm doing wrong?
Click to expand...
Click to collapse
fastboot oem writesecureflag 3 (notice the space)
Also make sure that fastboot is in your $PATH (on *UX) or %PATH%. You can try going to the folder (in command line) where fastboot resides before running the above command. The problem may be that you get "Device not found", case in which you have not selected "fastboot" from the menu (which seems to be the case of @rt1990 ). The menu should read "fastboot usb" i believe before writesecureflag will work.
Warnings:
1. Make sure that your hboot is stock! S-ON on custom hboot = you're screwed (brick).
2. If you upgrade to 4.2.2 you won't be able to get S-OFF back since the updated hboot does not currently work with revone!
3. Before S-ON run again revone -t to remove tampered flag (just in case)
3. If you have "TAMPERED" appearing after s-on/bl locked you must run a RUU for your device to make it go away (i have it and there is no 4.2.2 RUU that i can run to confirm this though)
What i'd suggest you is to take the advice and remove the damn apk from system and tell htc will completely go away. I could afford going back to S-ON/Locked BL because i won't run any custom roms. I have rooted my device but i have no use for root either
---------- Post added at 12:37 PM ---------- Previous post was at 12:35 PM ----------
See my above post.
---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------
From @kazprotos' post above (quoting from the link he posted): Regarding Tell HTC app, delete the Udove.apk in system/apps.

i have the same message...are there any different methods to root it or same method as others?

athulpmenon said:
i have the same message...are there any different methods to root it or same method as others?
Click to expand...
Click to collapse
Read the post above you. removing the apk is the best way to get rid of the Tell HTC message if you want to stay S-OFF.

It's already solved.
Please see this:
http://forum.xda-developers.com/showthread.php?t=2488696

[Q] How to root HBoot 1.13 with S-Off already

My phone is Hboot 1.13 with S-OFF already.
This is what is shown when I press volume down+power
VIVO PVT SHIP S-OFF RL
HBOOT - 1.13.0000
RADIO-3805.04.03.27_M
eMMC-boot
Apr 1 2011, 18:34:39
How do I root it and install custom recovery in this? Please guide.

moomal said:
My phone is Hboot 1.13 with S-OFF already.
This is what is shown when I press volume down+power
VIVO PVT SHIP S-OFF RL
HBOOT - 1.13.0000
RADIO-3805.04.03.27_M
eMMC-boot
Apr 1 2011, 18:34:39
How do I root it and install custom recovery in this? Please guide.
Click to expand...
Click to collapse
Reboot to fastboot.
Flash custom Recovery.
Flash superuser script.
Flash whatever ROM.
The specifics of how to do those 4 above steps should be in every guide. Just search the guide a bit

072665995 said:
Reboot to fastboot.
Flash custom Recovery.
Flash superuser script.
Flash whatever ROM.
The specifics of how to do those 4 above steps should be in every guide. Just search the guide a bit
Click to expand...
Click to collapse
Thanks a lot

072665995 said:
Reboot to fastboot.
Flash custom Recovery.
Flash superuser script.
Flash whatever ROM.
The specifics of how to do those 4 above steps should be in every guide. Just search the guide a bit
Click to expand...
Click to collapse
I tried to flash through my PC. But it says Failed (Not allowed) Can you tell what the problem might be?

moomal said:
I tried to flash through my PC. But it says Failed (Not allowed) Can you tell what the problem might be?
Click to expand...
Click to collapse
How can i fix your problem if i IBT even know what's wrong??
Can you post a screenshot of the cmd ??
Sent from my Incredible S using xda app-developers app

072665995 said:
How can i fix your problem if i IBT even know what's wrong??
Can you post a screenshot of the cmd ??
Sent from my Incredible S using xda app-developers app
Click to expand...
Click to collapse
{
"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"
}

moomal said:
Click to expand...
Click to collapse
i guess it doesn't work with win8. Try running cmd with admin rights. if fails then. try with Win7

mafie said:
i guess it doesn't work with win8. Try running cmd with admin rights. if fails then. try with Win7
Click to expand...
Click to collapse
Tried that too. Still won't work

moomal said:
Click to expand...
Click to collapse
windows 8 might be a bit different. Search a bit online.
Also search in google "writing recovery FAILED"
I'm sure other people have had this problem before.

072665995 said:
windows 8 might be a bit different. Search a bit online.
Also search in google "writing recovery FAILED"
I'm sure other people have had this problem before.
Click to expand...
Click to collapse
Can't find any for Incredible s.

mafie said:
i guess it doesn't work with win8. Try running cmd with admin rights. if fails then. try with Win7
Click to expand...
Click to collapse
My phone is refurbished and it's still on Android 2.3.3 (It won't update) In case it helps.

Okay. This is a stupid question.. but just in case.. is your bootloader locked or unlocked?? I feel something is wrong there..
The same happened with one of my friend too..
Sent from my HTC Incredible S

moomal said:
Click to expand...
Click to collapse
Were you able to flash anything? Mine says hboot 1.13 too but no locked or unlocked water mark with S-OFF but when I type in commands it sayas I cant. Did you fix it? I dont even have a custom recovery or rom. It's just dead

cowboysgz said:
Were you able to flash anything? Mine says hboot 1.13 too but no locked or unlocked water mark with S-OFF but when I type in commands it sayas I cant. Did you fix it? I dont even have a custom recovery or rom. It's just dead
Click to expand...
Click to collapse
Just run revolutionary. Flash custom recovery. Flash Superuser script and you're good to go.
Also stop posting the same issue multiple times. Its possibly the easiest way to piss another XDA member off. Post once about your issue in the general forum and DO NOT post again somewhere else.

cowboysgz said:
Were you able to flash anything? Mine says hboot 1.13 too but no locked or unlocked water mark with S-OFF but when I type in commands it sayas I cant. Did you fix it? I dont even have a custom recovery or rom. It's just dead
Click to expand...
Click to collapse
Yes I was able to do it. Since it's S-OFF but still unlocked so it won't allow you. So I followed this link:
http://forum.xda-developers.com/showthread.php?t=1591729
It would do it for sure

[RUU][Firmware]Sprint HTC One | 4.06.651.4 | Encrypted | Decrypted | Stock Rooted ROM

Here we have the RUU for the Sprint HTC One 4.06.651.4!!! This RUU is for the Sprint One ONLY to restore your phone back to stock. If you are S-ON, you MUST relock your bootloader prior to using this RUU.
HUGE Thanks to the dude who hooked me up, you're awesome!
credit to @-viperboy- for decrypting, thanks!
***IMPORTANT NOTE*** you must first update your hboot to 1.56 to flash this 4.06 RUU, see full firmware below ( I recommend being s-off before doing so)
{
"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"
}
How to use:
-Download Sprint_HTC_One_m7wls_4.06.651.4_RUU.zip
-extract zip to a folder on your pc
-boot into bootloader (various ways)
-using fastboot, type this cmd: fastboot oem lock this will relock the bootloader (S-ON ONLY)
-from pc, run ARUWizard.exe from the extracted folder. it will run the RUU utility & flash back to stock
DEVs, here is the Decrypted version!
Sprint_HTC_One_m7wls_4.06.651.4_RUU_decrypted.zip
These new RUU's now have the system.img split into 3 imgs. You must combine prior to extracting. Copy all 3 to a folder, then...
Use this cmd for Windows:
copy /b system_1.img + system_2.img + system_3.img newsystem.img
Use this cmd for Linux:
cat system_1.img system_2.img system_3.img > newsystem.img
credit to @-viperboy- for the cmds, thanks!
Here is the extracted Firmware:
Full Firmware from RUU (fastboot flashable): http://www.androidfilehost.com/?fid=23329332407568410
Modified Firmware w/ Radio....removed hboot, boot, recovery (fastboot flashable): http://www.androidfilehost.com/?fid=23329332407574146
some basic instructions for flashing the modified firmware....
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type Fastboot oem rebootRUU
-when u see the black screen w/ HTC, type Fastboot flash zip firmware.zip
-when it's done, type Fastboot reboot
Here's a nice video from @thoughtlesskyle showing you how to flash the firmware:

Stock Rooted Romz Made From The RUU
Sprint_One_Stock_Rooted_Deodexed_4.06.651.4.zip
MD5 5603e630ddffc29a9dd20c96867c1853
Sprint_One_Stock_Rooted_Odex_4.06.651.4.zip
MD5 022aad5e626f08ea6899d7390320324c
Unsecure boot img. init.d support, data/app support
If you get the Side by Side Configuration error while using the RUU you need to install Microsoft Visual C++​

Great work gents
Sent from my Nexus 7

If I were to do the Ruu and im s-off with hboot 1.55 will it update me to 1-56 hboot and still have s-off. I read on a thread that by flashimg the Ruu will eliminate my phone not able to update profile and prl. I jhave been having issues in updating my profile with code 1233, currently in Bad Boyz Rom 1.0 4.06
Sent from my HTCONE using xda app-developers app

Thank you for offering this option so soon, it's greatly appreciated and saves so much time!
Sent from my HTCONE using Tapatalk

there have been reports of the RUU not unzipping, I have re-upped... http://www.androidfilehost.com/?fid=23329332407573774

Will come in handy, thanks O.M.J.!
Sent from my HTCONE

This is what I get every time. After following this guide I am normally able to use fastboot/adb just fine.
I am on rumrunner hboot 1.55.5555
Let me know what other info I can provide.. Please help!
Edit:
I ran the utility on my XP computer, and it gave me a little more info: "The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."

Is the RUU different than the OTA?

numus said:
Is the RUU different than the OTA?
Click to expand...
Click to collapse
Are you asking me?

numus said:
Is the RUU different than the OTA?
Click to expand...
Click to collapse
The end result are the same.
The OTA will update the the version of android you are on and keepall of your data intact
The RUU will wipe everything on your phone and reset it as it was when it was brand new but with the latest version of android or the version of the RUU you are using.
---------- Post added at 03:19 AM ---------- Previous post was at 03:18 AM ----------
systemshock869 said:
This is what I get every time. After following this guide I am normally able to use fastboot/adb just fine.
I am on rumrunner hboot 1.55.5555
Let me know what other info I can provide.. Please help!
Edit:
I ran the utility on my XP computer, and it gave me a little more info: "The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
Click to expand...
Click to collapse
Can you confirm the windows 8.1 drivers are installed?

benny3 said:
The end result are the same.
The OTA will update the the version of android you are on and keepall of your data intact
The RUU will wipe everything on your phone and reset it as it was when it was brand new but with the latest version of android or the version of the RUU you are using.
---------- Post added at 03:19 AM ---------- Previous post was at 03:18 AM ----------
Can you confirm the windows 8.1 drivers are installed?
Click to expand...
Click to collapse
Thanks... knew that part but was wondering why anyone would rebase based on the RUU then.

numus said:
Thanks... knew that part but was wondering why anyone would rebase based on the RUU then.
Click to expand...
Click to collapse
when u install an OTA, alot of files are "patched", RUU is just cleaner. When I diffed the 4.06 dump against the RUU, most of the files were binary equal but there were 250+ that were not.

OP updated with 4.06 firmware, which includes the radio & much more that were not in the OTA....this will be especially handy for users that are on older versions of JB that need to get caught up.

no more simultaneous voice + LTE
O.M.J said:
OP updated with 4.06 firmware, which includes the radio & much more that were not in the OTA....this will be especially handy for users that are on older versions of JB that need to get caught up.
Click to expand...
Click to collapse
i updated to kit kat and now I don't have simultaneous voice and LTE which I used to have...anyone else notice this? I know that simultaneous voice and 3G was never an option(unlike the EVO 4G LTE) but I always had simultaneous LTE + Voice...this sucks!!

O.M.J said:
OP updated with 4.06 firmware, which includes the radio & much more that were not in the OTA....this will be especially handy for users that are on older versions of JB that need to get caught up.
Click to expand...
Click to collapse
I'm trying to run the RUU but I am getting an error 158. The installer runs and gets my phone to the black HTC screen then it fails. After exiting the installer my phone does a reboot and I'm back into my ROM (Bad Boys 4.4.2 v1.1). My phone is running unlocked HBOOT 1.44 and is S-OFF. Any ideas? Searching has netted some hits on other device forums but nothing terribly helpful for the One specifically. Should I take the Rom.zip out of the 4_06_651_4 folder and try to flash it with fastboot? If so is that ok to do unlocked or do I need to do an oem lock first?

jaybombz said:
This is exactly what I'm trying to do but I am getting an error 158. The installer runs and gets my phone to the black HTC screen then it fails. After exiting the installer my phone does a reboot and I'm back into my ROM (Bad Boys 4.4.2 v1.1). My phone is running unlocked HBOOT 1.44 and is S-OFF. Any ideas? Searching has netted some hits on other device forums but nothing terribly helpful for the One specifically. Should I take the Rom.zip out of the 4_06_651_4 folder and try to flash it with fastboot? If so is that ok to do unlocked or do I need to do an oem lock first?
Click to expand...
Click to collapse
You run this RUU from your PC not fastboot.

BD619 said:
You run this RUU from your PC not fastboot.
Click to expand...
Click to collapse
Understood, apologies if my post wasn't clear. When running the RUU installer from my PC I get an error 158. I was asking if anyone knows what is causing this/how to fix it or if I can work around it by manually running fastboot flash zip rom.zip and if that was safe to do unlocked.
Thanks for your help!

Unless I am mistaken, you have to relock your bootloader to run the RUU.
jaybombz said:
Understood, apologies if my post wasn't clear. When running the RUU installer from my PC I get an error 158. I was asking if anyone knows what is causing this/how to fix it or if I can work around it by manually running fastboot flash zip rom.zip and if that was safe to do unlocked.
Thanks for your help!
Click to expand...
Click to collapse

sevarious said:
Unless I am mistaken, you have to relock your bootloader to run the RUU.
Click to expand...
Click to collapse
OP says only if you're S-ON so I thought you didn't have to if you are S-OFF.

return phone for warrenty

I have custom recovery, bootloader unlocked and s-off. My phone does not power on anymore. Not a single signal. Not even the LED lights up when plugged into the charger.. I think i will send it to HTC. Is HTC able to spot that is it unlocked etc. ?

MICH_** said:
I have custom recovery, bootloader unlocked and s-off. My phone does not power on anymore. Not a single signal. Not even the LED lights up when plugged into the charger.. I think i will send it to HTC. Is HTC able to spot that is it unlocked etc. ?
Click to expand...
Click to collapse
If you unlocked it with HTCdev.com, then yes they will be able to. But usually unlocking the bootloader doesn't make the entire device stop working. They might blame you for over clocking or something, but there isn't anything you can do about it. You obviously can't re-lock it, so I would just send it in and hope that they don't care.

aooga said:
If you unlocked it with HTCdev.com, then yes they will be able to. But usually unlocking the bootloader doesn't make the entire device stop working. They might blame you for over clocking or something, but there isn't anything you can do about it. You obviously can't re-lock it, so I would just send it in and hope that they don't care.
Click to expand...
Click to collapse
The bootloader was unlocked before it stopped working. I was able to install the stock rom. I have i plan how i could make it completely stock.. but for my plan i need it to boot into recovery.

MICH_** said:
The bootloader was unlocked before it stopped working. I was able to install the stock rom. I have i plan how i could make it completely stock.. but for my plan i need it to boot into recovery.
Click to expand...
Click to collapse
You can't make it stock if you can't turn it on. Honestly, there is NOTHING you can do right now except send it in if the phone doesn't even get to the bootlaoder or RUU modes.
I don't think HTC will not fix it though. They should be fine with it.

aooga said:
You can't make it stock if you can't turn it on. Honestly, there is NOTHING you can do right now except send it in if the phone doesn't even get to the bootlaoder or RUU modes.
I don't think HTC will not fix it though. They should be fine with it.
Click to expand...
Click to collapse
Ok, i will send it to HTC and hope for the best thank you

I made the bootloader to show "locked" and flashed the stock recovery!
How to get s-on now?

Leave it s off
Sent from my GT-I9305 using xda app-developers app

nateboi81 said:
Leave it s off
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Are you sure? Do i have warranty with s-off?

MICH_** said:
Are you sure? Do i have warranty with s-off?
Click to expand...
Click to collapse
Well, it depends. Usually, HTC will only check for the TAMPERED flag and the bootloader status. But sometimes, they may have a problem with the phone being S-OFF.
I S-ON'ed my phone before giving it for warranty repair.
Anyways, whether u will S-ON the phone or not, ill tell u how to S-ON.
Put the phone in fastboot mode. On ur PC, open command prompt and type:
fastboot oem writesecureflag 3
Then, do what the screen shows
HOWEVER, DO NOT S-ON UR PHONE IF HBOOT IS 1.55 OR ABOVE. THE TAMPERED LOGO WILL RE-APPEAR

raghav kapur said:
Well, it depends. Usually, HTC will only check for the TAMPERED flag and the bootloader status. But sometimes, they may have a problem with the phone being S-OFF.
I S-ON'ed my phone before giving it for warranty repair.
Anyways, whether u will S-ON the phone or not, ill tell u how to S-ON.
Put the phone in fastboot mode. On ur PC, open command prompt and type:
fastboot oem writesecureflag 3
HOWEVER, DO NOT S-ON UR PHONE IF HBOOT IS 1.55 OR ABOVE. THE TAMPERED LOGO WILL RE-APPEAR
Click to expand...
Click to collapse
okay, i will try to get s-on. But how to do so? Does it work by just typing "fastboot writesecureflag 3" ?

MICH_** said:
I made the bootloader to show "locked" and flashed the stock recovery!
How to get s-on now?
Click to expand...
Click to collapse
fastboot oem writesecureflag 3
it will be S-ON

raghav kapur said:
Well, it depends. Usually, HTC will only check for the TAMPERED flag and the bootloader status. But sometimes, they may have a problem with the phone being S-OFF.
I S-ON'ed my phone before giving it for warranty repair.
Anyways, whether u will S-ON the phone or not, ill tell u how to S-ON.
Put the phone in fastboot mode. On ur PC, open command prompt and type:
fastboot oem writesecureflag 3
Then, do what the screen shows
HOWEVER, DO NOT S-ON UR PHONE IF HBOOT IS 1.55 OR ABOVE. THE TAMPERED LOGO WILL RE-APPEAR
Click to expand...
Click to collapse
I am on hboot 1.55... so no chace for s-on?

MICH_** said:
okay, i will try to get s-on. But how to do so? Does it work by just typing "fastboot writesecureflag 3" ?
Click to expand...
Click to collapse
Post the output after typing in that command. I don't remember TBH. But I will once u post the output
---------- Post added at 05:41 PM ---------- Previous post was at 05:40 PM ----------
MICH_** said:
I am on hboot 1.55... so no chace for s-on?
Click to expand...
Click to collapse
Downgrade to 1.44. You can do so because ur S-OFF. Then type in that command to S-OFF
If u do it on 1.55, TAMPERED will re-appear and there will be no warranty

raghav kapur said:
Post the output after typing in that command. I don't remember TBH. But I will once u post the output
---------- Post added at 05:41 PM ---------- Previous post was at 05:40 PM ----------
Downgrade to 1.44. You can do so because ur S-OFF. Then type in that command to S-OFF
If u do it on 1.55, TAMPERED will re-appear and there will be no warranty
Click to expand...
Click to collapse
How to downgrade?

MICH_** said:
How to downgrade?
Click to expand...
Click to collapse
Download this:
https://mega.co.nz/#!ORtGHIqT!qp1EZFa7jidXxO4DXhhdsiLL8SbDSA1FNJfoz9DgpIo
in bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <---- just in case the above said “failed flush again”
fastboot reboot-bootloader
--> and confirm hboot is now 1.44

raghav kapur said:
Download this:
https://mega.co.nz/#!ORtGHIqT!qp1EZFa7jidXxO4DXhhdsiLL8SbDSA1FNJfoz9DgpIo
in bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <---- just in case the above said “failed flush again”
fastboot reboot-bootloader
--> and confirm hboot is now 1.44
Click to expand...
Click to collapse
Does the phone reboot after "fastboot oem rebootRUU" ?
the version is 1.29.401.12 but 2.24.111.3 is running on my phone. Does this matter?

edit android-info.txt to meet your phone CID & MID

moha_moha20106 said:
edit android-info.txt to meet your phone CID & MID
Click to expand...
Click to collapse
which lines should i change?
My CID is: T-MOB101
{
"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"
}

MICH_** said:
which lines should i change?
My CID is: T-MOB101
View attachment 2662502
Click to expand...
Click to collapse
Don't change. Just add ur cidnum

raghav kapur said:
Don't change. Just add ur cidnum
Click to expand...
Click to collapse
So just add cidnum: T-MOB101 ?
And mainver shoud stay the same?