[GUIDE] Obtaining S-OFF on Sprint HTC One HBOOT 1.57 - Sprint HTC One (M7)

I had some trouble getting S-OFF using HBOOT 1.57, and I finally got it. Here is what I did in hopes someone may find it useful:
Before you Begin:
If you get stuck at the white HTC Logo when booting or you get "Process com.htc.dialer isn't responding" at any point in this guide, or even before it, you are likely missing your Radio. (I don't know exactly how this happens, but it apparently does sometimes.) I had this problem once, and flashing the latest radio from here in recovery fixed it.
Steps:
Flash this ROM. (Other ROMs may work, but this one gave me no trouble at all)
Flash this Kernel. <-- Important! Firewater will fail if you don't do this!
Follow the Firewater Instructions to obtain S-OFF. It should work the very first time. (Use the "normal, rooted device method" set of instructions.)
You should now be S-OFF! After this, you can proceed to flash your favorite ROMs Kernels, and HBOOTs. If you would like to downgrade to HBOOT 1.44 (I did), you can find the files here.
Please post if this works for you or if you need help. Thanks to all the developers who made this possible!

Thank you very so much
thank you very much you helped me save my htc was like brick but since I got resurrect from your guide

Branchys said:
thank you very much you helped me save my htc was like brick but since I got resurrect from your guide
Click to expand...
Click to collapse
Awesome! Glad I could help.

Question
Pew446 said:
I had some trouble getting S-OFF using HBOOT 1.57, and I finally got it. Here is what I did in hopes someone may find it useful:
Before you Begin:
If you get stuck at the white HTC Logo when booting or you get "Process com.htc.dialer isn't responding" at any point in this guide, or even before it, you are likely missing your Radio. (I don't know exactly how this happens, but it apparently does sometimes.) I had this problem once, and flashing the latest radio from here in recovery fixed it.
Steps:
Flash this ROM. (Other ROMs may work, but this one gave me no trouble at all)
Flash this Kernel. <-- Important! Firewater will fail if you don't do this!
Follow the Firewater Instructions to obtain S-OFF. It should work the very first time. (Use the "normal, rooted device method" set of instructions.)
You should now be S-OFF! After this, you can proceed to flash your favorite ROMs Kernels, and HBOOTs. If you would like to downgrade to HBOOT 1.44 (I did), you can find the files here.
Please post if this works for you or if you need help. Thanks to all the developers who made this possible!
Click to expand...
Click to collapse
Hi, what specific ROM and Kernel version did you use to get Firewater to work? I have flashed rom Bad_Boyz_Sprint_ONE_Sense_6_v1.0 and Kernel ElementalX-sprint-m7-13.1 but USB debugging is not working and Firewater is not working properly, I am guessing its a kernel issue. I leave everything on default while installing Kernel thru TWRP. Can you confirm? I appreciate the help

DanielGalan said:
Hi, what specific ROM and Kernel version did you use to get Firewater to work? I have flashed rom Bad_Boyz_Sprint_ONE_Sense_6_v1.0 and Kernel ElementalX-sprint-m7-13.1 but USB debugging is not working and Firewater is not working properly, I am guessing its a kernel issue. I leave everything on default while installing Kernel thru TWRP. Can you confirm? I appreciate the help
Click to expand...
Click to collapse
Did you check if your fastboot drivers are working?

StormyNight said:
Did you check if your fastboot drivers are working?
Click to expand...
Click to collapse
Yes, I did fastboot devices and I got the device listed there. Although I could see that in the phone it does not appear the 4 bars of USB debugging. I had it checked in the Dev Options. When I do the same with the stock 4.4.2 I do get those 4 bars and the indication that the USB debugging is active.

DanielGalan said:
Yes, I did fastboot devices and I got the device listed there. Although I could see that in the phone it does not appear the 4 bars of USB debugging. I had it checked in the Dev Options. When I do the same with the stock 4.4.2 I do get those 4 bars and the indication that the USB debugging is active.
Click to expand...
Click to collapse
Does fastboot devices work in the bootloader?

StormyNight said:
Does fastboot devices work in the bootloader?
Click to expand...
Click to collapse
Yes it gets recognized. But when I turn on the phone and try to run the firewater commands it does nothing. No error nor the prompt of the disclaimer. I thought I better asked you and see if you have any idea of what could be wrong.

DanielGalan said:
Yes it gets recognized. But when I turn on the phone and try to run the firewater commands it does nothing. No error nor the prompt of the disclaimer. I thought I better asked you and see if you have any idea of what could be wrong.
Click to expand...
Click to collapse
firewater, I believe runs with the phone booted into android, not fastboot.

Aldo101t said:
firewater, I believe runs with the phone booted into android, not fastboot.
Click to expand...
Click to collapse
Yeah. I just booted to fastboot to check the drivers. When I push the firewater file I get success. Its just the last command that does no action.

DanielGalan said:
Yeah. I just booted to fastboot to check the drivers. When I push the firewater file I get success. Its just the last command that does no action.
Click to expand...
Click to collapse
Verify if the file access permissions changed.. it might be that chmod isn't working.

StormyNight said:
Verify if the file access permissions changed.. it might be that chmod isn't working.
Click to expand...
Click to collapse
Hi. I meant adb devices. And I was wondering how do I check the file permissions. Can I try to copy firewater with a root file manager ? Thank you
This is what I get in adb
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
5927 KB/s (4522136 bytes in 0.745s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]:/ #
After this, there is no action from firewater. I should get a warning prompt, but I don't.

DanielGalan said:
Hi. I meant adb devices. And I was wondering how do I check the file permissions. Can I try to copy firewater with a root file manager ? Thank you
This is what I get in adb
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
5927 KB/s (4522136 bytes in 0.745s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]:/ #
After this, there is no action from firewater. I should get a warning prompt, but I don't.
Click to expand...
Click to collapse
Are you doing adb reboot before doing adb wait-for-device? Also make sure that your device has no lock mechanism enabled (pattern lock etc).

StormyNight said:
Are you doing adb reboot before doing adb wait-for-device? Also make sure that your device has no lock mechanism enabled (pattern lock etc).
Click to expand...
Click to collapse
I do, this is what I found weird. Screenshot 1 is stock rom 4.4.2 and it says USB debugging enabled. Screenshot 2&3 is Bad_Boyz_Sprint_ONE_Sense_6_v1.0 ROM with its default kernel, it shows no USB debugging enabled even when its selected

DanielGalan said:
I do, this is what I found weird. Screenshot 1 is stock rom 4.4.2 and it says USB debugging enabled. Screenshot 2&3 is Bad_Boyz_Sprint_ONE_Sense_6_v1.0 ROM with its default kernel, it shows no USB debugging enabled even when its selected
Click to expand...
Click to collapse
No idea :S You might want to uncheck Verify apps over USB in Screenshot 3 btw.

StormyNight said:
No idea :S You might want to uncheck Verify apps over USB in Screenshot 3 btw.
Click to expand...
Click to collapse
I tried but no luck. Is there any other ROM I could try firewater with? I was thinking maybe the Venom.

DanielGalan said:
I tried but no luck. Is there any other ROM I could try firewater with? I was thinking maybe the Venom.
Click to expand...
Click to collapse
Try following the instructions on this post.

StormyNight said:
Try following the instructions on this post.
Click to expand...
Click to collapse
Thank you for bearing with me.
I did as indicated on that post, but still having issues with firewater. This is what I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA34MS906354 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
4533 KB/s (4522136 bytes in 0.974s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
←7←[r←[999;999H←[[email protected]:/ $ su
su
←7←[r←[999;999H←[[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]:/ #
There is no action after this

DanielGalan said:
Thank you for bearing with me.
I did as indicated on that post, but still having issues with firewater. This is what I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA34MS906354 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
4533 KB/s (4522136 bytes in 0.974s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
←7←[r←[999;999H←[[email protected]:/ $ su
su
←7←[r←[999;999H←[[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]:/ #
There is no action after this
Click to expand...
Click to collapse
Try flashing an older release of CyanogenMod - I'd try Snapshot M8.

StormyNight said:
Try flashing an older release of CyanogenMod - I'd try Snapshot M8.
Click to expand...
Click to collapse
Hi, I tried but I had the same results, the commands are accepted but there is no action after the last one . I'm gonna do a last attempt on my other computer and see if it works.

Related

[Q] [Help needed] Fastboot doesn't provide token ID to unlock the bootloader

Guys, I have a problem with my HTC One M7. I am trying to unlock the bootloader using the HTCDev guide (available at htcdev site).
But suddenly I am not able to complete Step 8 (running command "fastboot oem get_identifier_token").
Command "fastboot devices" shows my phone in a fastboot mode:
\> fastboot devices
mt6589_phone_720pv2 fastboot
But none of fastboot oem commands executes successfully (including "get_identifier_token").
Instead I get only three dots ("...") and nothing changes after that:
\> fastboot oem get_identifier_token
...
Other commands (like fastboot reboot) function, but not "fastboot oem get_identifier_token". I can't unlock my bootloader, could you please help!
andrey o said:
Guys, I have a problem with my HTC One M7. I am trying to unlock the bootloader using the HTCDev guide (available at htcdev site).
But suddenly I am not able to complete Step 8 (running command "fastboot oem get_identifier_token").
Command "fastboot devices" shows my phone in a fastboot mode:
\> fastboot devices
mt6589_phone_720pv2 fastboot
But none of fastboot oem commands executes successfully (including "get_identifier_token").
Instead I get only three dots ("...") and nothing changes after that:
\> fastboot oem get_identifier_token
...
Other commands (like fastboot reboot) function, but not "fastboot oem get_identifier_token". I can't unlock my bootloader, could you please help!
Click to expand...
Click to collapse
Never seen that before but since we have S-off now you can unlock the bootloader without HTCDev
check out the revone thread in the Original Development section.
If you're using Windows 8, I would use the following link that I've seen floating around here"
http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
I had issues getting the token for mine until I used that guide to convert my Microsoft USB 3.0 drivers into Intel drivers.
gunnyman said:
Never seen that before but since we have S-off now you can unlock the bootloader without HTCDev
check out the revone thread in the Original Development section.
Click to expand...
Click to collapse
Thanks for this advice, I am now trying to do it with revone.
I have successfully pushed the file to the phone, but when executing adb shell commands I get a error:
"- exec '/system/bin/sh' failed: No such file or directory"
How to fix it?
andrey o said:
Thanks for this advice, I am now trying to do it with revone.
I have successfully pushed the file to the phone, but when executing adb shell commands I get a error:
"- exec '/system/bin/sh' failed: No such file or directory"
How to fix it?
Click to expand...
Click to collapse
Not sure, but the folks in that thread are super helpful
you're in an ADB shell when you execute the command?
gunnyman said:
Not sure, but the folks in that thread are super helpful
you're in an ADB shell when you execute the command?
Click to expand...
Click to collapse
Yes, I am now reading that thread to find the answer.
Here's what i do and what I get:
> adb devices
List of devices attached
0123456789ABCDEF recovery
> adb push revone /data/local/tmp/
4584 KB/s (648208 bytes in 0.138s)
>adb shell cd /data/local/tmp
- exec '/system/bin/sh' failed: No such file or directory (2) nRet(-1) -
Start the shell. Then do the cd command separately
gunnyman said:
Start the shell. Then do the cd command separately
Click to expand...
Click to collapse
same result
> adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) nRet(-1) -
Is the phone in recovery or booted up? Needs to be booted
gunnyman said:
Is the phone in recovery or booted up? Needs to be booted
Click to expand...
Click to collapse
It was in recovery mode - my mistake, thank you for pointing.
I have booted it and executed the needed commands, but still another mistake:
>sudo adb shell
[email protected]:/ # cd /data/local/tmp
[email protected]:/data/local/tmp # chmod 755 revone
[email protected]:/data/local/tmp # ./revone -P
revone v0.2.1
revone failed (error code = 1)
1|[email protected]:/data/local/tmp #
Step by step I am coming closer to the result, thanks so much for your help

[Q] My HTC One International is not showing any CID

Question 1: Is this normal, if yes, then how can i find my CID?
{
"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"
}
Question 2: S-OFF or HTCDev unlock?
Question 3: If S-OFF, which method is easier/better revolutionary or moonshine?
Asad_612 said:
Question 1: Is this normal, if yes, then how can i find my CID?
View attachment 2091535
Question 2: S-OFF or HTCDev unlock?
Question 3: If S-OFF, which method is easier/better revolutionary or moonshine?
Click to expand...
Click to collapse
1 Yes this is normal until you change it.
2 For me, s-off then you can always relock the bootloader without htc knowing you have ever unlocked it for warranty purposes.
3 Both do the same thing so personal preference. I used revone which was very easy but cannot comment on revolutionary as I have not tried it.
bobsie41 said:
1 Yes this is normal until you change it.
2 For me, s-off then you can always relock the bootloader without htc knowing you have ever unlocked it for warranty purposes.
3 Both do the same thing so personal preference. I used revone which was very easy but cannot comment on revolutionary as I have not tried it.
Click to expand...
Click to collapse
If we relocked the bootloader, it will show 'relocked' instead of 'locked' right?
Sent from my HTC One using xda app-developers app
randykzc said:
If we relocked the bootloader, it will show 'relocked' instead of 'locked' right?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
That is only if you do it with the instructions on HTCDEV. With S-OFf you can relock and it will show LOCKED.
fastboot oem readcid
randykzc said:
If we relocked the bootloader, it will show 'relocked' instead of 'locked' right?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
There is an ADB command to change it to 'locked' instead of 'relocked'. It's mentioned in revone's thread:
http://forum.xda-developers.com/showthread.php?t=2314582
I used revone to S-OFF and it was quite easy.
Code:
./revone -l
bobsie41 said:
1 Yes this is normal until you change it.
2 For me, s-off then you can always relock the bootloader without htc knowing you have ever unlocked it for warranty purposes.
3 Both do the same thing so personal prefierence. I used revone which was very easy but cannot comment on revolutionary as I have not tried it.
Click to expand...
Click to collapse
1. I saw other devices pictures which showed CID in bootloader mode, and also my previous HTC OneX had such information available.
2. I'be read somewhere users having issues with S-Off with HTC one. Previously I had Inc S and I S-Off it using revolutionary.
Thanks.
Asad_612 said:
1. I saw other devices pictures which showed CID in bootloader mode, and also my previous HTC OneX had such information available.
2. I'be read somewhere users having issues with S-Off with HTC one. Previously I had Inc S and I S-Off it using revolutionary.
3. Can you provide me the link of renove S-Off?
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2314582
TarekElsakka said:
There is an ADB command to change it to 'locked' instead of 'relocked'. It's mentioned in revone's thread:
http://forum.xda-developers.com/showthread.php?t=2314582
I used revone to S-OFF and it was quite easy.
Code:
./revone -l
Click to expand...
Click to collapse
while using adb, i keep getting this error:
Code:
1|[email protected]:/ $ adb push revone /data/local/tmp/
adb push revone /data/local/tmp/
error: device not found
1|[email protected]:/ $
any clue how to fix this?
I've updated all the HTC drivers, and adb drivers. My device is turned On, connected to PC via USB, with USB Debugging enabled.
Asad_612 said:
while using adb, i keep getting this error:
Code:
1|[email protected]:/ $ adb push revone /data/local/tmp/
adb push revone /data/local/tmp/
error: device not found
1|[email protected]:/ $
any clue how to fix this?
I've updated all the HTC drivers, and adb drivers. My device is turned On, connected to PC via USB, with USB Debugging enabled.
Click to expand...
Click to collapse
Uncheck in settings/energy/fastboot and close (at the bottom). That may help.
gee2012 said:
Uncheck in settings/energy/fastboot and close (at the bottom). That may help.
Click to expand...
Click to collapse
unchecked, but still the same error :/
Asad_612 said:
unchecked, but still the same error :/
Click to expand...
Click to collapse
Is usb debugging enabled and is HTC Sync manager not running?
gee2012 said:
Is usb debugging enabled and is HTC Sync manager not running?
Click to expand...
Click to collapse
usb debuggin enabled and sync manager updated and running as well...still device not connected error
Asad_612 said:
usb debuggin enabled and sync manager updated and running as well...still device not connected error
Click to expand...
Click to collapse
You have to close sync manager (best is to uninstall except the drivers).
gee2012 said:
You have to close sync manager (best is to uninstall except the drivers).
Click to expand...
Click to collapse
Tried that too, still nothing ... is there any shortcup sort of adb files?
I dont know if there is an issue with my adb files or something else...cause i can start adb shell, but im having problem with it detecting my device...
Asad_612 said:
Tried that too, still nothing ... is there any shortcup sort of adb files?
I dont know if there is an issue with my adb files or something else...cause i can start adb shell, but im having problem with it detecting my device...
Click to expand...
Click to collapse
There is a problem with your drivers somehow, go to device manager in windows and delete the phone from the list. Reboot the pc and try again.
Asad_612 said:
while using adb, i keep getting this error:
Code:
1|[email protected]:/ $ adb push revone /data/local/tmp/
adb push revone /data/local/tmp/
error: device not found
1|[email protected]:/ $
any clue how to fix this?
I've updated all the HTC drivers, and adb drivers. My device is turned On, connected to PC via USB, with USB Debugging enabled.
Click to expand...
Click to collapse
"adb push" command is not shell command!
you need type: adb push revone /data/local/tmp/ before you entered into shell by "adb shell".
1) adb push revone /data/local/tmp/
2) adb shell
3) and so on..
tash2013 said:
"adb push" command is not shell command!
you need type: adb push revone /data/local/tmp/ before you entered into shell by "adb shell".
1) adb push revone /data/local/tmp/
2) adb shell
3) and so on..
Click to expand...
Click to collapse
yea i figured that, but still got error, see this:
Code:
C:\fastboot>adb push revone /data/local/tmp/
2048 KB/s (648208 bytes in 0.309s)
C:\fastboot>cd /data/local/tmp
The system cannot find the path specified.
C:\fastboot>adb shell chmod 755 /data/local/tmp/revone
C:\fastboot>adb shell
[email protected]:/ $ busybox df -h
busybox df -h
/system/bin/sh: busybox: not found
127|[email protected]:/ $
Asad_612 said:
yea i figured that, but still got error, see this:
Code:
C:\fastboot>adb push revone /data/local/tmp/
2048 KB/s (648208 bytes in 0.309s)
C:\fastboot>cd /data/local/tmp
The system cannot find the path specified.
C:\fastboot>adb shell chmod 755 /data/local/tmp/revone
C:\fastboot>adb shell
[email protected]:/ $ busybox df -h
busybox df -h
/system/bin/sh: busybox: not found
127|[email protected]:/ $
Click to expand...
Click to collapse
"C:\fastboot>cd /data/local/tmp" What is it??? You need here to specify a way to yours adb.exe file.
if youer adb.exe in c:\fastboot folder you need
1) c:\fastboot> adb shell
2) [email protected]:/ $ cd /data/local/tmp
3) [email protected]:/ $ chmod 755 revone
4) and so on ..regarding s-off thread
tash2013 said:
"C:\fastboot>cd /data/local/tmp" What is it??? You need here to specify a way to yours adb.exe file.
if youer adb.exe in c:\fastboot folder you need
1) c:\fastboot> adb shell
2) [email protected]:/ $ cd /data/local/tmp
3) [email protected]:/ $ chmod 755 revone
4) and so on ..regarding s-off thread
Click to expand...
Click to collapse
My adb files are in c:\fastboot folder, i followed the process and this is the result, its still not detecting the device:
Code:
C:\fastboot>
C:\fastboot>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ chmod 755 /data/local/tmp/revone
chmod 755 /data/local/tmp/revone
[email protected]:/data/local/tmp $ adb devices
adb devices
List of devices attached
[email protected]:/data/local/tmp $ ./revone -P
./revone -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
251|[email protected]:/data/local/tmp $

[Q[ Reset to sell?? (HELP)

Hello,
I have rooted my phone with custom ROM, I am selling my phone back to the provder and need to unroot and back to standard ROM.
How do i do this?? Also how do i do the counter back to 0 so they know it hasn't been rooted??
Thank you
coolfreebies
coolfreebies said:
Hello,
I have rooted my phone with custom ROM, I am selling my phone back to the provder and need to unroot and back to standard ROM.
How do i do this?? Also how do i do the counter back to 0 so they know it hasn't been rooted??
Thank you
coolfreebies
Click to expand...
Click to collapse
First thing, are you S-Off?
If not you will only be able to get RELOCKED, not LOCKED. So that's a dead giveaway.
nkk71 said:
First thing, are you S-Off?
If not you will only be able to get RELOCKED, not LOCKED. So that's a dead giveaway.
Click to expand...
Click to collapse
Its says S-ON What does that mean??
Thank you
coolfreebies
coolfreebies said:
Its says S-ON What does that mean??
Thank you
coolfreebies
Click to expand...
Click to collapse
It means you're phone is Security On. Since you've unlocked the bootloader it probably says "UNLOCKED" and "TAMPERED", even if you go back to stock rom and stock recovery and lock your phone, it will show as "RELOCKED" (not sure if TAMPERED will go away, as there are conflicting reports about that).
The only way to really get your phone not to show any evidence of being unlocked, you would need to use revone to get it to show "LOCKED". In order to use revone, you would need to be on hboot 1.44 as hboot 1.54+ have been patched so that revone no longer works.
nkk71 said:
It means you're phone is Security On. Since you've unlocked the bootloader it probably says "UNLOCKED" and "TAMPERED", even if you go back to stock rom and stock recovery and lock your phone, it will show as "RELOCKED" (not sure if TAMPERED will go away, as there are conflicting reports about that).
The only way to really get your phone not to show any evidence of being unlocked, you would need to use revone to get it to show "LOCKED". In order to use revone, you would need to be on hboot 1.44 as hboot 1.54+ have been patched so that revone no longer works.
Click to expand...
Click to collapse
I am on HB 1.44.0000
Thank you for your advice
coolfreebies
coolfreebies said:
I am on HB 1.44.0000
Thank you for your advice
coolfreebies
Click to expand...
Click to collapse
Do some reading of the guides including revone's s-off, vomer's guide to s-off, etc.
Once you are comfortable with the procedure go ahead and S-Off. Then you'll be able to fully restore your device.
A note of advise (at your discretion of course) keep S-Off even after you fully go back to stock, as some phones do actually ship with S-Off.
Hit thanks of i helped
Have read very carefully but can't get past this part:
./revone -s 0 -u
Any suggestions
Thank you
coolfreebies
coolfreebies said:
Have read very carefully but can't get past this part:
./revone -s 0 -u
Any suggestions
Thank you
coolfreebies
Click to expand...
Click to collapse
Have you read this: http://forum.xda-developers.com/showthread.php?t=2431515
What's the error message you are receiving? Give us detailed output from the beginning of your adb shell.
EDIT: what custom ROM are you using, if it's 4.3 based it's a no go. download one that is either 4.1.2 (better) or 4.2.2 (should work also)
nkk71 said:
Have you read this: http://forum.xda-developers.com/showthread.php?t=2431515
What's the error message you are receiving? Give us detailed output from the beginning of your adb shell.
EDIT: what custom ROM are you using, if it's 4.3 based it's a no go. download one that is either 4.1.2 (better) or 4.2.2 (should work also)
Click to expand...
Click to collapse
Phone is 4.1.2
Sense 5.0
Mac/Linux: adb push /Users/vomer/Desktop/revone /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 755 revone
./revone -P (Revone successful) Asks for a reboot
adb shell
cd /data/local/tmp
./revone -P (Waiting for a reboot of phone)
adb shell
cd /data/local/tmp
./revone -s 0 -u - revone failed (error code = -1) This is where i get stuck
Thank you
coolfreebies
coolfreebies said:
Phone is 4.1.2
Sense 5.0
Mac/Linux: adb push /Users/vomer/Desktop/revone /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 755 revone
./revone -P (Revone successful) Asks for a reboot
adb shell
cd /data/local/tmp
./revone -P (Waiting for a reboot of phone)
adb shell
cd /data/local/tmp
./revone -s 0 -u - revone failed (error code = -1) This is where i get stuck
Thank you
coolfreebies
Click to expand...
Click to collapse
Not on my pc right now, I'll try to come back later. But -1 doesn't sound like too big of a problem, keep trying, it took some people up to 50 retries before it actually worked.
Head over to the s-off thread where u can see some other experiences.
Sent from my HTC One using xda app-developers app
coolfreebies said:
Phone is 4.1.2
Sense 5.0
Mac/Linux: adb push /Users/vomer/Desktop/revone /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 755 revone
./revone -P (Revone successful) Asks for a reboot
adb shell
cd /data/local/tmp
./revone -P (Waiting for a reboot of phone)
adb shell
cd /data/local/tmp
./revone -s 0 -u - revone failed (error code = -1) This is where i get stuck
Thank you
coolfreebies
Click to expand...
Click to collapse
Just gotta keep doing it, it will eventually work (took me about 20 minutes to do it with my phone). You just have to keep running the S-OFF command again, not the whole process
coolfreebies said:
Phone is 4.1.2
Sense 5.0
Mac/Linux: adb push /Users/vomer/Desktop/revone /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 755 revone
./revone -P (Revone successful) Asks for a reboot
adb shell
cd /data/local/tmp
./revone -P (Waiting for a reboot of phone)
adb shell
cd /data/local/tmp
./revone -s 0 -u - revone failed (error code = -1) This is where i get stuck
Thank you
coolfreebies
Click to expand...
Click to collapse
+1 what EddyOS said
Once you "./revone -P", and it gives you success, reboot the phone and start running " ./revone -s 0 -u" until it succeeds.
nkk71 said:
+1 what EddyOS said
Once you "./revone -P", and it gives you success, reboot the phone and start running " ./revone -s 0 -u" until it succeeds.
Click to expand...
Click to collapse
Thank you... I have been trying to do this for an hour now and no luck... I have gone from Erro 1 to Erro 2 now.
Any suggestion??
Thank you for your help...
coolfreebies
coolfreebies said:
Thank you... I have been trying to do this for an hour now and no luck... I have gone from Erro 1 to Erro 2 now.
Any suggestion??
Thank you for your help...
coolfreebies
Click to expand...
Click to collapse
From what I've read, but remember each user experience is different, try some of the following: (I know it's tedious, but if/when you get S-Off it's well worth it):
1- Try a different Sense 5 ROM 4.1.2 and/or try 4.2.2; I've even seen someone use a GPe 4.2.2 ROM and it worked
2- are you rooted? could improve chances, using "su" in the shell
3- try running the commands using terminal emulator directly on the phone; for some that worked, whereas adb didnt
So far error -1 and error -2 aren't a failure; from @The War Horse:
Code:
Error Code -1 = Potentially you need to try a different ROM or it could just be random and after a few tries and reboots it might work. A few people have reported that rebooting and using -p rather than -P has worked but I'm not convinced as -p isn't built as a command but you're free to try whatever you wish.
Error Code -2 = I've seen people report this but revone has actually worked so should you see this try and reboot and carry on, if not then try changing ROMs and try again.
Reboot, factory reset, start from the beginning again, etc etc you should get it working PLEASE :fingers-crossed:
I know it's a hassle, for some it works from the first time, for others it takes 50 times and many reboots.
PERSONALLY, I achieved S-Off while being unlocked, rooted, and on ARHD 8.x or 9.x (can't remember )
Keep going, you'll get there :fingers-crossed:
nkk71 said:
From what I've read, but remember each user experience is different, try some of the following: (I know it's tedious, but if/when you get S-Off it's well worth it):
1- Try a different Sense 5 ROM 4.1.2 and/or try 4.2.2; I've even seen someone use a GPe 4.2.2 ROM and it worked
2- are you rooted? could improve chances, using "su" in the shell
3- try running the commands using terminal emulator directly on the phone; for some that worked, whereas adb didnt
So far error -1 and error -2 aren't a failure; from @The War Horse:
Code:
Error Code -1 = Potentially you need to try a different ROM or it could just be random and after a few tries and reboots it might work. A few people have reported that rebooting and using -p rather than -P has worked but I'm not convinced as -p isn't built as a command but you're free to try whatever you wish.
Error Code -2 = I've seen people report this but revone has actually worked so should you see this try and reboot and carry on, if not then try changing ROMs and try again.
Reboot, factory reset, start from the beginning again, etc etc you should get it working PLEASE :fingers-crossed:
I know it's a hassle, for some it works from the first time, for others it takes 50 times and many reboots.
PERSONALLY, I achieved S-Off while being unlocked, rooted, and on ARHD 8.x or 9.x (can't remember )
Keep going, you'll get there :fingers-crossed:
Click to expand...
Click to collapse
Thank you for all that info... Will read though it now... But now my phone is stuck on the boot up screen, shall i try a factory reset bootlocker?
Thank you
coolfreebies
coolfreebies said:
Thank you for all that info... Will read though it now... But now my phone is stuck on the boot up screen, shall i try a factory reset bootlocker?
Thank you
coolfreebies
Click to expand...
Click to collapse
Stuck on bootloader? did u try "fastboot erase cache"
my laptop battery going dead... sorry ... c u tomorrow, hopefully with s-off
Hey,
Thank you so much for all your help it is much appreciated...
I tried using "su" in the shell but it kept aking me for a password and i am not sure what it could be...
Thank you
coolfreebies
coolfreebies said:
Hey,
Thank you so much for all your help it is much appreciated...
I tried using "su" in the shell but it kept aking me for a password and i am not sure what it could be...
Thank you
coolfreebies
Click to expand...
Click to collapse
Hi coolfreebies, did you get it working? Just curious
nkk71 said:
Hi coolfreebies, did you get it working? Just curious
Click to expand...
Click to collapse
Morning nkk71,
Nope didn't get it to work. I was trying for about 3 hours and i just gave up as it was getting to frustrating.
Gonna give it another go now.
Cheers
coolfreebies
Hey,
I managed to get ./revone -s 0 -u DONE... Yippy
Now i am stuck on ./revone -t fingers crossed it will work soon...
Thank you
coolfreebies

(SOLVED)--Require of sim unlock ...how to carry out instruction

------------------------------------SOLVED---------------------------------------------------------------------
JUST CARRIED OUT THE COMMANDS IN CWM RECOVERY ....THAT SOLVED ALL PROBLEMS
I have htc j one ...japanese htc one
Hboot is 1.52 and android 4.1.2
I have been able to s off, unlock bootloader using revone
I have flash cwm and rooted phone
Now I need to sim unlock the phone with some adb commands given in the below mentioned website :-
http://htcsoku.info/htcsokudev-news/au-m7-device-sim-unlock/
You can easily auto translate the above page if u open it in google chrome
Can anyone help me with that ?
Thanks in advance
Sent from my GT-N7000 using xda premium
download and unrar this in adb folder >>> http://www.androidfilehost.com/?fid=23159073880933098
they edited misc.img and say to do this :
adb push misc.img /
adb shell
# dd if=/misc.img of=/dev/block/mmcblk0p19
# reboot
hope it helps
criszz said:
download and unrar this in adb folder >>> http://www.androidfilehost.com/?fid=23159073880933098
they edited misc.img and say to do this :
adb push misc.img /
adb shell
# dd if=/misc.img of=/dev/block/mmcblk0p19
# reboot
hope it helps
Click to expand...
Click to collapse
Thanks for replying
I will download this file and put in adb folder
I shud do
adb push misc.img
( is this commabd correct or do I need to to put / ar back)
Then
Adb shell
It shows $ at the end
So it type
Su
Now it becomes #
Then I shud type
dd if=/misc.img of=/dev/block/mmcblk0p19
# reboot
Am I correct ?
Plz help as I am noob in this ...but am trying to learn
Sent from my GT-N7000 using xda premium
The auto-translated instructions are not good enough, and this is a very risky procedure. Fortunately, with code you usually don't need to read the words to understand it. Fortunately, with my Japanese-speaking colleague's help, I understand everything. Some things to know:
- Don't try this unless you are content to risk your phone, because I can tell he made mistakes in his instructions
- To reiterate, you either need to follow his incorrect instructions or you need to listen to me (why would you do that?)
- Look at the code blocks--all that code is meant to be run on your computer while the phone is connected to USB.
- There is only one complicated step, and this is the one with the incorrect instructions.
What he says:
Open misc.img in a hex editor, represent [00001023] as [11] and save. If you are lazy, use the file I modified already. <link>
There are two problems with this statement. First, "00001023" is not a reasonable position in the file. It means "line 10, column 3" (lines start with zero, columns start with zero). But there are 16 bytes per line, so what he really means is "byte 147". (Each pair of hex characters is a byte. The lowest value is 00, the highest value is ff.)
The second problem is that in his "already modified" file, that byte is "00", not "11". This is what I expected, because it's not reasonable for number="11" to mean "unlocked". More likely, "11" is his carrier and "00" is when the phone is unlocked.
What I advise is getting your carrier to unlock the phone, and if that's not possible, proceed only if you are willing to risk your phone. Follow his instructions, but when you get your misc.img file, download his modified version and compare them. If they differ in only one position, install his file to your phone (as per the instructions). If they are very different but the same size, you can try changing byte 147 to 00 (if the surrounding bytes are also all 00). Save the unmodified .img file, because you might be able to use it to rescue your phone if this fails.
Note: this is risky, with or without language barrier issues. At least 10% chance of bricking your phone.
Thanks a lot for your advice.
But it is not possible to carrier unlock the phone
Is there any safe way to sim unlock the phone ?
Currently am stuck ...
Sent from my GT-N7000 using xda premium
sitanshu91 said:
But it is not possible to carrier unlock the phone
Is there any safe way to sim unlock the phone ?
Click to expand...
Click to collapse
I think it's probably safe to flash the misc.img file he uploaded and linked to, if (and only if) it is exactly the same as yours, except for that one byte. Low chance of bricking the phone.
But currently can you tell me to how to pull the image coz I havr followed his command ...
Adb shell
It strt with $
Su
Now # come
Then somd dd comand
Here it shows operation cannot complete(will update what is exactly error in few min)
Exit
Adb pull misc.img
Here it shows error device not detected
Can you help me to first pull file so I can compare
Sent from my GT-N7000 using xda premium
Weird... you got a successful ADB shell, then it stopped detecting your device? I suppose you should just try again.
My phone is not the same as yours, so you shouldn't compare your partition19 to mine. You have a phone specific to Japan, right?
fenstre said:
Weird... you got a successful ADB shell, then it stopped detecting your device? I suppose you should just try again.
My phone is not the same as yours, so you shouldn't compare your partition19 to mine. You have a phone specific to Japan, right?
Click to expand...
Click to collapse
see this is what i get
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
/misc.img: cannot open for write: Read-only file system
1|[email protected]:/ #
can you tell me why it says " /misc.img: cannot open for write: Read-only file system "
requesting your help
thanks
sitanshu91 said:
can you tell me why it says " /misc.img: cannot open for write: Read-only file system "
Click to expand...
Click to collapse
That's actually normal (because you're not supposed to write to the root of the phone's filesystem). Every time the instructions say "/", you can replace it with "/sdcard/", and every time they say "/misc.img", you can think "/sdcard/misc.img". (The instructions were carelessly written.)
fenstre said:
That's actually normal (because you're not supposed to write to the root of the phone's filesystem). Every time the instructions say "/", you can replace it with "/sdcard/", and every time they say "/misc.img", you can think "/sdcard/misc.img". (The instructions were carelessly written.)
Click to expand...
Click to collapse
so you say i should proceed
see again i did the same
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb devices
List of devices attached
HT35Z******* device
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
/misc.img: cannot open for write: Read-only file system
1|[email protected]:/ # exit
exit
1|[email protected]:/ $ adb pull misc.img
adb pull misc.img
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $
now how should i proceed ....please help
Guys requesting help before the new year starts
So I can use my phone in new year
Sent from my GT-N7000 using xda premium
sitanshu91 said:
/misc.img: cannot open for write: Read-only file system
Click to expand...
Click to collapse
are you doing this is fastboot? / recovery? is your device bootloader unlocked through htc dev?
Kasi!995 said:
are you doing this is fastboot? / recovery? is your device bootloader unlocked through htc dev?
Click to expand...
Click to collapse
yes this is unlocked bootloader ...i have done it thru revone
now i have installed busybox
and i can progress
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb devices
List of devices attached
HT3******* device
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
2045+0 records in
2045+0 records out
1047040 bytes transferred in 0.106 secs (9877735 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ adb pull misc.img
adb pull misc.img
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $
can you help me now
i want to do as written in this
http://htcsoku.info/htcsokudev-news/au-m7-device-sim-unlock/
thanks
sitanshu91 said:
can you help me now
i want to do as written in this
http://htcsoku.info/htcsokudev-news/au-m7-device-sim-unlock/
thanks
Click to expand...
Click to collapse
what Recovery do you have flashed? TWRP?
Its cwm recovery
Sent from my GT-N7000 using xda premium
Run adb pull outside of adb shell.
1st problem :-
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
2045+0 records in
2045+0 records out
1047040 bytes transferred in 0.106 secs (9877735 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ adb pull misc.img
adb pull misc.img
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $
can you tell me where is my mistake
What can I do can you type command
2nd problem
similiarly when i try
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb push misc.img /
failed to copy 'misc.img' to '//misc.img': Permission denied
request you to please help me
thanks and regards
Sent from my GT-N7000 using xda premium
what is your status now?
criszz said:
what is your status now?
Click to expand...
Click to collapse
i am very glad that you asked .....happy new year
Now my status is sim unlocked ....but i can use only to make and receive phone calls and sms ...
now here is the problem
i cant use data (2g/3g) on my phone
do u know how to do that
thanks
sitanshu

S-off problem

Hi guys......
I have Butterfly s 901e with HBOOT 1.57, when I tried to s-off with firewater, I didn't get anything while in the process..... when I made the last step ([email protected]:/ # chmod 755 /data/local/tmp/firewater then [email protected]:/ # /data/local/tmp/firewater), I got nothing.... I tried to check data/local/tmp manually in ES File Explorer to see what is going on, I noticed that after pushing firewater through adb it will appear in the TMP folder and after executing [email protected]:/ # chmod 755 /data/local/tmp/firewater then [email protected]:/ # /data/local/tmp/firewater the firewater file just disappear from TMP folder, and nothing is starting....
please help.
Did you unlocked your device?
ling751am said:
Did you unlocked your device?
Click to expand...
Click to collapse
Yes Of course, hTC dev unlock
Bareq said:
Yes Of course, hTC dev unlock
Click to expand...
Click to collapse
Did you "adb reboot" first?
If u did that and the firewater disappeared in the folder
Make sure u have correctly rooted ur device
Sorry for my bad english

Categories

Resources