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

hboot 1.56 S-OFF

hboot 1.56
i am stuck here
my htc one information as foillowing ,,, i want S-OFF , but with the hboot 1.56. can i S-OFF ? with what method thanks
Device: HTC ONE
Android: 4.4
ROM: Android Revolution HD 40.3
Kernel: 3.4.10
Firmware: 4.06.1540.2
Radio: 4A.22.3263.14
HBoot: 1.56.0000

Use the rumrunner exploit, it should work...

Guich said:
Use the rumrunner exploit, it should work...
Click to expand...
Click to collapse
but rumrunner did not said will support hboot 1.56. i am aftraid will brick the phone if i use rumrunner

I used rumrunner and am HBOOT 1.56 and it not work, I get this error message each time:
Waiting for ADB (35/120)
Waiting for device
it's a little stinky here, hmm ....
bottles are packed, here we go, shhhhhh ....
Unfortunately This Is not going to work out with your configuration. you have 2
options:
1.) Flash an unsecure kernel that's consistent with your ROM and retry rumrunner
(MOST reliable and preferred method).
2.) Flash rom different.
NOTE: No Amount of messing around with su binaries and apk's is going to fix thi
s end for you!.
Better luck next time!! Bye
Press ENTER to exit

will you brick if S-OFF failed ?
are you able to get it s off with your htc one ? or with my current configuration ?
zincou said:
I used rumrunner and am HBOOT 1.56 and it not work, I get this error message each time:
Waiting for ADB (35/120)
Waiting for device
it's a little stinky here, hmm ....
bottles are packed, here we go, shhhhhh ....
Unfortunately This Is not going to work out with your configuration. you have 2
options:
1.) Flash an unsecure kernel that's consistent with your ROM and retry rumrunner
(MOST reliable and preferred method).
2.) Flash rom different.
NOTE: No Amount of messing around with su binaries and apk's is going to fix thi
s end for you!.
Better luck next time!! Bye
Press ENTER to exit
Click to expand...
Click to collapse

me it is not bricked

zincou said:
I used rumrunner and am HBOOT 1.56 and it not work, I get this error message each time:
Waiting for ADB (35/120)
Waiting for device
it's a little stinky here, hmm ....
bottles are packed, here we go, shhhhhh ....
Unfortunately This Is not going to work out with your configuration. you have 2
options:
1.) Flash an unsecure kernel that's consistent with your ROM and retry rumrunner
(MOST reliable and preferred method).
2.) Flash rom different.
NOTE: No Amount of messing around with su binaries and apk's is going to fix thi
s end for you!.
Better luck next time!! Bye
Press ENTER to exit
Click to expand...
Click to collapse
Exact same problem here. Running HTC one Dev edition Hboot1.56

zincou said:
you have 2
options:
1.) Flash an unsecure kernel that's consistent with your ROM and retry rumrunner
(MOST reliable and preferred method).
2.) Flash rom different.
Click to expand...
Click to collapse
Well you have 2 options. But seriously, you need to follow the instructions. The "insecure kernel" is a kernel with some of the security checks disabled. I don't know which kernels will do what you need, so I would just install a custom ROM and then try rumrunner again.

I'll wait for an update of RumRunner with support for HBOOT 1.56 and 4.4 ROM

Same here!

zincou said:
I used rumrunner and am HBOOT 1.56 and it not work, I get this error message each time:
Waiting for ADB (35/120)
Waiting for device
it's a little stinky here, hmm ....
bottles are packed, here we go, shhhhhh ....
Unfortunately This Is not going to work out with your configuration. you have 2
options:
1.) Flash an unsecure kernel that's consistent with your ROM and retry rumrunner
(MOST reliable and preferred method).
2.) Flash rom different.
NOTE: No Amount of messing around with su binaries and apk's is going to fix thi
s end for you!.
Better luck next time!! Bye
Press ENTER to exit
Click to expand...
Click to collapse
fujisan582 said:
Exact same problem here. Running HTC one Dev edition Hboot1.56
Click to expand...
Click to collapse
try ARHD 40.3, it's Sense, it's rooted, and kernel is w/p disabled.

