[Q] change "relocked" to "locked" when putting phone back to stock?
I followed this thread but mine says "relocked" and it still says S-OFF. is it possible to get it to say "locked" without going through the whole process of unlocking, rooting, and using revone again?
I'm sending my phone back to get the screen replaced which isn't under warranty, so does it even matter that it says "relocked?"
mcarswell said:
I followed this thread but mine says "relocked" and it still says S-OFF. is it possible to get it to say "locked" without going through the whole process of unlocking, rooting, and using revone again?
I'm sending my phone back to get the screen replaced which isn't under warranty, so does it even matter that it says "relocked?"
Click to expand...
Click to collapse
Use revone -l to change back to "locked"
There is not a way without rerooting for Tue device to day say locked and not relocked BUT you can easily get rid of S-Off. It doesn't take long either...
1.) Reroot.
2.) Download revone to computer.
3.) Navigate Using Command Prompt to where revone file is located on computer and move the Downloaded file to /data/local/tmp using the command "adb push revone /data/local/tmp" without quotations while phone is booted into OS and connected to computer.
3.) Use Command Prompt with phone connected to computer to run these commands or you can use Terminal Emulator app without a computer but will need a computer later on to run RUU again...
3A.) adb shell
3B.) su(SU Will Now Request SU Access For ADB Shell, Grant It)
3C.) cd /data/local/tmp
3D.) chmod 755 revone
4.) Reboot device
5.) Once device is fully booted back up run these commands again while connected to computer
5A.) adb shell
5B.) su(Will Not Need To Request Access Again)
5C.) cd /data/local/tmp
5D.) ./revone -P(If It Tells You "No Need To Reboot" Then Move On To Step 7 And If It Tells You To "Reboot To Continue" Move On To Step 6).
6.) Reboot
7.) Once fully booted back into OS open another command prompt and run these commands with Command Prompt while connected to computer.
7A.) adb shell
7B.) su
7C.) cd /data/local/tmp
7D.) ./revone -s 0 -u(To Be Safe).
7E.) Reboot
8.) Once again open another command prompt window and run these commands
8A.) adb shell
8B.) su
8C.) cd /data/local/tmp
8D.) ./revone -t -l
9.) Reboot
10.) Run RUU And Allow It To Successfully Complete.
11.) Once booted back into OS open command prompt and type in the final two commands
11A.) adb reboot bootloader
12.) Once it boots into bootloader and recognizes device type in this command
12A.) fastboot oem writesecureflag e
Sent from my HTCONE using Tapatalk 4
Related
I have a v6 stock phone, no root, no cwm. Thought I would run through the ADB manual method of root to see what happens. I get to this point...
Code:
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb usb' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/su
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
When I try to do the SU because I get the $ I get Permissions denied.
I know that this method does not work but I wanted to see where it fails. It appears that they may have fixed the glitch that allowed the rage exploit to work.
I also tried cubes other way and it failed as well.
Code:
Open ADB shell
Your command prompt should be "$"
Run
kill `busybox pidof adbd`
Re-run ADB shell, your command prompt should change to "#"
Just thought I would toss this out there in case someone wanted to know...
Thanks for the heads up on this good info to know when I get my rev on Saturday
Sent from my SHIFTAO5P using XDA Premium App
Haxcid said:
I have a v6 stock phone, no root, no cwm. Thought I would run through the ADB manual method of root to see what happens. I get to this point...
Just thought I would toss this out there in case someone wanted to know...
Click to expand...
Click to collapse
Mm, I went through that last night, then downgraded to the V4 software as shown by the other post - still, none of it worked for me.
Pull your SDcard out when trying to root after the downgrade. Or format the SD card. It should work then.
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
i got my htc one to s-off so that i could come flash RUU to come back to stock. But now i want to get my phone back to s-on. Have any idea how to do so??
susmit95 said:
i got my htc one to s-off so that i could come flash RUU to come back to stock. But now i want to get my phone back to s-on. Have any idea how to do so??
Click to expand...
Click to collapse
You might want to put a description of what you need into your thread titles, as people are much more likely to help you.
Back to S.ON - e.g. sent your device to HTC for service:
*Android SDK, ADB and Fastboot installed
*Stock unmodified hboot!!
*Download: revone
Enable USB-Debugging and boot your device into Android and connect it to your PC, then go on...
Boot your device into Android, enable USB-Debugging and connect it to your PC, then go on...
1. Put revone file in your fastboot/adb folder.
2. Open CMD and navigate to your fastboot/adb folder.
3. Insert following commands in CMD (step by step):
adb push revone /data/local/tmp/
adb shell
cd /data/local/tmp
su
./revone -l
4. Reboot your device to Bootloader
5. Insert following commands in CMD (step by step):
fastboot oem writesecureflag 3
cherrytontonne said:
Back to S.ON - e.g. sent your device to HTC for service:
*Android SDK, ADB and Fastboot installed
*Stock unmodified hboot!!
*Download: revone
Enable USB-Debugging and boot your device into Android and connect it to your PC, then go on...
Boot your device into Android, enable USB-Debugging and connect it to your PC, then go on...
1. Put revone file in your fastboot/adb folder.
2. Open CMD and navigate to your fastboot/adb folder.
3. Insert following commands in CMD (step by step):
adb push revone /data/local/tmp/
adb shell
cd /data/local/tmp
su
./revone -l
4. Reboot your device to Bootloader
5. Insert following commands in CMD (step by step):
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
its compulsory to get my phone rooted??
its compulsory to get my phone rooted??
Click to expand...
Click to collapse
You don't need a root to use "./revone -l " and "fastboot oem writesecureflag 3" commands.
I downloaded and installed the OTA today .I have a stock rooted installation.I clicked install and the phone went to perform the install but instead restarted quickly and reset all my settings back to factory. I checked and still on 4.1..
Help!
I would suggest getting S-OFF before updating
bigdaddy619 said:
I would suggest getting S-OFF before updating
Click to expand...
Click to collapse
Thanks.that would have been super helpful to know before hand lol. Anyway, here is how to resolve this problem for anyone else experiencing it:
http://qbking77.com/development/how-to-gain-s-off-on-the-htc-one-with-revone/
Revone Download:
http://revolutionary.io/revone
Big thanks to the Revolutionary dev team. The original thread can be found here.
Written instructions:
Download the Revone file above and transfer it to your phone (or download on your phone)
Use a root file explorer and paste the file inside the /data/local/tmp folder
Open a terminal emulator and type of the following:
su (enter)
cd /data/local/tmp (enter)
chmod 755 revone (enter) (IF revone doesn’t work, type revone.bin)
./revone -P (enter)
Reboot
Open terminal again and type:
su (enter)
cd /data/local/tmp (enter)
./revone -s 0 -u (That would be a ZERO) (enter)
Reboot
That’s it! To get rid of the tampered, or relock, follow instructions below
To remove “tampered”
open terminal
cd /data/local/tmp
su
./revone.bin -t
These are other commands that you can fill in above to
-u – Unlock the device
-l – Lock the device (as if it was never unlocked)
-r – Relock the device (mark the device as relocked)
-t – Reset the device’s tamper flag.
Click to expand...
Click to collapse
Hello forum. First experience with this device.
Software Version 7.4.8
ADB drivers working, finds device.
No factory Cable.
"adb shell reboot bootloader" returns /system/bin/sh: su Reboot-bootloader: Not found
"adb shell" returns prompt with "$"
"su" command returns "Operation not permitted"
Do I need to be root before I can get into fastboot?
I want to use fastboot to downgrade to version 7.2.3 in order to properly flash the second bootloader.
Thanks for your feedback.
FillTheVoid said:
Hello forum. First experience with this device.
Software Version 7.4.8
ADB drivers working, finds device.
No factory Cable.
"adb shell reboot bootloader" returns /system/bin/sh: su Reboot-bootloader: Not found
"adb shell" returns prompt with "$"
"su" command returns "Operation not permitted"
Do I need to be root before I can get into fastboot?
I want to use fastboot to downgrade to version 7.2.3 in order to properly flash the second bootloader.
Thanks for your feedback.
Click to expand...
Click to collapse
Nope, type "adb reboot bootloader"
FillTheVoid said:
Hello forum. First experience with this device.
Software Version 7.4.8
ADB drivers working, finds device.
No factory Cable.
"adb shell reboot bootloader" returns /system/bin/sh: su Reboot-bootloader: Not found
"adb shell" returns prompt with "$"
"su" command returns "Operation not permitted"
Do I need to be root before I can get into fastboot?
I want to use fastboot to downgrade to version 7.2.3 in order to properly flash the second bootloader.
Thanks for your feedback.
Click to expand...
Click to collapse
You need to be rooted, have the SDK package downloaded and the environment set up (set paths) and then CD from the tools folder and issue the command "adb shell su -c reboot bootloader"
Edit: Do I all in one line with no quotations. This is the way to access the bootloader on a Kindle with no factory cord.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
---------- Post added at 09:15 PM ---------- Previous post was at 09:04 PM ----------
stunts513 said:
Nope, type "adb reboot bootloader"
Click to expand...
Click to collapse
You need to be rooted, have the SDK package downloaded and the environment set up (set paths) and then CD from the tools folder and issue the command "adb shell su -c reboot bootloader" Probably don't have too set paths when CD but it's a good thing to do.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app