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.
Related
Hello fellow Wildfire owners ,
HTC have released their official bootloader unlocking tool for some more HTC devices, and among them is the Wildfire. I'm not 100% sure what the advantages or disadvantages are to using a tool like Revolutionary, but it is worth a look. To use it you will need a HTC dev account.
Check it out here.
I've been wondering about this tool after reading the HTC dev site warning about warranties being void and not being able to go back after using the unlock tool. As it stands atm I can just flash hboot to go back to s-on and stock whenever I like but does anyone know if this is the case with the tool and bootloader update HTC supplies?
Or am I just being paranoid? It doesn't affect me as I'm already unlocked but I'd hate to see people get screwed over and find out they've locked something else which means you can't downgrade and s-on again, kinda like with the froyo update.
Sent from my HTC Wildfire using xda premium
Gonna check it out.
Because I already used AlphaRevX, I'll check it up to the actual unlocking part.
---------- Post added at 10:39 PM ---------- Previous post was at 10:13 PM ----------
Here we go, some screen shots
First I get to know that this voids my warranty.
{
"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"
}
Then they tell you that you need to flash a RUU. (If they're stock, good for getting the right ruu for un-rooting! They're probably country specific, since you need to specify your country when registering.)
Step 1-4: USB Fastboot
Step 5-7 Getting ADB and Fastboot then navigating there with cd (skipped that part, because most of us knows how to start up cmd and use the cd command )
Step 8-10: Getting a unique ID token.
After this you should get the tool via e-mail.
Hello, I have HBoot-0-80-007 and my wildfire rooted with the unrevocked method, using this bootloader unlock will I be able to S-Off my terminal or I wiould need to change the H-Boot anyway?
Is there any manual to get S-Off on a Wildfire with HBoot 0.8?
Thank you.
shakeador said:
Hello, I have HBoot-0-80-007 and my wildfire rooted with the unrevocked method, using this bootloader unlock will I be able to S-Off my terminal or I wiould need to change the H-Boot anyway?
Is there any manual to get S-Off on a Wildfire with HBoot 0.8?
Thank you.
Click to expand...
Click to collapse
to use alpharev you must have hboot 1.001. so you must update hboot attention you mustn't update to hboot 1.002
Whichever way you choose to unlock you'll need to upgrade hboot. See here point 5 I think.
http://forum.xda-developers.com/showthread.php?t=1029318
This should get you ready to use revolutionary to unlock, if however you choose the HTC tool I presume it will unlock the phone so you can flash a new Rom but the radio and sim lock will still be locked.
From the looks of it so far I would go with revolutionary for now as that is tried and tested but the HTC tool is still new and I don't think anyone has posted of a successful unlock with it yet.
Edit: as the ninja said don't update to the latest hboot or else you'll need to downgrade again.
Sent from my HTC Wildfire using xda premium
shakeador said:
Hello, I have HBoot-0-80-007 and my wildfire rooted with the unrevocked method, using this bootloader unlock will I be able to S-Off my terminal or I wiould need to change the H-Boot anyway?
Is there any manual to get S-Off on a Wildfire with HBoot 0.8?
Thank you.
Click to expand...
Click to collapse
In my opinion, if you want S-OFF, do it with revolutionary as HTCDev doesn't unlock the radio.
To do this you will need to first flash this RUU: here. Then run Revolutionary
Scratch0805 said:
Edit: as the ninja said don't update to the latest hboot or else you'll need to downgrade again.
Click to expand...
Click to collapse
Ninja? I'm a ninja?
lol....because you beat me to answering the question.
Sent from my HTC Wildfire using xda premium
scratch0805 said:
lol....because you beat me to answering the question.
sent from my htc wildfire using xda premium
Click to expand...
Click to collapse
mega looool
Thank you al!!!!
Definitely not an offer to unlock bootloadera the official way that will offer from HTC. The main reason for this is that each authorized service account has specialized in information system of the HTC. If you send information to the identification code of smarttfona until HTC, which is obviously necessary to get the code to unlock the bootloader-a, then this information will have access and any authorized service. So easy, can be determined whether the service was unlocked smartphone, and according to the above quotation is accordingly limited or void warranty!
Unlocking procedure, which resembles that offered by AlphaRev a Revolutionary.
If informal way also allows you to unlock (although theoretically still would void the warranty), at least not openly declare it to HTC. And you can return the state of his phone to factory state!
jacktyler1807 said:
In my opinion, if you want S-OFF, do it with revolutionary as HTCDev doesn't unlock the radio.
Click to expand...
Click to collapse
Right, give one reason why the htc unlocking tool should be used?
Quotes from HTCdev:
Security is left on to protect things like the radio, and SIM lock.
HTC eagerly anticipates your innovations.
Click to expand...
Click to collapse
Bit late isn't it?
I successfully unlocked my bootloader with the HTCDev Tool (after getting S-ON again, of course) and so far, so good. Though I have no root on the stock ROM, even with Superuser. Maybe I'll have to flash a custom ROM, but has anybody got an idea on how to get SU on the stock ROM?
Sent from my HTC Wildfire using XDA App
Is it like AlphaRevX/rEVOlutionary?
As for SU on stock, try flashing a su package in a recovery.
http://androidsu.com/superuser/
Bootloader says UNLOCKED, but still S-ON. Weird.
Will try flashing CWM later.
Sent from my HTC Wildfire using XDA App
I really don't know why you bother with official unlock when revolutionary works just fine...
cheers
pl0ppy said:
Bootloader says UNLOCKED, but still S-ON. Weird.
Will try flashing CWM later.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Is the hboot version number any different, I presume you can use fastboot to flash cwm or PC49IMG maybe.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
Is the hboot version number any different, I presume you can use fastboot to flash cwm or PC49IMG maybe.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Yep, new HBOOT! I had 1.01.1001 before, now I have 1.02.0000. If flashing a recovery from fastboot doesn't work, then I am screwed, right?
pl0ppy said:
Yep, new HBOOT! I had 1.01.1001 before, now I have 1.02.0000. If flashing a recovery from fastboot doesn't work, then I am screwed, right?
Click to expand...
Click to collapse
You should be able to root with Gingerbreak as the Security is off. Once you've done that, you should be able to use ROM Manager/ Root Toolbox to flash a recovery
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
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
Hi and sorry if I am misplacing this question.
I have been trying for hours to get my phone to "S-Off" without any luck.
I have gone over 10-15 different tutorials but none of them work.
Htc One
HBoot 1.55
Anyone who knows a proper guide to the entire unlock/root/s-off procedure?
I can't watch the youtube tutorial due to youtube lag.
Have you tried this tutorial:
http://forum.xda-developers.com/showthread.php?t=2488772
And if so, what errors did you get?
alireza_simkesh said:
Have you tried this tutorial:
http://forum.xda-developers.com/showthread.php?t=2488772
And if so, what errors did you get?
Click to expand...
Click to collapse
Tried this just now (did this a couple of times earlier today aswell) and not much happening.
There is a screenshot attached.
benjamin336 said:
Tried this just now (did this a couple of times earlier today aswell) and not much happening.
There is a screenshot attached.
Click to expand...
Click to collapse
I used to get the same error.
I restarted my laptop (and didn't open or use anything else but just ran the script) and the problem was solved.
Apparently, there was another application that was using adb in the background and was not killed, so after restarting my laptop i didn't get this error anymore.
alireza_simkesh said:
I used to get the same error.
I restarted my laptop (and didn't open or use anything else but just ran the script) and the problem was solved.
Apparently, there was another application that was using adb in the background and was not killed, so after restarting my laptop i didn't get this error anymore.
Click to expand...
Click to collapse
Did this and came further though now it tells me to download a newer version even though I have the latest one.
Am I missing something?
benjamin336 said:
Did this and came further though now it tells me to download a newer version even though I have the latest one.
Am I missing something?
Click to expand...
Click to collapse
Hmm not quite sure, but can you write all the information shown on your bootloader?
Make sure you keep the screen alive during the process and hit allow when super user permissions are requested.
Same happened to me, because i let the screen turn off and rum runner couldnt get su.
AlwaysDroid said:
Make sure you keep the screen alive during the process and hit allow when super user permissions are requested.
Same happened to me, because i let the screen turn off and rum runner couldnt get su.
Click to expand...
Click to collapse
Placed autosleep to 30 min, watched the screen carefully and saw that SU was granted twice.
Same message came up again.
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1
eMMC-boot 2048MB
Oct 17 2013,23:06:14.0
That's all the info in bootloader.
Love how they define this as "tampered", in my opinion this is for the better not worse
Any thoughts anyone?
Tried at work today and got the following messages up, does anyone have a clue what this is about?
{
"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"
}
Any news on this matter?
This stock sense rom is killing me...
Sent from my HTC One using xda app-developers app
which ROM/Kernel are you running? I find it works best if you flash a stock 4.1.2 ROM and the kernel included with moonshine.
I had the same problem with hboot v1.55
after a sleepless night i was able to do s-off
but..... don't really know how i did it: D
iiNFAMOUS CHRiS said:
which ROM/Kernel are you running? I find it works best if you flash a stock 4.1.2 ROM and the kernel included with moonshine.
Click to expand...
Click to collapse
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1
eMMC-boot 2048MB
Oct 17 2013,23:06:14.0
This is what I have.
I have been trying every god damn instruction out there and every one-in-all toolkits, it just wont work...I really hate this phone. Id rather use my HOX though the battery life is equal to a 90 year old guy sexlife...
/dev/null/ said:
I had the same problem with hboot v1.55
after a sleepless night i was able to do s-off
but..... don't really know how i did it: D
Click to expand...
Click to collapse
How would you concider another sleepless night just to figure out how you did it?
You know Red Bull give you wings!
Windows 8.1?
benjamin336 said:
How would you concider another sleepless night just to figure out how you did it?
You know Red Bull give you wings!
Click to expand...
Click to collapse
Dude, rumrunner on Ubuntu Live USB: http://forum.xda-developers.com/showthread.php?t=2606577
(no need to install, just use the "Try Ubuntu")
here's a practical result: http://forum.xda-developers.com/showpost.php?p=49673069&postcount=46 (check the summary of what was used)
nkk71 said:
Dude, rumrunner on Ubuntu Live USB: http://forum.xda-developers.com/showthread.php?t=2606577
(no need to install, just use the "Try Ubuntu")
here's a practical result: http://forum.xda-developers.com/showpost.php?p=49673069&postcount=46 (check the summary of what was used)
Click to expand...
Click to collapse
I simply dont understand how Ubuntu works, I cant get any of the commands to work from the terminal.
Extract the archive
tar -zxf rumrunner<device>_<version>.tgz (Linux)
Click to expand...
Click to collapse
Nothing happens, though I can easily extract it within the folder without using the terminal.
Execute soju: linux: sudo ./soju
Click to expand...
Click to collapse
./soju: No such file or directory
Is there a guide for Linux dummies somwhere?
@ kamilmirza, I use Windows 7. [well normally, now I am on Ubuntu]
benjamin336 said:
Any news on this matter?
This stock sense rom is killing me...
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I've chosen an old post to quote, but you do know you don't need to be s-off to flash a custom rom don't you?
cr1960 said:
I've chosen an old post to quote, but you do know you don't need to be s-off to flash a custom rom don't you?
Click to expand...
Click to collapse
I have tried to flash MIUI but whenever I start the installation it tells me it cant get access to the right directory.
Isnt this what S-Off grants you?
*Sorry for the sloppy english but Ubuntu has a completely different keyboard layout at the moment then what I am used to*
Hi to all!!! :laugh:
Sorry if this was posted previously somewhere here...but i'm wondering trying to find a definitive answer to this...
I'm coming back to an HTC One (new, not used), so is there the possibility to have the S-OFF without get in touch with HTCdev with the latest H-BOOT version?
Please excuse me if this already exists here...but I just couldn't found a definitive answer...
Thanks in advance to everyone will post an help! :good:
--anx-- said:
Hi to all!!! :laugh:
Sorry if this was posted previously somewhere here...but i'm wondering trying to find a definitive answer to this...
I'm coming back to an HTC One (new, not used), so is there the possibility to have the S-OFF without get in touch with HTCdev with the latest H-BOOT version?
Please excuse me if this already exists here...but I just couldn't found a definitive answer...
Thanks in advance to everyone will post an help! :good:
Click to expand...
Click to collapse
1- There's no such thing as a definitive answer, because nobody can say that you will get S-Off even with unlocked (HTCdev) bootloader
2- there's no such thing as "latest hboot", that's why version numbers exist... "latest" (as far as i'm aware of) at the time of this writing is hboot 1.57
anyway, to answer your question:
3- you can try http://firewater-soff.com/ using the temproot exploit, but if it doesn't work, then i guess the answer would be no;
there's also WeakSauce temproot, which may or may not work also.
nkk71 said:
1- There's no such thing as a definitive answer, because nobody can say that you will get S-Off even with unlocked (HTCdev) bootloader
2- there's no such thing as "latest hboot", that's why version numbers exist... "latest" (as far as i'm aware of) at the time of this writing is hboot 1.57
anyway, to answer your question:
3- you can try http://firewater-soff.com/ using the temproot exploit, but if it doesn't work, then i guess the answer would be no;
there's also WeakSauce temproot, which may or may not work also.
Click to expand...
Click to collapse
Wow...to get a reply from an Android Revolution team member it's really perfect!!! :highfive:
I'll have to try the first option then the second and follow the instructions wrote down there right? But in all the two cases I'll have to request the HTCdev token I'm afraid... :crying:
I just have planned to install the Android Revolution with the last Sense 6 right after unboxing the brand new phone...
--anx-- said:
Wow...to get a reply from an Android Revolution team member it's really perfect!!! :highfive:
I'll have to try the first option then the second and follow the instructions wrote down there right? But in all the two cases I'll have to request the HTCdev token I'm afraid... :crying:
I just have planned to install the Android Revolution with the last Sense 6 right after unboxing the brand new phone...
Click to expand...
Click to collapse
Why so worried about HTCdev?
Anyway, you can give the temproot exploits a try; maybe you'll be one of the lucky ones and it/they work for you.... if not then you'll need to unlock using HTCdev
nkk71 said:
Why so worried about HTCdev?
Anyway, you can give the temproot exploits a try; maybe you'll be one of the lucky ones and it/they work for you.... if not then you'll need to unlock using HTCdev
Click to expand...
Click to collapse
Well...the only thing that annoy me about HTCdev it's the fact that they'll know that you've unlocked the phone and can bother you if you'll send the phone to them in case of need of assistance...even if it had hardware faults...that's the only thing...
--anx-- said:
Well...the only thing that annoy me about HTCdev it's the fact that they'll know that you've unlocked the phone and can bother you if you'll send the phone to them in case of need of assistance...even if it had hardware faults...that's the only thing...
Click to expand...
Click to collapse
well,
1- plenty of guides around to returning 100% to stock (including mine )
2- just because you used HTCdev, can they actually prove you used the unlock code? maybe you requested one, and then got scared and didn't use it after all... how can they prove you unlocked your device just because you asked for a code?
nkk71 said:
well,
1- plenty of guides around to returning 100% to stock (including mine )
2- just because you used HTCdev, can they actually prove you used the unlock code? maybe you requested one, and then got scared and didn't use it after all... how can they prove you unlocked your device just because you asked for a code?
Click to expand...
Click to collapse
Oh...so, even if I'm S-ON I can return 100% back to stock? tampered signature deletion included?
Excuse me again, but I've left for too much time HTC One development, my fault....
--anx-- said:
Oh...so, even if I'm S-ON I can return 100% back to stock? tampered signature deletion included?
Excuse me again, but I've left for too much time HTC One development, my fault....
Click to expand...
Click to collapse
with S-On, you can only set it back to RELOCKED not LOCKED, so you still need S-Off for that, the problem isn't HTCdev, the problem is whether S-Off is going to work or not, very likely yes, but there have been a lot of "unable to get S-Off" threads recently.
nkk71 said:
with S-On, you can only set it back to RELOCKED not LOCKED, so you still need S-Off for that, the problem isn't HTCdev, the problem is whether S-Off is going to work or not, very likely yes, but there have been a lot of "unable to get S-Off" threads recently.
Click to expand...
Click to collapse
So there's a possibility of that problem...but generally the trick have to work in most of the cases I've read...
But in order to gain S-OFF you still have to unlock the phone via HTCdev and then try the trick...if I'm not wrong at least...
--anx-- said:
So there's a possibility of that problem...but generally the trick have to work in most of the cases I've read...
But in order to gain S-OFF you still have to unlock the phone via HTCdev and then try the trick...if I'm not wrong at least...
Click to expand...
Click to collapse
Hopefully it will work, but you can try the temproot exploit method first, it's very likely to fail on newer ROMs, but you can try!!
from firewater method 2:
{
"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"
}
nkk71 said:
Hopefully it will work, but you can try the temproot exploit method first, it's very likely to fail on newer ROMs, but you can try!!
from firewater method 2:
Click to expand...
Click to collapse
Wow! So before the real unlock bis via HTCdev I can try this temp root and see if this work to gain the S-OFF prior to act with HTCdev usual method...
Seems really good...hope it will work...
When I'll receive the phone I'll try these steps as you suggested: first try with temp root method...if this didn't work I'll have to go with HTCdev and after that try one of those methods to gain S-OFF...hoping that them will work...
I'm on the right wave?
--anx-- said:
Wow! So before the real unlock bis via HTCdev I can try this temp root and see if this work to gain the S-OFF prior to act with HTCdev usual method...
Seems really good...hope it will work...
When I'll receive the phone I'll try these steps as you suggested: first try with temp root method...if this didn't work I'll have to go with HTCdev and after that try one of those methods to gain S-OFF...hoping that them will work...
I'm on the right wave?
Click to expand...
Click to collapse
lol
"]When I'll receive the phone"... maybe the phone will come S-Off, or on hboot 1.44, etc.
so first get the phone, do a "fastboot getvar all" and then you can see which method will/should work for you (revone, rumrunner, firewater, weaksauce)
nkk71 said:
lol
"]When I'll receive the phone"... maybe the phone will come S-Off, or on hboot 1.44, etc.
so first get the phone, do a "fastboot getvar all" and then you can see which method will/should work for you (revone, rumrunner, firewater, weaksauce)
Click to expand...
Click to collapse
Why "fastboot getvar all" and not a simple boot into recovery to see the actual hboot version?
I'm just keeping myself "ready" for the big one...
--anx-- said:
Why "fastboot getvar all" and not a simple boot into recovery to see the actual hboot version?
I'm just keeping myself "ready" for the big one...
Click to expand...
Click to collapse
same difference
fastboot getvar all won't harm your phone, but you could keep it as a record.
and you are right bootloader will give you 1 piece of information that the getvar won't ... the date of hboot (only significant if it's hboot 1.44)
oh and the big One, is the M8, the M7 is a bit smaller
nkk71 said:
same difference
fastboot getvar all won't harm your phone, but you could keep it as a record.
and you are right bootloader will give you 1 piece of information that the getvar won't ... the date of hboot (only significant if it's hboot 1.44)
oh and the big One, is the M8, the M7 is a bit smaller
Click to expand...
Click to collapse
So I can go into fastboot like very other phone an see the hboot version if it's good for s-off or I can use the getvar all command in equal...
Well you're right anyway...the Big One it's the M8...but a phone that keeps itself actual and still rockin after one year out...well...it's big too...
--anx-- said:
So I can go into fastboot like very other phone an see the hboot version if it's good for s-off or I can use the getvar all command in equal...
Well you're right anyway...the Big One it's the M8...but a phone that keeps itself actual and still rockin after one year out...well...it's big too...
Click to expand...
Click to collapse
I have the One just here!
The HBOOT is 1.56.0000, with RADIO-4A.25.3263.21, date Feb 26 2014...with Android 4.4.2 and Sense 5.5...
I still can try the S-OFF procedure with these parameters???
--anx-- said:
I have the One just here!
The HBOOT is 1.56.0000, with RADIO-4A.25.3263.21, date Feb 26 2014...with Android 4.4.2 and Sense 5.5...
I still can try the S-OFF procedure with these parameters???
Click to expand...
Click to collapse
It's highly unlikely the temproot exploits will work (so you'll have to unlock using HTCdev), but:
to be perfectly honest, I think you're jumping the gun a little with S-Off. I think you should do some more research into the M7, because the information you provided sounds like you're quite new this phone.
I can more or less guess, what ROM and firmware you have, but maybe you should first understand the differences between ROM, firmware, radio, kernel, etc.
and where you get that information and using which tools.
Also take a look at Do we really need S-OFF?
I'm not trying to be say you shouldn't get S-Off, but all in good time, once you are familiar with it and what it allows you to do.
nkk71 said:
It's highly unlikely the temproot exploits will work (so you'll have to unlock using HTCdev), but:
to be perfectly honest, I think you're jumping the gun a little with S-Off. I think you should do some more research into the M7, because the information you provided sounds like you're quite new this phone.
Click to expand...
Click to collapse
Honestly yes, I've already had the One in last year's July, but never unlocked it...only stock since I've sold it...so I've never get deep into modifications, rom, tools etcetera...
nkk71 said:
I can more or less guess, what ROM and firmware you have, but maybe you should first understand the differences between ROM, firmware, radio, kernel, etc.
and where you get that information and using which tools.
Also take a look at Do we really need S-OFF?
I'm not trying to be say you shouldn't get S-Off, but all in good time, once you are familiar with it and what it allows you to do.
Click to expand...
Click to collapse
If HTC don't let the HARDWARE warranty die or make it complicated with unlocking the phone, I'd probably unlocked the phone in 0 time since unboxing the phone, via HTCdev...but the fact that the warranty will be a trivia (even with hardware faults...) with the "tampered" and "relocked" question...well...I'm really afraid to let "the rom game" begin like I've done with almost all the phones that I've had...in fact now I know ADB, Fastboot, push commands via Terminal (MacOs) like the palm of my hand... :laugh:
--anx-- said:
Honestly yes, I've already had the One in last year's July, but never unlocked it...only stock since I've sold it...so I've never get deep into modifications, rom, tools etcetera...
If HTC don't let the HARDWARE warranty die or make it complicated with unlocking the phone, I'd probably unlocked the phone in 0 time since unboxing the phone, via HTCdev...but the fact that the warranty will be a trivia (even with hardware faults...) with the "tampered" and "relocked" question...well...I'm really afraid to let "the rom game" begin like I've done with almost all the phones that I've had...in fact now I know ADB, Fastboot, push commands via Terminal (MacOs) like the palm of my hand... :laugh:
Click to expand...
Click to collapse
fair enough, but what I meant before:
1- ROM is usually found in Settings->About
2- firmware is what you get from a fastboot getvar all
3- Android version is irrelevant as we're more interested in the base
4- radio doesn't matter, cause you can flash any radio you want (even with S-On) on the M7
you can go ahead and try the temproot exploits, but I doubt that they will work on a 4.xx ROM.... so you will have no choice but to use HTCdev to unlock... and again, how can they prove you actually used the code, not just asked for one, and then got scared
and even if you don't get S-Off, you can still install a custom recovery (TWRP 2.6.3.3+ preferred at the moment), and install a custom ROM.
nkk71 said:
fair enough, but what I meant before:
1- ROM is usually found in Settings->About
2- firmware is what you get from a fastboot getvar all
3- Android version is irrelevant as we're more interested in the base
4- radio doesn't matter, cause you can flash any radio you want (even with S-On) on the M7
you can go ahead and try the temproot exploits, but I doubt that they will work on a 4.xx ROM
Click to expand...
Click to collapse
Yes, got it...and I've checked but I've noticed that 4.4.2 isn't supported for the temproot, only 4.3...sadly...
nkk71 said:
.... so you will have no choice but to use HTCdev to unlock... and again, how can they prove you actually used the code, not just asked for one, and then got scared
and even if you don't get S-Off, you can still install a custom recovery (TWRP 2.6.3.3+ preferred at the moment), and install a custom ROM.
Click to expand...
Click to collapse
Yes, with S-ON pratically I can do everything, I've done that before on my old HTC ONE S some months ago, I remember it...but...HTC can recognize the unlocking because I'll have the "TAMPERED" and "RELOCKED" signatures in fastboot...so they can prove that I've used the token...while with S-OFF you can restore these signatures back to "stock" totally...like you've never used that token...
This is the only hassle...