nkk71 said:
try ARHD 40.3, it's Sense, it's rooted, and kernel is w/p disabled.
Click to expand...
Click to collapse
Rumrunner works even on 1.56
Unlock your bootloader if not.
Install TWRP recovery
Install ARHD 40.3
When done then try Rumrunner again. Remember to disable fastboot and powersave mode and no lockscreen at all

Updated to ARHD 40.3, still can't s-off. Gets to pouring then I get WTF what are you doing and phone reboots

nkk71 said:
try ARHD 40.3, it's Sense, it's rooted, and kernel is w/p disabled.
Click to expand...
Click to collapse
Hi there I upgraded new OTA rom and my hboot changed from 1.44 to 1.56. (still S-ON) then I did rumrunner and got the same problem as you guys. Then i flashed with Android Revolution HD 41, wipe everything except sdcard. then I tried again and it works. still stinky but then it start pouring 3 times and DONE now it's S-OFF haha.
If you got it work please donate to them, I did already . Thank so much guys

HBOOT 1.56 success
rumrunner, run on Ubuntu 32, works in a snap.
I tried over and over on Win 7, with no success. The process took less than 10 minutes on Ubuntu.
I logged in as root, and extracted the rumrunner in the same directory as the adb tools. I made sure that $PATH included the adb tools directory.
Then I watched as the rum brewed.
Many thanks, developers.

Hmm unlocking bootloader is losing guarantee right ??
If yes then I prever a s-off method without unlocking bootloader (but yeah there are no methodes yet)

IT Works!!! with [ROM] Android Revolution HD 41.0 & 31.6
wasdvd said:
rumrunner, run on Ubuntu 32, works in a snap.
I tried over and over on Win 7, with no success. The process took less than 10 minutes on Ubuntu.
I logged in as root, and extracted the rumrunner in the same directory as the adb tools. I made sure that $PATH included the adb tools directory.
Then I watched as the rum brewed.
Many thanks, developers.
Click to expand...
Click to collapse
Rumrummer just dont like the OEM rom, once i used AR HD, (i have hboot 1.56) it completed and now is S-OFF
thanks so much everyone

rogersmithjr said:
Rumrummer just dont like the OEM rom, once i used AR HD, (i have hboot 1.56) it completed and now is S-OFF
thanks so much everyone
Click to expand...
Click to collapse
i used ARHD 41.0 not s-off :crying::crying:..pls.
{
"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"
}

viperone 4.4
Hello guys
I have unlocked version of m7 with unlocked boot loader & hboot 1.56 running viperone 4.4 Rom can I get s-off with rumrunner ?

fujisan582 said:
Exact same problem here. Running HTC one Dev edition Hboot1.56
Click to expand...
Click to collapse
Guys!! I'm finally S-off. Rumrunner worked with Hboot 1.56; I was running a stock rom, you need to install a custom rom (Android Revolution 31.6) for it to work. At least that's what did the trick for me.
Cheers!

i want to install cyanogen 12.1 on my s-on bootloader unlocked htc incredible s

hey guys thanks for all your helps
{
"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"
}
i flashed teamwin custom recovery by command prompt on my device and flashed a stock rom on it i recently downloaded cyanogenmod 7.2 and flashed it on my device but the problem is the android version is too low then i decided to download a cyanogenmod 12.1 based on lollipop android version and flash it on my device then i extracted the zip file flashed its boot.img on my device and when i entered custom recovery mode to flash the zip file it just fails i tried several times but still the same i'm kinda disappointed please someone tell me how can i at least update my android version to at least 4.4.4 kitkat or 5 or 5.1 lollipop i really want to try new features and new android games that only support android version 4.2 and higher thanks in advance

Have you installed one of these recoveries? http://forum.xda-developers.com/htc...ment/recovery-twrp-2-8-7-0-cwm-touch-t3143957

vuvkar said:
Have you installed one of these recoveries? http://forum.xda-developers.com/htc...ment/recovery-twrp-2-8-7-0-cwm-touch-t3143957
Click to expand...
Click to collapse
hey, do you mean the famous teamwin and clockworkmod custom recoveries? if yes i tried both of them but i chose teamwin cause i like its user interface i told in my subject section that i have an unlocked bootloader and s-on do you think s-on status prevents me to flash cyanogenmod on my device? my original factory rom software number is 4.14.415.1 and it's an arabic one and i have hboot 2.02.0002 and i have radio 3831.18.00.11-m any suggestions would be appreciated

The thing is that you must install twrp from that post. If you have the twrp by szezso and it fails installing, then you must be s-off

thanks man i could finally flash a custom kitkat cyanogenmod using TWRP_2.8.7.0_vivo.img now my android version is 4.4.4 but i still want to install the 12.1 lollipop version using this custom recovery i mentioned but it fails any suggestions?

Sorry dude, this is the problem of S-Off I think. I was looking through internet for revolutionary alternatives, but couldn't find exact information, maybe I can help if you if you say what error does the recovery show.

after several attempts i could finally install cyanogenmod 12.1 lollipop on my device that's good and yeah i was looking for ways to s-off my device but revolutionary and firewater doesn't exist anymore and seems there's just 25 $ amazon gift card sunshine method but i keep searching let me know please if you got any free working method thanks man

rev.alpharev.nl
jason405 said:
i was looking for ways to s-off my device but revolutionary and firewater doesn't exist anymore
Click to expand...
Click to collapse
Its here:
Revolutionary

ze7zez said:
Its here:
Revolutionary
Click to expand...
Click to collapse
thanks man you're a life saver i thought revolutionary site is down for good that's good news thanks now i have the beta key for both hboots 1.09.0000 and 1.13.0000 but the problem is revolutionary program seems can't detect my device cause my hboot is 2.02.0002 can you tell me how can i downgrade my hboot to at least 1.13.0000 or 1.09.0000 much appreciated

LOCK S-ON -> UNLOCK S-ON -> BlackRose S-OFF -> Revolutionary S_OFF
jason405 said:
thanks man you're a life saver i thought revolutionary site is down for good that's good news thanks now i have the beta key for both hboots 1.09.0000 and 1.13.0000 but the problem is revolutionary program seems can't detect my device cause my hboot is 2.02.0002 can you tell me how can i downgrade my hboot to at least 1.13.0000 or 1.09.0000 much appreciated
Click to expand...
Click to collapse
Everything is described in the forum.
My path was:
1. Initial state
Code:
*** LOCKED ***
VIVO PVT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.18.00.11_M
eMMC-BOOT
May 22 2012,14:22:00
2. HTCDEV unlock
3. BlackRose
Code:
*** BlackRose ***
VIVO PVT SHIP S-OFF RL
HBOOT-2.03.0000
RADIO-3805.06.03.03_M
eMMC-BOOT
Fab 03 2013,04:40:53
4. @Nonverbose method with this post
Code:
dd if=/sdcard/revhboot.img of=/dev/block/mmcblk0p18
5. Flash a new Modem
6. The final state
Code:
--Revolutionary--
VIVO PVT SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-3831.19.00.19_M
eMMC-BOOT
Apr 1 2011,18:34:39
You can also try another method of @Nonverbose :
[TOOL][SCRIPT][05 Sep 2012]S-off for HBOOT 1.16 and above[v3.4.1]

you best man thank thanks thanks very much to all people who helped me to gain s-off using revolutionary tool my bootloader status is now like the final state god gives you anything you want you can't imagine how happy i am to see s-off status after all these efforts and days of searching for different non-working methods thanks again :v now i have 2 questions: 1. can i install any rom or application i want? 2. do i have complete freedom to do anything with my device or do i need supercid 111111? thanks again